Freshdesk SMS
Freshdesk SMS is the highest open rate channel you have and the least forgiving. Text rewards short, transactional support and punishes everything else.
What SMS is genuinely good for
Not general support. Be honest about that up front and the channel works well.
What it's bad at: anything requiring nuance, attachments, formatting or a paragraph of explanation. A 600 character answer split across five texts is a worse experience than an email, and the customer will reply "call me" anyway.
How SMS gets into Freshdesk
Freshdesk isn't a telecoms carrier. Every route involves a provider who owns the number and the delivery, and something that bridges them into tickets.
App names and provider coverage change, so check the current Freshworks marketplace listing and the provider docs for what is supported in your country before you commit.
The threading problem
This is where SMS support quietly falls apart, and it is worth thinking through before day one.
Email has message identifiers and subject lines. SMS has neither. All you get is a phone number, a body, and a timestamp. So the bridge has to decide: does this text belong to an existing ticket, or is it a new one?
Every inbound text is either a reply to something or the start of something, and nothing in the message tells you which.
The usual rule is a time window. A text from a number with an open ticket within, say, 24 hours appends to that ticket. Outside the window, it opens a new one. Pick the window deliberately, because too long merges unrelated conversations into one thread and too short scatters one conversation across five tickets.
Second issue: identity. Your contacts are keyed on email. A text arrives with a phone number and no email, so unless the number is already on a contact record you get a new, thin contact with no history. Populate mobile numbers on your contacts before launching, or plan for a merge step afterwards.
Third: replies to a one-word answer. "Yes" with no context is unreadable in a ticket unless the outbound message is quoted above it. Make sure your bridge writes the outbound text into the conversation too, not just the inbound.
Consent, compliance and the boring bits
SMS is regulated far more tightly than email in most markets, and the penalties are not theoretical.
Get consent recorded before you send anything, and keep the record. Honour STOP and its local equivalents automatically, at the provider level, not through an agent remembering. Respect quiet hours. And know whether your numbers need registration or sender ID approval in the countries you serve, because unregistered traffic gets filtered silently and you'll think the integration is broken.
Costs work differently too. You pay per message, sometimes per segment, with different rates by country and by direction. A long reply that splits into four segments costs four times a short one, which is an unusual incentive for support and worth telling agents about.
Setting expectations on the channel
Customers assume texting is instant. If your team answers texts twice a day, say so in the first automated reply and you avoid a chase.
Two practical guards. Keep SMS in its own group with its own hours, so a text at 11pm doesn't sit against a business hours SLA that implies a reply is coming. And decide what happens when a conversation outgrows the channel: a scripted line offering to continue by email or phone, with the ticket carrying on underneath, works better than an agent typing three paragraphs into a text field.
If you are also running WhatsApp or social messaging, treat them as one design problem rather than three. The WhatsApp and social guide covers the shared patterns, and they're mostly the same patterns.
Frequently asked questions
How does SMS actually connect to Freshdesk?
Through a provider. A Freshdesk Twilio SMS setup is the common route, and any Freshdesk SMS integration turns Freshdesk text messaging into tickets like every other channel. As an SMS support channel Freshdesk handles it best for short transactional exchanges.
Does Freshdesk support SMS natively?
SMS reaches Freshdesk through a marketplace app, the wider Freshworks messaging products, or a custom API integration with a provider. Freshdesk itself is not the carrier. Check the current Freshworks marketplace for what is available in your region.
How do texts thread into tickets?
Usually by phone number plus a time window. A text from a number with a recent open ticket appends to it, otherwise a new ticket opens. Set the window deliberately, because it determines whether conversations merge or scatter.
Do I need customer consent to text them?
In most markets yes, with a recorded opt-in, automatic STOP handling and quiet hour rules. Some countries also require number or sender registration. Check the rules for every country you send to.
What does SMS support cost?
Per message through your provider, often per segment, at rates that vary by country. Long replies split into multiple segments and cost proportionally more, on top of any app or platform fee.
One customer, three channels, three tickets
A text plus an email about the same problem produces two records. Ticket Merger detects the pair and merges them into one thread.
Start free trial14-day free trial. No credit card required.