Speed-to-Lead overview

Speed-to-Lead brings new leads into Avoca, assigns them to outreach, and tracks the journey from receipt to booking. Open Products → Speed-to-Lead in dashboard.avoca.ai.

​

How a lead moves through Avoca

1. A connected source sends a lead to Avoca.
2. Avoca parses and attributes the lead to a configured source.
3. Audience and duplicate checks determine whether the lead is eligible.
4. The source’s active campaign, or an enabled fallback campaign, assigns the outreach workflow.
5. Calls and messages run according to the workflow.
6. Replies, calls, campaign entry, and bookings appear in the lead journey.
7. Overview metrics report response and conversion performance.

​

Speed-to-Lead pages

• Overview: lead volume, qualification, response, bookings, and source performance
• Leads: searchable lead records and the complete journey for a selected lead
• Campaigns: campaigns available to the team
• Workflows: workflow definitions available to the team
• Emails: inbound lead email history when enabled
• Settings: lead sources, ingestion, mappings, and launch status
• Webhooks: endpoint configuration, source routing, field mappings, logs, and testing

Campaigns and workflows are shared with Outbound. Use clear names and confirm the campaign’s audience assignment so a lead source is not connected to the wrong outreach sequence.

​

Choose an ingestion path

Avoca can receive leads through:

• Forwarded lead alert emails
• Direct team webhooks and API keys
• Supported CRM polling or booking alerts
• Native provider connections, including GLSA, Yelp, and Angi when enabled

The correct method is configured per source. Do not switch a production source to another ingestion path until a controlled lead passes through the new path.

​

Use the Overview page

1. Set the date and time range.
2. Filter by lead-source group and service area when needed.
3. Compare Total Leads with Qualified Leads to identify ingestion or eligibility gaps.
4. Review Call Pickup Rate, Text Reply Rate, Jobs Booked, and the booking-rate metrics.
5. Compare source rows and charts to find high-volume or high-converting sources.
6. Select a source row to open the Leads page with that source and date range applied.

UTM reporting appears only for configurations that support it.

​

Interpret booking and revenue cards

• AI Booking Rate: jobs booked by Avoca AI without a human escalation, divided by Qualified Leads
• Holistic Booking Rate: every booked job attributed to a qualified lead—including AI bookings, bookings after escalation, and external or manual bookings—divided by Qualified Leads
• AI Booked Revenue: realized revenue from completed ServiceTitan jobs booked by Avoca AI through outbound calls or native conversations, excluding manually booked jobs
• Holistic Revenue: AI Booked Revenue plus completed jobs booked externally or manually in ServiceTitan

Use the Revenue attribution window to choose how many days after outreach a completed job can count toward the two revenue cards. The booking-rate cards do not use this slider. Unavailable is different from $0. It means ServiceTitan job sync is disabled, has not populated the required data, or the revenue query could not return a reliable value. Confirm the ServiceTitan connection and job-sync status before comparing revenue across sources or periods.

​

Run a lead-source A/B experiment

When Speed-to-Lead A/B testing is enabled for your organization, a source can split new leads across two or more published Speed-to-Lead workflows. Open Speed-to-Lead → Settings, edit the source, and continue to the launch step. Under Advanced settings:

1. Turn on Run A/B experiment.
2. Name the experiment.
3. Select a different published workflow for each variant.
4. Assign a positive traffic percentage to every variant. The total must equal 100%.
5. Review every workflow, delay, channel, and message before selecting Launch experiment.

The draft stays in the browser until launch; it does not change lead routing. Launching is immediate and sends the source’s next eligible leads through the configured workflow split. Only one experiment can be active for a source at a time. While an experiment is running, its workflows and percentages are read-only. You can rename it, Pause experiment, or End experiment. Pausing sends new leads through the source’s normal workflow until you resume. Ending archives the experiment and cannot be undone; new leads continue through the normal workflow. When experiments exist, the Overview adds A/B Experiments with Live, Paused, and Past filters. Expand an experiment to compare traffic, leads, qualified leads, call pickup, reply rate, jobs booked, and conversion for each workflow variant. Conversion is booked leads divided by qualified leads; a dash means the relevant denominator is zero.

​

Trace lead outcomes in Lead Flow

Use the Lead Flow card to understand where leads move or drop off within the selected date range and filters.

• Qualified View emphasizes qualification and source performance.
• Lead View follows total leads through qualification, reply, and booking outcomes.
• Select the Booked or Unbooked node in Lead View to open its text-reason breakdown.

The breakdown shows the count and share for each classified reason. Unclassified means the lead has not received a reason yet or the daily classifier could not determine one. It is not a separate customer outcome. Match the date range, lead sources, and service-area filters before comparing the Lead Flow totals with another report. Close the reason panel or select the same node again to return to the complete flow.

​

Daily operating review

1. Compare expected provider volume with Total Leads.
2. Review Qualified Leads and top not-contacted reasons.
3. Inspect sources with no recent leads or a sudden conversion change.
4. Open several Lead Journeys from each high-volume source.
5. Check the workflow and conversation when a lead did not receive the expected first contact.
6. Confirm bookings in the CRM before changing attribution or reprocessing a lead.