Skip to content

The problem

You are under a sink. The phone rings. That job goes to whoever answers.

HVAC, plumbing, electrical, roofing. The agent answers while crews are on site, captures the job and the address, books the visit, and pushes it into whatever your dispatcher already uses.

What Grepiv does on the line

  • Answer while every technician is already on a job
  • Job type, address and urgency captured from the call
  • Visit booked and assigned round-robin to a crew
  • Webhook the job into your dispatch or field-service tool

Pipelines you would name

Pipelines and custom fields are yours to define. These are the ones a desk in this trade usually ends up with.

  • Emergency
  • Quotes
  • Maintenance

The outcome

Every call lands on the desk.

Whatever the agent captured on the call arrives as a lead in the pipeline you named, with the fields you asked for, ready for whoever picks it up.

Leads
NamePipeline
Dana WhitfieldIntake
Marcus ReyesNew quotes
Priya NairRenewals
Tom AldermanIntake

Leads as they arrive, tagged with the pipeline and the source that created them.

Setup

Live in an afternoon.

The same five steps whatever the trade. Only the script and the pipelines differ.

  1. 01

    Connect your numbers

    Add Twilio credentials, fetch your inventory, and tag the lines Grepiv should use.

  2. 02

    Write the agent

    Script, greeting, voice, extraction fields, tools, and transfer rules. Per inbound number or outbound config.

  3. 03

    Turn on texting

    Attach an AI SMS config, and WhatsApp if you want it. Optional auto-reply on the same numbers.

  4. 04

    Catch every lead

    Pipelines and forms decide where a person lands. Webhooks and the dashboard both create leads.

  5. 05

    Book and hand off

    Appointments land on the calendar. Webhooks push the outcome to your CRM.

A call, start to finish

What it sounds like.

An emergency call while both engineers are already out on jobs.

  1. GrepivHalston Plumbing, how can I help?
  2. CallerThere is water coming through the kitchen ceiling.
  3. GrepivRight, that is urgent. Have you been able to turn the stopcock off?
  4. CallerYes, it is off now, but the ceiling is still dripping.
  5. GrepivGood, that is the main thing. Can I take the address and postcode?
  6. CallerFourteen Bellfield Road, LS8 2QR.
  7. GrepivThank you. Both engineers are on jobs, but I can get someone to you between four and six today. Does that work?
  8. CallerYes, please.
  9. GrepivBooked for four to six. Dan will call twenty minutes before he arrives.

On the desk afterwards

Extracted from the transcript, no retyping.

  • Job: leak, kitchen ceiling
  • Urgency: emergency
  • Address: 14 Bellfield Rd, LS8 2QR
  • Visit: today 16:00–18:00, Dan
  • Pipeline: Emergency

Questions

Home services, specifically.

01

Can it tell an emergency from a quote request?

You define the fields the call should extract, and conditions decide what happens next — which pipeline the lead lands in, whether a text goes out, and which webhook fires.

02

Does it assign work to a specific crew?

Unassigned bookings rotate round-robin across your active staff and skip anyone already busy in that slot. You can also pick a person from the calendar.

03

Can it reach our dispatch software?

Post-call workflows are HTTP with body templates, so the job can be posted to any endpoint your field-service tool exposes.

Constant

What never changes.

Whatever the trade, these four are the same, which is why one platform covers all of them.

  • 01

    Your numbers

    You connect your own Twilio account and tag the lines Grepiv may use. Numbers you already have can be ported in, and they stay on your account whatever the trade.

  • 02

    Your script

    Greeting, script, voice, transfer rules and duration cap are set per number. That is what makes a line sound like it belongs to your trade rather than to a call centre.

  • 03

    Your fields

    You define what each call should extract and which lead fields it fills. Pipelines and custom fields are yours to name.

  • 04

    Your system of record

    Pre-call enrichment and post-call workflows are plain HTTP, so the outcome lands in the case management system, agency management system, CRM or ATS you already run.