What You Get Instead Of Running ClickSend Yourself

What changes is that candidate history follows the record. Somebody misses out on one role and comes back for the next one, and the whole thread stays in one place, so whichever recruiter picks them up in six months can read what was said.

No. The extension is built in Deluge and runs inside your own Zoho account, using your own Twilio credentials. Message content stays in your SMS History module, and we have no access to it.

Yes. Candidates, client contacts, and accounts are all in scope. That matters because most candidate conversation happens over text rather than email, and this keeps that conversation attached to the candidate record rather than trapped on somebody’s personal phone.

Yes. You connect your own Twilio account and use your own numbers, so carrier charges are billed to you directly at Twilio rates rather than resold through us with a margin on top. It also means your message records sit in your Twilio console under your name, and you can change providers or numbers whenever you want.

Candidates, contacts, and accounts. You text the person on the record, so the conversation belongs to that candidate or client relationship rather than to one application. That keeps the thread readable as somebody applies for one role, misses out, and comes back for the next one.

Yes. Select the records you want and compose the message once. Everybody selected receives it, and each send is logged against that individual record rather than into one shared pile. That is the fastest way to update a whole shortlist when a role is filled or an interview day moves.

In the SMS History module, as a new entry linked to the record that replied. Nobody has to copy anything across or check a separate inbox. Because history is attached to the record itself, any recruiter who picks up that candidate later can read the full exchange without asking around for context.

No. The extension has no phone home capability. It runs inside your Zoho environment and does not transmit your candidate records, phone numbers, or message content to us. We hold no copy of any of it, and there is no vendor side dashboard collecting data in the background. This is the main structural difference between this extension and most alternatives.

Entirely on the Zoho platform, written in Deluge. There is no embedded third party interface, no external web application, and no separate service your data has to travel through. Everything happens inside your own Zoho Recruit deployment, which keeps the data boundary simple to explain to a client running a vendor assessment.

Yes. Dynamic text pulls values straight out of Zoho Recruit and drops them into the message body when it is sent. Candidate name, job title, or interview time can all be used. That means a message going out to forty shortlisted candidates still reads as though it was written for each one individually.

Yes. Templates let recruiters save the messages they send most often and pick one instead of typing it again. Templates work alongside dynamic fields, so a saved message still fills in each candidate’s own details at send time. It removes most of the retyping from interview confirmations, reminders, and follow ups.

The extension detects every phone field on the record rather than assuming a single default. Candidates often have a mobile, a home number, and a work line on file, and all of them are available for you to choose from. That matters when the mobile sits in a custom field rather than the standard one.