This document provides answers to the most common questions agencies and partners ask during the TextMarks-to-Swiftly transition. Swiftly is committed to making this transition seamless with minimal disruption to riders and your existing service.
General - the transition
Why is TextMarks going away?
The TextMarks team has decided, after 20 years, to wind down the business and move on to their next chapter. Before doing so, they spent several months finding a trusted partner to ensure continuity for all TextMarks customers and selected Swiftly as their ideal partner to work with.
Who is Swiftly, and why were they chosen?
Swiftly is the leading Transit Data Platform, partnering with 200+ transit agencies - including LA Metro, SEPTA, and MBTA - to power real-time passenger information, operations management, and service performance improvements. The TextMarks leadership team selected Swiftly specifically because of their deep transit expertise, industry-leading reputation and customer satisfaction, and existing SMS capabilities. Swiftly already powers SMS for 100+ agencies today.
What is the timeline for this transition?
Swiftly will work with each agency individually to set a transition date. The TextMarks platform will be fully shut down on November 1, 2026. All agencies must complete their transition to Swiftly or another provider before that date to ensure uninterrupted service for riders.
Do we need to do anything right now?
Not immediately. A member of Swiftly's implementation team will reach out to schedule a kick-off call and walk through your specific Swiftly transition plan and timeline. To keep your timeline on track, we'll need you to confirm a few data items (see the 'Transition Process' section below).
The 41411 shortcode & rider experience
Will riders still be able to text 41411?
Yes, absolutely. Swiftly now manages the 41411 shortcode, and it will remain active before, during, and after the transition. Riders do not need to change anything. The number printed on your bus stop signs and websites stays the same.
Will there be any service disruption for riders during the transition?
No. The transition to Swiftly SMS is designed to be seamless for riders. The 41411 shortcode will continue to function throughout the transition period, and Swiftly will carefully coordinate the technical cutover to avoid any interruptions.
Will we need to replace any bus stop signage?
No. Because Swiftly now manages the 41411 shortcode, all existing signage with that number remains valid.
Will the text format riders use change (e.g., keyword + stop ID)?
The format riders use to request ETAs will remain the same — they text a keyword plus their stop ID to 41411 and receive arrival times back. Swiftly has built support for the existing TextMarks agency keyword format specifically to ensure continuity.
Will arrival time accuracy change after the transition?
Yes — it should improve. TextMarks has historically passed through arrival predictions from whichever CAD/AVL system an agency uses. Swiftly generates its own real-time predictions using its proprietary algorithm, which is independently verified to increase ETA accuracy by up to 50% as measured by the industry standard ETA Accuracy Benchmark. Agencies that transition to Swiftly-powered predictions will get more accurate ETAs for their riders.
Can I use a different vendor and still keep using the 41411 shortcode?
Unfortunately, no. The Shortcode registry does not allow different companies to manage the same shortcode. If you decide to switch to a different vendor, you will need a new shortcode or phone number for your agency. Please note that you may have to reprint physical bus stop signs, update your website, and inform riders of the change if you pursue this path.
Can I use Swiftly but shift away from the 41411 shortcode?
Yes. If you would like to switch your number, Swiftly can help find you a new 10-digit phone number for your agency. Please note that you may have to reprint physical bus stop signs, update your website, and inform riders of the change if you pursue this path.
Contracts & pricing
What happens to our current TextMarks contract and pricing?
Your existing service and pricing will be honored through June 30, 2027. Swiftly will work with you on contracting details to retain service through this date and beyond to minimize disruption for your riders and staff.
What if my agency receives SMS service through a CAD/AVL vendor rather than directly through TextMarks?
Regardless of how your agency's SMS service is currently contracted, all agencies must transition to Swiftly's SMS platform by November 1, 2026. Your existing contract will be honored through June 30, 2027, giving your agency time to work through the transition with your CAD/AVL vendor. After that date, agencies will need to contract directly with Swiftly to continue SMS service on 41411. A Swiftly representative will reach out to walk through your specific situation and next steps.
Will our pricing change when we move to Swiftly?
Your current pricing is honored through June 30, 2027. Any pricing changes at renewal will be shared with you by your Swiftly Account Executive or Account Manager well before this date to assist with the budgeting process.
Transition process
What does the transition process look like?
The transition is designed to be straightforward and minimally disruptive for your team. We'll start with a 30-minute kick-off call with your Swiftly implementation manager to walk through your agency's current setup, review your options for maintaining service continuity, and align on a go-live date. From there, Swiftly handles the configuration and testing on our end. When everything is ready, we'll let you know, and then we’ll cut over to the Swiftly platform seamlessly without impacting riders.
What information will Swiftly need from us to complete the migration?
To migrate your agency, Swiftly will need two things: your GTFS static feed URL and your real-time vehicle location (AVL) data. Swiftly uses these inputs to generate its own arrival predictions through its proprietary algorithm. This means your riders can expect to receive more accurate ETAs than those currently provided. Your implementation manager will confirm whether Swiftly already has your feeds on file and, if not, walk you through the next steps.
We are already a Swiftly customer. Does this affect us?
If you already use Swiftly for real-time passenger information and your SMS is powered by TextMarks, your transition will generally be straightforward. In this case, your SMS is already supported by Swiftly’s predictions behind the scenes, and Swiftly can often migrate you quickly since your data is already powered by our platform. Your Swiftly Account Manager will be in touch to confirm details.
How long will the transition take?
The technical transition itself is typically fast once the required data sources are integrated and validated within Swiftly. The overall timeline depends on how quickly we can verify your data feeds and schedule your go-live. Your implementation manager will work with you to set a realistic target date well ahead of the November 1, 2026, deadline.
Who will be our main point of contact at Swiftly?
You will be introduced to a Swiftly Implementation Manager, who will lead technical integration and transition work, and to a Swiftly Account Executive or Account Manager, who will connect with you after go-live to discuss your long-term plan. You can also reach Swiftly's customer support team anytime at support@goswift.ly.
Features & functionality
Does Swiftly support service alerts via SMS?
Yes. If your agency provides a GTFS-RT Service Alerts feed, or if you use Swiftly's Rider Alerts product to create alerts, those will be reflected in SMS responses. Your Swiftly implementation team will work with you and recommend the right configuration for your agency during the transition process.
Will riders be able to subscribe to specific service alerts?
No. Riders cannot subscribe to receive a specific service via Swiftly’s SMS feature. Swifty’s SMS Request/Response allows riders to text 41411 and receive real time arrival information by text message.
Does Swiftly support disruption-aware ETAs (e.g., detours, canceled trips)?
Yes. Swiftly's SMS is disruption-aware if Service Adjustments are entered in Swiftly or available via a GTFS-RT Trip Modifications feed. If your current TextMarks setup reflects disruptions, your Swiftly implementation team will work with you and recommend the right configuration for your agency during the transition process.
TextMarks allowed us to send broadcast messages to all subscribers. Will Swiftly support that?
No. The prior TextMarks broadcast functionality may introduce compliance concerns. For this reason, the 41411 number will no longer be available for broadcast use cases after November 1, 2026. A Swiftly representative will discuss alternative options with you.
We use TextMarks for paratransit communications. Will Swiftly support that?
No. Individual paratransit rider SMS flows are outside Swiftly's platform scope. If your agency relies on TextMarks specifically for paratransit, a Swiftly representative will discuss alternative options with you. The 41411 number will no longer be available for paratransit use cases after November 1, 2026.
We use TextMarks for internal communications among agency staff and drivers. Will Swiftly support that?
No. Internal staff and driver communications via 41411 are not supported in Swiftly's platform. TextMarks will no longer be available for internal communication after November 1, 2026. A Swiftly representative will discuss alternative options with you.
Support & next steps
Who do we contact if we have questions before our kick-off call?
You can reach Swiftly's customer support team at support@goswift.ly.
Comments
Article is closed for comments.