Your customers are already on WhatsApp Your campaigns are not

When someone leaves a cart in your store, the platform fires an event and Revio receives it by webhook with the contact, the products and the amount. That kicks off a journey with four pre-send checks: that the contact has valid consent, that they are not on the suppression list, that the product still has valid stock and price, and that they have not received another campaign within the frequency window you defined. Only then is the message chosen. If the customer wrote to you in the last 24 hours, the conversation is still open and the text goes out free-form; if not, it goes out as a marketing template approved by Meta, with the variables filled in with real order data. The first touch usually goes out after 30 minutes, the second after 4 hours and the third the next day, and the sequence cancels itself if the purchase closes in between. When the customer replies, a 24-hour window opens and the conversation passes to Sellium or to your sales rep with the full history. The sale is attributed to the campaign that started it, not to the last click.

All of the channel's mechanics rest on a distinction almost nobody explains before selling: inside the 24-hour window you can write whatever you want; outside it you can only use a template Meta has reviewed in advance. The window opens when the customer writes to you and resets with each of their messages; your replies do not extend it. Conversations that start from a click-to-WhatsApp ad add a free window: if you reply in time, Meta doesn't charge for messages for up to 7 days, according to its pricing documentation. Outside the 24-hour window, the approved template comes in: a text with a fixed structure, variables in curly braces and a declared category. Meta recognizes three categories: marketing, utility and authentication. The category is not an administrative detail: it sets the price and the review criteria. An order reminder is utility; a promotion is marketing, even if you word it like a notice. Every template is submitted for review before it is used and can come back rejected for formatting, for suspicious links or for a wrongly declared category. That is why the campaign calendar is built around templates that are already approved: approval is part of the schedule, not a last-minute formality.

Your contact base matters more than the message. Revio does not send marketing to a contact who has not given consent, and that consent is stored with date, channel and wording: it is your evidence with Meta and with your country's regulator. The capture points that work are the natural ones: a dedicated WhatsApp checkbox at checkout or at customer sign-up, an inbound conversation from someone who already wrote to you, the QR code in your store or on your packaging, and click-to-WhatsApp ads. A purchased list is not a contact base; it is a burned number with a few extra steps. On the other side is the opt-out: a keyword removes the contact instantly and adds them to the suppression list, which is honored in every following campaign with no manual work. That back-and-forth feeds the metric that matters most in the long run, your number's quality rating: Meta calculates it from the blocks and reports you generate, and your daily sending limits depend on it. Watching frequency and relevance is not a courtesy; it is what keeps the channel open.

The channel is paid by usage, not by license, and the cost has two separate line items. The first is Meta's fee, charged per message, which varies by country and by template category: in every market on Meta's rate card, marketing costs more than utility or service, and service messages (replies inside the 24-hour window) get 1,000 free per number each month. You pay Meta directly for those messages through your own WhatsApp Business account, and the current rate for your country is in Meta's official rate table. The second is Revio: a one-time implementation, quoted for each company, that leaves the campaigns up and running, and a monthly subscription with AI credits, which you can expand if your sending volume grows, with no minimum term. The useful question is not how much a message costs but how much each dollar you send brings back. The full breakdown of the model is in our WhatsApp Business API cost guide, and the commercial terms are on our pricing page.

Revio does not replace your systems; it reads them. The standard connection is to your store (Shopify, VTEX, Tiendanube, WooCommerce), your CRM (Salesforce, HubSpot) and your payment provider (Mercado Pago), so the purchase closes in the same chat. What it needs on the other end is simpler than it looks, and it is also where projects fall behind: phone numbers normalized with the country code, a consent field per contact, an order history with date and amount, and a catalog with queryable price and stock. Without history there is no segmentation by recency; without stock, the message offers what you cannot deliver. If your data lives in an on-premise ERP or in a spreadsheet, it still connects: what changes is the latency, with a scheduled sync instead of a real-time webhook, not the campaign logic. Whatever is missing at kickoff does not block the first campaign: the source that defines the segment comes first and the rest is added later.

Better to say it before the demo. Revio does not send bulk messages to lists without consent: that is not a product limitation, it is the rule that keeps your number alive. Nor does it guarantee that Meta will approve a template; we write it and manage the review, but the decision is Meta's. It is not a sales agent: Revio opens the conversation, and the one that advises, quotes and collects payment inside the chat is Sellium. And it does not replace your email tool or your social media management; it works alongside them. There are three scenarios where it is not a fit yet. The first is a small contact base or one with no purchase history: without recency or repeat purchases, segmentation has nothing to hold on to and the return does not pay for the implementation. The second is an operation that cannot keep up with the replies: if the message triggers questions nobody answers, the channel degrades fast. The third is a catalog or price list that does not live in any queryable system, because then every campaign goes back to being manual work. In all three cases, the honest move is to get the data in order first and run campaigns afterward.