Twilio + Zapier
A common setup has three parts. It works well for simple alerts, and it is cheap to start.
Create a Twilio account, buy a number, and register it for US messaging if you text US customers.
When Twilio receives a text, the Zap posts the message to a Slack channel.
When someone posts in Slack, a second Zap sends the text back through Twilio.
Comparison
Simple alerts are easy. A real two-way conversation needs more work.
The parts that you would connect yourself are already done.
Each conversation is one thread. Reply in the thread and the customer gets a text. There is no mapping table to keep and no Zap to fix.
Text several people at once and keep everyone in the same conversation.
Calls to your number can leave a voicemail. The transcript arrives in Slack next to your texts.
Send texts from your own code with the SMS to Slack API. Relays forward Slack messages to any phone number.
Read the API docs
Two-way texting, threads and group messages depend on the number you choose and its country. US numbers may need an approved 10DLC campaign before replies are delivered.
Choose
Pricing
Everyone in the channel can reply, and you never pay for seats. No contracts, cancel any time.
See full pricingFree trial: a number for 7 days and up to 50 messages, no card required. Paid plans are billed from the day you upgrade.
FAQ
One business number for the whole team, answered in Slack threads.
A texting inbox inside Slack, or a separate texting app.
Answer customer texts from the place your team already works.
Say goodbye to the chaos of using your phone to handle all communication. Move all messaging communication to Slack, where you can keep all conversations organized and accessible to your entire team.
“Streamlined the SMS workflow for our team in just a couple of minutes!”