JollygreenQ: Allow Phone Field to Update Subscriber Record
Can you please add phone number as another identifier to update a subscriber record? I added it to the roadmap requests but reposting here for visibility.
I am trying to create an SMS opt in flow with Twilio + Pabbly Encharge connector. I only have the subscriber phone number to update a subscriber record (tagged for sms_opt_in), but I cannot update a record without an email! (since Encharge uses the email field as the unique identifier for updating subscriber records)
I am using a Pabbly connector with:
- Routes to webhook SMS replies of "Y" to opt in and "STOP" to opt out
- Encharge: Add or Update Person action step
- SMS reply filter
- "Y" = assign tag sms_opt_in
- "STOP" = assign tag sms_opt_out
PLEASE UPVOTE IN ROADMAP - feedback(dot)encharge(dot)io/feature-requests/posts/allow-phone-field-to-update-subscriber-record
David_Encharge
Dec 4, 2025A: Hey Jollygreen! 🙌
First off, huge thanks for sharing this so clearly—and for already submitting it to the roadmap 🙏 That helps a ton.
You're absolutely right: right now, Encharge requires the email field to identify and update a subscriber record, which makes phone-only workflows like SMS opt-ins a bit tricky. That’s a limitation we’ve heard from a few others as well, especially those using Twilio or Pabbly for SMS workflows.
We’d love to allow phone number (or other fields like user ID) to act as unique identifiers in the future. It’s definitely on our radar, and your upvote at feedback.encharge.io
gives it more weight with the team.
For now, your workaround using tags via the Pabbly connector is the best way to go, but we know it's not ideal if you're starting with just a phone number.
We're building out more flexible identification logic, but don’t want to commit to a timeline we might shift later—especially for something as foundational as identity logic.
Keep the ideas coming, and thanks again for your persistence here!! If you need help exploring alternate setups in the meantime, feel free to drop us a line at support@encharge.io