Overview
Avoca’s Speed to Lead platform ensures you never miss a hot lead. Our AI-powered system automatically contacts new leads within 30 seconds of form submission, dramatically increasing your conversion rates by reaching prospects when their interest is highest.See how the audience builder routes fresh leads into Speed to Lead campaigns.
Dynamic Speed to Lead in Avoca
How Avoca dynamically turns any inbound lead (emails, partner feeds, forms, ads, or manual adds) into a live, branded conversation within minutes, then keeps nurturing if the first touch does not connect.Flow at a glance
- Capture leads from your shared lead inbox and connected sources (forms, ads, partner feeds, or CSV/manual adds).
- Parse the message with Avoca’s lead extractor to pull name, phone, email, address, job summary, and source; dedupe against recent leads.
- Route the lead to the right team list and queue it for immediate outreach.
- Auto-schedule an outbound call using your configured caller ID, greeting, and assistant persona.
- The AI caller dials within minutes, follows your script and brand, and respects your retry rules and quiet hours.
- Outcomes are recorded: answered vs. voicemail, transcript, summary, recordings, and bookings.
- Follow-up texts/emails and multi-step workflows continue until the lead is reached or booked.
Lead capture
- Lead inbox: Avoca watches your designated inbox address for new lead emails, extracts the contact details, and identifies the source based on sender/body cues.
- Connected sources: Online forms, ad platforms, and partner feeds can push leads directly; Avoca normalizes and formats phones/addresses automatically.
- Deduplication: Leads are checked against recent records (primarily phone/email) to avoid double-calling.
- Manual adds: Teams can key in a lead from the admin panel to force an immediate speed-to-lead call.
Contact speed
- Brand-ready call setup: Configure caller ID, brand name, assistant name/persona, and the opening script once; reuse across all incoming leads.
- Immediate dialing: When a valid phone arrives, Avoca schedules and launches the outbound call within your set hours and throttles.
- Smart retries: Optional spacing and retry limits to avoid over-dialing; holiday/quiet-hour controls keep outreach compliant.
Outcomes and follow-up
- Call intelligence: Transcripts, summaries, and disposition (answered, voicemail, requested callback, booking) are captured automatically.
- Booking-ready: If booking is enabled, the agent can capture commitment details and pass them to your downstream system.
- Voicemail and callbacks: Voicemail detection flags unanswered calls and can prompt a follow-up text or rescheduled call.
- Text/email follow-up: Missed calls can trigger polite follow-up messages with the lead’s context filled in (name, address, notes, source).
Workflows and multi-touch
- 15-20 touchpoint journeys: Build or use templates that mix calls, SMS, and optional emails over days or weeks, so no lead stalls after the first dial.
- Sequences that mix calls and texts: Leads can be enrolled in a workflow that chains calls with follow-up texts until contact or booking.
- Progress-aware: Each touch updates the workflow so future steps only run when needed (for example, skip SMS if the call was answered and booked).
Visibility and analytics
- Pickup and booking: Track answer rate, bookings, and conversion from first touch to scheduled job.
- Speed: Measure time-to-first-call and time-to-first-response.
- Sources: Break down performance by lead source and campaign tags (including UTM data where available).
- Quality: Review transcripts and recordings to coach or update scripts.
Configuration highlights
- Caller ID and assistant persona
- Greeting, script, and variables to personalize outreach
- Quiet hours, holidays, and retry spacing
- Follow-up message templates for missed calls
- Booking preferences (if you want Avoca to collect appointment intent)
Key Features
Instant Webhook Triggers
Connect any form to trigger immediate AI-powered calls
Real-time Appointment Booking
Schedule appointments during the first call
Webhook Integration
Avoca provides you with a custom webhook URL that instantly triggers our AI to contact new leads. Here’s an example webhook endpoint:Your specific webhook URL will be provided in your Avoca dashboard under Settings → Integrations → Speed to Lead Webhook. The URL already maps to your team, so you only need to send
customer_name and phone_number plus any optional context.Integration Guides
Simple HTML Form Example
Here’s a basic HTML form that sends data directly to the Avoca webhook:WordPress Sites
Follow these steps to add the Avoca webhook to your WordPress forms:- Contact Form 7
- WPForms
- Gravity Forms
1
Install Webhook Plugin
Install and activate the “Contact Form 7 - Webhook” plugin from the WordPress repository
2
Configure Webhook
Go to your form settings and find the “Webhook” tab. Enter your Avoca webhook URL:
3
Map Form Fields
Map your form fields to the webhook payload:
4
Test Integration
Submit a test form and verify the lead appears in your Avoca dashboard
Zapier Automation
Use Zapier to send leads from any supported app directly into Avoca’s webhook.1
Create a New Zap
In Zapier, click Create Zap and pick the app that collects your leads (e.g., Webflow, Typeform, Google Sheets) as the trigger. Walk through the connection prompts and pull in a recent sample lead so the fields are available later.
2
Add Webhooks by Zapier Action
Click + Add action, search for Webhooks by Zapier, and choose the POST event. This action delivers the lead data to Avoca.
3
Configure Request
Set up the POST action with these settings:Only
customer_name and phone_number are required—remove unused keys or add additional custom_fields__{key} entries as needed. Zapier automatically turns the double-underscore syntax into a nested custom_fields object.4
Optional: Clean Phone Numbers
If your trigger sends numbers with formatting (parentheses, dashes, etc.), insert a Formatter → Numbers → Format Phone Number step before the webhook. Map the formatted output to
phone_number so Avoca receives a clean 10 or 11 digit value.5
Test and Publish
Send a test from Zapier. Confirm the Zap step returns a 201 status, then check the Avoca dashboard for the new lead. Once validated, click Publish to activate the Zap.
The webhook queues calls immediately when it’s between 7 AM and 9 PM in the assistant’s timezone (Eastern by default). If you send
push_until_later=true, the call will wait for the next window even during business hours. Campaign metadata (UTM parameters or any custom keys) can live at the top level or inside custom_fields; the raw payload is stored for reporting either way.Webflow Sites
Integrating Avoca’s Speed to Lead webhook with Webflow forms:1
Access Form Settings
In the Webflow Designer, select your form element and open the settings panel
2
Configure Form Action
In the form settings, set the Action field to your Avoca webhook URL:
3
Set Method to POST
Ensure the Method is set to
POST4
Add Hidden Fields
Add hidden input fields for metadata:
5
Configure Field Names
Ensure your form input names match Avoca’s expected fields:
customer_name- Full name (required)phone_number- Phone number (required)email- Email address (optional)message- Any additional details (optional)
6
Add Success/Error States
Create success and error states in Webflow for better user experience
7
Publish and Test
Publish your site and submit a test lead to verify the integration
Custom JavaScript Solution for Webflow
For more control over the webhook integration:Webhook Payload Format
Your webhook accepts both JSON and form-urlencoded data with the following fields:Required Fields
customer_name- Full name of the leadphone_number- The lead’s phone number (10 or 11 digits, will be formatted to +1XXXXXXXXXX)
Optional Fields
email- Email addressaddress,city,state,zip- Individual address piecescustomer_address- Full address as a single field (alternative to individual address fields)notes/message- Any additional context or questionsservice_type- Type of service requestedpage_title/page_url- Landing page information for attributionsource- Lead source label (defaults toAPIif not provided)utm_source,utm_medium,utm_campaign- Campaign attribution (top-level)push_until_later- Settrueto delay the call until the next 7 AM windowcustom_fields- Object for any additional keyed data (e.g.,utm_*, preferences)- Additional properties are stored verbatim in
raw_webhookfor downstream use
Phone Number Formatting: The webhook automatically formats US phone numbers to +1XXXXXXXXXX format. Both 10-digit (XXXXXXXXXX) and 11-digit (1XXXXXXXXXX) formats are accepted.
Testing Your Integration
1
Submit Test Lead
Fill out your form with test data (use your own phone number)
2
Check Avoca Dashboard
Log into Avoca and navigate to Leads → Recent to see your test lead
3
Verify Call Placement
You should receive a call within 30 seconds of form submission
4
Review Call Recording
Listen to the AI conversation in your dashboard to ensure proper qualification
Best Practices
Optimize Form Fields
Optimize Form Fields
Keep forms short with only essential fields. Every additional field reduces conversion by 7%. Let our AI gather additional information during the call.
Set Clear Expectations
Set Clear Expectations
Add text near your form: “We’ll call you within 30 seconds!” This prepares leads for the immediate response.
Mobile Optimization
Mobile Optimization
Ensure phone number fields are tel input types for better mobile experience:
Lead Routing Rules
Lead Routing Rules
Configure routing rules in Avoca to send different types of leads to specific team members based on service type, location, or urgency.
Analytics & Reporting
Track your Speed to Lead performance in the Avoca dashboard:- Response Time: Average time from form submission to call placement
- Connection Rate: Percentage of leads successfully reached
- Qualification Rate: Percentage of leads that meet your criteria
- Conversion Rate: Percentage of leads that book appointments
Troubleshooting
- Webhook URL: Ensure you’re using your specific account webhook URL
- Phone Format: Phone numbers must include country code (+1 for US)
- Field Names: Form field names must match exactly (case-sensitive)
- SSL Certificate: Your website must have HTTPS enabled
- CORS Policy: Some forms may require CORS headers configuration