Picture starting your day in support and finding a ticket that no customer sent. Overnight, a store’s checkout stopped working. The store owner doesn’t know yet, but you do, along with details of what’s not working and what to do about it.
That’s what we’ve been building in Woo Happiness, the team that looks after WooCommerce merchants at Automattic.
The morning it worked
Earlier this fall, this exact scenario happened for real. Our system spotted repeated fatal errors on a WooCommerce store’s checkout, the kind of error that stops a page from loading at all. It opened a ticket with the technical details for one of our Happiness Engineers (that’s the job title for everyone on the team) and emailed the store owner offering to take a look. Twenty-two minutes later, they wrote back and asked us to dig in.
They never had to contact us. We went to them.
Why proactive support matters
Almost all support starts when someone writes in, but plenty of people who need help never ask. If you work in support, you mostly see the people who reach out. A store can have issues for days while the owner is busy running a business, and by the time they notice, they’ve lost sales and maybe some trust in us.
So we flipped it. Instead of waiting for merchants (that’s what we call the people who run WooCommerce stores) to come to us, we look for moments when they might need a hand or when it would be helpful to hear from us. Right now we’re testing three scenarios: when a store’s checkout is throwing errors, when a store hits a big sales milestone for the first time, and when a bigger store starts using a new extension.
Our system figures out what each moment needs. Sometimes that’s a quick email written for that store and sent automatically. Sometimes it’s a heads-up to one of our Happiness Engineers to double-check things before anything goes out. It looks at the bigger picture, too: if a store hits a big sales milestone while its checkout is broken, we fix the problem first and save the congratulations for later.
Why we started with five a day
We like to test small, watch closely and adjust fast. So we started with just five error emails a day. I know, that’s tiny, especially for something I was this excited about. But this was brand new, and these are some of our biggest stores. We wanted to make sure we were reaching out to the right people, that everything worked the way we planned, and to get a feel for how often these problems pop up. Once we’re sure it’s working, the plan is to scale it up fast.
Starting small also means we find out what doesn’t work before lots of people see it. One of our early emails was too generic, nobody followed up on it, and the store owner wasn’t happy. Fair enough! Within a few days we changed how it works.
What’s working, and what we’re still figuring out
People are writing back. When a store hits a big sales milestone, we send a congratulations email and offer a call. Store owners booked calls from those emails more than 20 times as often as they did from an older email campaign. One owner told us they weren’t sure what came next as their business grew, and talking to someone was exactly what they wanted. That kind of feedback hit our team right in the feels. We’re not bugging people. We’re reaching out right when they’re wondering who to ask.
The error emails are trickier. Nobody likes hearing their checkout is broken, so we’re still trying out different ways to say it, being clear about what we found and what we’ve already checked, and letting folks know we’re right on the other side of the email to help them figure out next steps.
What’s next
Next up, we turn it up. Adding new moments to watch for is way easier now than when we started, so we’re on the lookout for the next ones.
If you work in support, I’d love to know: have you ever reached out to a customer before they asked, and how did it land?


Leave a Reply