> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pulsyai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build an Inbound AI Agent

> Build an Inbound voice AI agent in PulsyAI — receive phone calls, handle customer inquiries, route to bookings, and integrate with your CRM. Step-by-step guide to script, knowledge base, and integrations.

An inbound AI agent is a voice AI agent that answers incoming calls to a phone number you (or your client) own. Common use cases include AI receptionists for service businesses, lead-capture front-lines for high-volume callers, after-hours coverage when human staff are unavailable, and full call deflection so human agents can focus on the conversations that need them.

<Columns cols={3}>
  <Card title="Voice-first capture" icon="phone-incoming">
    The AI answers, qualifies, and captures contact info on every inbound call.
  </Card>

  <Card title="Up to 1,000 calls in parallel" icon="users">
    No more busy signals, no more voicemails — every caller gets through.
  </Card>

  <Card title="Recovers the hangups" icon="rotate-cw">
    Stale Recovery + Call Back catch leads who disconnect before capture completes.
  </Card>
</Columns>

This page covers the inbound-specific setup. The script methodology, conversion principles, and the four-step structure that go into your agent's prompt are universal — they live on the [Build a Script](/platform/build-your-agent/build-a-script) page, and we recommend reading that first if you haven't already. The PulsyAI advantage for inbound is the combination of methodology plus a stack of inbound-specific features that together produce the conversion numbers we publish.

<Tip>
  **Before you start:** Read [Build a Script](/platform/build-your-agent/build-a-script) end-to-end. The eight principles on that page — short scripts, fast capture, never repeating user information, Whisper post-call correction, inline knowledge base, the pre-call intro message, short sentences, and stale conversation recovery — are the difference between an inbound agent that books 92% of qualified callers and one that gets hung up on. This implementation guide assumes you've drafted a script following that methodology.
</Tip>

## The inbound conversion stack

PulsyAI inbound agents combine four features that work together to maximize lead capture from every call:

<Columns cols={2}>
  <Card title="1. Pre-call intro voice recording" icon="megaphone">
    A short human voice plays before the AI picks up, psychologically priming the caller for the AI handoff. Configured in [Agent Settings](/platform/agent-settings).
  </Card>

  <Card title="2. The four-step PulsyAI script" icon="list-checks">
    Greeting with virtual assistant disclosure, fast need identification, immediate contact capture without read-back, and SMS verification closure. See [Build a Script](/platform/build-your-agent/build-a-script) for the full methodology.
  </Card>

  <Card title="3. Whisper + Verify User Information" icon="shield-check">
    Live STT errors corrected automatically post-call, with an optional SMS sent to the caller for any remaining corrections. Configured in [SMS Configuration](/platform/sms-configuration).
  </Card>

  <Card title="4. Stale Conversation Recovery" icon="rotate-cw">
    Automatic SMS follow-up to leads who hang up before completing the capture, using the caller ID as the fallback contact point. See [Stale Conversations](/platform/integrations/stale-conversations).
  </Card>
</Columns>

Here is how the full inbound flow runs end-to-end, from the moment the caller dials in to the moment the lead lands in the client's system of record:

```mermaid theme={null}
flowchart TD
    A[Caller dials inbound number] --> B[Pre-call intro voice<br/>10-15 sec human recording]
    B --> C["AI greeting<br/>'Hello, you're online with Luna<br/>the virtual assistant from...'"]
    C --> D[Step 1: Need identification]
    D --> E[Step 2: Technical clarification<br/>1-2 targeted questions]
    E --> F[Step 3: Capture lead info<br/>Never repeat back]
    F --> G[Step 4: Closure with<br/>SMS verification mention]
    G --> H[Call ends]
    H --> I[Whisper post-call correction<br/>backend, runs in seconds]
    I --> J{All critical<br/>info captured?}
    J -->|Yes| K[Verify User Information SMS<br/>sent to caller for any corrections]
    J -->|No| L[Stale Conversation Recovery triggers<br/>3 SMS attempts at 5-min intervals]
    K --> M[Lead lands in CRM, Slack,<br/>email, or webhook]
    L --> M
    style A fill:#EEF2FF,stroke:#6366F1
    style M fill:#D1FAE5,stroke:#10B981
    style B fill:#FEF3C7,stroke:#F59E0B
    style I fill:#FEF3C7,stroke:#F59E0B
    style K fill:#FEF3C7,stroke:#F59E0B
    style L fill:#FEF3C7,stroke:#F59E0B
```

The yellow-highlighted nodes are the PulsyAI-specific differentiators that make this stack convert better than a generic voice AI setup — the intro message that primes the caller, the Whisper correction layer that lets the agent skip read-backs without losing accuracy, the SMS verification that closes the accuracy loop, and the stale recovery that catches the hangups before lead capture completes.

## Setup walkthrough

<Steps>
  <Step title="Assign a phone number" icon="phone">
    Every inbound agent needs a phone number that callers can dial. PulsyAI supports four ways to bring a number into your account:

    <Columns cols={2}>
      <Card title="Purchase in-app" icon="shopping-cart">
        Buy a new number directly from PulsyAI. Note that numbers purchased in-app are inbound-only for security reasons.
      </Card>

      <Card title="Import from Twilio" icon="download">
        Bring a number you already own on Twilio.
      </Card>

      <Card title="Import from Telnyx" icon="download">
        Bring a number you already own on Telnyx.
      </Card>

      <Card title="Import via SIP" icon="network">
        Connect a SIP trunk if you operate your own telephony infrastructure.
      </Card>
    </Columns>

    Once a number is in your account, assign it to your inbound agent. For full details on each option, see the [Phone Numbers](/platform/phone-numbers) page.
  </Step>

  <Step title="Build the agent and paste your script" icon="file-text">
    Inside your agent builder, create a new agent of type **Inbound**. Paste the script you drafted using the [Build a Script](/platform/build-your-agent/build-a-script) methodology into the agent's prompt.

    The four-step structure (**greeting → need identification → capture → closure**) applies as-is for inbound. Keep the greeting in the exact PulsyAI pattern — `"Hello, you're online with Luna the virtual assistant from {company_name}. How can I help you today?"` — without a comma after "virtual assistant", since this is the configuration that performs best in production.

    <Info>
      If your client's knowledge base fits inline in the prompt (under approximately 100 pages of equivalent text), include it directly in the prompt below the closure section to avoid function-call latency. For larger knowledge bases, use the dedicated [Knowledge Base](/platform/knowledge-base) section instead.
    </Info>
  </Step>

  <Step title="Upload the pre-call intro voice recording" icon="mic">
    The pre-call intro message is one of the highest-ROI features for inbound agents specifically — it doesn't apply to outbound or SMS because those don't have the same "caller about to hear an AI for the first time" moment.

    In the agent settings, upload a 10-15 second recording of a human voice that plays the instant the call connects, before the AI greeting. Something like:

    > *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling*  *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."*{company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling*  *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."*{company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."* *"Hi, thanks for calling* {company}*. You're being connected to our virtual assistant who will help direct your call. Don't worry — a human representative will follow up with you immediately after this call. One moment please."*

    **Why it works — three purposes in one recording:**

    <Columns cols={3}>
      <Card title="Primes the caller" icon="brain">
        Sets the expectation of an AI handoff — no surprise factor when the agent picks up.
      </Card>

      <Card title="Reinforces legitimacy" icon="building">
        Confirms there's a real business on the other end of the line.
      </Card>

      <Card title="Promises a human callback" icon="user-check">
        Reduces resistance to engaging with the AI for the initial intake.
      </Card>
    </Columns>

    The combination of the pre-call human voice and the explicit human callback promise produces measurably higher conversion than either alone. Resellers who skip this step typically see a measurable drop in conversation duration past the greeting.

    For setup details and recording requirements, see [Agent Settings](/platform/agent-settings).
  </Step>

  <Step title="Configure Verify User Information" icon="shield-check">
    Verify User Information is the SMS-based safety net that catches any errors that slipped through during the call — even after Whisper post-call correction. It's a separate layer from the "never repeat user information" principle, which is enforced inside your agent's prompt (see [Build a Script](/platform/build-your-agent/build-a-script)).

    **How the two layers work together:**

    1. Inside your **prompt**, you instruct the agent to never read user information back out loud during the call. This is a script-level directive — the agent simply acknowledges captures with "noted" or "registered" instead of reading the info back. For the full reasoning behind this directive, see [Principle 3: Never repeat user information back](/platform/build-your-agent/build-a-script#principle-3-never-repeat-user-information-back) in the Build a Script methodology. For a working example of how to phrase the directive inside an agent prompt, see the [PulsyAI Plumber example script](/platform/build-your-agent/build-a-script#full-example-script-pulsyai-plumber) — its Step 3 demonstrates the full capture sequence with the "never repeat" instructions inline.
    2. After the call ends, **Whisper** corrects any STT errors in the recorded audio and updates the captured info with the corrected version.
    3. With **Verify User Information enabled**, the caller then receives an SMS summarizing the final captured information.
    4. If anything is still wrong, the caller replies to the SMS with the correction and the data is fixed automatically in your client's CRM.

    <Info>
      For inbound agents this is essentially **mandatory** — it's what closes the accuracy loop after Whisper. The configurable time delay also ensures the SMS sends even if some captured information is missing, so the partial data still reaches the client's CRM with whatever was collected.
    </Info>

    For configuration details, see [SMS Configuration](/platform/sms-configuration).
  </Step>

  <Step title="Configure Call Back and Stale Conversation Recovery" icon="rotate-cw">
    For inbound voice agents, two integrations work together to recover leads who didn't complete the capture flow during the live call.

    **Call Back — the fallback trigger**

    Open your agent's **Integrations** tab and configure **Call Back**. This is the integration that triggers the fallback when your condition fires (for inbound this is typically "the agent did not collect a phone number or email before the call ended"). In the Call Back settings, you choose the action:

    <Columns cols={2}>
      <Card title="SMS Agent action" icon="message-square">
        Send an SMS to follow up. The dropdown lets you select any SMS AI agent on your account, OR the current inbound voice agent itself (which uses the same phone number for the SMS fallback, with the script and configuration shared from the voice agent).
      </Card>

      <Card title="Phone agent action" icon="phone-outgoing">
        The AI calls back the lead to finish the conversation by voice instead of SMS.
      </Card>
    </Columns>

    For inbound speed-to-lead and missed-capture recovery, the **SMS Agent action typically outperforms the Phone agent action** — leads who already hung up once are less likely to answer a second call but will often respond to a text. For full Call Back configuration details, see the dedicated [Call Back](/platform/integrations/call-back) page.

    **Stale Conversation Recovery — the relaunch sequence**

    Once Call Back has sent the initial fallback SMS, Stale Conversation Recovery handles the automatic retries if the lead doesn't respond. Configure it in the same Integrations tab.

    The PulsyAI recommendation for inbound:

    <Columns cols={3}>
      <Card title="Push delay" icon="upload">
        Push the partial information to your client's CRM relatively quickly (a few minutes) so the human team is aware of the incomplete lead.
      </Card>

      <Card title="Relaunch delay" icon="timer">
        5 minutes after the conversation goes stale.
      </Card>

      <Card title="Max attempts" icon="repeat">
        3 attempts at 5-minute intervals, covering the "hot lead window" of \~15 minutes after the disconnect.
      </Card>
    </Columns>

    <Info>
      For inbound specifically, the **caller ID detected by the telephony layer serves as the fallback contact point** — so even if the caller hangs up before saying their phone number out loud, the Call Back SMS still reaches the right phone.
    </Info>

    The full configuration guide lives on the dedicated [Stale Conversations](/platform/integrations/stale-conversations) page.
  </Step>

  <Step title="Connect integrations and test" icon="plug">
    The last step is wiring up where the captured leads should land. Inbound agents typically integrate with:

    <Columns cols={3}>
      <Card title="CRM connectors" icon="database">
        Send lead data directly into your client's CRM (HubSpot, GoHighLevel, etc.).
      </Card>

      <Card title="Webhooks" icon="webhook">
        Custom destinations for clients with bespoke systems.
      </Card>

      <Card title="Email or Slack" icon="bell">
        Simple notification channels for smaller operations.
      </Card>
    </Columns>

    For the full list of available integrations and setup guides, see the [Integrations](/platform/integrations) section.

    <Check>
      **Final test:** place a test call to the agent's phone number, run through the full flow as if you were a caller, and verify three things:

      1. The captured data lands correctly in the configured destination.
      2. The SMS verification message arrives within seconds of the call ending.
      3. If you deliberately hang up before completing capture, the stale recovery SMS arrives at the expected interval.
    </Check>
  </Step>
</Steps>

## Common inbound use cases

<CardGroup cols={2}>
  <Card title="The voicemail replacement" icon="voicemail">
    The no-brainer pitch. During business hours, the agent doesn't replace anyone — it only picks up the calls that would have gone to voicemail after 3-4 rings. The client keeps their phone setup as-is. Since most callers hang up rather than leave a voicemail, the AI captures leads that would have been lost entirely, then notifies a human representative immediately. The easiest sale for AI-skeptical clients.
  </Card>

  <Card title="Receptionist overflow" icon="users">
    The AI supports existing receptionists rather than replacing them. Human receptionists can only take one call at a time — when they're busy, the next caller goes to voicemail or gets a busy signal. PulsyAI inbound agents handle up to 1,000 simultaneous calls and pick up the overflow seamlessly. The framing that closes deals: "we're not replacing your team — we're making sure they never miss another call."
  </Card>

  <Card title="AI receptionist (full migration)" icon="headset">
    For service businesses without an existing receptionist, or those ready to fully migrate phone intake to AI. Plumbing, HVAC, dental, legal — anywhere a missed call equals a lost lead. The agent handles initial intake and books the human callback.
  </Card>

  <Card title="After-hours coverage" icon="moon">
    The agent answers when the human team is offline, captures the lead, and sends everything to the CRM for the next-day follow-up. Same implementation as during-hours, routed via the client's carrier scheduling.
  </Card>

  <Card title="High-volume campaign capture" icon="chart-line">
    Marketing campaigns generate spikes the human team can't absorb. The agent takes the overflow. Particularly useful for campaigns generating hundreds or thousands of inbound calls in short windows — TV spots, viral social posts, mass SMS blasts.
  </Card>

  <Card title="Call deflection for repetitive queries" icon="filter">
    Hours of operation, pricing questions, service areas — handled by the agent with the inline knowledge base, freeing the human team for the calls that actually need them.
  </Card>
</CardGroup>

## Next step

<CardGroup cols={2}>
  <Card title="Build an Outbound AI Agent" icon="phone-outgoing" href="/platform/build-an-outbound-ai-agent">
    The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the  The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback.{name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the  The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback.{name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback. The implementation guide for outbound agents — speed-to-lead, the {name} greeting variant, Auto Callback, and SMS fallback.
  </Card>

  <Card title="Build an SMS AI Agent" icon="message-square" href="/platform/build-an-sms-ai-agent">
    The implementation guide for SMS agents — text-only nuances, conversation cadence, and stale recovery as a core feature.
  </Card>
</CardGroup>
