The Managed Way To Replace ClickSend

What changes is that no data phones home to a vendor. We hold no copy and run no dashboard on our side. There is nothing for us to lose in a breach and nothing for you to ask us to delete, because we were never holding it.

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.

Contacts and accounts. You text the people on the record rather than a document, which means the conversation belongs to the customer relationship rather than to one invoice or one estimate. That keeps the thread readable as documents come and go over the life of the account.

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. Bulk sending to a saved list or view is also supported, which is easier when the same group gets messaged on a regular basis.

In the SMS History module, as a new entry linked to the record that replied. You do not have to copy anything across or check a separate inbox. Because history is attached to the record itself, anyone who picks up that account 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 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 Books deployment, which keeps the data boundary simple to explain to a security reviewer or an auditor.

Yes. Dynamic text pulls values straight out of Zoho Books and drops them into the message body when it is sent. Customer name, invoice number, amount, or due date can all be used. That means a reminder going out to two hundred accounts still reads as though it was written for each one individually.

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

The extension detects every phone field on the record rather than assuming a single default. If a contact has ten numbers on file, all of them are available and you choose which ones to text. That matters for records where the mobile number sits in a custom field rather than the standard one.

Yes. Compose the message now and set the date and time it should go out. The send happens at the moment you chose rather than the moment you were at your desk, which is useful for time zones, business hours, and anything that needs to land on a particular day such as the morning a payment falls due.