A Small Studio's Client Workflow: Invoices, WhatsApp Updates, and One Deploy Command

Picture a five-person design and web studio juggling six or seven client projects at once — a rebrand for one client, a WooCommerce rebuild for another, ongoing maintenance retainers for the rest. Each project throws off the same three kinds of events on a normal day: a client needs to know something changed, a client needs an invoice, and a client asks a question that doesn't warrant a call. None of those map cleanly onto "log into the dashboard and find the thing." Here's how that studio's stack — transactional email, the WhatsApp Business API, and an MCP-connected assistant — handles those events as they happen, mostly without anyone having to switch tools to do it.

The invoice that sends itself

A project manager marks "homepage design — approved" complete in the studio's project tracker. That status change is wired to call Tricknowtech's Email API, which sends the client an invoice and a receipt for the milestone payment. The API only sends transactional mail — order confirmations, receipts, invoices, and similar — enforced by the AWS SES production-access condition it runs under, not something the studio has to remember to respect on its own. Every call, templated or freeform, is checked by an LLM before it goes out to confirm it's genuinely transactional; a saved invoice template gets reviewed once and then approves automatically, usually within seconds, while a one-off freeform send is checked live on that call.

If a client's mailbox is full or their mail server blocks the sending address, the studio doesn't have to guess why the invoice never got a reply. The API logs the exact rejection reason in real time, and because the studio's sending domain is verified with automatic DKIM, a bounce or complaint webhook — HMAC-signed, since they set a secret — fires back into their own system so the invoice gets flagged as undelivered instead of just sitting there marked "sent."

A one-line update on WhatsApp

Same afternoon, the PM wants the client to see the actual draft before it shows up as a line item on any invoice. Email isn't the right channel for that — it's the WhatsApp Business API instead, sending a pre-approved HSM template: "Your homepage draft is ready for review — link inside." Tricknowtech handles the Meta submission and review for that template, so the studio doesn't deal with Meta's approval process directly.

The message goes out from the studio's shared team inbox rather than one person's phone, so any PM covering for a colleague can see the same thread and the same delivery and read receipts. When the client opens it, the PM sees the read timestamp and knows to expect a reply rather than following up blind.

The reply that goes out before anyone's at a desk

Clients message outside working hours. A common one: "still on track for Friday?" sent at 11pm. A keyword-triggered automation rule, available on the Growth plan and above, matches the pattern and sends an acknowledgment immediately, so the client isn't staring at an unread message until morning.

Questions that need more than a canned line sit in the shared inbox until a PM is at their desk. By the time they open it, an AI-drafted reply is often already sitting under the message — the LLM reads the thread and proposes a response, but nothing sends until a human edits or approves it. It's billed separately as usage-based WhatsApp AI Credits rather than bundled into any plan, so the studio can see exactly what it's costing per month regardless of which base plan they're on. If the question turns out to be an actual bug report on the deployed site rather than a scheduling one, the PM bridges the WhatsApp thread straight into a support ticket instead of trying to track it by scrolling back through chat history.

Between focus blocks, without opening the dashboard

The same studio's lead developer works in long, heads-down blocks and treats the dashboard as something to open only when necessary. Between blocks, Claude Desktop is connected to the studio's Tricknowtech account through one API token — the MCP server exposes 39 tools across account, domains, hosting, VPS, billing, email, WhatsApp, and app deployment, callable from inside the same assistant they're already using to write code.

A five-minute break covers a lot: a quick check of the billing tools shows which clients haven't paid yet, no login screen involved. A client who paid by bank transfer that morning gets a receipt fired off with send_email, still transactional, still checked before it sends. Then, with a small copy fix ready for a client site, deploy_app pushes it from the connected GitHub repo — if the deploy had failed instead, a push notification would have said so without anyone needing to poll a build log.

The WhatsApp tools available through MCP are deliberately narrower than the API itself — send_whatsapp_text, send_whatsapp_template, and the two list tools, nothing that touches broadcasts or automation rules. Setting up that Friday-night keyword reply still meant opening the dashboard once. Sending a one-off "shipped, take a look" message to a client afterward doesn't.