Guides
A step-by-step guide to building Revenue Autopilot workflows in Thoughtly — trigger outbound calls on every new lead, orchestrate voice/SMS/email follow-up, qualify through conversation, and hand off qualified leads to reps with full CRM sync.
Last updated
Most revenue teams lose the majority of their inbound leads to slow follow-up. A lead fills out a form at 9:47 PM, sits in a CRMCRMThe system of record for leads, contacts, deals, and activity. Thoughtly reads from and writes to your CRM continuously. queue overnight, and by the time a human BDR dials at 9:15 AM, the prospect has already moved on. Thoughtly's Revenue Autopilot exists to close that gap.
Revenue Autopilot orchestrates voice, SMS, and email follow-upEmail follow-upEmail follow-up is the process of sending timely, context-aware replies or reminders that keep an inbound lead moving toward qualification, scheduling, or handoff. so every inbound lead gets contacted in under 60 seconds, qualified through a conversation, and handed off to a human rep only when they're ready to talk. This guide walks through how to set it up, step by step, using actual Thoughtly product mechanics.
Before you start building, make sure you have the following:
Revenue Autopilot is not a single feature toggle. It's a workflowWorkflowAn automated, multi-step process — usually triggered by an event (form fill, new lead) and orchestrating one or more voice / SMS / email actions. pattern built from Thoughtly's Automations engine, Voice Agents, and integrations. The core promise: every inbound lead gets called, texted, and emailed until they respond or opt out, and your reps only talk to people who are qualified and ready.
The key components are:
The result: 100% lead coverage, sub-60-second speed-to-lead, and reps starting at yes instead of dialing from a list.
Before you wire up automations, you need a working Voice AgentVoice agentAn autonomous, conversational interface that interacts with humans over the phone — answering, qualifying, and routing calls without human staffing.. If you haven't built one yet, start in the Agent Builder (Tools > Agents in the Thoughtly dashboard).
For a Revenue Autopilot use case, your agent should:
Use the Agent Builder's node system to structure the conversation: Start node, Speak nodes for each section, Transfer node for warm handoffs, and End node to close gracefully. Set up outcomes (rule-based or prompt-based) to branch the flow based on what the caller says.
Test thoroughly using the Test Agent (text chat) and Call Me (real call) features before connecting automations. Never wire up outbound dialing to an untested agent.
A mortgage lender builds an agent that calls every rate inquiry within 60 seconds. The agent asks about property type, loan amount range, timeline, and whether the borrower has already applied elsewhere. If the borrower is ready, the agent offers to warm-transfer to a loan officer. If not, the agent sends an SMS with a Calendly link and logs the disposition in HubSpot.
Revenue Autopilot starts with a triggerTriggerThe event or condition that starts an automated workflow, such as a new lead, missed call, CRM status change, calendar booking, or completed call.. The trigger is what tells Thoughtly "a new lead just arrived, start the workflow."
Thoughtly supports several native integration triggers:
If your lead sourceLead sourceThe channel, campaign, marketplace, referral partner, or form that generated a lead. Lead source often determines routing, compliance rules, and follow-up cadence. isn't listed, use the Incoming WebhookWebhookAn event-based integration that sends data from one system to another when something happens, such as a form submission, booked appointment, or completed call. trigger. Most CRMs, form tools, and ad platforms can send a webhook on new lead creation. You'll get a unique URL from Thoughtly; point your source's webhook at it.
To set up the trigger, go to Tools > Automations in the Thoughtly dashboard, create a new automation, and select your trigger. After configuring it, click the Output tab and refresh to capture the sample payload. You'll need those field paths (like {{ trigger.payload.contact.phone }}) when you map data into the call step.
After your trigger, add a Call Contact or Call Phone Number step. This is where the actual outbound dial happens.
Use Call Contact if you want to persist lead data as Attributes on a Thoughtly contact record (recommended for multi-touch sequences). Use Call Phone Number for simpler one-off calls.
Map the phone number from your trigger payload. For example:
{{ trigger.payload.properties.phone }}Select your tested Voice Agent. Optionally attach a Genius knowledge baseKnowledge baseA structured source of business information, FAQs, policies, product details, or procedures that an AI agent can use to answer accurately. if your agent needs product or pricing information during the call. You can also override language and voice per call if you serve multilingual markets.
Add metadata to tag the call with campaign context:
{"campaign": "q3_mortgage_rates", "lead_source": "google_ads", "priority": 1}Not every lead picks up on the first call. Revenue Autopilot's value is in persistent, multi-touch follow-up. After the call step, add Conditions to check the call outcome, then branch:
| Condition | Next step |
|---|---|
| Call connected, lead qualified | Warm transfer or book meeting |
| Call connected, lead not ready | Send SMS with scheduling link, schedule callback in 3 days |
| Voicemail detected | Drop voicemail, send SMS, retry call next day |
| No answer | Send SMS, retry call in 2 hours, then email next day |
| Opt-out | Update CRM, stop all follow-up |
Use the Delay For step between contact attempts. For example, delay 2 hours before the second call attempt and 1 day before the third. Use Delay Until to respect quiet hoursQuiet hoursTime windows when outbound calls or texts should not be sent, based on legal rules, customer preferences, or business policy. — delay until 9 AM the next business day if the first call is after business hours.
Add Send SMS steps for non-connecting calls. Keep SMS messages short and actionable:
Hi {{ trigger.payload.properties.firstname }}, this is Riley from LenderStone. I just called about your rate quote request. You can book a quick call here: {{ steps.calendly_schedule.scheduling_link }}Add Send Email steps for leads that don't respond to voice or SMS within 48 hours. Configure your email domain first in Settings > Email Domains.
For a full cadence (call, SMS, delay, call again, email, delay, final call), use a combination of Conditions (If/Else for call outcome branching) and Loop (to iterate through a list of follow-up attempts). The Loop step is useful when you have a predefined list of retry times or channels.
A typical mortgage follow-up cadence:
When the agent qualifies a lead, the next step is getting them to a human. You have two options:
Option A: Warm transferWarm transferA live transfer where the agent connects a qualified caller to the right human while preserving context, instead of sending the caller to a cold queue or voicemail.. Use the Transfer node in your agent (Phone Router or Agent Transfer) to connect the lead to a rep in real time. This is best for high-intent leads where speed matters — mortgage rate inquiries, insurance quote requests, urgent home service calls.
Option B: Self-scheduling. Add a scheduling integration step (Calendly, Cal.com, or Acuity) to the automation. The agent offers available times during the call, books the appointment, and sends an SMS confirmation. This is best for leads who aren't ready to talk right now but want to book a specific time.
For scheduling, add the integration step after the call connects and the agent reaches the qualification outcome. Map the booking link into an SMS step so the lead gets a confirmation immediately.
After every call, use the On Call Completed trigger in a separate automation to sync outcomes back to your CRM. This is critical for pipeline visibility and attribution.
The On Call Completed trigger fires after any call ends and provides rich payload data:
Use this data to update CRM records with dispositions, qualification scores, and next-step notes. For example, in HubSpot, use the Create or Update Contact action to write the call outcome as a custom field. In Salesforce, use a custom object or task record.
You can also use the AI step (Extract Fields) to pull structured data from the transcriptTranscriptThe text record of a voice conversation, used for review, training, compliance audit, and search. — things like budget range, timeline, and service areaService areaThe geography where a business can serve a prospect. Service-area checks prevent routing or booking leads a team cannot actually handle. — and write those as attributes or CRM fields.
Before going live, test your automation in Draft mode. Fire a test webhook or create a test CRM contact, then check the automation run log to verify each step executed correctly. Click the Output tab on each step and refresh to confirm data is flowing.
When you're confident, click Activate in the top right of the automation editor. The automation will now run on every trigger event.
Monitor performance in Thoughtly Analytics (Tools > Analytics). Key dashboards to watch:
The most common mistakes teams make when setting up Revenue Autopilot:
Once Revenue Autopilot is live, measure success against your pre-Autopilot baseline. The metrics that matter:
| Metric | What good looks like | How to measure |
|---|---|---|
| Lead coverage | 95-100% of inbound leads receive at least one contact attempt | Compare CRM lead count against Thoughtly call logs |
| Speed-to-lead | Under 60 seconds from form submission to first call | Check automation run timestamps vs trigger timestamps |
| Contact rate | 40-60% of leads answer at least one call in the cadence | Thoughtly Analytics — call status breakdown |
| Qualified transfer rate | 15-30% of connected calls result in a warm transfer or booking | On Call Completed outcomes + CRM disposition sync |
| Pipeline influenced | Measurable lift in meetings booked vs pre-Autopilot | CRM reporting — compare pre/post periods |
| Cost per qualified lead | Lower than human BDR equivalent | Thoughtly usage + CRM pipeline value |
Track these weekly for the first 30 days, then monthly. The biggest initial gains typically come from speed-to-lead and lead coverage — you're going from 20-30% of leads contacted to near-100%, and from hours-of-delay to under-a-minute response.
AI SDR tools focus on cold outbound prospecting — finding net-new contacts and emailing them. Revenue Autopilot focuses on converting the leads you've already paid to acquire. It calls, texts, and emails every inbound form fill, returning call, or aged leadAged leadA lead that is no longer fresh but may still convert with the right re-engagement cadence, especially when intent, eligibility, or timing has changed. until they're ready to talk to a human. The distinction matters: Autopilot works opted-in inbound leads, not cold outbound lists.
No. Revenue Autopilot is built from Thoughtly's no-code Automations builder. A RevOps operator or marketing ops manager can build the full workflow: trigger configuration, call steps, conditions, delays, SMS/email follow-up, and CRM syncCRM syncCRM sync is the two-way flow of lead records, conversation notes, outcomes, and next steps between an AI agent platform and a CRM so human teams inherit current pipeline instead of manual updates.. For custom integrations, a developer can use the Incoming Webhook trigger or the REST API, but that's optional.
Your agent should capture opt-outOpt-outA recipient’s request to stop receiving calls or messages. Compliant systems must capture opt-outs and suppress future outreach where required. during the call (add an outcome for "opted out"). The On Call Completed automation can then update the CRM with an opt-out flag and a suppression list attribute. Subsequent automations should use a Conditions step to check the opt-out attribute before dialing. Thoughtly also supports DNC scrubbingDNC scrubbingFiltering outbound dialing lists against federal and internal Do-Not-Call registries. Required for compliant outbound — Thoughtly scrubs every call. and suppression lists for compliance.
Yes. Create separate automations with different triggers (one for HubSpot form fills, another for Typeform responses, a third for imported lists). Or use a single automation with Conditions to branch based on lead source in the trigger payload. For example, Google Ads leads get a 5-touch cadence over 3 days, while organic leads get a 3-touch cadence over 5 days.
Most teams ship their first Revenue Autopilot workflow in under a week. The typical timeline: day 1-2 to build and test the Voice Agent, day 3 to connect the CRM trigger and call step, day 4 to add the multi-channel follow-upMulti-channel follow-upA follow-up motion that uses more than one channel — usually voice, SMS, and email — to improve contact rates after a prospect raises their hand. sequence, day 5 to test in Draft mode and activate. Complex multi-CRM or multi-language setups may take longer.
Thoughtly Revenue Autopilot product page — overview of the feature and its promise
Thoughtly Automations docs — how triggers, actions, and steps work
Thoughtly Automation Triggers — available trigger types and configuration
Thoughtly Automation Actions — call steps, SMS, email, conditions, loops, and integrations
Thoughtly Attributes vs Metadata — data persistence patterns for multi-touch workflows
How to Build a Speed-to-Lead AI Agent with Thoughtly — companion guide for the speed-to-lead use case
How to Build a Multi-Channel Follow-Up Sequence with Thoughtly — deep dive on the follow-up cadence mechanics
Thoughtly Solutions — industry-specific positioning for Autopilot workflows