WhatsApp to Web Chat: keep the conversation, drop the per-message fee

On October 1, 2026, WhatsApp starts charging businesses for service messages: the replies your agents and bots send inside the 24-hour customer service window. For almost two years those replies were free. Now each one has a price.

Most platforms handled the change the same way. They sent an email with the new rate card, maybe a help article, and moved on. A few didn't even do that. The cost landed on their customers' invoices, and that was the end of the conversation.

We handled it differently. Over the past few weeks we sat down with our largest customers and partners, opened their numbers, and worked through one question together: how do you keep WhatsApp as your front door without paying for every message that follows?

This article is the answer we shipped. It's long on purpose. If you run a contact center, a support operation or a sales team that lives on WhatsApp, you'll find what changed, how the new feature works (including the technical side), and a cost projection for an operation handling 30,000 conversations a day.

1. What changed on October 1, and why it hits large operations the hardest

WhatsApp Business Platform pricing is per message. Until now, the expensive part was the template: the first message a business sends to start a conversation (marketing, utility or authentication). Once the customer replied and the 24-hour window was open, everything your team sent back was free.

That second part is what ends now. According to Meta's official pricing documentation, starting October 1, 2026:

• Service messages are billable. Every free-form reply sent inside the 24-hour window is charged at the same rate as a utility or authentication message in the customer's country.
• Utility templates sent inside the window are billable too. They were free until now.
• There are no volume tiers for service messages. The rate stays the same whether you send ten thousand messages a month or ten million.
• Each business phone number gets 1,000 free service messages per month, reset monthly and without rollover, as detailed by 360dialog. For an enterprise operation, that allowance runs out within the first hours of the month.
• The free entry point stays. Conversations started from Click to WhatsApp ads or Facebook call-to-action buttons remain free for 72 hours.

In Brazil, the rate is US$ 0.0068 per message. On a single message, that's nothing. The problem is that support conversations aren't single messages. A billing question, a technical troubleshooting session or a contract negotiation easily takes ten, fifteen, twenty replies from your side. Multiply by every conversation, every day, and a rounding error becomes a budget line.

There's a second effect that's easy to miss. Until now, a long conversation and a short one cost the same. From October on, the conversations where your team works hardest become the most expensive ones: complex support cases, onboarding, collections, retention. That's backwards. Nobody wants a pricing model that nudges agents to be brief exactly when the customer needs more attention.

"Yes, the cost per message is small. But if your operation is large, that cost grows with your scale, and for some companies it can make WhatsApp a prohibitive channel. That doesn't mean WhatsApp has to go. It means it has to be part of a smarter strategy, one where WhatsApp opens the conversation and the rest of the journey happens where it makes the most sense for your business."

João Miranda • Founder, Talqui

When we talked to our customers, nobody said "let's leave WhatsApp". It's where their customers are, and it's the channel people actually answer. What they wanted was a way to keep WhatsApp as the entry point and stop paying for every message after that. So that's what we built.

2. Introducing WhatsApp to Web Chat

WhatsApp to Web Chat lets an agent move a live conversation from WhatsApp to Talqui's Web Chat in one click. The customer doesn't download anything, doesn't create an account and doesn't fill in a form. They tap a link and the conversation continues in their browser, with the same agent and the recent history in front of them. From that moment on, the messages no longer go through the WhatsApp Business Platform, so there's no per-message fee.

What the customer sees

1. The conversation starts on WhatsApp, like always. Either your company sent a template (a billing reminder, a delivery update, a campaign) or the customer reached out to your number.
2. The agent sends an invite. A message arrives in the same WhatsApp chat: "Shall we continue on Web Chat? Just open the link below:", followed by a link.
3. One tap. The link opens Talqui's Web Chat in the phone's browser. The customer is already identified, so there's no pre-chat form to fill in, and the recent messages from the conversation are right there.
4. The conversation continues. The customer can type, send photos, record audio, attach documents, share video and reply to specific messages, just like they would on WhatsApp.

We tested the flow on Android, iOS and a long list of devices and browsers before this launch, and several of our active customers are already running it in production.

What the agent sees

For your team, nothing about the workflow changes. The invite lives in the conversation's shortcut menu as "Invite to another channel". When the agent clicks it, Talqui generates the link and places it in the message composer as an editable draft, so the agent can adjust the wording before sending it (a warmer tone, a short explanation, a reason to switch).

When the customer taps the link, the conversation moves to Web Chat and stays with the same agent and in the same inbox. If the agent had the conversation open, Talqui takes them straight to the new one and shows a notice: "The contact switched channels. You were moved to the new conversation." If the conversation was still waiting in the queue, it stays in the queue. Nobody has to look for it, reassign it or ask the customer to repeat anything.

This is the part we care about most. Cutting costs by pushing customers to a worse experience is easy. What makes this work is that neither side loses anything: the customer keeps their context and their media, and your agent keeps the conversation, the history and the ownership.

When to use it

WhatsApp to Web Chat pays off the most in conversations that are going to be long. A few patterns we've seen with our customers:

• Technical support. Troubleshooting sessions with many back-and-forth steps, screenshots and audio explanations.
• Onboarding and implementation. Conversations that go on for days, with documents, contracts and configuration steps.
• Collections and renegotiation. Sensitive conversations where the agent needs time, not a stopwatch.
• Consultative sales. Quotes, proposals and several rounds of questions before closing.

For short exchanges ("what's my bill due date?"), staying on WhatsApp is perfectly fine. The point isn't to move every conversation. It's to give your operation a choice it didn't have before.

3. Under the hood: how the unique link works

Enterprise buyers rightly ask what's behind a link that "moves" a customer from one channel to another. Here's how it works.

A link that belongs to one contact, one conversation and one destination

When the agent clicks "Invite to another channel", Talqui's core API creates a handoff link. Each link carries a random token generated with a cryptographic random number generator and stored together with everything it's allowed to do:

• the contact it was created for;
• the source conversation (the WhatsApp session it came from);
• the destination: the specific Web Chat connection of your company where the conversation will continue;
• an expiration time (24 hours by default);
• a status that starts as pending and changes to used when the customer opens it.

The token is scoped to your company's workspace. A link generated by one company can never open a conversation in another.

Single use, time-bound, atomic

When the customer opens the link, the Web Chat sends the token back to Talqui, and the core API redeems it in one atomic database operation: it only succeeds if the token exists, is still pending and hasn't expired, and it marks the token as used in the same step. If two devices try to use the same link at the same time, only one wins. Unknown, used and expired tokens all return the same answer, so the API reveals nothing to someone who's guessing.

If the link expires before the customer opens it (for example, they come back the next day), the agent simply sends a new one.

Nothing sensitive travels to a server log

The link is served over HTTPS, and the parameters that identify the conversation travel in the URL fragment (the part after the #). Browsers don't send the fragment to web servers, so these values don't appear in server access logs, proxies or analytics tools along the way. The Web Chat reads them locally and talks to Talqui's API directly.

What happens to the conversation

When the token is redeemed, Talqui:

1. Opens a new conversation on Web Chat for the same contact.
2. Carries over the inbox and the agent from the WhatsApp conversation (or keeps it in the queue, if it hadn't been picked up yet).
3. Closes the WhatsApp conversation with a specific reason (channel handoff), without sending the customer a closing message, so your reports can tell a handoff apart from a regular resolution.
4. Moves the agent to the new conversation in real time.

On the customer's side, the Web Chat restores the recent messages of the contact, so the conversation reads as a continuation and not as a new ticket. Media is uploaded through signed URLs, with support for images, PDF and Office documents, spreadsheets, audio and video (up to 12 MB per file).

It isn't only WhatsApp to Web Chat

The same handoff mechanism is channel-aware: it lists only the destinations your company actually has active, and it also works in other directions (for example, inviting a Web Chat visitor to continue on WhatsApp, Telegram or Instagram). We're launching with WhatsApp to Web Chat because that's where October's pricing change hurts, but the idea is broader: the conversation belongs to your company and your customer, not to a channel.

4. The numbers: a projection for 30,000 conversations a day

Let's make this concrete with an operation our enterprise customers will recognize: 30,000 conversations a day on WhatsApp. The assumptions below are conservative and easy to adjust to your reality:

• 30,000 conversations per day, 30 days per month;
• on average, 10 messages sent by the business (agents and bots) per conversation, inside the service window;
• rate of US$ 0.0068 per message (Brazil);
• when a conversation moves to Web Chat, it still uses 3 WhatsApp messages (the first replies plus the invite itself). Everything after that is free;
• we leave out the 1,000 free messages per number (irrelevant at this volume) and the free entry point from ads.

Baseline: everything stays on WhatsApp

30,000 conversations × 10 messages = 300,000 billable messages per day, or 9 million per month. At US$ 0.0068, that's US$ 61,200 per month, or US$ 734,400 per year, just in service messages. This is a new cost that didn't exist on September 30.

With WhatsApp to Web Chat

Conversations moved to Web Chat	Billable messages per month	Monthly cost	Monthly savings	Annual savings
0% (baseline)	9.00 M	US$ 61,200	–	–
30%	7.11 M	US$ 48,348	US$ 12,852 (21%)	US$ 154,224
50%	5.85 M	US$ 39,780	US$ 21,420 (35%)	US$ 257,040
70%	4.59 M	US$ 31,212	US$ 29,988 (49%)	US$ 359,856

Two things stand out. First, the savings come from the longest conversations, the same ones that became the most expensive in October. If your average conversation has 15 or 20 messages instead of 10, the savings grow accordingly. Second, the adoption rate is in your hands: it depends on which queues and which types of conversation you decide to move, not on a contract renegotiation.

Why this beats the usual alternatives

• Shorter replies and fewer messages. Asking agents to write less is a direct hit on customer experience, and it only goes so far.
• Moving customers to email or phone. It works, but you lose the real-time conversation, the history in one place and the media the customer already uses. Most customers simply don't follow.
• A generic chat link. Sending the customer to the chat on your website means starting over: new form, new queue, new agent, repeating the problem. People drop off. WhatsApp to Web Chat keeps the identity, the agent and the context, which is why customers actually make the switch.
• Negotiating volume discounts. For service messages, there aren't any. Meta doesn't offer volume tiers on this category.

How we suggest rolling it out

1. Measure first. Look at your average number of business messages per conversation by queue. That tells you where the cost is concentrated.
2. Start with one queue. Technical support or onboarding are usually the best candidates.
3. Adjust the invite message. The default text is short and neutral. Some customers prefer to explain the benefit ("so we can send you the files and keep talking without interruptions").
4. Expand gradually. Compare resolution time and satisfaction between conversations that moved and those that stayed, then extend to other queues.

Our customer success team can help you run this analysis with your own numbers.

A partner, not just a vendor

A pricing change like this is a test for every platform your company depends on. The easy path is to pass the cost on and call it "market conditions". We don't think that's our role.

Talqui's goal has always been to go beyond a product you pay for every month. We want to be the communication backbone of your company: the layer that connects WhatsApp, Instagram, Web Chat, marketplaces and your own systems, and that adapts when the rules of any one of those channels change. That's why we don't need to lock you into WhatsApp. If the best thing for your operation is to open conversations there and continue them somewhere else, we'll build the bridge.

WhatsApp to Web Chat is available now for Talqui customers with WhatsApp and Web Chat connected. As far as we know, no other customer service platform offers anything like it today. If you want to understand what this means for your operation, talk to us.

This is just the beginning of our Launch Week. Stay tuned, there's more coming.

Sources

• Meta for Developers: Upcoming pricing updates for service and utility messages
• 360dialog: Service Message Charging Starts October 1, 2026