Skip to content

TE Sync: A partner solution redefined by UX research.

Role
Product Manager and Senior Product Designer
Outcome
RQ is a B2C point of sale, and a major carrier wanted us to support B2B sales. I designed a solution that eliminated manual data entry, fixing data entry errors, and manual effort to track the status of sales. TE Sync launched, and it’s still sold to the carrier’s retailers today.
Design of one imported sale with three lines. Each line has shipped and activated progress bars. One line has both complete and a green tick marking it ready, and the Review button is active.
The TE Sync design. Each line of a business sale shows whether it has shipped and been activated, and is marked ready once it has.

The problem

The company I worked for made RQ, retail software that was 25 years old. Over those years, RQ had been connected to many carriers and partners, one integration at a time.

The brief came from a major US wireless carrier that wanted to enable B2B sales for its authorized retailers. Their reps sold phones to businesses through a portal the carrier ran, and each sale then had to go into RQ. One business sale could include a handful of new phones, or hundreds. RQ was built for B2C, and it had big gaps when it came to selling multiple phones to businesses and entering the data into RQ.

The research

For the carrier's brief, I ran user interviews with all five of the largest retailers and about half of the smaller ones before I designed anything.

On one call, a retailer shared their screen. They had two separate spreadsheets open. One tracked every business sale from the carrier portal that had to reach a certain status before it could be entered into RQ. The other was a list of data entry errors that were in the process of being fixed. It had 270 lines, and five people were going through it line by line. They had been at it for 2 days already. They did this every month. It usually took five people 3 days a month just on fixing data entry errors.

  • 270

    lines of data entry errors in one spreadsheet

  • 5

    people fixing them line by line

  • 3

    days a month spent fixing data entry errors

  • 30

    minutes for a rep to enter one sale

Entering one sale took their sales reps about 30 minutes. When a sale was entered wrong, it didn't match the carrier's records, and the carrier didn't pay the retailer for it. A back office reconciliation expert had to call the carrier for each missing payment, and submit a dispute. The retailer only paid the rep once the carrier had paid, resulting in what could be commission paid several months after the original sale. This broke the rep's trust, and impacted them financially.

Sales repMakes the sale in the carrier's portalCarrier's systemShips and activates each lineSales repChecks the portal again and againSales repTracks the sale on a spreadsheetRetail softwareRep types every line in by handBack officeFinds and fixes the errorsCarrier's systemHolds payment to the retailerSales repCommission can be months lateHours to daysWhen a line is readyTyping errors
Before TE Sync, a rep checked the carrier's portal until each line was ready, kept track of the sale on a spreadsheet, and then typed every phone line into the retail software by hand. Any mistakes in that typing went to the back office to find and fix, and the carrier didn't pay the retailer for those sales until they matched.

Decisions and trade offs

  1. Because RQ was a B2C POS desktop app, I did not want to change any of the core workflows that hundreds of thousands of sales reps were familiar with. I designed a separate responsive web app, TE Sync so B2B sales reps could use the product anywhere, on any device.

  2. The brief said that we should just give the sales rep a way to import each sale into RQ. Large invoices could be added over multiple invoices. I decided that the better solution was to address the very first problem I discovered - the spreadsheet they were using to track their sales until they were shipped by the carrier or activated by the customer.

The work

Importing a sale

As soon as a sale is done, the rep enters the application ID from the carrier's portal into TE Sync. The new app imports all of the phone lines from the sale, and regularly checks each line's status and lets the user know when it is ready to be added to RQ. Once it's ready, the rep can push one button, which auto imports every new phone line into RQ, eliminating the data entry errors caused by manual entry.

Design of the Import a transaction screen, with a required application ID field, the store location, an optional point of contact name, and Cancel and Import buttons.
This is the design for importing a sale. As soon as the sale is done, the rep enters the carrier's application ID, and the app brings in the rest.

Outcome

TE Sync launched, and it's still sold to the carrier's retailers today. Reps no longer waste time checking the carrier's portal every few hours to see if the devices are ready to enter into RQ. They no longer keep a spreadsheet of waiting sales, or type lines in by hand. There are no more manual data entry errors, so the back office team members no longer spend days fixing the manual data entry errors. Everyone gets paid faster, and more accurately, and the retailers have earned back the trust of the sales reps.

What I would do differently

On TE Sync, I would start with what the problem was costing the retailers. I went in thinking about the brief and how to make the integration work. Once I realized the brief was not the whole story, I designed a solution that met the brief and also eliminated data entry errors and time-consuming, repetitive tasks, so sales reps could focus on selling instead of data entry.