AI voice agent for outbound followup automation.

Outbound call placed. Answer detection runs as call connects: live human answer ('hello?'), voicemail greeting (longer pause + greeting pattern), IVR/menu system (touch-tone detection + automated voice patterns), busy signal, no-answer/timeout. Answer-detection accuracy matters — calling AI talking to a voicemail greeting before the beep wastes the message; AI talking to an IVR confused by 'press 1 for...' wastes the call. Different answer types route to different lanes with different scripts.

Live human answer. AI's first sentence is critical: identify the company, identify itself as AI assistant, state the call's purpose, immediately make the action available. 'Hi, this is Maya, the AI assistant for Coastal Dental — I'm calling to confirm your appointment Tuesday at 2pm. Can I confirm or would you prefer to reschedule?' Recipient knows in 8 seconds: who's calling, why, what's needed. The single biggest mistake outbound voice AI makes is sounding human-but-not-disclosing-AI; that's both ethically wrong and increasingly illegal in many jurisdictions.

Recipient responds — confirms appointment / reschedules / asks question / requests human / requests do-not-call. AI handles the standard responses (confirmation, simple reschedule, info request) and warm-transfers anything outside scope. Do-not-call request is hard rule: AI immediately confirms ('Got it — I've taken you off the call list. Apologies for the interruption today.'), updates internal opt-out registry, ends call, never calls again. The opt-out moment defines whether your outbound voice program respects recipients or treats them as targets.

Voicemail detected. AI waits for the beep (or end-of-greeting silence pattern) before leaving the message. Message script: clear identification (AI from your company), specific reason for call, action item with options (call back, click SMS link, reply to email), reference number for tracking. Keep it under 25 seconds — long voicemails get deleted unheard. Send parallel SMS or email with the same call-to-action; voicemail alone has 15-20% callback rate, voicemail + SMS has 45-60%.

Voicemail left + SMS sent immediately + email at 2 hours if no response. Each channel reinforces the other; recipient sees the SMS first usually, voicemail sits as evidence the call happened. Action confirmation via SMS reply or click-through link reduces friction — 'Reply Y to confirm, N to reschedule' converts at 3-5x voicemail-callback alone. Multi-channel reach is what makes outbound voice actually convert; voicemail-only is a 1990s playbook.

Touch-tone menu or automated answering system detected. AI doesn't try to navigate IVR menus — it's almost always wrong, sounds broken, and frustrates downstream humans who eventually hear 'press 1 for billing... press 2 for...' followed by AI confusion. AI hangs up cleanly and routes to the followup-cascade lane. Different recipient phone setups (business main lines, phone trees, automated assistants) all classify as IVR; the rule is consistent: don't navigate menus, retry via different channel.

SMS + email sent with the same purpose and call-to-action. Phone number flagged as 'IVR-protected' in the contact record so future outbound attempts default to digital channels first rather than spending the calling cost on a known IVR. Some recipients have all calls routed through corporate phone systems by default; the system learns recipient-by-recipient patterns and allocates channel mix accordingly.

Busy signal or timeout (no answer + no voicemail picked up). Retry scheduled within compliance windows: typical pattern is 4-6 hours later for high-priority (appointment day-of), next business day for standard. Maximum 2-3 attempts per recipient per outreach cycle — repeated calls without contact become harassment regardless of intent. Failed attempts logged; persistent no-answer recipients flagged for digital-only channels going forward.

After max retries with no contact, switch to digital channels: SMS with action link, email with full context, in-app notification if applicable. The voice channel served its purpose — multi-attempt confirmation. Quarterly review: which recipients consistently no-answer? They might prefer digital-only outreach by default; system learns and allocates channels per recipient. The voice channel is precious budget; spend it where it converts.

Call achieved its goal — appointment confirmed, payment promised, info collected, satisfaction logged. Downstream action triggered: confirmation logged in scheduling system, payment-promise added to AR ledger, info captured to CRM. Confirmation receipt sent via SMS or email. The outbound call's success metric isn't 'call answered' — it's 'goal achieved.' Confirmed appointments reduce no-show rate 30-40%; qualified leads reach sales 2-3 days faster; promised payments correlate with actual collection 70-80%.

Goal not yet achieved. Next attempt scheduled within compliance window. Different time-of-day from first attempt to maximize chance of contact (morning try → afternoon try → next-day morning). Maximum total attempts capped per outreach cycle — typically 2-3 calls plus parallel digital channels. Beyond that threshold, the recipient is signaling 'no contact' even without explicit opt-out; respect it.

Persistent no-contact pattern signals what isn't being said: this recipient doesn't want voice contact. Pattern analysis identifies segments with consistent no-answer; those segments shift to digital-only outreach. Recipients who never engage across 6+ outreach cycles get flagged for de-prioritization in calling lists. The discipline is recognizing that recipients vote with their behavior; ignoring that signal is how outbound voice programs become harassment programs without anyone deciding to make them so.