Wins counter is live: revenue, leads, and customers served, always in view

A new wins counter sits at the top of the Text App. It doesn't go away when you switch sections, doesn't tuck into a dashboard you have to remember to open. Three numbers, visible all day, updating as wins land.

What the counter shows

The counter tracks three categories:

• Sales closed: dollars from orders placed during chat. Currently sourced from Shopify and BigCommerce stores.
• Leads qualified: new leads where the conversation gathered contact info.
• Customers served: customers who had a chat or whose ticket was solved or closed.

It updates shortly after each win, not on a schedule. If a chat closes a $400 order at 10:42, the counter moves at 10:42.

Why dollars sit in the chrome

For months, the brand line has been that service is a profit engine, not overhead. The product surface needed to say the same thing. Now it does.

Most reporting dashboards in customer service tools surface tickets closed, response times, handle time. The wins counter shows none of that. It shows what the company actually made from service today. That's a deliberate choice, not a feature decision.

For an admin, it's an instant gut check on ROI. For an agent, every closed chat feeds a number they can see grow. The counter is always there, which means the question "did service make money today?" never goes more than a glance away.

The Shopify-first wrinkle

Revenue tracking starts with Shopify and BigCommerce because those are the stacks the team can pull verified order data from. Customers on other platforms still see the revenue metric - by design. The team wants the counter to communicate how the product is meant to be used, even before every customer can plug their store in. Custom and headless stores are next on the roadmap, with WooCommerce after that.

What's coming

The team is already working on customization. Targets are the first thing users will be able to set, which pairs neatly with the targets-on-reports release from earlier this month. Further out: more granular metric selection and potentially API access for teams that want to wire the numbers into their own dashboards.

Jakub Firuta, who leads the project, put the team's ambition this way: he wants users asking for a way to mute the notifications because their numbers are growing faster than they can keep up with.