Twilio SMS for Zoho Desk

What the Extension Does in Zoho Desk

Picture a customer who texts your agent about a late delivery. The agent answers from a phone, the customer replies, and later someone types a summary into a note. Twilio SMS for Zoho Desk cuts out that last step. The text conversation sits on the customer record in your Zoho Desk, where the rest of the team already works.

Zoho Desk can send SMS notifications on its own, but a notification is a one-way street. A reply has nowhere useful to go. This extension catches the reply and logs it against the record. It also lets an agent text a whole group at once instead of firing notifications one by one.

You Text People, Not Tickets

You send from a Contact or an Account. You do not send from a ticket. That choice shapes the rest of the extension, and it is the first thing a ticketing-minded team trips over. The thread belongs to the customer, not to one case.

Say a ticket closes in March and a new one opens in May. The texts from both are still on the same Contact. The agent who picks up the May ticket reads the March exchange without opening a closed case or asking a colleague. Fewer customers end up explaining their history twice.

There is a cost. A text is not a ticket event, so if every message must sit inside one case timeline, this is the wrong shape. The section on what it is not says so plainly.

Where It Runs

The code runs inside your own Zoho account. It is written in Deluge, Zoho's native scripting language, so no embedded web app is involved and no outside service keeps a copy of your contacts. If you want the longer story, we wrote up what Deluge is and how it fails quietly.

You bring your own Twilio account. The numbers are yours, and you pay the rates Twilio publishes with no markup from us. The architecture is the same across the whole extension family, so the data path and permission model are written out once, in the Twilio SMS for Zoho CRM documentation. Everything there applies to Desk too.

Sending to One Person, Several, or a Defined List

Most of a day is one-to-one. An agent opens a Contact, or searches for one, and sends a single message.

Bulk send to selected records is the feature Desk teams reach for first. Filter a list down to the people affected, select them, and send the same message to all of them. That is how an outage update looks when someone has thought about it in advance.

Send to a specific list is the careful variant. You point at a defined list rather than whatever is highlighted on screen, so the audience can be repeated and checked before anything leaves. Support sends often happen under pressure, which is when a mis-selected filter does the most damage.

Composing Without Retyping

Dynamic text fills in values from the Desk record: a name, an account, a reference, a date. Nobody copies them by hand, and copying by hand is where mistakes creep in during a busy hour.

Reusable templates keep the wording steady across agents who write nothing alike. Customers judge a company partly by its tone, so a consistent voice is worth having on a support desk.

Scheduled delivery holds a message until the time you choose. Two uses come up constantly on a desk. A maintenance notice should arrive the evening before the work, not during it. And a customer several time zones away should not be woken by a message simply because your engineers were awake. Neither works if sending depends on someone being at a keyboard at the right minute.

Numbers, and Which One You Appear to Be

Support records tend to carry several phone numbers. An Account might list a main switchboard while the Contact has a direct mobile. A text to a switchboard fails silently: no bounce, no error, only nobody answering. Automatic phone field detection lists the number fields the record really holds, so the agent picks one on purpose instead of taking whichever came first.

You also pick which of your Twilio numbers a message goes out from. On a desk that matters more than it seems, because the number you text from is the number the customer will text back the next time something breaks. Use one the team actually watches.

History That Survives the Ticket

Every message is logged against the record, outbound and inbound alike. Inbound replies are filed automatically, so the history does not depend on someone remembering to paste it in. Because the log hangs off the Contact or Account and not a single ticket, it reads as a relationship history, not a case attachment.

Tickets are episodes and customers are not. Anything attached only to an episode vanishes from view when the episode closes, often just before it would have been useful.

Where Support Teams Use It

Telling Everybody at Once That Something Is Broken

An incident starts and the queue fills with people asking the same question. Email lands next to everything else vying for attention. A text stands out.

Filter Contacts down to the affected accounts, select them, and send one message that carries each account name from a field instead of a generic apology. Replies land on the records, so follow-up questions stay attached to the customers who asked them and do not pool in a shared inbox that someone sorts out afterward.

Build that filter before you need it. Nobody writes a good one late at night with the queue climbing.

Cutting First Response Time on Urgent Tickets

First response time is the number most desks are measured on. When it slips, the cause is usually the channel, not effort: a customer with an urgent problem is not watching their inbox for your reply.

A short text that acknowledges the ticket and names who owns it can serve as that first response. The customer's answer comes back to the record, not to an agent's personal phone. Firing that text automatically, without an agent clicking, is automation work and not a feature of the extension.

Scheduled Work and Field Visits

Anything with a time on it fits here: an engineer visit, a maintenance window, a callback someone promised. Scheduled delivery sends the reminder the evening before whether or not anyone is at a desk, and the date comes from the field, not from an agent reading a screen and retyping it.

If the customer replies to move the appointment, that reply is on their record. Whoever handles it sees the original arrangement without asking what was agreed.

Chasing the One Thing You Cannot Close the Ticket Without

Plenty of open tickets wait on the customer for something small: a serial number, a screenshot, confirmation that they tried the step you suggested. A text puts that request where the customer is already looking.

The answer returns to the record, and the ticket moves without anyone copying text between windows.

Checking Whether the Fix Held

The moment after a ticket closes is the cheapest time to ask if the fix worked. Few teams do, since it usually means one more email nobody opens. A single line by text a few days later is easy to answer.

History sits on the Contact, so the answer stays findable after the case is gone. It is also a gentle way to catch the repair that never really took, the kind that returns as a far angrier ticket.

Support Teams Working Under Strict Data Rules

A support desk holds sensitive detail: account numbers, site addresses, often the reason someone is upset. If your obligations say that detail stays in systems you control, an SMS platform that keeps its own copy of your contact list is ruled out before the demo. This extension runs inside your Zoho organization and talks to Twilio with your credentials, so nothing is copied elsewhere for texting to work.

An administrator can check that for themselves. The Deluge is readable and the endpoints it calls are visible. No third party has standing access to your data, so no third party's breach becomes your notification duty.

Teams Running Support Alongside the Rest of Zoho

Support seldom stands alone. If billing questions go to Zoho Books or subscription questions to Zoho Billing, the same extension exists for those apps and texting behaves the same way as the customer moves between them.

Teams already on Zoho One get something that behaves like the rest of the stack, not a tool that bolts on from outside and calls it an integration.

What You Need First, and What It Does Not Do

What You Need Before You Install

Two things: a Zoho Desk account, and a Twilio account of your own with at least one number that can send SMS to the countries you text. That is the whole list. No developer is needed and nothing is hosted for you to maintain.

Pricing is a flat organization price, not per agent. On a desk that matters. Per-seat pricing on a communication tool nudges you to give fewer agents access, and a channel only half the team can use confuses customers, who cannot tell which half they reached.

Installing, and the Step People Skip

Install from the Zoho Marketplace into the organization you actually use, signed in as an administrator. Then connect Twilio with your own Account SID and Auth Token and choose which numbers agents may send from. The step-by-step setup lives in the CRM documentation and is identical here, except that you test on a Contact.

The step people skip is the round trip. Seeing a message leave is easy to mistake for a working setup. The failure that actually bites is a reply that reaches Twilio and never reaches the record. Put a colleague's mobile number on a test Contact, send one message, and have them reply from the handset. Two minutes, and it is the only test that covers the half of the product you bought it for.

The Twilio Side, and Who Owns What

Since the Twilio account is yours, several jobs are yours too. You buy and provision numbers. You watch your own balance. You deal with Twilio directly if a carrier starts filtering your traffic. And you complete carrier registration wherever the country you text requires it.

In the United States that means A2P 10DLC, and it is not optional. Registration has two parts: a Brand that says who is sending, and a Campaign that says what you send and how people opt in, opt out, and ask for help. Both are created in the Twilio Console. The Brand type you qualify for sets a daily ceiling, quoted against T-Mobile because that carrier limits first. Unregistered traffic is filtered and also charged extra, so waiting costs money as well as deliverability.

Twilio owns these rules and revises them. Read the Twilio A2P 10DLC overview rather than any summary, ours included. We also wrote up the parts of registration that catch people out. Skipping it is the most common reason a new setup works in testing and delivers badly at volume, so finish it before you promise anyone a launch date.

Consent and the Service Message Exemption That Is Not One

Many support teams assume service messages sit outside consent rules. Not in the way they mean. You still need a basis for texting someone. You still must honor an opt out at once. And you still cannot let marketing slide into a service thread because the number is already there.

In practice: record consent on the record, treat a STOP reply as final, and keep service messages recognizably about service. Every message is logged on the Contact, so if anyone asks what was sent and when, you can show them. Teams texting from personal phones cannot.

Before You Switch It On for the Whole Team

Two decisions are far cheaper now than later. The first is which numbers agents can send from. If every agent can use every number, the experience turns inconsistent and a support thread looks no different from a sales one. Assign numbers to teams before anyone starts, not after a month of habit.

The second is the template set. A desk under load grabs the nearest template, so whatever you ship on day one is what customers receive for the next year. Write the four or five that cover most traffic. Ask someone who does not work the desk to read them aloud. Delete the rest so nobody picks one by accident.

Agree, too, on what never goes by text: anything the customer needs to forward as a record, anything with an attachment, and anything you would not want screenshotted. SMS suits short and urgent messages and does poorly at what a long email does well. Settling this up front beats working it out one message at a time.

When Messages Do Not Arrive

On a desk this usually comes up after a bulk send where part of the batch landed and part did not. That pattern points at the records. A phone field that is empty or badly formatted explains it best, and phone field detection shows which records are missing one. If nothing landed, look at the account: carrier registration may be incomplete, which shows as messages that send but never deliver, or the Twilio balance may have run out, which stops everything at once.

For a single customer, the Twilio message logs name the cause. A delivered status clears the message itself. An undelivered status carries an error code worth reading rather than guessing at. Two answers turn up most. One is a landline or VoIP number that cannot receive SMS, which is what an office number typed into a mobile field looks like to the carrier. The other is a customer who replied STOP at some point. Opt outs are honored upstream, so everything sent afterward disappears without an error anyone on the desk sees.

A third pattern: messages send fine but never show on the record. When one agent complains and everyone else is fine, the answer is permissions, not messaging. The extension inherits Zoho permissions, so an agent who cannot edit a Contact cannot write history to it. Compare the two agents' profiles before looking anywhere else.

What It Is Not

It is not an omnichannel inbox. Messages attach to Contacts and Accounts, not tickets, so an inbound text does not open a ticket, update one, or stop a response clock. If you want SMS as a first-class Desk channel with its own queue and targets, this is the wrong shape, and it is cheaper to learn that now than three weeks into a rollout.

It is not a marketing platform. There is no campaign builder, no drip sequences, and no attribution reporting.

It does not resell messaging either. Twilio bills you directly at Twilio rates. That is kinder to your budget and less kind on the day finance asks why support has a second vendor. Decide it knowingly, not at the first invoice.

The Rest of the Family

The same extension exists for Zoho CRM, Zoho Books, Zoho Billing, Zoho Projects, and Zoho Recruit. The architecture is identical in each. Only the record you text from and the job you are doing change.

Where to Go Next

The full feature list, how the cost works, and the questions people ask before buying are on the Twilio SMS for Zoho Desk product page.