WhatsApp Is the CRM: A Small Brokerage's Daily Playbook

A small real estate brokerage — one or two agents, no back office — runs almost entirely out of pocket. Listings sit on a couple of property portals, but the actual selling happens over WhatsApp: buyers messaging about a unit, agents replying between site visits, a visit time getting fixed and re-fixed over calls. There's no receptionist, and the agent doing the showing is rarely the agent at a desk.

The failure mode is specific. Inbound interest arrives while an agent is mid-visit with someone else, so it sits for a few hours and the buyer moves on to the next listing in their feed. And the paperwork that does happen — a confirmed visit time, a deposit received — often exists only as a WhatsApp screenshot or a promise to "email it later," which becomes a problem the day a buyer or their bank asks for something in writing.

The first reply happens before anyone's at a desk

A buyer messages the number listed against a property, usually quoting the locality or a listing code straight off the portal. On a Growth-tier plan or above, a keyword-triggered automation rule matches on that locality name or code and fires an immediate reply confirming the unit is live and that an agent will follow up, then drops the conversation into the shared team inbox.

The auto-reply isn't the whole conversation — it's what keeps the buyer from moving on before a human gets to it. Whichever agent is free next picks it up from the shared inbox, with the AI-drafted reply feature available to sketch a starting response that agent still reviews and sends themselves before anything goes out.

Locking a site visit without ten phone calls

Once a buyer and agent settle on a time — over a call, or inside that same WhatsApp thread — the slot needs to be confirmed in writing. That confirmation often goes out after the open conversation window has closed, or it doubles as a reminder the evening before, which means it has to be a pre-approved HSM template rather than a freeform message. Tricknowtech handles getting these templates submitted and approved with Meta on the brokerage's behalf, so the confirmation reads as a proper business message with the date, time, and address filled in, not a copy-pasted line typed out on a phone.

The deposit gets a receipt, not a brochure

When a buyer decides to hold a unit and transfers a booking token or deposit, the office needs a receipt out immediately — proof of payment, not marketing. That's exactly what the Email API is scoped for: transactional sends only, whether the office is using a saved receipt template (reviewed and approved once) or writing the amount and buyer detail freeform for that specific payment, which gets checked live by an LLM on that call before it's allowed to send.

The same integration can't be used to email that buyer a brochure roundup or a "here's what's new this week" note — that's promotional content, and it's outside what a transactional-only sending setup is allowed to carry, so it doesn't go through this API at all. What it's good for here: a sending domain that's already verified with automatic DKIM if the brokerage's domain is hosted with Tricknowtech, bounces or complaints handled automatically through a maintained suppression list, and real-time API logs with the actual rejection reason if a receipt doesn't land, instead of it just quietly vanishing.

New listings go to the list that wants them, not the whole database

A brokerage's contact list accumulates fast — everyone who ever asked about anything. Segmenting it by locality and budget range turns that pile into something usable: when new inventory in Sector 12 comes in within a buyer's stated budget range, only the buyers who opted in for that locality and range get the broadcast, not the entire contact list.

Delivery and read tracking on the campaign then tells the office which buyers actually opened the message, so the follow-up call goes to someone who saw the listing first, rather than working down the full list in order.

Running the desk from between viewings

Most of an agent's day happens standing outside a building, not at a laptop. With an API token generated once from profile settings, an agent can point Claude Desktop, Cursor, or any MCP-compatible assistant at their account and issue one-off requests from their phone between appointments.

The MCP tools stay deliberately narrow. send_whatsapp_template and send_whatsapp_text send one message to one named contact; send_email sends one email. There's no MCP tool for firing a broadcast to a segment or touching automation rules — those stay dashboard and API features. What MCP covers well is the in-between-viewings task: confirm the next slot, or get a receipt out for a deposit that just cleared, without waiting to be back at a desk.

What changed

• Inbound listing inquiries get acknowledged the moment they arrive, not whenever an agent is next free.
• A site-visit confirmation is something a buyer can point back to, instead of a half-remembered phone call.
• Deposit receipts go out as soon as payment clears, not whenever someone is next at a laptop.
• New-listing messages reach buyers who actually asked for that locality and budget, instead of the whole contact list at once.
• A second agent can pick up any conversation straight from the shared inbox without needing the buyer's number saved on their own phone.
• Confirming a visit or sending a receipt happens between viewings, from a phone, instead of waiting to sit down at a desk.