Fifty owners by approved template, charged only on delivery, at the rate Meta prints. The cost with no line on the card is the number itself.
Fifty owners, one phone, one morning. The messages from chapter 6 go out one paste at a time, from the phone the whole business runs on. For a six-person brokerage the shortcut is a free server that logs into that phone. No templates, no opt-in record.
By hand today
The rail is Meta’s, and Meta publishes the rules. On the official lane a product already does this stage at per-message pricing: a business number, an approved template, a fee per message delivered. What no product holds is the rules, read before the morning and after it: the build.
Chapter 7 laid out the two lanes; this chapter sends on the official one. The shortcut is the other: lharries/whatsapp-mcp, 6,269 stars and no push since July 2025. The Business Terms you accepted say a company must not “develop or use any applications that interact with our Business Services without our prior written consent”, and the Messaging Policy says that for “messaging people at scale in an unauthorized manner” Meta has “the right to limit or remove your access to WhatsApp Business Services”. No number attaches to that sentence, and this book will not invent one. Named once; never used.
What it costs you each week
Fifty paid messages
One template per owner, charged only when delivered, at a rate Meta prints per currency on its own card. The cost with no line on the card is the number itself.
Source: Meta, WhatsApp Business Platform pricing pages, read 14 September 2026
“Effective July 1, 2025, Meta charges on a per-message basis”, and “You are only charged when a template message is delivered”. The rate is a card per currency at business.whatsapp.com. This chapter prints no figure; every per-country price found came from a company selling the sending.
A number that stops working is the one every reply from chapter 7 lands on.
The build
Open Codex. Ask for the morning. A thin server on the Cloud API: the template tools, and two that read the quality rating and the sending limit. Templates approved the day before. Fifty sends. Every failure written by its error code, and a capped row never retried.
Open Codex in the engine folder, beside reach.csv and the chapter 6 messages. Meta publishes no MCP server, so the build is a thin one of yours, a handful of HTTPS calls, in the shape of two one-day community repos: tkhattar14/whatsapp-business-mcp (template and analytics tools; github.com) and marco2901/whatsapp-mcp-server (a send and a webhook receiver; github.com). Read their tool lists, depend on neither, and say what you want:
Build a thin MCP server on the WhatsApp Cloud API in the shape of the
two repos above: create a template, read its status, send it, receive
the webhook, read the quality rating and the messaging limit. Today:
submit the chapter 6 message as a marketing template with a variable for
the owner's name and one for the building, and stop until its status
reads APPROVED. Tomorrow: print the rating and the limit before sending
anything. Send only to rows in reach.csv whose basis is opted in, inside
the hours the row allows, one message per owner. Write every send and
every failure to sends.csv with its error code. On error 131049 mark the
row capped; never retry it. At the end print the rating again beside the
morning's. Report four counts: delivered, capped, failed otherwise,
replied.
What comes back is a server, a run and four counts.
Every rule it obeys is on a Meta page. “You can only send messages to WhatsApp users who have opted in to receiving messages from you”, so the run reads the chapter 5 basis column and nothing else. “You may only initiate conversations using an approved Message Template”, and “Templates are automatically reviewed upon creation or after editing”, a review that can take up to 24 hours, so the template goes in the day before.
The cap shapes the morning. “The per-user marketing limit adapts automatically over time based on a person’s recent engagement levels”. It is the recipient’s, shared with every business messaging them; when it is spent the send fails with error 131049 and nothing queues. Your own limit starts at 250 unique recipients a day and rises only while the quality rating holds (developers.facebook.com), so the run reads it before and after.
Two honest limits, which Codex will tell you about. The fifty voices of chapter 6 become one reviewed text with two variables. And marketing templates never reach US numbers, while the cap applies in full in the UAE and not in the EEA, the UK, Japan or South Korea (same page).
Twilio is the on-ramp if you would rather not stand up a Meta app: “Send and receive WhatsApp messages using the WhatsApp Business Platform and Twilio APIs”, the same rules, its own fee on top.
What it feeds
The reply. An owner who writes back opens a window where every message is free and nothing counts against the cap. The number to read: replies over templates delivered, by Friday. Sends are the cost. Replies are the result.
A reply changes the rules. “When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts”, and inside it “All non-template messages are free”. Marketing sent inside it does not count toward the cap (per-user limits page, above). Chapter 11 runs the conversation there.
The number that proves this stage worked is replies over delivered. A high capped count means other businesses spent that owner first.
What stays with a person
The words in the template. Meta reviews it and fifty owners read it. Its category, and whether it earns their attention, is a judgement. A person writes it once, the day before, and the run sends nothing else.
The server submits the text it is given. It cannot say whether that text is marketing or utility, and the category sets the price and the cap, so a person rules on it. Nor whether a chapter 5 opt-in is strong enough for a marketing template. And when the evening rating sits below the morning one, a person decides whether Wednesday runs.
The tools you already pay for
A fee per message, nothing to install.
WhatsApp Business is the number and the account.
CRM gains sent when, failed why, replied when.
Sheet is reach.csv in, sends.csv out.
Fifty owners messaged by approved template, and the number still answering clients on Friday. Then the reply can be the objective.
Ask: Which number did your last fifty WhatsApp messages go out from, and what would stop if it did?
This is stage 8 of twenty, after picking the channel they answer on and before answering the enquiry that lands at eleven at night. The whole engine in order is the book, Building a real estate sales engine with Claude Code and Codex, end to end.