stacijordansheltonQ: Are you Considering native SMS?
I'm absolutely going to grab this, the question for me is which tier. But also...are you going to add SMS as a native feature? It's being included in more and more email marketing platforms, and that would be a win.
David_Encharge
May 22, 2025A: Hey Staci! 🙌
Love hearing you’re jumping in — and great question on SMS.
Right now, native SMS isn’t in active development, but it’s definitely on our radar. We’ve seen more and more platforms adding it, and we totally agree — it would be a win for a lot of use cases.
If enough people upvote it on our feedback board, we’ll seriously consider building it in. That’s how several recent features made it onto the roadmap, so your voice really does matter.
You can upvote SMS here 👉 https://feedback.encharge.io
Until then, quite a few users are using tools like Twilio or ClickSend via Zapier or Make to handle SMS alongside Encharge — it’s not native, but it gets the job done for now.
Appreciate you being here — let us know if you need help picking a tier or mapping out your setup!
I’m confused by the mention of needing to use Zapier or Make for SMS.
Twilio is listed in the integrations area of Encharge: https://encharge.io/integrations/twilio/
What would we use Zapier or Make for in this case?
Twilio is a native integration in Encharge. You can send SMS directly inside your Flows using the built-in “Send SMS” step — no Zapier or Make needed for that part.
What I meant to say is: if you're looking to go deeper — like triggering based on delivery status, replies, or using conditional logic tied to external systems — some folks bridge through Zapier or Make to get more granular control.