Skip to content

The problem

Quote requests need a call back fast, and renewals need chasing.

A new quote request triggers an outbound call as soon as it arrives. Renewal lists become an outbound config, with the sources you must never cold-call excluded.

What Grepiv does on the line

  • Auto-dial a new quote request the moment it lands
  • Exclude the lead sources you must never cold-call
  • Pre-call webhook pulls the existing policy before hello
  • Push the outcome into your agency management system

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.

  • New quotes
  • Renewals
  • Claims

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.

A quote request dialled back in under a minute, with the policy already loaded.

  1. GrepivHi Mrs Okafor, this is Redgate Insurance returning your quote request. I can see your home policy renews on the eleventh — is that what this is about?
  2. CallerYes, the renewal came in much higher than last year.
  3. GrepivI understand. Has anything changed — the property, the contents, or any claims this year?
  4. CallerNo claims, but we fitted a monitored alarm in August.
  5. GrepivThat can matter. Is the alarm professionally monitored, or a self-monitored system?
  6. CallerProfessionally monitored.
  7. GrepivNoted. I will have an adviser call you back today with a revised figure. Is this number best?
  8. CallerYes.

On the desk afterwards

Extracted from the transcript, no retyping.

  • Renewal: 11th
  • Change: monitored alarm fitted
  • Claims: none
  • Callback: today
  • Pipeline: Renewals

Questions

Insurance, specifically.

01

Can we stop it calling certain people?

Outbound configs exclude lead sources you choose, and inbound is excluded by default, so someone who just phoned you is never dialled back automatically.

02

Can the agent know the policy before it calls?

A pre-call webhook runs before the agent speaks, so details from your system are in the conversation from the first sentence.

03

How do outcomes reach our system?

Post-call workflows chain HTTP requests with conditions and body templates, and every attempt is logged with the response.

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.