WhatsApp and RCS Flows Built Around the Inbound Reply

WhatsApp has billed per message since 1 July 2025, so every template you add carries a line cost and the flow logic that was free to be wrong in email is now priced. The first thing we do is cut the list of conversations you want to move into the channel down to the ones where the customer's reply changes what happens next. Everything else stays in email, where being ignored costs you nothing. The first decision: Three tests. Does a reply change the outcome, meaning there is a slot to confirm, a document to send, a candidate to accept? Is the message expected inside a window the person can predict? Would you be comfortable with it arriving at nine on a Sunday evening? A flow that fails any one of the three is an email. This takes the first week and it usually removes more than half of what the brief contained, which is the part of the engagement clients remember. What we build: Template architecture across Meta's four categories, treated as a cost decision rather than a labelling exercise. Utility templates sent inside the 24-hour customer service window have been free since 1 November 2024, while a marketing template outside that window is billed every time. So the design question becomes what earns the customer's opening message: the inbound is the asset, and the flows are shaped to produce one rather than to interrupt with one. We write the templates, submit them, and rebuild the ones Meta rejects, which for anything promotional is a normal part of the first fortnight rather than a setback. Quality rating is your budget: Meta rates templates and numbers, tiers messaging limits at 1,000, 10,000, 100,000 and unlimited unique recipients per rolling day, and pauses templates whose quality falls. A programme that hits its tier ceiling on launch day and a programme that gets a template paused over a subject line look identical in a revenue report and are opposite problems with opposite fixes. We instrument both: per-template quality reviewed weekly, block-and-report rate treated as the leading indicator rather than the post-mortem, and a written volume plan that assumes the next tier is not granted on schedule. RCS and the second channel: Apple added RCS support in iOS 18 in September 2024, which is why US reach is now worth modelling instead of assuming. Verified sender branding lifts reply rates and does nothing whatsoever for consent: an RCS marketing message to a US mobile is a message under the TCPA and needs the same prior express written consent as SMS. We do not treat a change of channel as a consent event, and we will not migrate an SMS list into RCS marketing on the argument that it is a richer format. Sector notes: In marketplaces the supply side earns this channel and the demand side usually does not: a booking to confirm or a shift to accept is a conversation, a weekend promotion is a broadcast wearing a conversation's clothes. In recruiting, interview scheduling and document collection carry the load, and candidate messaging stays clear of anything that reads as marketing. In pharma and medtech, patient-facing conversation is built on the assumption that a reply may contain an adverse event or personal health information: intake is screened, routed the same business day, and no health inference is written back into a marketing profile. The handoff: Every flow has a defined exit to a human, a stated response window shown to the customer, and a rule for what happens outside working hours. Automation without that exit produces the complaint, and in this channel the complaint arrives as a block you cannot appeal. Not included: BSP contract negotiation on your behalf, though we will tell you exactly what to ask for. Agent staffing. Translation beyond English and Portuguese; we brief your translators and review the variables. Free-form NLU model work, because the flows we build are deterministic, and if your case genuinely needs open-ended understanding you want a different supplier. Not for you if: You want the email calendar mirrored into WhatsApp. Or you are looking for a channel where the unsubscribe pressure of email does not apply; it applies harder here, and it is permanent.