Notifications
Connect Twilio
SMS and WhatsApp for your quotes, from your own Twilio account.
Overview
Twilio + TackQuote
TackQuote sends SMS and WhatsApp messages through Twilio's Messages API. Connect your own Twilio account and every message goes out from your sender, your brand, and your own A2P 10DLC registration — TackQuote resolves your credentials first and only falls back to the platform sender if you haven't connected one, and it tells you which set a message was sent with. WhatsApp keeps its own sender field, because Twilio will not deliver WhatsApp from a plain SMS long code. Numbers are validated as E.164 at connect time so a malformed sender fails in settings instead of dying quietly in the delivery queue, and sends are queued with retries rather than fired inline.
TackQuote calls Twilio's Messages resource with the credentials resolved for your workspace. Two fields plus a sender, and a test send to confirm it.
Before you start
What you'll need
- Twilio account with an active status (a suspended account authenticates but cannot send)
- Account SID and Auth Token
- An E.164 sender number, plus a WhatsApp-enabled sender for WhatsApp
- TackQuote Basic plan or above
Setup
How to connect Twilio
Get your Twilio credentials
From the Twilio Console dashboard, copy your Account SID (it starts with AC) and Auth Token, and note the phone number you send from.Connect in TackQuote
Enter the Account SID, Auth Token, and E.164 from number in TackQuote Integrations → Twilio. Add a separate WhatsApp-enabled sender if you plan to use WhatsApp.Send a test message
Use the test-message button to send to your own phone. It reports the Twilio message SID and status, or a readable reason it failed.Wire it to your workflows
Add an SMS action to the workflow automations you want texting on — quote sent, expiring, accepted — and pick the recipient for each.
Capabilities
What you get
Your Twilio Account, Your Sender
Connect your own Account SID, Auth Token, and from number. TackQuote prefers your credentials over the platform ones and reports which were used on every send.
SMS And WhatsApp, Separately Configured
WhatsApp gets its own sender field. Twilio will not send WhatsApp from an SMS long code, so leaving it blank keeps SMS working instead of silently breaking WhatsApp delivery.
Workflow-Triggered Sends
A workflow automation action is what puts a message on the queue, so you decide which quote events are worth a text. Delivery is queued with retries.
Verified Before You Rely On It
Connect makes a real authenticated call to Twilio, refuses credentials Twilio rejects, and flags a suspended account up front. A test-message button proves delivery end to end.
FAQ
Twilio questions
Do messages come from my number or TackQuote's?
Yours, once you connect a Twilio account — TackQuote resolves your credentials first. If you have not connected one, sends fall back to the platform sender, and the send result names which was used.
What triggers an SMS?
A workflow automation action. TackQuote does not blanket-text your buyers; you add an SMS step to the automations where a text is actually warranted.
Why does WhatsApp need a second number?
Twilio will not deliver WhatsApp from a plain SMS long code — it has to be a WhatsApp-enabled sender (sandbox or approved business number). Keeping it as its own field means an SMS-only setup cannot accidentally break WhatsApp.