Trace Id is missing
January 17, 2022

T-Mobile uses RPA in Power Automate to integrate systems during Sprint merger

During its merger, T-Mobile needed to integrate its Orbit app with Sprint’s legacy back-end system. It was experiencing challenges that could not be solved with legacy APIs: data latency, time-consuming manual processes, and data entry errors. T-Mobile turned to the robotic process automation capabilities in Power Automate to help the two systems operate as one.

T-Mobile

“In order for us to work across the organization in a real-time way, we need real-time data access, and the RPA scenario allows us to do that.”

Brian Hodel, Principal Developer, Power Platform, T-Mobile

Technology integration between merging companies can be daunting, particularly with large, well-established firms. In April 2020, T-Mobile—a United States telecommunications company, delivering 4G LTE and 5G networks—completed its $26 billion merger with Sprint, another major United States telecommunications company. Together, the two became the country’s third-largest wireless communications firm.  

Before the merger, T-Mobile had developed an app named Orbit to run a steady stream of overlapping customer initiatives such as device promotions, service offers, new product launches, and other workflows. Each initiative requires a complex, months-long process that involves up to 15 project members, team leads, and executives. The Orbit app, developed with Microsoft Power Platform by Brian Hodel, Principal Developer, Power Platform at T-Mobile, has been instrumental in helping the company stay competitive.  

The Sprint side of the business was using Quickbase for detailed project management aspects such as tracking tasks and timelines. When the merger was finalized and the companies began to integrate their business operations and IT systems, Hodel and his team started designing a way to integrate the Orbit app with Sprint’s legacy system.  

Helping two companies operate as one

Building a complicated integration across two legacy IT systems was no small task. “At first, this was a very manual process,” says Hodel. “We would pull reports, see what's changed, and then go in and either create or update the records of the legacy system. There were data-entry errors and a large time commitment. Unlike most processes that are repetitive, things ended up being batch-inserted. Eventually, updates were only happening once a week. There was a latency of the data, which is really challenging when you have to work on things that are moving as fast as they do in this world.”   

Automation greatly reduced the number of manual steps needed to create records in Sprint’s legacy system.

To connect the two systems and eliminate some of the manual steps, Hodel and his team members first attempted to integrate into the APIs of Sprint’s legacy customer initiative and promotion system, Quickbase. There was no technical API documentation available, and the process became overwhelmingly complex. Hodel and his team started looking at other options.  

They had a long history of using Power Automate cloud flows, including within the existing Orbit app, so they decided to try the robotic process automation (RPA) capabilities within Power Automate Desktop. The UI-based approach in RPA turns manual tasks into automated workflows by recording and playing back human-driven interaction with software systems that don’t support API-based automation. “Robotic process automation has solved a ton of problems with our integration with Sprint because we don't have to develop custom APIs. We can use the RPA process to just go right into the system and quickly ramp up a solution without having to worry about the complexities of APIs and authentication,” Hodel says. “Within a very short period, we were able to get the RPA solution working without any training. Using the RPA capabilities in Power Automate was a very natural process.” 

Watch the video to hear more about Hodel’s RPA journey and see the flows in action.  

 

Once they began using RPA, Hodel and his team were able to roll out a solution in a matter of weeks, quickly eliminating data lags and making huge strides in the T-Mobile and Spring IT integration work. Hodel says, “I spent more time researching APIs than I did building out the entire RPA system.”  

Integrating back-end systems using RPA

Within the Orbit app, there is an executive application (canvas app) and an admin-focused, model-driven interface. The back end is driven by Power Automate business process flows and all the data is stored in Microsoft Dataverse.

Before the Sprint merger, the majority of the automation workflows within the Orbit app were built with Power Automate cloud flows. Now when specific criteria are met— device promotions, service offers, or device launches—these flows trigger the Power Automate RPA desktop flow within Sprint’s legacy Quickbase system. The flow either updates the existing record or creates a new record. This keeps the Orbit app and the legacy Sprint system in sync. 

 Power Automate flows keep the legacy Sprint system in sync with the T-Mobile Orbit app.
 Power Automate flows keep the legacy Sprint system in sync with the T-Mobile Orbit app.

Using Power Automate flows and RPA capabilities eliminated the need for a complicated API scenario, and because the team was able to ramp up so quickly, it was able to implement the solution right away. 

Saving time, improving accuracy with RPA

The RPA capabilities in Power Automate solved the issues caused by the need for manual data input, greatly improving processing time and data accuracy. “Power Automate is simple and easy to use. After automating the manual process, we could process 11x more requests in real time, improving the average processing time by 12x, reducing human data entry errors to 0 percent, which freed up the analyst’s time to work on more strategic projects and increase job satisfaction,” says Hodel. “You can even build apps using Power Apps to modernize your automation steps. In order for us to work across the organization in a real-time way, we need real-time data access, and the RPA scenario allows us to do that," he says.  

Using the RPA capabilities in Power Automate, T-Mobile experienced a measurable increase in efficiency and decrease in human errors.

 

Hodel advises other teams not to underestimate the power of a low-code solution. “Don’t be fooled by the low-code branding. It is absolutely low code because anyone can go in, and quickly get in, and learn the tools, and to move forward and to investigate them. But it is fully capable of delivering on any sort of business requirements. Anything you can build with the full-code solution, you’re likely to be able to do with this as well. Really, consider it a no-limits platform.”  

Looking to the future

Going forward, Hodel is continuing to build and nurture T-Mobile’s robust community of other Power Platform users across the company and is putting in place appropriate processes for governance using the CoE Starter Kit.

The goal is to help leverage the success of his team to create similar automation success stories across the organization with Power Virtual Agents, AI Builder, and process advisor.  

“Power Automate is simple and easy to use. It allowed us to process 11x more requests in real time, improving the processing time by 12x and reducing human data entry errors to 0 percent. This freed up the analyst for more strategic projects.”

Brian Hodel, Principal Developer, Power Platform, T-Mobile

Take the next step

Fuel innovation with Microsoft

Talk to an expert about custom solutions

Let us help you create customized solutions and achieve your unique business goals.

Drive results with proven solutions

Achieve more with the products and solutions that helped our customers reach their goals.

Follow Microsoft