Indian cloud telephony for high-volume recruiting desks

Voice runs through Twilio, which is live. You connect your own Twilio account with your own credentials, buy your own numbers, and Surhires provides click-to-call from the candidate record, structured call dispositions, activity logging and jurisdiction-aware recording controls.

For an Indian desk, Twilio delivers and the numbers are available, though local number economics, regional DID coverage and existing commercial relationships are the exact reasons a firm might prefer Exotel. That is a real preference, and it is why the item is on the roadmap rather than dismissed.

Where the desk's primary channel is WhatsApp rather than voice, the live stack already covers screening, availability collection, document requests and interview reminders without any telephony at all.

The scope, when it is built, follows the same shape as the Twilio integration rather than inventing a new one. Click-to-call from a candidate or client record with the record on screen. Inbound routing to the recruiter who owns the matching record. Call outcomes recorded as structured dispositions rather than free-text notes.

IVR is the piece that is genuinely different. A high-volume Indian desk running mass outreach frequently wants an inbound number that greets a returning candidate, identifies them against the database and routes to the right recruiter or the right requisition queue. That is a telephony capability rather than a CRM one, and it is the main reason a firm names Exotel specifically.

Call recording would follow the same posture as everywhere else in the product: restricted by jurisdiction, with a spoken disclosure played before recording begins and per-tenant retention limits.

Volume changes the design. A US contingent desk making forty calls a day and an Indian bulk-hiring desk making four hundred are not the same operation, and the second one needs answer-rate management, call outcome coding at speed and an inbound path that does not depend on a recruiter picking up.

It also changes the economics. At that volume, the per-minute rate and the local number cost stop being a rounding error and start being a line item worth negotiating, which is precisely why a firm already has a provider relationship and wants the CRM to fit it rather than the other way round.

The general principle on this site is that telephony accounts belong to the customer. Whichever provider ships, that principle does not change.

There is a reporting consequence too. At four hundred calls a day, the difference between a coded disposition and a free-text note is the difference between knowing that a particular requisition has a fifteen percent connect rate and guessing at it. Whatever provider carries the call, the outcome has to land on the record as structured data, because that is what the recruiter performance dashboard and the source attribution reporting are computed from.

An item moves from roadmap to in development when it is actually being built, and from in development to live when it ships, at which point the page carries an evidence line naming the functions or files that carry the capability. The WhatsApp and Twilio pages carry those lines today; this one does not, and that absence is the honest signal.

Customer demand moves the order. If Indian desks on the product tell us that Exotel specifically is blocking them, that is the strongest input there is. Telling us is more useful than waiting for it to appear.

We will not put an Exotel logo on the integrations page, list it in a directory of connected tools, or let a sales conversation imply that a connector exists. There is no partnership, no certification and no commercial relationship to imply.

We will also not build a thin pass-through and call it an integration. A click-to-call button that does not write a disposition, does not log to the activity stream and does not respect recording rules is a demo, not a capability, and shipping one would make this page dishonest in a subtler way than leaving it on the roadmap.