WhatsApp and Email for the Shop Downstairs: A Local Retail Playbook

A neighborhood store runs on interruptions. Someone calls to ask if an item is in stock while a bill is being made at the counter. A regular customer wants to know if their order came in. Someone else wants last week's receipt because they've misplaced the paper slip. None of this is complicated work — it's just constant, and every interruption pulls the one or two people running the shop away from the person standing in front of them.

None of it gets written down either. A promise made on a phone call ("yes, it'll be ready by evening") lives only in memory until someone forgets it, and there's no way to reach past customers about a sale without either calling each one or printing flyers nobody reads twice. This is what a WhatsApp + email setup is actually for in this vertical — not a marketing upgrade, just a way to move the routine questions off the counter and onto a channel that keeps a record.

The stock-check question, before it reaches a person

Most "is this in stock" questions are for the same handful of items — the products that sell every day. Those get set up as keyword-triggered automated replies (available from the Growth plan up): a customer texts a common product name, gets an instant reply confirming availability and price, no staff involved. This only matches on keywords, so it's deliberately narrow — it answers "paracetamol" or "extension board," not "do you have this in blue, size L, from the new stock."

Anything that doesn't match a keyword lands in the shared inbox instead, where any staff member on shift can pick it up — not just whoever answered the phone that day. A push notification alerts the owner the moment a new message comes in, even away from the shop. For the messages that do need a written reply, someone drafting in the shared inbox can pull up an AI-drafted suggestion to start from — a separate metered add-on, and the reply is still reviewed and sent by a person, never auto-sent.

Order ready for pickup

Once an item is set aside — a special order, a repair, stock that came in for someone who asked last week — the store needs to tell that specific customer without waiting for them to call in. That message usually goes out as an HSM template: a pre-approved message format, since the original conversation window with the customer may already be closed by the time the item actually arrives. Tricknowtech handles getting the template approved by Meta once, and after that it's a single send whenever an order is ready — triggered from the dashboard, or automatically from the shop's own order-tracking sheet or POS through the WhatsApp API using the published SDK, if the item being "marked ready" already happens somewhere else.

The receipt, by email instead of paper

A paper receipt gets lost within a week, and then someone's back at the counter asking for a duplicate. Once a customer's email is on file, the receipt goes out as a transactional email — itemized, timestamped, sitting in their inbox instead of a drawer. The sending domain is verified against the store's own domain, with DKIM set up automatically if that domain is hosted with Tricknowtech; every send, including this one, is checked by an LLM confirming it's genuinely transactional before it goes out, and any bounces or complaints are handled automatically through a maintained suppression list rather than quietly retrying a dead address.

This channel is scoped to exactly this kind of message — receipts, order confirmations, account alerts. It isn't used for anything promotional; that restriction is enforced at the infrastructure level, not a house rule the store has to remember.

The seasonal sale, sent to people who've actually bought before

When a sale is coming — festive season stock, end-of-season clearance — the store isn't emailing anyone about it, since email here is transactional-only. It goes out as a WhatsApp broadcast instead, to a segmented list built from customers who've opted in (the same people who've already given their number for a pickup notice or a receipt). The broadcast comes with delivery and read tracking, so the owner can tell whether the message actually landed and was opened, which a stack of printed flyers never tells anyone.

Closing out the day without opening the dashboard

At closing, before deciding what to reorder, the owner wants two numbers: what's still unpaid, and what's actually in the wallet to spend on new stock. Instead of logging into the dashboard on a phone with one hand while locking up with the other, this goes through Claude Desktop or another MCP-connected assistant, using the API token from the account's profile settings.

The assistant pulls the wallet balance and invoice list directly through the account's MCP tools. It's worth being precise about what this can and can't do: it can check balances, list invoices, or send one WhatsApp message to one specific contact — a supplier confirming a delivery time, say. It can't kick off the seasonal broadcast itself; that stays a dashboard or API action tied to a segment, not a single MCP call.

What changed

• Stock questions on common items get answered before they ever reach a person, so counter time goes to the customer standing there, not the phone
• Anything that does need a person still reaches one — through a shared inbox any staff member can pick up, not just whoever happens to answer the phone
• Order-ready messages go out as a written notice instead of a remembered phone call, so pickups happen closer to when they're actually said to happen
• Receipts stop getting lost, and the counter stops fielding requests to reprint them
• Sale announcements reach people who've bought before, with visibility into whether the message was actually opened, instead of a flyer with no way to tell
• End-of-day stock decisions happen from wherever the owner is standing, based on real numbers, instead of waiting to sit down at the till system