Two Customer Bases, One Number: A Manufacturer's WhatsApp and Email Playbook

A small manufacturer that sells both wholesale to retail stores and direct to consumers online is really running two different customer relationships through the same phone number and the same inbox. A retailer wants a reorder confirmed, a dispatch date, and a proper invoice for their books. A consumer who bought one item off the website wants to know if their single package has shipped. Mixed into one WhatsApp chat list and one shared inbox, the retailer's operational message sits next to the consumer's one-off question, and neither gets handled the way its audience actually expects.

In practice this gets improvised. Someone retypes the same wholesale confirmation by hand each time a retailer reorders. Invoices go out as attachments from whatever inbox happens to be open. A new product line gets announced to the entire contact list at once, retailers and one-time consumer buyers together, because there was never a reason to keep two lists. None of that holds up once the order volume across both channels grows past a handful of accounts a week.

A wholesale reorder shouldn't be retyped from scratch

When a retail buyer messages on WhatsApp to reorder a SKU they've bought before, the reply doesn't need to be composed fresh. An HSM template message — reviewed and submitted to Meta once by Tricknowtech, reusable after that — carries the order quantity, dispatch date, and invoice reference as fill-in fields. Whoever is covering the shared team inbox that hour sends the same confirmation format, so nothing depends on one staff member remembering how a particular retailer likes to be updated.

One receipt system, two very different orders

Both order types generate a payment receipt, but they're not the same document. A wholesale order needs a GST invoice with buyer details and line-item quantities; a direct consumer order needs a simple order confirmation and shipping notice. Both go out through the same transactional email setup, sent from the brand's own verified sending domain rather than a generic address — DKIM is set up automatically if that domain is hosted with Tricknowtech, or via CNAME records the manufacturer adds if it's hosted elsewhere — so the receipt looks like it came from the manufacturer, not a third-party billing tool. Because the email product only sends transactional mail — an SES production-access condition, not just a policy — every send is checked before it goes out to confirm it's genuinely a receipt or confirmation and not something promotional riding along with it. Standard templates for both order types get reviewed once and then send automatically; anything sent as freeform text is checked live on that call.

Answering "do you have stock of ___" before it reaches a person

A large share of inbound WhatsApp messages to a manufacturer selling direct are some version of a stock question before someone commits to buying. Left in the general queue, these sit until a person gets to them, even though the answer is often just yes or no. A keyword-triggered automation rule — available on the plans that include automation — watches for stock-related phrasing or a product name and sends back current availability or standard lead time immediately.

If the customer's question goes past what the automated reply covers, the conversation bridges into a support ticket automatically, so it's not lost once it leaves the automation and a person needs to take over.

Telling retailers about a new line without telling everyone

When a new product line is ready ahead of the public catalog, retailers are the audience that needs to hear about it first, with details a browsing consumer doesn't need — case pack sizes, wholesale pricing, minimum order quantities. A broadcast campaign goes to a contact segment built specifically for wholesale buyers, kept separate from the segment made up of direct consumer contacts collected through the website. Delivery and read tracking on the broadcast shows which retailers actually opened it, which is useful information for sales to follow up on before the line goes live to consumers.

Running the floor and the inbox from the same place

The person managing production scheduling is usually not the person sitting at the shared inbox all day, but they're often the one a retailer calls directly when something needs fixing — a lost invoice, a one-off order confirmation that didn't go out. With the Tricknowtech MCP server connected to an AI assistant through a single account token, that person can handle a quick request without stepping out of whatever scheduling work they're in the middle of.

The assistant uses the same send_email action available through the MCP server, restricted to transactional sends only, the same as everywhere else the product is used. Nobody has to open the dashboard, log a support ticket internally, or wait for whoever normally handles billing correspondence to be free.

What changed

• Wholesale confirmations look the same and carry the same information regardless of which staff member sends them, instead of depending on who's covering the inbox that day
• Stock questions get an immediate answer instead of waiting in the same queue as everything else, with a clear path to a person when the automated answer isn't enough
• Retailers and direct consumers are addressed as two separate lists, so a wholesale announcement doesn't reach someone who bought one item off the website, and vice versa
• Invoices and receipts arrive from the brand's own verified sending domain instead of a generic sending address
• A one-off billing or invoice request no longer requires the production scheduling lead to stop and open a separate dashboard