Text consent, on the supporter record
Supporters who agreed to texts in your other systems, and have a mobile number, join the Powered By Text group FROM iPaaS.com as they are added or changed, and Powered By Text texts each one its welcome message. Keyword sign-ups and STOPs are built to come back TO iPaaS.com with each person’s text status, with a daily check that catches any notification missed. Optionally, a new gift or order FROM iPaaS.com sends one thank-you text, only to a number that already subscribes, and never twice for the same transaction.
Your donor database, CRM or store stays the system of record for each person’s name, email and address. Powered By Text stays the system of record for text consent: a number that texted STOP is never added back FROM iPaaS.com. The integration sends SMS to one group per subscription. It does not load existing supporters all at once, does not run broadcasts or segment lists, and does not pass replies on. Subscribers and opt-outs already in Powered By Text before the subscription starts reach iPaaS.com only when that number next texts the group. The text status is kept in three iPaaS.com customer custom fields, which another system sees only if its integration maps them. Powered By Text never shares emails, so a keyword sign-up arrives with a placeholder email.
It is event driven, not a continuous sync. Customers and gifts move FROM iPaaS.com when iPaaS.com's webhooks fire. Keyword opt-ins and STOPs are built to move TO iPaaS.com from Powered By Text's notifications, and a daily check of Powered By Text's message report catches any that were missed. Changes made only inside Powered By Text that it doesn't announce, such as removing a number in its app, don't come across, and a STOP answered by the phone carrier instead of the group leaves the number subscribed.
The integration covers customers (with their address) and thank-you texts for new transactions. You can map your own custom fields into Powered By Text contact fields, add mapping collections with other filters, and change the thank-you wording with Dynamic Formula. Broadcasts, segment lists and replies are not part of this version.
No. You subscribe, enter the Powered By Text settings, create four customer custom fields, set collision handling to Update and Link, and turn on the webhooks you want. A MiSP can set it up and adjust filters and mappings without code.
A failed transfer shows in the subscription's errors with a PBT code, its cause and what to do, and iPaaS.com retries it, except a thank-you text Powered By Text didn't answer, which may have gone out and is never sent again. Outcomes that are not errors, such as a skipped thank-you for a number that doesn't subscribe, are logged as warnings. A wrong setting shows as "Unable to connect", with the coded reason in Logs.
*Not all data objects flow bi-directionally
Change MiSPs whenever you need to. Your configurations stay yours, fully portable, with nothing rebuilt from scratch. iPaaS.com is a certified standard, not a proprietary lock-in.
Connect a system once and route data everywhere it needs to go, standardized and consistent across every system in your dataflow. No rebuilding the same integration five times. No cleanup on the other end.
Predictable monthly pricing replaces the per-connector, per-integration cost creep that defines the status quo. You know what you're paying, every month, no exceptions.
Every dataflow is logged, governed, and audit-ready from day one. When compliance asks questions, you already have answers. Governance isn't a bolt-on: it's built into how data moves.
Discover how iPaaS.com can simplify even the most complex integrations.
