Call and text from the candidate record, on your own Twilio account

A recruiter clicks the number on a candidate record and the call connects through your Twilio number. The screen stays on the record, so notes, disposition and next steps are captured during the call rather than reconstructed afterwards from memory and a scribbled name.

Outcomes are logged as structured call dispositions: connected, no answer, voicemail left, wrong number, not interested, call back requested with a date. A wrong-number disposition flags the phone field for correction rather than leaving the same bad number to be dialled by the next recruiter next month.

Caller ID presents your Twilio number, and inbound calls to that number route to the recruiter who owns the record where the number is recognised.

Recording a call is not a global setting. Consent law differs by country and, in the United States, by state, and a handful of states require every party on the call to consent rather than just one.

Surhires follows the posture set out in the compliance matrix: recording and transcription can be restricted by jurisdiction, with a spoken disclosure played before recording begins and per-tenant retention limits. All-party-consent states are handled by disabling recording rather than by assuming consent. That is a deliberately conservative default, and it is the right one for a system that recruiters use at speed without checking a map.

Retention is configurable per tenant, and recordings are deleted on schedule rather than accumulating indefinitely in object storage.

Application-to-person SMS to United States numbers runs over 10DLC, and the carriers require the sending business to be registered. That means a brand registration identifying your company and a campaign registration describing the use case, the message samples and the opt-in flow.

This is your registration, not ours. The compliance matrix is explicit about where the line sits: SMS sending requires your own brand and campaign registration with the carriers, and we provide the fields and the sending integration while the registration remains yours. Registration takes time, it carries carrier fees, and an unregistered number sending recruitment messages will be filtered or blocked rather than delivered.

We would rather tell you this on a marketing page than have you find out in week two of a trial with a campaign that silently stopped delivering.

The same consent machinery that governs WhatsApp and email governs SMS. Opt-in is captured on the candidate record with a timestamp, a channel and the wording used. STOP, UNSUBSCRIBE and the other standard keywords are handled and suppress the number tenant-wide.

Message footers can carry the identification and opt-out language your campaign registration commits to, applied at send time rather than depending on a recruiter remembering. Suppression is checked at send, so a record that opted out five minutes ago does not receive a message that was queued ten minutes ago.

As with every other channel, whether a given campaign is lawful depends on how you configure and send it. The product supports the controls; it does not certify your usage.

The Twilio connection is also one of the supported paths for WhatsApp sending. An agency already running WhatsApp through Twilio, with numbers and templates in place, can keep that arrangement rather than starting a new Meta Cloud API onboarding.

This is the reason the Twilio integration ships alongside the WhatsApp stack rather than after it: send-whatsapp-twilio is live infrastructure, and it is the same credential set. Choosing between Twilio and direct Meta sending is a configuration decision made per tenant, usually on price and on which template library already exists.

It is not a contact centre. There is no predictive dialler, no queue management and no supervisor barge, because those belong to a different product category and a different regulatory conversation.

It also does not carry your carrier registration, your number provisioning or your Twilio bill. Those stay with you by design, and the honest summary is that this integration gives a recruitment desk telephony inside the record rather than replacing a telephony platform.