A Salon's Day, Run Through WhatsApp and Email APIs

Picture a two-chair salon in a Mumbai suburb — one owner-stylist, one part-time assistant, a WhatsApp number clients already have saved, and a Sunday morning spent chasing no-shows. This is a composite scenario, not a specific customer, but it maps closely to how salons and other personal-care businesses end up using Tricknowtech's WhatsApp Business API and Email API together, without hiring anyone new to run them.

The reminder that keeps the chair full

The highest-value message a salon sends isn't a promotion — it's the appointment reminder. A client books a 6pm haircut on Thursday, and the salon's booking flow fires a WhatsApp template message confirming the slot: service, time, stylist. Tricknowtech handles getting that template submitted and approved through Meta before it can be sent, since HSM templates require review.

A second template goes out a few hours before the appointment — same mechanism, same pre-approved message shape, timed differently. That reminder is the direct lever against no-shows: a client who forgot is far less likely to forget twice when the message lands on the app they check constantly, rather than an email they'll see after the slot has passed.

"Are you open today?" answers itself

Every salon's inbox has the same five questions on repeat: are you open today, what time do you close, do you take walk-ins. On the Growth plan and above, keyword-triggered automation rules catch these before they ever need a human. A message containing "open" or "timing" gets an instant reply with the day's hours; no one on staff has to break from a client's hair to answer it.

Anything the keyword rules don't catch — a question about a specific product, a complaint, a request to reschedule — lands in the shared team inbox, visible to both the owner and the assistant, so nothing sits unread because one person's hands are busy. For conversations that need more than a canned line, an LLM can draft a suggested reply inside that inbox for a human to read, edit, and send — it never sends on its own. That drafting capability is a separate usage-based add-on (WhatsApp AI Credits), billed independently and stacking on top of whatever base plan the salon is on, not something bundled free into a tier.

A receipt that sends itself

Payment for a service or a retail product — a bottle of the shampoo the stylist recommended — should produce a receipt without someone typing one up. The Email API, built on AWS SES, handles exactly that kind of transactional send: order confirmations, payment receipts, appointment reminders, account alerts. It does not send marketing or promotional email; that's an AWS SES production-access condition the platform enforces, not a policy the salon could opt out of even if it wanted to.

Every send — whether it's a saved template or a freeform message composed on the fly — is checked by an LLM before delivery to confirm it's genuinely transactional. A receipt passes without friction. A message that drifts into "and don't forget our new offer" gets flagged. Templates are reviewed once and approved automatically, usually within seconds; freeform sends are checked live, every time. The salon verifies its own sending domain, with DKIM set up automatically if it's hosted with Tricknowtech or via CNAME records if not, so receipts arrive from the salon's own domain rather than a generic address, and delivery/bounce/complaint webhooks let the salon's system know if an email address on file has gone bad.

Filling a slow Tuesday

Tuesdays are slow at most salons. A broadcast campaign — another pre-approved WhatsApp template — goes out to a segmented list: regulars who haven't booked in a while, or clients tagged for a specific service like color touch-ups. The contact list and segments live in the same dashboard as the shared inbox, so building "clients who had a haircut 5+ weeks ago" as a segment doesn't require exporting anything to a spreadsheet.

Delivery and read tracking on the campaign tell the owner roughly how many people actually saw the message — useful for deciding whether next month's slow-Tuesday push is worth repeating, without guessing.

Between clients, from a phone

The owner isn't sitting at a desk during business hours. The Tricknowtech MCP server connects an AI assistant — Claude Desktop, Cursor, GitHub Copilot, anything MCP-compatible — to the account using a single API token generated from profile settings, and exposes 39 tools spanning account, domains, hosting, VPS, billing, email, WhatsApp, and app deployment. For a salon owner, the relevant slice is narrow but genuinely useful between appointments: send_whatsapp_text to fire off a quick confirmation to a walk-in ("Yes, 4pm tomorrow works, see you then") without opening the full dashboard, or send_whatsapp_template for a reminder that needs the pre-approved wording — plus the billing category among those 39 tools for a quick account check without digging through the dashboard.

That access is deliberately narrow. Broadcasts and automation rules stay dashboard- or API-only — an MCP tool call can send one message to one contact, not trigger a campaign to a segment. The same split applies to email: the MCP-callable actions are send_email, list_email_templates, list_email_domains, and create_email_account, all bound by the same transactional-only rule the API enforces everywhere else. The tools are built for the two-minute gap between clients, not for running the marketing side of the business from a phone.