Two hundred fifty "Niko wapi?" messages in three weeks
I run a small online shop selling phone accessories—cases, chargers, earbuds, power banks—through WhatsApp and Instagram. I'm based in Nairobi, working from a shared office in Kilimani. Most orders come through WhatsApp catalogue messages: someone sees a post on Instagram, clicks through, picks a case for KSh 800, and sends "I want this one." Then I have to reply with payment details, confirm when the M-Pesa comes through, arrange boda delivery, and send tracking updates.
In February, I counted how many times customers sent follow-up messages before I'd replied to their first one. The number was 250 over three weeks. "Niko wapi?" "Umepata pesa?" "Delivery iko wapi?" Every follow-up meant I was slow, unclear, or both. I was copying and pasting bits of old messages, rewriting the M-Pesa till number every time, forgetting to include the delivery timeframe. It worked, but it didn't scale, and it made me look disorganised.
I decided to write four prompt templates—one for each common scenario—and test them across real customer conversations. I wanted to know which formula got faster replies, fewer confused follow-ups, and fewer "Niko wapi?" messages. I used Kryotta's Claude Sonnet 4.5 to draft the templates, then tracked results over 250 conversations: 80 order confirmations, 70 M-Pesa payment follow-ups, 60 boda delivery updates, and 40 out-of-stock alternatives.
Template one: order confirmation (greeting + detail + action)
When someone sends "I want the Samsung case," I need to confirm the product, give the price, explain how to pay, and set expectations for delivery. My first instinct was to keep it short—just the till number and the amount. That got me a lot of "Then what?" and "How long?" replies.
The formula that worked: greeting + product detail + payment instruction + delivery timeframe + closing question. Here's the template I used:
"Hi! Confirmed—Samsung A54 case, black, KSh 800. Please send M-Pesa to till number 987654, then screenshot and send here. I'll dispatch within 2 hours once payment clears, delivery by boda tomorrow if you're in Nairobi. Sound good?"
I tested this across 80 order confirmations. Seventy-two customers replied with the M-Pesa screenshot within an hour. Five asked clarifying questions ("Do you deliver to Rongai?"), and only three sent "Niko wapi?" follow-ups before I'd confirmed payment. The "sound good?" at the end mattered—it invited a quick "Yes" reply, which kept the conversation active and made customers feel heard.
The version without the delivery timeframe got 18 follow-up questions out of 20 tests. People wanted to know when to expect the package. The version without "screenshot and send here" got 12 customers who paid but didn't send proof, then messaged two hours later asking why I hadn't dispatched. Specificity saved time.
Template two: M-Pesa payment follow-up (emoji + brevity + confirmation)
Once the M-Pesa notification hits my phone, I need to confirm receipt and tell the customer what happens next. I used to write "Payment received, will send soon," which is vague and led to "When is soon?" replies.
The formula that worked: emoji + payment confirmation + dispatch action + thank you. Here's the template:
"✅ KSh 800 received, thank you! Packing your Samsung case now—boda leaves in 30 minutes. I'll send the rider's number once he's on the way."
I tested this across 70 payment confirmations. Sixty-four customers didn't reply at all, which is what I wanted—they had the information they needed. Four replied with "Thanks," and only two sent follow-ups asking for the rider's number before I'd sent it. The emoji worked—it's visual, immediate, and signals "done" without extra words.
The version without the 30-minute dispatch window got 15 "When will it leave?" follow-ups out of 20 tests. The version without "I'll send the rider's number" got 11 customers asking for it an hour later. People want to know what to expect and when.
Template three: boda delivery update (rider detail + ETA + contact)
Once the boda rider is on the way, I need to send the customer enough information to track the package without having to message me. I used to send "Rider is coming," which got me 30+ "Niko wapi?" messages a day.
The formula that worked: rider name + phone number + ETA + what to do if delayed. Here's the template:
"Rider is John, number 0712345678. He left Kilimani 10 minutes ago, should reach you in Westlands by 3pm. If he's delayed, call him directly—he has your number."
I tested this across 60 delivery updates. Fifty-three customers didn't message me again until they'd received the package. Five messaged to confirm the rider had arrived, and only two called me instead of calling the rider when there was a delay. The rider's phone number was the key detail—it moved the responsibility for tracking off my phone and onto the customer and rider.
The version without the ETA got 18 "How long?" follow-ups out of 20 tests. The version without "call him directly" got 14 customers calling me when the rider was stuck in traffic, even though I'd included his number. You have to tell people what to do with the information.
Template four: out-of-stock alternative (apology + substitute + discount)
When a customer orders something I don't have, I used to say "Out of stock, sorry." That ended the conversation 80% of the time. I needed a formula that kept the sale alive.
The formula that worked: apology + reason + alternative + small discount + easy yes/no. Here's the template:
"Sorry, the black Samsung case sold out this morning—restocking Friday. I have the same case in navy blue, or a clear one with a ring holder. KSh 750 instead of 800 if you want either of those today. Interested?"
I tested this across 40 out-of-stock scenarios. Twenty-three customers picked one of the alternatives. Twelve said "I'll wait for the restock," and only five didn't reply at all. The discount wasn't huge—KSh 50—but it acknowledged the inconvenience and gave people a reason to say yes now instead of waiting.
The version without the alternative got 3 conversions out of 20 tests. The version without the discount got 9 conversions out of 20. The version without "Interested?" got 7 conversions—people needed the explicit invitation to decide.
What didn't work: over-explaining and false urgency
I tested two other formulas that failed. The first was a long, detailed message explaining our dispatch process, M-Pesa confirmation delays, and boda routing. It was 120 words. Sixteen out of 20 customers replied with "Okay" and then sent follow-up questions anyway, because they hadn't read the whole thing.
The second was a fake urgency formula: "Only 2 left in stock, order now!" I tested it on 15 customers who were asking about restocks. Zero conversions, and three people called me out: "You said that last week." Don't lie. It's a small market, and people remember.
The one habit that mattered more than the templates
I saved all four templates in a Google Doc on my phone, with placeholders for the variables—product name, price, till number, rider name, ETA. Before I reply to any customer message, I copy the right template, fill in the blanks, and send. It takes 20 seconds. The old way—rewriting from scratch every time—took two minutes and introduced errors. I once sent the wrong till number to three customers in one morning because I was typing fast.
The templates also made it easier to hand off customer service. I hired a part-time assistant in March to handle WhatsApp replies while I'm restocking or meeting suppliers. I sent her the Google Doc, walked through two examples, and she was ready. She's used the templates for 80 conversations so far, and I've had one customer complaint (a delivery delay that wasn't her fault). Before the templates, I couldn't delegate customer service because I didn't have a system—just me, improvising.
Questions people ask
Do these templates work for chama orders or bulk buyers?
Yes, but you need a fifth template for group orders. Add a line confirming the total quantity and asking for one point of contact: "Confirmed—20 cases for your chama, KSh 15,000 total. Please confirm one M-Pesa number and one delivery address, then I'll send payment details." Chama orders fall apart when five people are messaging you separately.
Should I use the same till number in every template?
Yes, unless you're running multiple businesses. Changing the till number confuses customers and makes it harder for you to reconcile payments. I use the same till number in all four templates, and I update the Google Doc once if it ever changes.
What if a customer doesn't reply after I send the order confirmation?
Wait two hours, then send a short follow-up: "Still interested in the Samsung case? Let me know—I'm holding it for you until 5pm." If they don't reply by end of day, move on. Some people browse and don't buy. Don't chase.
Can I automate these templates with WhatsApp Business API?
You can, but the API costs money and requires approval from Meta. For most small shops doing under 500 orders a month, copy-paste templates in a Google Doc are faster and free. I looked into automation and decided it wasn't worth it until I'm doing 1,000+ orders.
If you're writing these templates from scratch or adapting them for a different product category, try drafting them in Kryotta—Claude Sonnet 4.5 is very good at matching tone to audience, and you can test three variations in under a minute. I used it to tighten the wording on all four formulas before I started tracking results.
