Live interview

Interview with James Okonkwo

The audit agent is conducting a one-on-one interview with James about how their day-to-day work flows. Insights are extracted live and folded into the audit report.

Back to dashboardWrapped up
Hi James, thanks for jumping on. I'm interested in how customer service actually works day-to-day, not how the playbook says it should. Could you walk me through what your inbox looks like when you start your shift?
3d ago
Chaos, basically. I open Gmail and there are usually 50-60 emails from overnight, plus another 20-30 Instagram DMs, and a handful of messages on the Shopify chat widget. I use Front to triage them but I read every single one myself because the categories aren't clean. About 70% of them are 'where is my order?' or 'has my order shipped yet?'.
3d ago
So most of the volume is order status. What does your workflow look like to answer one of those? Take me step by step from reading the email to sending a reply.
Manual work3d ago
I read the email, copy the order number, switch to Shopify, paste it in, look up the order, check the fulfilment status, copy the tracking number if there is one, switch back to Front, paste it into a reply template, personalise the greeting, hit send. Maybe 90 seconds per email if everything goes smoothly. With 60 status queries a day that's 90 minutes minimum, but it usually takes longer because customers ask follow-ups.
3d ago
And the same five questions get asked over and over you said. What are the top five, roughly?
Pain points3d ago
1) Where's my order? 2) Can I change my order? 3) Why hasn't my subscription renewed/renewed early? 4) How do I return something? 5) Can I get a discount? Numbers 1, 2, and 3 could be fully automated I reckon. Number 4 is more nuanced because of damaged goods. Number 5 we just say no to politely.
3d ago
You mentioned subscriptions — that's interesting. Are subscription issues a meaningful chunk of inbound? And which system handles subscriptions?
Tools3d ago
Recharge handles subscriptions on top of Shopify. Subscription issues are maybe 15% of my volume. The most common one is people getting charged when they forgot they signed up. Recharge sends a renewal reminder email but it goes to spam for some providers. So I refund and pause, then the customer is happy. But that's another 3-5 minutes per case.
3d ago
How do you track returns once you start a return process? You mentioned earlier that returns is a separate workflow.
Data flow3d ago
Honestly, in a Google Sheet that only I have access to. I log the order number, customer name, reason, and status. When the return arrives at the warehouse, Tom WhatsApps me a photo of it and I update the row. Then I message Priya to refund. If I'm sick or on leave, returns just stop until I'm back, which is bad.
3d ago
That bus-factor risk is significant. If you could wave a magic wand and have any tool built for your inbox specifically, what would it do?
Wish list3d ago
An AI that reads incoming emails, identifies the order number, looks up the status in Shopify and Recharge, and either auto-replies for the simple cases or drafts a reply for me to review for the nuanced ones. Plus a proper returns system that's not just my private spreadsheet. If I got 60% of the volume off my plate I could actually do proactive customer experience work — onboarding new subscribers, recovering churned ones, building a knowledge base.
3d ago
Where does information get stuck between you and the rest of the team? You mentioned WhatsApp from Tom and messaging Priya for refunds.
Handoffs3d ago
Mostly with Priya on refunds. I message her, she's deep in reconciliation work, replies maybe an hour later, by which time the customer has emailed me again asking why they haven't been refunded yet. Then I have to interrupt her again. We've talked about giving me Stripe access to refund directly but Priya wants the audit trail in Xero so we haven't done it.
3d ago
Last question: do you ever get insights from customer emails that the rest of the team would find useful — patterns, complaints, product feedback — and if so, how do you share those?
Data flow3d ago
All the time, but it dies in my inbox. Last month a bunch of subscribers complained the new bag design leaks. I told Marcus on Slack but never compiled the data. Looking back, that should have been a flag but I just didn't have time. A simple weekly summary of customer feedback themes would actually be really valuable.
3d ago
James, that's exactly the type of insight that gets lost when there's no system around it. To recap: 60-80 inbound contacts a day, 70% order-status that could be auto-replied, 15% subscription issues, returns trapped in your private spreadsheet, refund handoffs to Priya creating delays, and customer-feedback intelligence dying on the floor. Anything I missed?
3d ago
That's basically it. The spreadsheet thing keeps me up at night, honestly. If I got hit by a bus, returns would be a black hole.
3d ago
Understood — and that single-person dependency is a real continuity risk that the report will flag. Thanks for being so candid, James. The analysis will be ready shortly.
3d ago

Interview wrapped. The analyser will now fold James's answers into the audit report.

View dashboard