How to set up Zendesk SMS follow-up: A complete guide for 2026

Stevia Putri
Written by

Stevia Putri

Reviewed by

Stanley Nicholas

Last edited March 5, 2026

Expert Verified

Banner image for How to set up Zendesk SMS follow-up: A complete guide for 2026

SMS has a 98% open rate compared to email's 20%. For support teams, that means your follow-up messages actually get seen. If you're using Zendesk and want to add SMS capabilities, you have several options ranging from native features to third-party integrations.

This guide covers everything you need to know about setting up Zendesk SMS follow-up: native capabilities, automation triggers, third-party alternatives, compliance requirements, and how AI can enhance your SMS workflows.

Let's break it down.

With a 98 percent open rate, SMS ensures your support follow-ups are actually seen compared to traditional email.
With a 98 percent open rate, SMS ensures your support follow-ups are actually seen compared to traditional email.

Understanding Zendesk's native SMS capabilities

What is Zendesk Text?

Zendesk offers SMS functionality through Zendesk Talk/Text, which is integrated directly into the Zendesk Suite. It's available on all Suite plans (Team, Growth, Professional, and Enterprise), though you'll need Talk Team, Professional, or Enterprise as an add-on.

Zendesk landing page showing the customer service platform interface
Zendesk landing page showing the customer service platform interface

The native SMS feature supports both inbound and outbound messaging. Customers can text your support number directly, and agents can respond from within the Zendesk interface. It handles the basics well: two-way conversations, ticket creation from texts, and standard routing.

Here's the short version: Zendesk Text works if you need straightforward SMS support without complex requirements. But it's an add-on, not a core feature, which means additional costs on top of your base Zendesk subscription.

Setting up text numbers

To get started with Zendesk SMS, you'll need to add a text number in the Admin Center. You can either use a new number provided by Zendesk or text-enable an existing landline in supported countries.

The setup process involves:

  • Navigating to Admin Center > Channels > Talk
  • Adding a text number or enabling SMS on an existing voice number
  • Configuring routing rules for incoming texts
  • Setting up business hours and auto-responses

A communication platform's interface for choosing and configuring a new phone number, showing available local numbers with call and text capabilities.
A communication platform's interface for choosing and configuring a new phone number, showing available local numbers with call and text capabilities.

Important: If you're operating in the US, you'll need to complete A2P 10DLC registration before sending business texts. This is a carrier requirement, not optional. The registration process involves submitting your business details and use case to The Campaign Registry.

Automating Zendesk SMS follow-up with triggers

How triggers work for SMS

Zendesk's trigger system lets you automate SMS notifications based on ticket events. You can set up rules that automatically text customers when specific conditions are met.

The key components are:

  • Conditions: Ticket > Channel | Is | Text (to target SMS tickets specifically)
  • Actions: Notify by > Group text or Notify by > User text

Common use cases for SMS triggers include:

  • Sending status updates when a ticket changes status
  • Notifying customers when their issue is resolved
  • Proactive outreach for appointment reminders or delivery updates
  • Escalation alerts for urgent issues

Setting up a basic trigger looks like this: create a condition that checks if the ticket channel is "Text," then add an action to notify the requester by text when the ticket status changes to "Solved."

Important limitations

Before you build your entire workflow around Zendesk SMS triggers, know the constraints:

  • Spam threshold: Approximately 250 notifications per day before Zendesk's spam detection kicks in
  • Character limit: 1,600 characters per message (longer messages get truncated)
  • User requirement: The end-user must already exist in your Zendesk system
  • A2P 10DLC: Mandatory registration for US messaging

The user requirement is particularly limiting for proactive outreach. You cannot send SMS to phone numbers that aren't already associated with existing Zendesk users. This makes cold outreach or pre-appointment reminders difficult if the customer hasn't contacted you first.

Bottom line? Zendesk's native SMS works for reactive support but struggles with proactive follow-up workflows.

Third-party SMS integrations for Zendesk

When native features fall short, third-party integrations fill the gaps. Here are the main options worth considering.

When to consider alternatives

You should look beyond native Zendesk SMS if you need:

  • Multi-channel messaging (combining SMS with WhatsApp, Facebook Messenger)
  • Higher volume than ~250 messages per day
  • Advanced automation beyond basic triggers
  • Proactive outbound messaging to non-existing contacts
  • Better analytics and reporting on SMS performance

Decision flowchart for choosing between native Zendesk SMS and third-party integrations
Decision flowchart for choosing between native Zendesk SMS and third-party integrations

Textline

Textline is a business texting platform with a native Zendesk integration. It connects via webhooks, allowing you to send texts directly from Zendesk triggers.

Textline business texting platform landing page
Textline business texting platform landing page

Key features:

  • Webhook-based integration with Zendesk Support and Sell
  • Unified inbox for SMS and social media messages
  • CSAT and NPS surveys via text
  • Time-based and event-based automations
  • HIPAA compliance available

Textline uses a message credit system rather than per-seat pricing. Plans include Essentials, Pro, and Enterprise tiers, with message credits starting at 600 per month on the Essentials plan. Additional credits cost $0.03 each.

The Zendesk integration works by setting up webhook actions in your triggers. When conditions are met, Zendesk sends a webhook to Textline, which then delivers the SMS. It's a bit technical to set up but provides more flexibility than native SMS.

Heymarket

Heymarket takes a different approach with a shared inbox widget that embeds directly within Zendesk. Instead of switching between platforms, agents can manage SMS conversations without leaving Zendesk.

Heymarket shared inbox platform for team messaging
Heymarket shared inbox platform for team messaging

Key features:

  • Embedded widget within the Zendesk interface
  • Multi-channel support (SMS, WhatsApp, Facebook, Instagram, Apple Messages)
  • AI assistance for message translation and sentiment analysis
  • Campaign and list broadcast capabilities
  • Team-based conversation management

Heymarket's pricing is per-user, starting at $20 per user per month (billed annually) for the Standard plan. The Plus plan at $41 per user adds campaigns, automations, and AI features. Pro at $62 per user includes API access and advanced security.

The integration syncs conversations between platforms bidirectionally. When a customer texts your Heymarket number, it creates a ticket in Zendesk. When an agent responds in Zendesk, it sends via Heymarket.

Clerk Chat

Clerk Chat focuses on AI-powered messaging with Zendesk integration. It's particularly strong for bulk messaging and Microsoft Teams integration.

Key features:

  • AI agents for automated responses
  • Bulk messaging to multiple customers
  • Landline SMS enablement (use your existing business number)
  • Native Microsoft Teams integration
  • Multi-channel support (SMS, WhatsApp, RCS, Voice)

Clerk Chat uses a unique per-conversation pricing model at $1 per conversation (defined as 24 hours of unlimited calls and messages with a contact). This can be cost-effective for high-volume, short interactions but adds up for ongoing conversations.

The Zendesk integration syncs conversations and can create tickets automatically. It's a good fit if you're already using Microsoft Teams and want SMS capabilities within that ecosystem.

Compliance and best practices

A2P 10DLC registration

A2P 10DLC (Application-to-Person 10-Digit Long Code) is mandatory for business texting in the United States. Carriers require registration to reduce spam and improve message deliverability.

Following these registration steps is essential for US-based businesses to maintain high deliverability and avoid carrier filtering.
Following these registration steps is essential for US-based businesses to maintain high deliverability and avoid carrier filtering.

The registration process involves:

  • Registering your business with The Campaign Registry
  • Providing your business address and use case details
  • Paying a $15 monthly campaign fee for 10DLC numbers
  • Waiting for carrier approval (typically a few business days)

Without registration, your messages may be blocked or heavily filtered. This applies regardless of which SMS solution you choose.

Opt-in and opt-out requirements

Legal compliance for SMS goes beyond registration. You must:

  • Obtain explicit consent before texting customers
  • Maintain records of opt-in consent
  • Automatically process STOP keywords to unsubscribe
  • Include your business name in messages
  • Send only during reasonable hours (typically 8 AM to 9 PM local time)

The Telephone Consumer Protection Act (TCPA) governs business texting in the US. Violations can result in fines ranging from $500 to $1,500 per message.

SMS follow-up best practices

Beyond legal requirements, follow these guidelines for effective SMS support:

  • Keep it concise: SMS is not the channel for lengthy explanations
  • Identify yourself: Always include your business name
  • Provide value: Every message should serve a clear purpose
  • Time appropriately: Respect time zones and business hours
  • Make opting out easy: Include instructions or auto-process STOP
  • Use it strategically: SMS works best for urgent updates, not routine communication

Enhancing follow-up with AI automation

Limitations of basic SMS triggers

Zendesk's native triggers are rules-based. They work on simple if/then logic: if the ticket status changes, then send a text. They cannot:

  • Understand the content or context of a message
  • Personalize responses based on ticket history
  • Make intelligent routing decisions
  • Learn from past interactions

This is where AI-powered solutions become valuable.

How eesel AI improves SMS follow-up

eesel AI works alongside Zendesk SMS or third-party integrations to add intelligence to your follow-up workflows. Instead of rigid triggers, you get AI that understands context.

eesel AI dashboard for configuring AI agents with a no-code interface
eesel AI dashboard for configuring AI agents with a no-code interface

Here's what that means in practice:

AI-powered responses: eesel AI trains on your knowledge base, past tickets, and help center articles. When a customer texts, it can draft responses grounded in your actual documentation, not generic templates.

Smart triage before SMS: Rather than sending the same SMS to every customer, eesel AI can analyze tickets first and route them appropriately. Urgent issues get escalated immediately; routine requests get automated responses.

Workflow comparing basic Zendesk AI automation with advanced ticket triage capabilities
Workflow comparing basic Zendesk AI automation with advanced ticket triage capabilities

Context-aware escalation: The AI learns when to involve humans. It can recognize complex issues that need personal attention and escalate those while handling straightforward requests autonomously.

Continuous improvement: Unlike static triggers, eesel AI learns from corrections. When agents edit AI-drafted responses, the system incorporates that feedback for future interactions.

Pricing: eesel AI starts at $239 per month (billed annually) for the Team plan, which includes up to 3 bots and 1,000 interactions. The Business plan at $639 per month adds AI Agent capabilities, unlimited bots, and 3,000 interactions.

The integration with Zendesk allows you to run simulations on past tickets before going live. You can see exactly how the AI would respond and measure resolution rates before touching real customers.

Choosing the right SMS approach for your team

Decision framework

The right solution depends on your specific needs:

ScenarioRecommended SolutionWhy
Small team, basic needsNative Zendesk TextSimple setup, no additional vendors
Multi-channel requirementsHeymarketWhatsApp, Facebook, Instagram in one place
High-volume automationTextlineWebhook flexibility, credit-based pricing
Intelligent automationeesel AI + SMSContext-aware responses and routing

Getting started with Zendesk SMS

If you're just beginning with SMS support, here's a practical path:

  1. Start with native features: Test Zendesk Text on a small scale to understand your volume and use cases
  2. Monitor delivery rates: Track which messages get through and which get filtered
  3. Gather feedback: Ask customers if SMS is helpful or intrusive
  4. Scale intentionally: Move to third-party tools only when you hit native limitations
  5. Consider AI enhancement: Add intelligent automation once you have established workflows

SMS is a powerful channel when used correctly. The key is matching the solution to your actual needs rather than defaulting to the most feature-rich option.

Frequently Asked Questions

Native Zendesk SMS requires the end-user to already exist in your system. For proactive outreach to new contacts, you'll need a third-party integration like Textline or Heymarket that supports outbound messaging to new numbers.
Zendesk Text is an add-on to Suite plans, which start at $55 per agent per month. Third-party options vary: Heymarket starts at $20 per user per month, Textline uses message credits starting at $0.03 per message, and Clerk Chat charges $1 per conversation.
Yes, if you're sending business SMS in the United States, A2P 10DLC registration is mandatory regardless of which platform you use. This applies to native Zendesk SMS and all third-party integrations.
Yes, Zendesk's native triggers allow basic SMS automation without code. For more advanced workflows, third-party tools like Heymarket provide visual automation builders. eesel AI adds intelligent automation that learns from your existing tickets.
Native Zendesk SMS has a spam threshold of approximately 250 notifications per day. Third-party integrations typically have higher limits, though exact numbers vary by provider and plan.
All SMS solutions, including Zendesk and third-party integrations, must automatically process STOP keywords to unsubscribe recipients. This is a legal requirement under TCPA regulations.

Share this post

Stevia undefined

Article by

Stevia Putri

Stevia Putri is a marketing generalist at eesel AI, where she helps turn powerful AI tools into stories that resonate. She’s driven by curiosity, clarity, and the human side of technology.