Build a Speed-to-Lead Callback Campaign

​

Prerequisites

• A scheduling provider connected in Settings → Apps — Calendly, Cal.com, ChiliPiper, or HubSpot. See Scheduling & Booking with Agents for the four providers and their setup.
• At least one team phone number for outbound calls — see Phone Numbers.
• Your team’s API key, from Settings → General → Privacy & Security (see Workspace Settings).
• A way to make an HTTP request when a lead submits: your backend, your CRM’s workflow engine, or a form tool that can send a webhook.

​

Step 1: Build and publish the qualification voice agent

• Voice agent name — e.g. “Speed-to-lead callback — [Product]”.
• Custom requirement — describe your company, product, target customer, and the call goal (“qualify inbound demo requests and book a meeting with sales”).
• Contact fields the bot will know — check {{fullName}} (and any other fields your form captures) so the agent can greet the lead by name instead of opening cold.

You are [Alex], calling on behalf of [Acme], a [B2B invoicing platform
for mid-size companies]. The person you are calling, {{fullName}}, just
submitted a form on our website asking about [a demo]. This is a
callback they asked for, not a cold call — say so early.

Open by confirming you're speaking with {{fullName}}, then reference
their request: "You just asked about [a demo] on our site, so I wanted
to reach you while it's fresh."

Qualify conversationally, one question at a time:
1. What problem are they trying to solve?
2. [Company size — rough headcount or team size].
3. Timeline — evaluating now, or researching for later?

A lead is QUALIFIED if [they have a problem we solve, a company size of
10+ employees, and an active timeline (now or within 3 months)].

If qualified, book the meeting on this call: check the calendar for
availability, offer two or three concrete slots out loud, and book the
one they pick. Collect anything still missing for the booking — their
email and timezone — before you book.

Never quote custom pricing or discounts, never promise features, and
never press a lead who says it's a bad time — offer to call back at a
time they name instead. If they're clearly not a fit, thank them and
end warmly.

​

Step 2: Attach the calendar tools

​

Step 3: Create the campaign

​

Engagement Flow

​

Instructions

This campaign calls back leads who just submitted a form on our
website. Speed is the whole point: place the first call as soon as a
lead is enrolled — within minutes, not hours — as long as it falls
inside the allowed calling hours below. A lead enrolled outside those
hours gets the first call when the next window opens.

Call each lead up to [5] times. If a call goes unanswered, try again
[later the same day, then once per day after that]. Calls must only be
scheduled between [8:00 and 20:00] in the lead's timezone.

The goal per lead is a booked meeting with [the sales team]. If a lead
is qualified but can't book on the call, schedule one follow-up call
at the time they suggest. If a lead asks not to be contacted again,
stop all outreach immediately.

​

Exit Conditions

A lead exits the campaign successfully when a meeting is booked with
the sales team. A lead exits unsuccessfully when they are clearly not
a fit, when they ask not to be contacted again, or after [5] call
attempts with no answer.

​

Step 4: Wire the trigger from your form or CRM

curl -X POST https://app.revve.ai/api/campaigns/contact-enrollments \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "teamId": "TEAM_UUID",
    "campaignId": "CAMPAIGN_UUID",
    "phoneNumber": "+84775352590",
    "name": "Jane Doe",
    "email": "[email protected]"
  }'

• phoneNumber and teamId are required. Send the lead’s phone from your form’s phone field.
• campaignId — this campaign’s ID. (It’s technically optional on the endpoint — omitting it just creates/updates the contact without enrolling — but for speed-to-lead you always include it.)
• name and email — from your form. name and email come from your form — the contact’s name is what fills the {{fullName}} placeholder your agent’s greeting uses.
• Returns 200 with a contactId.

​

Step 5: Protect the experience

• Do Not Call list — you don’t need an opt-out rule in your form handler. Every outbound call is checked against the team’s Do Not Call List before it’s placed; a matching call step is simply skipped, and post-call analysis adds numbers automatically when a lead says “don’t call me again” on a call.
• Call Window — the Instructions’ calling hours are a request to the AI; the Enable Call Window setting in Workspace Settings is a hard stop that automatically fails any outbound call outside the allowed hours. Turn it on where calling-hours regulations apply, and keep its hours aligned with what you wrote in the Instructions — a mismatch looks like a campaign that mysteriously stopped dialing.
• Caller ID rotation — a single number making all your speed-to-lead calls is exactly what gets spam-labeled, and a “Spam Likely” caller ID defeats the entire recipe. Create a number pool on the Number Pools tab of Phone Numbers and attach it in the voice agent’s phone number configuration, so each call picks a caller ID from the pool.
• Voicemail — voicemail detection is off by default, which means a missed callback is a silent hangup. Enable it in the agent’s Advanced Settings → Voicemail (see Voice Agent Settings) and write a Voicemail Message using contact placeholders, e.g. “Hi {{firstName}}, this is [Alex] from [Acme] — you asked about [a demo] on our site. I’ll try you again shortly.” A personalized message measurably improves callback rates versus silent hangups.

​

Step 6: Test by enrolling yourself

1. Time the gap between the request and your phone ringing — this is your speed-to-lead number.
2. Answer, let the agent qualify you, and book a test meeting. Confirm the invitation arrives from your scheduling provider and the appointment shows on your contact record in Revve.
3. Open the campaign’s Enrollments tab and click your row to see the engagement timeline — the enrollment, the call, and the state the AI moved you to.
4. Run the curl again with the same contact via POST /api/campaigns/enrollments and confirm the 409 — your double-submit protection.

​

Test scenarios

​

Variations

• SMS fallback for unanswered calls: attach a published SMS Chat Agent as a second Campaign Agent, turn on Enable Multi Channels, and add an Instructions line telling the AI to text the lead when calls go unanswered. The full voice-then-SMS mechanism is the subject of Build a Payment Reminder Campaign — same pattern, different script.
• Automatic reminders after the booking: teams can configure a default “after appointment booked” campaign — every contact your agent books is auto-enrolled into it, so no-shows drop without anyone sending manual reminders. See Scheduling & Booking with Agents.
• Trigger from inside Revve instead of your form: if the lead event already happens inside Revve, an automation rule with the Enroll in Campaign action can enroll contacts without any external API call — see Creating Automation Rules.
• Nurture the unreached: set the campaign’s Next Campaign so leads who exit after [5] failed attempts flow into a slower nurture campaign instead of going cold.

​

What’s Next

• Creating a Campaign — the full campaign reference: publishing, the enrollment API, managing in-flight enrollments, and monitoring.
• Voice Agent Settings — tune turn-taking, voicemail, and retry behavior once real calls surface rough edges.