Inside a Coaching Institute's Front Desk: WhatsApp, Email, and MCP in One Day

Picture a coaching institute in Thane running four batches out of two rooms — Class 10 boards, Class 12 boards, a NEET batch, and a spoken-English batch — with one front-desk coordinator handling enrollment, fees, and parent questions between walk-ins. This is a composite scenario, not a specific real institute, built to show what a day looks like when WhatsApp, transactional email, and an MCP-connected AI assistant are doing the repetitive parts of the job.

• A parent enrolls a child in a batch — WhatsApp sends the confirmation
• The fee gets paid — email sends the receipt
• A parent asks about timings — an automated reply answers before a human sees it
• A new batch is announced — a broadcast reaches only the parents who already asked about it
• Mid-walk-in, the coordinator sends one reminder or resends one receipt through an AI assistant

Enrollment confirmation and the fee receipt

A parent enrolls their child in the NEET batch and pays the first installment in cash at the counter. The coordinator adds the student to the batch roster, which fires an HSM template message on WhatsApp — Tricknowtech handles the Meta submission and review on these templates, so the institute never deals with Meta's approval process directly — confirming the batch name, days, timing, and start date. The parent has it in their WhatsApp chat within seconds, with no portal login or app download involved.

The fee payment itself doesn't go through WhatsApp. It triggers a transactional email — a receipt with the amount, batch, and payment method, sent through the Email API's AWS SES backbone. Every send, templated or freeform, is checked by an LLM before it goes out to confirm it's genuinely transactional; templates are reviewed once and approved automatically, usually within seconds, while a freeform note gets checked live on that call. A fee receipt clears without anyone at the institute having to think about it. If the institute sends from its own domain instead of a shared one, DKIM is set up automatically when it's hosted with Tricknowtech, or via CNAME records if it isn't.

Answering "what are the timings" before a human has to

Any front desk gets the same three or four questions on repeat: what time is the XI Commerce batch, how much is the NEET batch, is there a demo class. On the Growth plan and above, keyword-triggered automation rules catch these directly inside WhatsApp — a message containing "timings" or "fees" gets an immediate reply with the schedule or fee structure, no coordinator involved.

Questions that don't match a keyword — "can my daughter switch from the morning batch to the evening one" — fall through to the shared team inbox, where WhatsApp-to-support-ticket bridging turns the thread into a ticket a staff member can pick up later without losing the conversation history. When someone does sit down to answer it, the shared inbox can surface an AI-drafted reply: an LLM's suggested response sitting in the compose box, ready to edit or send as-is, never sent automatically. It's billed separately as a usage-based WhatsApp AI Credits add-on, stacking on top of whatever base plan the institute is already on, so it only costs something on the days staff actually use the draft.

Telling past inquirers about a new batch

Contact management keeps a segment for everyone who asked about a subject but didn't enroll — the parents who inquired about a NEET batch a few months back and went quiet. When a new batch is confirmed, a broadcast campaign goes out to that segment specifically, not the full contact list, with delivery and read tracking showing which parents actually opened it.

Replies to the broadcast land in the same shared inbox as everything else. A parent asking "is there a scholarship test" gets caught by an automation rule if the phrasing matches a configured keyword, or goes to a staff member if it doesn't — the same routing that handles every other inbound message, broadcast reply or not.

Running it from a phone between walk-ins

The coordinator isn't at a desk all day. Between enrollments, they run Claude Desktop connected to the institute's account through the Tricknowtech MCP server — one API token generated from profile settings, no separate login to manage. Reminding a parent that tomorrow's 6pm class is happening is one send_whatsapp_text call, triggered by typing the request in plain language. Resending a parent's fee receipt because they lost the original is one send_email call over the same connection. Both are single, specific actions directed at a known person — broadcasts and automation rules stay on the dashboard and API, not something an AI assistant can trigger on its own, so there's no path from a chat window to a mass send.

The same MCP connection has 39 tools available across domains, hosting, VPS, billing, email, WhatsApp, and app deployment. For a coaching institute's day-to-day, it comes down to two things repeated between walk-ins: send this message, send this receipt, then get back to the parent standing at the counter.