Activ SMS
Two-way messaging that fits the workflow, not another inbox.
Send, receive and route SMS from your systems and your team, with the conversation attached to the customer record instead of a separate inbox.
Messaging for operations
Most business SMS is operational. Treat it that way.
Confirmations, reminders, document requests, quick replies. Activ SMS handles the sending, the replies and the routing so the workflow keeps moving.
- Two-way messaging with replies routed to the right team or workflow
- Templates and scheduled sends for the routine messages
- A simple API and webhooks for your own systems
- Conversations attached to the CRM record, not a standalone inbox
- Opt-out handling and sender identity managed for you
Hi Sam, your appointment is on Thu 14 at 10:30. Reply YES to confirm or CHANGE to rearrange.
YES
Appointment confirmed · CRM updated
Can I bring my ID?
Routed to case owner · Rachel
- YES / CONFIRM→ Appointment
- CHANGE→ Rebook flow
- STOP→ Opt-out
- Anything else→ Case owner
Core capabilities
The parts of messaging an operations team actually needs.
Deliberately smaller than a contact-centre platform. Everything here is there because a workflow needed it.
Two-way conversations
Send from the team or from automation, and see replies in a conversation view against the customer.
Reply routing
Route replies by keyword, workflow state or team so a 'yes' updates the appointment and a question reaches a person.
Templates and scheduling
Approved templates with merge fields, scheduled sends and quiet hours.
API and webhooks
A small, well-documented API for sending, plus webhooks for delivery status and inbound messages.
Consent and opt-out
Opt-out keywords, preference tracking and audit trail handled as standard.
Delivery reporting
Status per message and per campaign, with failures surfaced to the workflow rather than hidden in a report.
How it fits
A document chaser, from trigger to closed task.
A typical automated messaging workflow. The same building blocks apply to confirmations, reminders and service updates.
- Step 1
Trigger
A document request in the CRM passes its due date without a response.
- Step 2
Send
A templated message goes out with a secure link, inside the customer's contact preferences.
- Step 3
Route the reply
A reply with a question is routed to the case owner. A 'sent' reply updates the request status.
- Step 4
Close the loop
The task closes when the document arrives, or escalates to a call if the chaser sequence completes.
Integrations
Messaging that plugs into the rest of the operation.
Activ SMS is designed as a component. Use it from Activ CRM, from Activ Agent or from your own systems.
- Activ CRM
- Native: conversations on the customer timeline, templates driven by workflow.
- Activ Agent
- Messaging channel for AI agent workflows and human handoff.
- REST API
- Send and receive from any system that can make an HTTP call.
- Webhooks
- Delivery status and inbound messages pushed to your endpoints.
- Automation platforms
- Ready to use from Make, n8n and Power Automate.
- Existing systems
- Integration services for platforms without a modern API.
FAQ
Questions we get asked
Is this a contact-centre platform?
No, and that is deliberate. Activ SMS covers operational messaging: sending, replies, routing and reporting. It can sit alongside a contact centre where you have one.
Can we use our own systems to send messages?
Yes. The API and webhooks are designed for that. Activ CRM is not required.
How are opt-outs handled?
Opt-out keywords are processed automatically, preferences are recorded against the customer and the audit trail is kept.
See it in your workflow
Tell us which messages your team sends most.
We'll show you how they would run through Activ SMS, and where automation would take the routine ones off the team's plate.