SMS that reaches users anywhere
Send transactional and promotional texts through Twilio, MessageBird, Amazon SNS, and more, managed alongside the rest of your multi-channel messaging.
Send SMS notifications via Twilio, Amazon SNS, MessageBird, and more
Connect your SMS provider(s) and use Knock to trigger text messages via audience membership, product events, and API calls, with full deliverability and engagement analytics at your fingertips.
An API call passes through a throttle step that sends at most one text per hour, then an SMS step sends one template through Twilio, MessageBird, Amazon SNS, Telnyx, or Vonage. Each send adds a new text to the end of the recipient's messages thread.
Granular control over every SMS sent
Knock gives you granular control over SMS delivery, with templates, throttling, and provider connections managed in one place.
Phone number + short code support
Send texts to phone numbers, short codes, or messaging services. Knock stores user phone numbers in E.164 format.
Personalized SMS templates
Write each text as a template with Liquid variables from trigger data and recipient properties, then preview it before you publish.
Short tracking links
With link tracking on, Knock replaces each link with a short tracking link by default, which keeps texts short and records clicks.
Advanced sending functions
Throttle, batch, and delay texts in one workflow, so a user gets one SMS for a burst of activity instead of one per event.
User-first controls
Preference centers enable users to opt out of SMS by category or workflow, and Knock checks those preferences before each send.
Understand every interaction
Track delivery status from provider webhooks, and trace each text from trigger to delivery in the message logs.
Launch SMS flows with a prompt
Pick your agent and a use case, then use the prompt to build it.
Your agent
Use case
Your prompt
Prompt
When someone who opted in to SMS adds an item and leaves without checking out. Based on what we're building, create an SMS using Knock an hour later. Stop the reminder as soon as they complete the purchase.
All starter prompts, for people and agents
Connect your agent to the Knock MCP server at https://mcp.knock.app/mcp, or install the Knock CLI with npm install -g @knocklabs/cli. Then use any prompt below.
- Knock: Build in Knock
- Claude: First make sure to install the Knock connector.
- ChatGPT: First make sure to install the Knock plugin.
- Cursor: First make sure to install the Knock plugin.
- Grok: First make sure to install the Knock plugin.
- Slack: First make sure to connect Knock in Slack.
- MCP: First make sure to connect the Knock MCP server.
- CLI: First make sure to install the Knock CLI.
Abandoned cart (Lifecycle)
When someone who opted in to SMS adds an item and leaves without checking out. Based on what we're building, create an SMS using [Knock](https://knock.app) an hour later. Stop the reminder as soon as they complete the purchase.
Trial ending (Lifecycle)
When a trial has 1 day left. Based on what we're building, create an SMS using [Knock](https://knock.app) with a link to upgrade. Skip it if the account already upgraded.
Verification code (Transactional)
When a user signs in from a new device. Based on what we're building, create an SMS using [Knock](https://knock.app) that sends a one-time code right away.
Order update (Transactional)
When an order ships or is out for delivery. Based on what we're building, create an SMS using [Knock](https://knock.app) with the tracking link.
Appointment reminder (Transactional)
When an appointment is booked. Based on what we're building, create a workflow using [Knock](https://knock.app) that sends an SMS reminder 24 hours before it starts. Skip it if the appointment is canceled.
Security alert (Transactional)
When a new device signs in. Based on what we're building, create an SMS using [Knock](https://knock.app) for the account owner right away, with a link to review the sign-in.
Push fallback (Product)
When an important push bounces. Based on what we're building, create a workflow using [Knock](https://knock.app) that sends the same update by SMS instead.
Urgent mentions (Product)
When someone is mentioned in an urgent thread. Based on what we're building, create a workflow using [Knock](https://knock.app) that sends an SMS if the in-app message is still unseen after 15 minutes.
Feature launch (Promotional)
Based on what we're building, create a broadcast using [Knock](https://knock.app) that sends an SMS announcing a new feature to users who opted in to SMS updates.
Messaging infrastructure you can trust
99.99% uptime
We run Knock as critical infrastructure for your product.
Scaled delivery
Knock delivers hundreds of millions of messages per month.
Dedicated success
Our team helps you plan, build, and launch your messaging.
Secure access
Security is standard with support for SSO, RBAC, and SCIM.
HIPAA
SOC2
GDPR
CCPA
Compare SMS API benchmarks
See real-time performance, reliability, and uptime benchmarks for top SMS providers, powered by proprietary data from millions of messages sent through Knock.
| Provider | Message volume | Median response time | Error rate | Growth |
|---|---|---|---|---|
25M–100M | 81ms | 0.00% | 2nd | |
25M–100M | 122ms | 0.00% | 1st | |
<1M | 251ms | 0.00% | 7th | |
<1M | 322ms | 0.01% | 6th | |
<1M | 419ms | 0.02% | 3rd | |
<1M | 424ms | 0.01% | 4th | |
<1M | 584ms | 0.00% | 5th |
Frequently asked questions
Knock sends SMS through Twilio, Amazon SNS, Telnyx, Plivo, MessageBird, Modica, Africa's Talking, Vonage, Sinch, Sinch MessageMedia, and MailerSend. You can send to more than one of them from the same workflow.
No. Knock is an orchestration layer that sits on top of SMS providers like Twilio, Amazon SNS, and Telnyx. You connect the provider you already use, and Knock sends each text through it, with workflows, broadcasts, and templates in one place.
Knock sends SMS to the phone_number property on each user. Store it in E.164 format, such as +15555550123.
Yes. The Twilio channel can send from a phone number, a short code, or a Messaging Service, and supports sandbox mode for testing.
Yes, for providers that send delivery webhooks. Knock maps each provider status to a message status. With Twilio, delivered maps to delivered, failed maps to bounced, and undelivered maps to undelivered.
Yes. With link tracking on, Knock replaces each link in an SMS with a short tracking link by default, which keeps the message shorter and records clicks.
Yes. A throttle step caps how many times a workflow sends to a recipient in a time window, and a batch step rolls several events into one message. Preferences enable users to opt out of SMS by category or workflow, and Knock checks them before each send.
Yes. A step condition can check the status of an earlier message, such as an unseen in-app message or a bounced push, and send the SMS only in that case.
SMS messages count toward the same message allowance as every other channel. The Free plan is $0 per month and includes 10,000 messages per month. The Starter plan is $250 per month and includes 50,000 messages, then $0.005/ea. Enterprise plans use volume-based pricing.
A message is one message delivered to one user on one channel. Knock doesn't charge for workflow triggers, for messages that a user's preferences suppress, or for messages that bounce or fail.
Yes. Knock doesn't manage billing for downstream providers. Your SMS provider bills you for each text it sends, at its own rates.
