Skip to content
Back to AI Glossary
AI Definition

Inbound Support AI

"Inbound Support AI is an AI agent that answers incoming calls, chats and messages from customers, resolving routine requests and routing the rest."

In short

What is an Inbound Support AI?

Inbound Support AI is an AI agent that answers incoming calls, chats and messages from customers, resolving routine requests and routing the rest. Related product: Chat Agents.

Reviewed by , Co-Founder · Last reviewed

Deep Dive

Inbound support AI is the agent that picks up when a customer reaches out: the phone line, the website widget, the WhatsApp number, the support inbox. Its job is to resolve what it can and route what it cannot, with enough context that the person who takes over does not start from zero. It differs from a sales or booking agent in who it talks to (existing customers, mostly) and what it is asked (status, how-to, something went wrong).

How it works. The agent identifies the customer where possible (caller ID, email, login) and loads their recent orders, tickets or appointments. It classifies the request and either answers from the knowledge base, runs a tool (track, reschedule, resend, reset) or escalates. On voice, it listens for barge-in and keeps responses short; on chat it can share links and images. Escalation rules are explicit: named topics, low-confidence answers, repeated failure to resolve, or a direct request for a person. The handoff includes the transcript, a summary and the customer record. Outside business hours, escalations go to a callback queue or an on-call route rather than a dead end.

Why it matters for support operations. Inbound volume sets staffing, and most of it arrives in a few predictable intents. Moving those to an agent changes the economics: the team no longer scales with ticket count, after-hours coverage exists, and hold times fall because the agent answers every line at once. Quality is the constraint, so the knowledge base and the escalation list need an owner.

Example. A regional internet provider gets 2,000 calls a month, a third of them "is there an outage in my area." The voice agent checks the outage map by the caller's postcode, reads the estimated restoration time, and offers an SMS update when service returns. Billing questions go to the agent with account lookup; a caller who says the word "cancel" is transferred to retention with the transcript. The human team's call volume drops to the cases that need judgment, and the outage calls stop queuing behind them.

Inbound support AI vs chatbot deflection. Deflection measures how many contacts never reach a person; it can be achieved by a good agent or by an unhelpful one that makes people give up. Inbound support AI is the capability; deflection is one metric for it, and should be read next to resolution rate and satisfaction so you know which kind you have.

What to measure. First contact resolution by the agent, per intent. Escalation rate and the reasons logged. Average handle time on voice. Customer satisfaction split by agent-only and escalated conversations. After-hours share of resolved conversations. Repeat contacts within 7 days on the same issue, which exposes false resolutions.

Botcadence chat agents and voice agents answer inbound requests on website chat, WhatsApp, phone, email and SMS, handing off to a person with the full transcript; see the inbound customer service voice agent.

See Inbound Support AI in a Botcadence agent

Start on the Free plan and configure an agent that uses Inbound Support AI on your own website chat or WhatsApp number. No card needed.

Get Started Free

Website chat live in about 5 minutes

Common Questions

Inbound Support AI FAQs

For status and change requests, yes; without it the agent can only explain policy and take a message. Read access is enough to start; add writes for the specific actions you want it to complete.

Use a short explicit list: named topics (refund disputes, complaints, cancellations), a confidence threshold on retrieval, two failed attempts to resolve, and any request for a person. Log the reason on every escalation.

The knowledge, tools and escalation rules can be shared. Voice needs shorter replies, barge-in handling and a transfer path; chat needs link and image handling. Configure them as two channels on one agent rather than two agents.

It should take a callback request with the issue summarized, create the ticket, and give the customer a reference number. Transfers only make sense to a destination that is staffed.

Ask AI about this page