> ## Documentation Index > Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Inbound Lead to Booked Demo Voice AI Workflow > Build the Inbound lead to booked demo workflow with DialNexa voice AI. Follow the prerequisites, system handoffs, launch checks, and safety rules. This **Inbound Lead to Booked Demo voice AI workflow** turns a defined business event into a DialNexa conversation, a structured outcome, and a traceable next action. **Best for:** B2B SaaS, EdTech, Marketplaces Inbound demo requests are one of the highest-value automation points for a sales team. The lead has already raised a hand, but conversion drops quickly when the first response is slow, the wrong rep follows up, or the context never reaches the CRM. This workflow connects DialNexa voice AI to the systems that already run the revenue motion: CRM for ownership and qualification, calendar for booking, email and WhatsApp for confirmation, Slack for rep alerts, and reporting for funnel review. Inbound lead to booked demo workflow diagram ## Who Should Use This Inbound Lead to Booked Demo Workflow Use this workflow when inbound demand arrives through forms, paid campaigns, pricing pages, webinar signups, partner referrals, or missed calls. It is strongest when your team already receives qualified intent but loses meetings because response time, routing, or manual data entry is inconsistent. Good-fit examples include: * A B2B SaaS company responding to demo and pricing requests. * An EdTech business qualifying course enquiries before routing to a counsellor. * A marketplace or services business assigning inbound leads to the right sales pod. * A financial-services team separating serious prospects from research-only traffic. ## Before You Begin Prepare the following before building the workflow: * A clear source event that should start the call. * A [published DialNexa agent](/docs/agents/agent-versions-and-publishing) with an approved prompt and human-handoff rule. * A test contact who has agreed to receive the call. * Access to each source and destination system in the example stack. * A short list of structured outcomes to store with [post-call analysis](/docs/agent-settings/post-call-analysis). * An owner for failed runs, sensitive requests, and low-confidence matches. ## How The Inbound Lead to Booked Demo Voice AI Workflow Works ### 1. Trigger from a high-intent event The workflow starts when a lead submits a demo form, pricing request, webinar CTA, referral form, or missed-call callback request. The trigger should pass source, campaign, landing page, phone number, email, company, country, and any form answers into DialNexa. Before calling, the workflow searches the CRM for an existing contact, company, open deal, or previous activity. This prevents duplicate records and helps the AI conversation adapt to the lead's history. ### 2. Call within the response window DialNexa calls quickly, ideally within five minutes for demo and pricing requests. The agent confirms the person, why they requested a call, the business problem, role, company size, timeline, budget signal, and any required region or compliance constraints. The AI should not over-qualify a clear buyer. The goal is to collect enough context to route correctly, book the right next step, and avoid wasting rep time on students, vendors, spam, competitors, or low-fit contacts. ### 3. Branch by qualification outcome The first split is between qualified, nurture, and not reached. Qualified leads move to booking. The workflow checks territory, segment, product interest, language, account owner, and calendar availability. It then books a meeting and writes the reason for qualification into the CRM. Nurture leads receive the promised material, such as pricing context, course details, product information, or a callback option. The CRM should store the low-intent reason so the person is not pushed into the same sales queue as a ready buyer. Not-reached leads enter a retry path. The workflow waits for the configured window, retries once or twice, and then sends WhatsApp or email follow-up before marking the record cold or sending it to human review. ### 4. Book the meeting and confirm the promise When the lead is qualified, the workflow books into the right calendar instead of a generic round-robin. Routing can use region, company size, account ownership, product interest, preferred language, or campaign source. After booking, the workflow sends a confirmation by email and WhatsApp. The message should include the meeting time, agenda, joining link, rep name, and any documents the lead asked for on the call. ### 5. Update CRM and notify the owner The CRM update is the operational source of truth. Store the call ID, transcript link, lead source, qualification answers, objection, urgency, meeting URL, owner, and next action. If a deal or opportunity is created, include why the lead was considered qualified. The owner alert should be short enough to act on immediately: who the lead is, what they need, why they are qualified, what was promised, and where the meeting or CRM record lives. ## Build The Inbound Lead to Booked Demo Workflow Step By Step 1. **Define the trigger.** Choose one source event and document which records are eligible for the workflow. 2. **Prepare the agent.** Add the goal, questions, approved actions, disallowed actions, and transfer conditions to the agent prompt. 3. **Map call context.** Pass only the required customer and business fields through [dynamic variables](/docs/agents/dynamic-variables). 4. **Connect the systems.** Use a workspace connector when it is available. Otherwise use a [custom function](/docs/agent-settings/custom-functions), [agent webhook](/docs/api-access/agent-webhooks), or external automation service. 5. **Store structured outcomes.** Define the exact status, reason, owner, due date, and destination record ID that the workflow must produce. 6. **Add the next action.** Configure the workflow or application node that updates the destination system, sends a message, or creates a human-owned task. 7. **Test every branch.** Test success, rejection, no answer, wrong person, opt-out, missing data, provider failure, and human escalation before launch. ## Data Contract For This Workflow Store enough data to explain what happened without requiring the next owner to read the entire transcript: * Source event ID, source record URL, and workflow start time * DialNexa call ID, agent version, call status, and end reason * Matched customer or account ID and identity confidence * Structured outcome, reason, urgency, requested next step, and any promise made * Destination record ID, assigned owner, due date, and update result * Transcript or recording link only when your privacy and retention rules allow it ## Example Integration Stack * **[HubSpot](/docs/integrations/hubspot) or [Salesforce](/docs/integrations/salesforce) for CRM ownership, lead status, and pipeline updates** * **[Calendly](/docs/integrations/calendly) or [Google Calendar](/docs/integrations/googlecalendar) for booking** * **[Gmail](/docs/integrations/gmail) for confirmations and promised recaps** * **[WhatsApp](/docs/integrations/whatsapp) for quick reminders and fallback nudges** * **[Slack](/docs/integrations/slack) for owner alerts** * **[Google Sheets](/docs/integrations/googlesheets) or [Google BigQuery](/docs/integrations/googlebigquery) for workflow reporting** Provider pages describe possible connection patterns. Confirm the provider and required action in your DialNexa workspace before relying on a native connector. ## Human Review And Failure Paths Send leads to review when the CRM match is uncertain, account ownership conflicts, the caller requests legal or security information, or qualification depends on a policy exception. Stop all outreach immediately when the caller opts out or says the number belongs to someone else. Always send opt-outs, complaints, identity uncertainty, policy exceptions, sensitive data, and actions that change money, access, legal terms, or customer commitments to a trained person. ## Verify The Workflow Before Launch Run at least one test for every outcome branch and confirm that: 1. Only eligible records enter the workflow. 2. The agent receives the expected variables and does not expose internal field names. 3. The destination system stores the correct status, owner, and DialNexa call ID. 4. Retried events do not create duplicate calls or duplicate downstream records. 5. Opt-outs and human-handoff cases stop automation immediately. 6. The next owner can understand the result and promised next step from the destination record. ## Measure The Inbound Lead to Booked Demo Workflow Compare the baseline with the first 50 to 100 completed runs, then review results by source, segment, owner, and outcome. * Median time from form submit to first call * Connect rate by source and time of day * Qualified meeting rate * Meeting show rate * Duplicate CRM record rate * Percentage of leads routed to review * Revenue or pipeline created from booked meetings Track error rate, duplicate rate, human-review rate, and opt-out rate alongside the business metrics above. ## Troubleshoot Common Workflow Problems | Problem | What to check | | ------------------------------------ | -------------------------------------------------------------------------------------------- | | The wrong records enter the workflow | Tighten source filters and record the exact enrollment reason | | The call sounds generic | Pass fewer, higher-quality variables and explain how the agent should use each one | | The downstream record is incomplete | Require structured post-call fields before the destination action runs | | Duplicate calls or writes appear | Use the source event ID and DialNexa call ID as idempotency keys | | A provider action fails | Verify workspace availability, authentication, permissions, rate limits, and required fields | | Too many cases need review | Group review reasons and improve one high-volume branch at a time | ## Frequently Asked Questions ### Which lead sources should trigger the fastest call? Prioritize pricing requests, demo forms, missed calls, enterprise inquiries, and high-intent campaign forms. Lower-intent downloads can go through nurture unless the lead matches a high-value segment. ### What makes a lead qualified enough to book? Define qualification before launch: use case, urgency, company size, region, buying role, timeline, and any disqualifying rules. DialNexa should book only when the lead meets those routing rules. ### How do we avoid duplicate CRM records? Search by phone, email, company domain, and existing open deals before creating anything new. If the match is uncertain, create a review task with possible matches instead of updating the wrong account. ### What should sales managers review first? Review qualified meeting rate, show rate, duplicate record rate, owner routing, and whether reps can understand the call summary without listening to the recording. ## Related Pages * [DialNexa voice AI quickstart](/docs/quickstart) * [Create and publish agents](/docs/agents/agent-versions-and-publishing) * [Build DialNexa workflows](/docs/workflows/overview) * [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations) * [Test DialNexa agents](/docs/agents/testing-agents) * [Monitor call results](/docs/monitoring/call-detail-page)