The week I stopped sleeping
I sell baby clothes and children's shoes through Jumia. Onesies, rompers, tiny Adidas knock-offs that look convincing enough for a naming ceremony, school sandals that survive three terms of playground football. I'm based in Kumasi, but I ship across Ghana—Accra, Takoradi, Tamale, anywhere Jumia reaches. Most months it's steady. I pack ten orders a day, answer maybe twenty customer messages, and still have time to restock at Kejetia Market on Fridays.
Then I ran a clearance sale. Forty percent off all baby clothes, buy-two-get-one-free on shoes. I listed it on Jumia Thursday evening. By Friday morning I had 180 orders. By Saturday I had 180 return requests, refund questions and angry messages asking why the pink onesie was actually coral, why the sandals were half a size too small, and whether I understood that mobile money refunds take "too long" and could I please just send cash with the next dispatch rider.
Jumia's return policy is clear: customers have seven days from delivery to request a return, the item must be unused and in original packaging, and refunds go back to the original payment method—usually MTN MoMo—within five to seven business days after we confirm the return. Explaining that 180 times, in patient language, to people who are annoyed and typing in all caps or pidgin or a mix of both, nearly killed me. I was copying and pasting replies, making mistakes with names, sending the wrong refund timeline to the wrong person. By Sunday night I'd answered maybe sixty messages and still had 120 waiting.
I decided to test whether AI could draft the replies. Not send them—I'm not handing my Jumia seller account to a robot—but write a first version I could edit in ten seconds instead of two minutes.
I tested Claude, Gemini and DeepSeek on the same ten messages
I picked three models that Kryotta offers: Claude Sonnet 4.5, Gemini Flash and DeepSeek V3. I copied ten return requests from my Jumia inbox—mix of complaints, refund questions and people who clearly hadn't read the policy—and fed each one to all three models with the same prompt:
"You are replying to a Jumia customer in Ghana who has requested a return or refund. Follow Jumia's return policy: 7 days from delivery, unused item in original packaging, refund to MTN MoMo within 5–7 business days after return confirmation. Keep the tone patient and helpful. Customer message: [message]"
The first message was: "I ORDERED SIZE 6 SANDALS YOU SENT SIZE 5 I WANT MY MONEY BACK NOW MY SON CANT WEAR THIS."
Claude's reply was perfect. It apologised for the error, explained the return process in three short steps, and ended with "We'll process your refund to your MTN MoMo account within 5–7 business days once we receive the sandals back." Polite, clear, no extra fluff. I changed one word and sent it.
Gemini's reply was also good but longer. It apologised, explained the same steps, then added two sentences about how to pack the sandals and a line about contacting Jumia support if the refund took longer than seven days. Helpful, but I'd have to trim it—most customers don't read past the second paragraph.
DeepSeek's reply was strange. It apologised, explained the return process, then said "Please note that refunds are processed within 5–7 business days after we receive the item, subject to verification of condition." That last bit—"subject to verification of condition"—sounded like I was expecting a fight. The customer was already angry; I didn't need to add a clause that implied I might reject the return.
I tested the other nine messages. A woman who wanted a refund in cash because "MoMo takes too long". A man who opened the package, tried the onesie on his baby, decided it was too small, and wanted to return it (not allowed under Jumia's policy, but I wasn't going to say that harshly). Someone who paid GH₵85, received the item, changed their mind, and wanted a refund "today".
Claude understood the policy and the tone
Claude won on almost every message. It drafted replies that followed Jumia's rules, stayed patient when the customer was rude, and adjusted the explanation depending on the situation. When someone asked for a cash refund, Claude wrote: "I understand MoMo refunds can feel slow, but Jumia processes all refunds to the original payment method—in your case, MTN MoMo. It usually takes 5–7 business days once we confirm the return. I can't send cash, but I'll make sure your return is processed as quickly as possible."
That's exactly what I would have written, except Claude did it in three seconds and I would have spent two minutes trying to sound firm without sounding cold.
When the customer who'd already opened the package asked to return the onesie, Claude wrote: "I'm sorry the size didn't work out. Jumia's policy requires items to be unused and in original packaging for a return, so I won't be able to process a refund in this case. If you'd like, I can offer a discount code for your next order—let me know." I added the discount code myself (GH₵10 off), but the structure was perfect. It said no without being rude, and it offered something small to keep the customer happy.
Gemini was fine but verbose. Every reply was 30% longer than it needed to be, with extra reassurances and instructions the customer hadn't asked for. I'd have to edit most of them down, which saved me time but not as much as Claude.
DeepSeek kept adding phrases that sounded defensive. "Subject to verification", "pending inspection", "provided the item meets return criteria". Technically accurate, but it made me sound like I didn't trust the customer. I used maybe two of its replies out of ten, and I rewrote both.
The refund timeline question broke two of them
A lot of customers wanted to know exactly when they'd get their money back. The question usually came in one of three forms: "How long for refund?", "When will MoMo credit my account?" or "I returned the item yesterday, where's my money?"
Jumia's process has three steps: the customer ships the item back, I confirm it's unused and in original packaging, then Jumia processes the refund to MTN MoMo within five to seven business days. That's at least a week, often ten days, and people get impatient.
Claude explained it clearly every time: "Once you ship the item back and I confirm it's in original condition, Jumia will process your refund to MTN MoMo within 5–7 business days. In total, expect about 7–10 days from when you send the item." It broke the timeline into steps without making it sound complicated.
Gemini did the same but added a paragraph about how MoMo sometimes takes an extra day to credit the account, and what to do if the customer didn't see the refund after two weeks. Again, helpful, but too much information upfront. I'd rather answer a follow-up question than overwhelm someone in the first reply.
DeepSeek just said "Refunds are processed within 5–7 business days after return confirmation." It skipped the shipping time and the MoMo credit time, so customers would read "5–7 days" and then message me on day eight asking where their money was. I had to rewrite every single refund-timeline reply from DeepSeek.
I used Claude for 90% of the remaining messages
After testing ten messages with all three models, I switched to Claude for the rest. I'd paste the customer message into Kryotta, let Claude draft a reply, spend ten seconds checking it matched the situation, and send it. Some replies I didn't edit at all. Others I'd add a sentence—"I've noted your MoMo number as 024-XXX-XXXX, I'll confirm once the refund is sent"—or soften the tone if Claude was a bit too formal.
I got through the remaining 120 messages in two days. Normally that would have taken me a week. I didn't make a single mistake with refund amounts or timelines. I didn't send the wrong reply to the wrong person. And I didn't lose my temper with anyone, because Claude's drafts were already patient and I just had to match that tone.
Three customers replied to say thank you for the quick response. One person, who'd been angry about a size mix-up, apologised for "shouting" in her first message and said she appreciated that I explained the return process clearly. That doesn't happen often.
The one thing I still wrote myself
Claude couldn't handle the edge cases where I wanted to bend the rules. A woman in Accra ordered a onesie, received it on time, then messaged two days later to say her sister had bought the same one as a gift and now she had two. She asked if she could return it even though she'd opened the package to check the size. Technically no, but I said yes because she was polite and it was an honest mistake.
Claude's draft said no, cited the policy, and offered a discount code. I rewrote it: "I understand—that's frustrating! Normally we can't accept returns once the package is opened, but I'll make an exception this time. Just send it back in the original packaging and I'll process the refund." I wanted her to feel like I was doing her a favour, not like I was following a script.
That's the trade-off. Claude is excellent at following rules and staying polite, but it won't break the rules for you. If you want to be generous or flexible, you still have to write that part yourself.
What I'd do differently next time
I'd still use Claude for most replies, but I'd write a better prompt. Instead of just pasting the return policy, I'd include examples of edge cases and how I usually handle them—opened packages where I make an exception, customers who are rude but have a valid complaint, people who clearly didn't read the listing and now want a refund. Claude's good at following examples, and I think it would draft replies closer to my actual tone if I gave it more context.
I'd also test Gemini for the long explanations. A few customers asked questions that needed detail—someone wanted to know how to pack fragile items for return, another person asked what happens if the courier loses the package on the way back. Gemini's longer, more thorough replies would work better for those.
DeepSeek I wouldn't use again for customer service. It's fine for straightforward questions, but the defensive phrasing made me sound like I expected trouble. That's the wrong tone when someone's already annoyed.
Questions people ask
Can AI actually send the replies for you, or do you have to copy and paste?
You have to copy and paste. I wouldn't trust any tool to send customer messages without me reading them first—too much risk of a weird reply or a factual mistake. But drafting the reply in three seconds and then sending it yourself still saves a lot of time.
What if the AI gets the refund amount wrong?
It didn't for me, because I included the order details in the prompt—"Customer paid GH₵85, item was GH₵85, refund should be GH₵85." If you just paste the customer message without context, the AI might guess or leave it vague. Always double-check amounts before you send.
Does this work for other platforms, or just Jumia?
It works anywhere you're replying to customer questions—WhatsApp, Instagram DMs, your own website. You just need to tell the AI what your return policy is and what tone you want. The process is the same.
Which model if you sell on WhatsApp instead of Jumia?
Still Claude. The platform doesn't matter—what matters is whether the AI understands your policy and writes replies that sound like you. Claude did both better than the others.
I'm still using Claude for return requests, and now I'm testing it for order confirmations and shipping updates. If you're drowning in customer messages and you're not sure where to start, try Kryotta with ten messages and see which model sounds most like you. You'll know in five minutes whether it's worth the effort.
