Conversational Commerce Flows Measured Against Holdout

Holdout first: A ten percent holdout is carved out before the first flow goes live and stays out for the length of the engagement, and every number we report to you is incremental revenue per thousand sends measured against it. The reason is unpleasant and consistent: when we have run this properly, somewhere between a third and two thirds of the cart revenue a messaging platform attributes to itself would have arrived anyway, through email, through a return visit, or through the same customer finishing the order twenty minutes later. If your board has been shown attributed recovery figures with no holdout behind them, expect the real number to be materially smaller, and expect us to say so in the first readout rather than the fourth. Flows we build: WhatsApp Flows, meaning actual forms rendered inside the thread: screens defined in flow JSON, a data exchange endpoint you host, and the key pair registered against your WABA so the payload is encrypted end to end. Product and multi-product messages within the thirty item limit. Order detail and payment messages where the market supports them. Around those, the operational set that carries the volume: back in stock, delivery exception, address correction before dispatch, return initiation. Each one is triggered by a system event and each one is priced by category before it is written, because a flow that opens with a marketing template costs several times one that opens with a utility template. Travel disruption: The flow that consistently pays for itself. A cancellation or a schedule change pushes the options into the thread, the passenger confirms in the thread, the PNR is referenced and there is no link to a login screen at any point. It is measured in deflected call minutes and completed rebookings, not in opens, and we agree the deflection baseline with your contact centre before build so the result is theirs as well as ours. The human handoff: Every flow has one defined exit to a person, with the thread transferred through the handover protocol carrying the full context, and a stated response window during staffed hours plus an honest message outside them. A flow with no exit is a maze, and it produces blocks rather than complaints, which means you stop hearing about it while it keeps costing you. Excluded: No free-form language model quoting price, stock or availability, and none making a statement that binds you. Where generation is used at all it sits behind a deterministic layer that owns the numbers. No bot presented as a person, and no countdown, fake scarcity or manufactured urgency inside a channel the customer treats as private, which is the fastest way to convert a subscriber into a block. We do not build website chat widgets. Say no if: Average order value under roughly forty euros, where the template cost and the incremental margin do not meet. No order or inventory API, since a flow that cannot read state is a broadcast wearing a form. And any team that is not prepared to keep the holdout intact for a full quarter, because the alternative is a dashboard that always agrees with the invoice and we will not sign our name to that.