If your texting program depends on external intake, the handoff matters. A supporter donates, opts in or fills out a form and you have a narrow window to confirm, onboard and move them to action. When that intake lands in the wrong place or requires manual sorting, follow-up slows down and your team pays the price in time and consistency.
This release is built for that intake-to-action pipeline, focusing on the exact friction points that slow down high-output campaigns and advocacy programs:
RumbleUp now supports all major texting traffic channel types:
Building around your actual program needs instead of forcing your workflow into whatever lane your texting vendor happens to support, or juggling multiple vendors, matters.
This is one of the most requested contact-management upgrades we have heard from clients over the years, and it removes a common time sink.
You can now import contacts directly into an existing group, bypassing the extra step of uploading a list and then merging it into a target group via the Segmentation tool.
This option applies only to the specific subaccount where the import takes place. A parent account cannot import contacts across multiple subaccounts in a single action.
Drip Campaigns help you run consistent follow-up without adding staff load. Until now, Drip Campaigns have centered on how a contact interacts inside the conversation. Now you can also start automation the moment a contact lands in the right bucket.
This trigger is built for programs that add contacts to groups programmatically or at high volume, including:
In our next release, we will expose this functionality in our API to support fully automated pipelines.
If your team imports contacts directly into an existing group, this trigger can power immediate next steps without requiring manual enrollment.
The Opt-In Dashboard (formerly the Switchboard Dashboard) is now accessible inside subaccounts that carry the opt-in account tag.
If you manage opt-in activity across multiple programs, subaccounts or teams, you should not need to bounce between workspaces to gain visibility. This change keeps opt-in monitoring closer to the people running the program day to day.
Over the years, our team has added tons of functionality to our project screen, including many client-requested features. In turn, what was once a highly intuitive interface has now become a cluttered and confusing mess with all those new additions! To fix this, we revamped the project screen last year to restore its intuitive state.
The new project UI is now graduating out of beta and will become the default experience for all accounts.
The new UI keeps the same capabilities but organizes them so you can find what you need when you need it. It is still built to support high-output power users with multi-project workflows, and also results in fewer clicks/actions needed for the single-account user.
If your team needs time to adjust, you can use the reversal toggle to switch back while you transition.
We are building a completely refreshed RumbleUp experience beyond the current project UI improvements. We expect to bring alpha testers on in May.
If you want to shape what ships, tell your primary point of contact on our team today. Early input helps us prioritize what matters most for how you run texting.
The hardest part of running texting at scale is not writing messages. It is managing channel types and list movement without creating risk or extra clicks for your team. When those pieces live in different places or require workarounds, you get inconsistent follow-up, fragmented reporting and preventable mistakes.
You need a platform that keeps up with how political and advocacy programs operate now: multiple intake sources, multiple teams, multiple sending lanes and constant pressure to move quickly without losing accuracy. That means fewer workarounds, more automation triggers tied to real program events and infrastructure that supports your line strategy as it evolves.
These updates help you run a tighter program today and lay the foundation for the big things we are building next.