Automation
Take the repetition out without taking the people out
Most of what a messaging team does twice a day is not judgement — it is typing the same answer, re-sending to the people a channel missed, and copying an event into another system.
These are the pieces that exist today to remove that. There is no chatbot or auto-reply builder: the conversations that need a person still go to a person.
- Templates with variables for SMS, WhatsApp and Viber
- Campaigns that go out on schedule and move each recipient through your channel order
- Delivery reports posted to your callback URL for SMS sent through the API
- Webhook subscriptions for short-link events, retried when your endpoint fails
The building blocks
What is available today
-
Canned answers
Saved replies your team inserts from the inbox, so quality does not depend on who is on shift.
-
Templates with variables
An SMS template takes up to five variables per send; WhatsApp and Viber templates take parameters filled per recipient.
-
Scheduled campaigns
Set the time and the timezone once, and the campaign goes out when it comes round.
-
Channel order
Each recipient moves down your channel order when a channel cannot be used for them — no manual re-send to the ones a channel missed.
-
Link webhooks
Subscribe to link created, clicked, updated and deleted events, with failed deliveries retried and every attempt listed.
-
Idempotent link creation
Create short links with an idempotency key, so a retry after a timeout does not create a duplicate.
-
Pipedrive activities
Connect your own Pipedrive account and campaign sends can be logged as activities on Pipedrive records.
Automation questions
Is there a chatbot or auto-reply builder?
No. There is no visual flow builder, chatbot or auto-reply today. What exists is templates, canned answers, scheduled campaigns with a channel order, delivery reports and link webhooks.
Can delivery reports be pushed to me?
For SMS sent through /api/SendSMS, yes: give a callback_url and the delivery report is posted to it as JSON. Webhook subscriptions cover short-link events.
How do webhooks handle failure?
Each delivery is recorded with its attempt count, last status code and error, and retried with growing delays — up to eight attempts — before it is set aside.
Can I retry safely?
For short links, yes. Link creation accepts an idempotency key, so a retry after a network timeout returns the original link instead of creating a second one.
Automate the repetitive half
Start with templates and a scheduled campaign, and keep people on the conversations that need them.