Pilot ready Template ready inbound

Inbound line (answering)

Main or after-hours number: company info, hours, take a message, callback ticket. Same agent stack.

inbound_line_answering

One of our most popular starters—not the only shape we support. For production, we customize the agent (open, intents, tools, guardrails, CRM hooks) to your exact specifications.

Sample open

Thank you for calling. This is an AI assistant for our team. I can share hours and location, take a message, or connect you for a callback. How can I help?

Identity required: yes
AI disclosure: yes
Paid-for-by flag: no

Lawful basis tags

{
  "type": "CONSENT_PEC",
  "consentArtifactRequired": false,
  "notes": "Inbound: caller initiates. Pre-dial outbound gate does not apply. Configure AI + recording disclosure; customer owns sector rules."
}

Agent

{
  "intentsAllowed": [
    "business_hours",
    "location_parking",
    "services_overview",
    "take_message",
    "request_callback"
  ],
  "intentsBlocked": [
    "medical_advice",
    "legal_advice",
    "quote_guarantees",
    "impersonate_staff"
  ],
  "tools": [
    "leave_message",
    "escalate_human",
    "end_call"
  ]
}

Destinations & frequency

Classes: wireless, residential_landline, other

Purpose: inbound_answering · Default enabled on seed: no (enable in Campaigns)

{}

Customize to your program

Opens, disclosures, intents, tools, CRM fields, and escalation rules are configured to your scripts and ops process. If your use case isn’t listed, we still build it—starters are shortcuts, not a ceiling.

→ Inbound number and knowledge snippets (hours, address, FAQs)
→ leave_message → notes + escalation ticket for staff
→ Recording disclosure policy by jurisdiction
→ You own lists/consent (outbound) or knowledge + recording policy (inbound)

Open campaigns Start a pilot Product