Intent detection and routing in conversational banking
Intent detection decides what a customer wants; routing sends it to the right capability. Here is how both work in a conversational banking system.
Aug 18, 2026 · 2 min read · By The TwelveAI Team
A conversational banking system can do dozens of things: transfers, airtime, bills, swaps, card controls, savings, support. On every message it has to answer one question first: what does this customer actually want, and who should handle it? That is intent detection and routing.
Detection: what does this mean?
Intent detection classifies the request into an actionable category. "Move 200 dollars to naira" is an FX swap. "My card was declined" is support. "Send 5k to Ada" is a transfer. Strong detection copes with vague, multi-part, and follow-up messages, not just textbook phrasing, building on solid natural-language understanding.
Routing: who handles it?
Once intent is known, routing sends the request to the right capability, the payments logic, the FX logic, the cards logic, or a support agent. In a multi-agent setup, routing also decides when to hand off between specialists mid-conversation without losing context.
The hard cases
Routing quality is defined by the edge cases:
- Multi-intent messages. "Check my balance and send 10k to my landlord" is two actions in one sentence.
- Mid-flow switches. A customer starts a transfer, then asks "wait, what is my balance first?" The system should answer, then resume.
- Near-misses. "Fund my card" (a card top-up) versus "create a card" (issuing) look similar and route very differently.
Getting these right is what makes a conversational banking product feel intelligent rather than brittle.
Confidence and fallbacks
Good routing knows when it is unsure. Below a confidence threshold, the system should ask a clarifying question or escalate to a human rather than execute the wrong action. In banking, "I am not sure, let me confirm" is a feature, not a failure.
Why it belongs in infrastructure
Detection and routing are not one-off code; they need tuning, evaluation, and guardrails as your product grows. That is why they live in the conversational banking stack rather than being reinvented per feature.
TwelveAI handles intent detection and routing so your team adds capabilities, not classifiers. Explore the platform.