How to Automate Form-Fill Follow-Up Calls with Thoughtly

How to Automate Form-Fill Follow-Up Calls with Thoughtly

A lead fills out your quote request at 2:14 PM. Your CRMCRMThe system of record for leads, contacts, deals, and activity. Thoughtly reads from and writes to your CRM continuously.Read full definition → logs it. A rep sees it at 4:30 PM — maybe. By then the lead has talked to two competitors, forgotten your brand, and stopped answering unknown numbers. This is the speed-to-lead problem, and it costs high-volume teams more pipeline than most realize.

Thoughtly solves it by triggering an AI voiceAI voiceAn artificially generated, natural-sounding voice produced by a TTS model. Thoughtly supports a library of AI voices and brand-specific cloning.Read full definition → call within seconds of a form submission — no human in the loop, no batch processing delay, no leads sitting in a queue. This guide walks through the full setup: building the agent, wiring the form trigger, passing context into the call, adding fallback channels, syncing outcomes back to your CRM, and measuring the results.

Why Form-Fill Response Time Determines Conversion

Research from the Lead Response Management Study found that contacting a lead within five minutes of a form submission makes you 21 times more likely to qualify that lead compared to waiting 30 minutes. After an hour, the odds drop by more than 60 times.

The math is simple: a form submission is a high-intent signal. The lead is actively comparing options, probably has the browser open, and is expecting a response. Every minute of delay moves you from "timely" to "one more voicemail in the stack."

At scale — 500, 1,000, or 5,000+ inbound leads per month — manual follow-up cannot hit that window consistently. Reps get pulled into existing conversations. Leads submitted at 11 PM sit until morning. Weekend forms wait until Monday. An automated voice agentVoice agentAn autonomous, conversational interface that interacts with humans over the phone — answering, qualifying, and routing calls without human staffing.Read full definition → eliminates the bottleneck entirely.

What You'll Need

• A Thoughtly account with at least one active voice agent (or you will build one in Step 1)
• A phone number with outbound calling enabled — buy one from Thoughtly or bring your own carrier via BYOC
• A web form tool that sends data on submission. Native integration triggers exist for Typeform, GoHighLevel, and JotForm. For Google Forms, WordPress, HubSpot forms, or any other tool, you can use the Incoming Webhook trigger or route through Zapier or Make
• A CRM (optional but recommended) — HubSpot, Salesforce, GoHighLevel, Keap, Pipedrive, or Zoho all have native Thoughtly integrations

Step 1: Build Your Lead Qualification Agent

If you already have an agent that qualifies inbound leads, you can reuse it. Otherwise, open the Agent Builder and create a new voice agent designed for form-fill callbacks.

Start Node

The Start node is always step 0. It fires the moment the call connects. Keep it short — the lead just submitted a form and knows why you are calling.

First Speak Node: Greet with Context

Add a Speak node (prompt mode) immediately after Start. Reference the form context using metadata variables so the greeting is personalized, not generic:

Example prompt: "Hi {{metadata.first_name}}, this is [Agent Name] from [Company]. You just requested a quote for {{metadata.interest}} — I'd love to help you with that. Do you have a couple of minutes?"

Metadata is injected per-call from the automation (configured in Step 3). This makes every call feel immediate and relevant rather than cold.

Variables: Capture Consumer-Fit Signals

Configure Variables on your Speak nodes to extract structured data from the conversation. For high-consideration consumer funnels, focus on:

• Intent or need — What specifically are they looking for? (e.g., "auto insurance for a new vehicle," "refinance on a 30-year fixed")
• Urgency — When do they need it? (e.g., "closing next week," "shopping for fall enrollment")
• Location or service area — Where are they? Does your team cover their area?
• Eligibility or fit — Do they meet basic requirements? (e.g., licensed driver, homeowner, enrolled student)
• Availability — When can they talk to a human or attend an appointment?
• Preferred next step — Do they want a callback, a quote emailed, an appointment booked?

Variables extract immediately after the caller replies and before outcomes evaluate. Set clear extraction instructions and include "do not invent values" to prevent hallucinationHallucinationWhen an LLM-driven agent confidently states something incorrect. Mitigated with RAG, strict prompting, and evals against ground-truth data.Read full definition →.

Outcomes: Route by Qualification

Use Outcomes to branch the conversation based on what the agent learned:

• Qualified and available now → Transfer node to a live rep with an early summary attached
• Qualified but not available → Book an appointment (via Calendly, Cal.com, or GoHighLevel scheduling action) and confirm via SMS
• Not yet ready → End the call warmly, trigger an SMS follow-up sequence
• No answer or voicemail → Leave a voicemail drop and trigger SMS/email follow-up

Step 2: Create the Form-Trigger Automation

Open Tools → Automations in the Thoughtly dashboard (or go directly to app.thoughtly.com/automation). Create a new automation and select your trigger.

Option A: Native Integration Trigger

If your form tool has a native Thoughtly integration, select it directly:

• Typeform → "New Form Response" trigger. Connect your Typeform account, select the form, and Thoughtly receives every submission with all field values.
• GoHighLevel → "On Contact Created" trigger. When a GHL form creates a new contact, the automation fires.
• JotForm, Google Forms, Meta Ads → Use their respective integration triggers where available.

After selecting the trigger, go to the Output tab and click Refresh after submitting a test form. This locks the schema so you can map fields accurately in later steps.

Option B: Incoming Webhook Trigger

For form tools without a native integration — or when you want maximum flexibility — use the Incoming Webhook trigger:

1. Select "Webhook → Incoming Webhook" as your trigger.
2. Copy the unique webhook URL that Thoughtly generates.
3. In your form tool, configure a webhook or integration that POSTs a JSON payload to that URL on every submission.
4. Submit a test form, then click Refresh in the Output tab to lock the schema.

A typical webhook payload looks like this:

{ "contact": { "first_name": "Maria", "last_name": "Gonzalez", "phone": "+18005551234", "email": "[email protected]" }, "interest": "home_insurance", "zip": "90210", "source": "website_quote_form" }

Option C: Route Through Zapier or Make

If your form tool connects to Zapier or Make but not directly to Thoughtly, create a Zap or scenario that triggers on form submission and sends a POST to Thoughtly's automation webhook endpoint. This works with virtually any form tool — WordPress Gravity Forms, Webflow, Unbounce, Leadpages, and hundreds more.

Step 3: Map Form Data to the Call

The trigger fires. Now your automation needs to create a contact record and place the call — with the form data attached.

Create or Update Contact

Add a "Create or Update Contact" step. Map the phone number, name, and email from the trigger output using the data picker (lightning icon). This ensures a Thoughtly Contact record exists before the call, enabling persistent Attributes and call history tracking.

Add Attributes for Persistent Data

Use the "Add Attributes to Contact" step to store data that should survive across calls. Attributes persist on the contact record and are available to the agent via {{metadata.system.contact.attributes.ATTRIBUTE_NAME}}.

Good attributes for form-fill contacts include lead source, form name, zip or service area, interest category, and any vertical-specific detail (policy type, property type, program of interest).

Call Contact with Metadata

Add a "Call Contact" step. Select the agent you built in Step 1. In the Metadata field, pass a JSON object with form-specific context that the agent needs for this call only:

Example metadata: {"first_name": "Maria", "interest": "home_insurance", "zip": "90210", "lead_source": "website_quote_form"}

Inside the agent, reference these values as {{metadata.first_name}}, {{metadata.interest}}, and so on. Metadata is temporary — it exists only for this call. Anything you need long-term should be an Attribute.

Step 4: Add Fallback Channels for Missed Calls

Not every lead answers on the first ring. Your automation should handle non-connects gracefully instead of dropping the lead.

After the Call Contact step, add a Conditions step that checks the call outcome:

• If connected and qualified → No further action needed (the agent handled routing during the call)
• If no answer or voicemail → Add a Send SMS step with a short, contextual message:

Example: "Hi Maria, we just tried reaching you about your home insurance quote request. Reply here or call us back at [number] — we have your details ready."

• If no answer after SMS → Add a Send Email step with more detail, a link to self-schedule, or a summary of next steps

This creates a multi-channel sequence that mirrors how high-performing sales teams work — voice first, then SMS, then email — without any human effort.

Step 5: Configure Post-Call CRM Sync

Create a second automation triggered by On Call Completed. Scope it to the agent(s) handling form-fill callbacks.

This automation captures everything the agent learned and writes it back to your CRM:

1. Parse the call payload — The On Call Completed trigger provides call duration, transcript, variables captured, disposition, and outcome.
2. Add Disposition — Tag the contact with a clear result: booked, qualified, not-ready, no-answer, or disqualified.
3. Write to CRM — Use the HubSpot, Salesforce, GoHighLevel, or other CRM integration step to update the lead record with call outcome, qualification data, and a summary note.
4. Notify the team — For hot transfers or booked appointments, add a Slack notification or email alert so reps see it immediately.

This replaces legacy post-call settings (which Thoughtly is phasing out in favor of Automations). The On Call Completed trigger gives you full access to branching, conditions, and multi-step post-call workflows.

Step 6: Activate and Test

1. Test the agent first — Use the Test Agent (text chat) in the Agent Builder to verify variables extract correctly and outcomes route properly.
2. Test the automation in Draft mode — Submit a test form and verify the trigger fires. Check the Output tab to confirm field mapping is correct.
3. Call yourself — Use the Call Me feature or submit a real form with your own phone number. Verify the greeting references your form data, variables capture correctly, and the fallback SMS arrives if you decline the call.
4. Verify CRM sync — Check that the post-call automation writes the correct disposition, variables, and summary back to your CRM.
5. Switch to Live — Once everything passes, activate both automations. Thoughtly will now call every form submission automatically.

Important: The "Refreshing Output" action on Call steps places a real call. Always test with internal phone numbers.

Common Mistakes

• Forgetting to activate the automation. Draft automations never execute, even when trigger events fire. This is the single most common support issue.
• Not enabling outbound calling on the phone number. If your Thoughtly phone number has outbound calling disabled, calls will not go out. Check Phone Number settings and enable "Allow Outbound Calls."
• Skipping the Create or Update Contact step. Calling with "Call Phone Number" instead of "Call Contact" means you lose persistent Attributes and call history tracking. Always create the contact first.
• Calling outside business hours. Leads submitted at midnight should not get a call at midnight. Use a Conditions step to check the time, or pair with a Recurring Schedule to batch after-hours leads into the next morning's window.
• Over-qualifying on the first call. The goal of a form-fill callback is to confirm interest and book a next step — not to run a 15-minute intake. Keep it tight: verify intent, confirm fit, schedule the conversation.
• Ignoring voicemail and no-answer paths. Roughly 60–70% of first outbound attempts go unanswered. If your automation has no fallback, you are losing the majority of your form leads.

Measuring Success

Track these metrics weekly to evaluate your form-fill follow-up automation:

Frequently Asked Questions

Which form tools work with Thoughtly?

Thoughtly has native integration triggers for Typeform, GoHighLevel, and JotForm. Any other form tool that can send a webhook — including Google Forms, HubSpot Forms, WordPress (Gravity Forms, WPForms, Contact Form 7), Webflow, Unbounce, and Leadpages — works via the Incoming Webhook trigger. If your tool connects to Zapier or Make, you can route submissions to Thoughtly through those platforms as well.

Can I pass custom form fields to the AI agent?

Yes. Every field in the form submission payload is available as a variableVariableA named value the voice agent stores during a conversation — caller name, intent, qualifying answers — and uses to drive routing and post-call actions.Read full definition → in the automation. You can pass any field as metadata when placing the call, and the agent can reference it during the conversation using {{metadata.field_name}}. Common examples include interest type, zip code, preferred language, referral source, and any vertical-specific detail.

What happens if the lead does not answer?

Configure your automation to branch on the call outcome. For no-answer or voicemail results, trigger a Send SMS step immediately, followed by a Send Email step. You can also add a Delay step and retry the call once or twice over the next 24 hours. The key is having a defined path for non-connects rather than letting those leads go cold.

How fast does Thoughtly call after form submission?

With a native integration trigger or webhook, the automation fires within seconds of form submission. Total time from form submit to first ring is typically under 60 seconds, depending on the trigger path and any pre-call steps (like CRM lookup) in the automation.

Do I need a separate automation for each form?

Not necessarily. If multiple forms use the same webhook URL and payload structure, a single automation handles all of them. You can differentiate by passing a form_name or source field in the webhook payload, then use Conditions steps to branch the automation logic based on which form triggered it. For forms with very different qualification flows, separate automations and agents may be cleaner.

Sources and Further Reading

• Thoughtly Automations documentation — Full reference for triggers, actions, and data mapping
• Thoughtly Triggers reference — All available trigger types including webhooks and integrations
• Variables in voice agents — How to capture and reuse data during calls
• Attributes vs. Metadata — When to use persistent vs. per-call data
• Speed-to-Lead solution page — Thoughtly's sub-60-second inbound lead response
• How to Build a Speed-to-Lead AI Agent with Thoughtly — Related implementation guide
• How to Qualify Inbound Leads Over Voice and SMS with Thoughtly — Lead qualification guide
• How to Sync AI Conversations Back to HubSpot — CRM sync walkthrough
• InsideSales.com Lead Response Management Study — Original research on speed-to-lead and qualification odds