Xale logo
Xale

Inbound call routing

Inbound call routing: the right counsellor answers, chosen while the phone rings

Your cloud telephony provider asks Xale CRM who should answer while the call is still ringing. A student who already has a counsellor reaches that counsellor. A new number becomes a lead on the spot, and the same automations that share your Meta and website leads choose who picks up. After the call, the log and the recording are on the lead, and a “Call received” trigger is ready for your next rule. Bonvoice has its own preset; any provider that can call a URL works through the Generic one.

Updated · By

Talk to the Xale team
WhatsAppCall +91 90616 63675hello@xale.inBook a demo

Call by call

How inbound call routing works in Xale CRM

Five things happen between the first ring and the note on the lead, and none of them needs a person at a switchboard.

  1. The phone rings, and the provider asks Xale

    Your cloud telephony provider sends Xale the caller's number and the line they dialled while the call is still ringing. Xale answers with whom to connect, in the provider's own shape: JSON, XML or plain text, with the counsellor's number or the provider's own agent id for them.

  2. A known caller reaches their own counsellor

    Xale looks the number up across every lead's phone and WhatsApp number. When the caller is a lead, the person who holds that lead answers, dialled on the profile phone they keep in Xale, so the student who called last week hears the same voice again.

  3. A new caller becomes a lead while the call rings

    An unknown number is created as a lead on the source, through the same path as every other new lead. Your "Lead created" automations choose the counsellor exactly as they do for a Meta or website lead: shared equally or by results, by branch or territory, with anyone checked out passed over. The ringing call waits for that pick, up to a wait you set, and connects to the chosen person.

  4. A number always answers

    The line's own fallback number, then the workspace default, stand behind every decision, so a caller is connected even when the rule finds nobody at that moment. The lead is already in the CRM with its source, ready for the next rule.

  5. After the call, everything lands on the lead

    The provider's post-call report becomes a call log on the lead, credited to the person whose phone answered, with direction, duration and outcome. The recording is copied into Xale's own storage and attached to the lead, an activity entry is written, and a "Call received" trigger lets an automation act on the call.

The counsellor is always the person Xale already knows holds the lead, which is why a follow-up for every role and automations you can rely on matter more here than any menu the provider could play.

Setup

What you set up, on one screen

Everything a provider can differ on is a setting, not a change to Xale: field names, the shape of the answer, who counts as the destination, and what happens when nobody is free.

One screen under Sources

Open Sources, add a Custom source and switch on Call routing. Xale shows the two URLs to paste at your provider: one it calls while a call rings, one it calls after the call.

A preset for Bonvoice, Generic for the rest

Pick Bonvoice and Xale reads its ringing request and post-call report as they arrive. Pick Generic for any provider that can call a URL and type the field names it uses for the caller, the line, the call id and the post-call details, in that provider's own words.

Name the counsellor the way the provider expects

Answer with each person's profile phone, or map users to the provider's own agent ids. Numbers go out as 10 digits or in international format, whichever the provider's sample shows.

Your answer, as a template

Write the found and not-found answers as templates with placeholders such as the destination, the counsellor's name, the lead id and the call id, in JSON, XML or plain text, and Xale sends them byte for byte with the matching content type.

Fallbacks, lead creation and the wait

Set a default number, a fallback per line, whether unknown callers become leads, and how long the ringing call waits for your automation's pick. An optional token on the URLs and extra headers for protected recordings sit under Advanced.

See the decision before the first call

The screen lists the "Lead created" automations that will choose the counsellor for a new caller and the people the provider could not reach yet, and a dry run for any caller number shows the exact answer Xale would send, with both templates rendered on sample values.

The CRM shows calls ringing right now, so an admin can watch a new provider’s first calls arrive. Other ways leads reach Xale, the website webhook, web forms and Send API request, are on the integrations and webhooks page.

Why route from the CRM

What the CRM knows that a dial plan never will

A provider’s own routing sees a number. Xale sees the lead: who holds it, which branch it belongs to, who is at work today and what the last call said.

The owner answers, and keeps their own follow-up

One active person per role holds each lead and each deal, so the routing has one clear answer. Each role keeps its own follow-up with its own reminder, and the counsellor who takes the call sets the next one without leaving the lead.

Follow-up management →

New callers are shared by the same rules as every lead

26 automation actions run on a new caller exactly as on a Meta or website lead: Auto-distribute equally or by results, branch and territory rules, and anyone checked out is passed over. Each run is queued after the save, retried and logged with a plain-English summary.

CRM automation →

Every call on the lead, with its recording

Every counsellor call logged and recorded, two routes. The Xale Android app syncs each call from the counsellor's own phone to the right lead with direction, duration and outcome, no per-minute charges, and attaches the phone's own recording. TeleCMI cloud telephony records calls from a business number on any phone, iPhone included. Routed calls join them as a third route, each one logged on the lead and recorded, and recordings transcribe on demand for calls that mix Malayalam and English.

CRM with call recording →

Access follows the role

a 5-level lead-access dial on every pipeline stage, branch and territory scope, and call recordings stay off for each role until an admin switches them on, so a routed call is heard only by the people allowed to hear it.

Role-based access control →

Calls you can count

Calls are one of the Custom Report Builder's sources, so inbound calls by line, by counsellor, by branch or by hour of day are a report you build yourself, with every cell opening the calls behind it.

Custom Report Builder →

The AI telecaller for the call-back

When the counsellor wants to return a routed call, they can open the Xale AI telecaller on that lead and hand the phone over: it runs the conversation in Malayalam or English, writes the note and the agreed callback, and hands the lead back to its counsellor when the caller asks for a person.

The AI telecaller →

Providers

Bonvoice, and any provider that can call a URL

Bonvoice

A preset that reads Bonvoice’s ringing request and post-call report as they arrive, so the setup is the two URLs and your fallback numbers.

Generic

For any cloud telephony provider that can call a URL while a call rings and again after it ends: type its field names, shape the answer as a template, and dry-run a caller number.

TeleCMI and the Android app

Xale’s other two call routes stay as they are: TeleCMI cloud telephony records calls from a business number on any phone, and the Xale Android app logs and records calls from the counsellor’s own phone. All three land on the lead.

The provider bills the calls as it does today; Xale sells neither minutes nor numbers. Plans are per workspace with every feature on every plan, on the pricing page.

Frequently asked questions

Inbound call routing: common questions

What is inbound call routing in a CRM?

It means the CRM decides who answers an incoming call while the phone is still ringing, instead of the telephony provider working from a fixed list. In Xale CRM the provider sends the caller's number and the dialled line, Xale finds the lead and answers with the counsellor who holds it, and for a new number it creates the lead and lets the workspace's own automations choose the counsellor. After the call, the log and the recording land on the lead.

What happens when a number Xale has never seen calls?

The caller becomes a lead on the call-routing source through the same path as every other new lead, so your "Lead created" automations pick the counsellor: equally or by results, by branch or territory, passing over anyone who is checked out. The ringing call waits for that pick, up to a wait you set, and connects to the chosen person; the line's fallback number or the workspace default answers otherwise, and the lead is already in the CRM for the next rule.

Which cloud telephony providers work with Xale's call routing?

Bonvoice has its own preset, which reads its ringing request and post-call report as they arrive. Any other provider that can call a URL while a call rings and again after it ends works through the Generic preset, where you type the field names the provider uses and shape the answer as a JSON, XML or plain-text template. TeleCMI cloud telephony remains Xale's other cloud route for calls from a business number.

Does the counsellor need a special phone or app to receive routed calls?

No. The provider dials the phone number each person keeps on their Xale profile, or the agent id the provider itself uses for them, so any phone that number rings on will do. The call is logged on the lead from the provider's report, credited to the person whose phone answered, and the recording is copied into Xale's own storage.

How is a routed call recorded and who can hear it?

The provider's post-call report carries the recording link; Xale copies the file into its own storage and attaches it to the lead's call log with direction, duration and outcome. Recordings stay off for each role until an admin switches them on, so the people who can hear a routed call are the people allowed to hear calls on that lead, and recordings transcribe on demand for calls that mix Malayalam and English.

How do I test call routing before pointing a live number at it?

The Call routing screen shows which "Lead created" automations will choose the counsellor for a new caller and which people the provider could not reach yet, and a dry run for any caller number shows the exact answer Xale would send, with both response templates rendered on sample values. Nothing is created and no automation runs during the dry run, so you can rehearse the decision before the first real call.

Let the CRM decide who picks up.

Switch on Call routing under Sources, paste two URLs at your provider, and run a dry call before the first student rings.

Talk to the Xale team
WhatsAppCall +91 90616 63675hello@xale.inBook a demo