Cut WhatsApp API costs, keep the conversation
Since October 1, Meta bills every reply sent inside the customer service window. With Talqui, WhatsApp opens the conversation and the rest happens on Web Chat: one click, the same agent and the history.
7-day free trial, no credit card required.
Billed messages
3/ 10
$0.0204 for this conversation
0 on Web Chat, no fee
US$ 0.0068 per service message in Brazil
Since October 1, every WhatsApp reply has a price
Until September 30, replies sent inside the 24-hour window were free. Now each one is billed, and the conversations where your team works hardest became the most expensive ones.
US$ 0.0068
per service message in Brazil
The same rate for 10 thousand or 10 million messages a month.
| What | Since Oct 1, 2026 |
|---|---|
| Reply inside the 24-hour window (service message) | US$ 0.0068 each, in Brazilbefore: free |
| Utility template sent inside the window | Billedbefore: free |
| Free allowance per phone number | 1,000 a month, no rollover |
| Conversation started from a Click to WhatsApp ad | Still free for 72 hours |
Source, checked in October 2026: Meta for Developers
What Web Chat saves in your operation
The formula to cut official WhatsApp API costs without leaving WhatsApp or switching off your number. Set the controls and see how much your operation saves by moving part of its conversations to Talqui's Web Chat.
Savings per month
$857
monthly cost = conversations per day × 30 × US$ 0.0068 × [messages × (1 − % on Web Chat) + 3 × % on Web Chat]How we calculate
One rate, no tiers
US$ 0.0068 per service message, the rate in Brazil since Oct 1, 2026. Meta offers no volume discount in this category.
3 messages before the handoff
Every conversation moved to Web Chat still uses 3 WhatsApp messages: the first replies and the invite. The rest has no fee.
What we left out
We leave out the 1,000 free messages per number and the free conversations from ads. At scale they barely change the bill.
A projection with a 30-day month, not an invoice: Meta's billing depends on the customer's country and the category of each message.
One conversation, two channels, the same agent
The customer downloads nothing, creates no account and fills in no form. Your team doesn't hunt for the conversation or reassign it.
The conversation starts on WhatsApp
As always: a template from your company or a message from the customer opens the conversation.
The agent sends the invite
In "Invite to another channel", Talqui creates the link and drops it into the composer as a draft, so the agent can adjust the wording. With the automatic reply on, the invite also goes out on its own on the first message.
One tap on the link
Web Chat opens in the phone's browser, with the customer already identified and the recent messages on screen.
Same agent, same inbox
The agent is taken to the new conversation with the notice "The contact switched channels". If it was waiting in the queue, it stays in the queue.
Support continues, with no fee
Photos, audio, documents and videos up to 12 MB. The WhatsApp conversation is closed as a channel handoff, with no goodbye message.
The conversation continues, it doesn't start over
The customer doesn't repeat the problem and your team doesn't switch tools. When the link is opened, Talqui moves the conversation to Web Chat with the same agent, the same inbox and the recent history.
Security
The link works once, lasts 24 hours and only opens conversations in your workspace. If the customer comes back the next day, the agent sends a new one in one click.
No screen switching
The agent stays in the same shared inbox: Talqui takes them straight to the new conversation, with a notice that the contact switched channels.
The shared inboxThe history comes along
Web Chat opens with the contact's recent messages, already identified and with no form. The customer reads it as a continuation, not as a new ticket.
Same inbox and queue
The conversation stays in the same inbox and, if it was in the queue, it stays in the queue. WhatsApp closes as a channel handoff, with no goodbye message, and reports tell a handoff apart from a resolution.
Move long conversations to Web Chat
The savings come from the longest conversations, the same ones that got more expensive in October. For a quick question, like a bill's due date, staying on WhatsApp is perfectly fine.
Technical support
Troubleshooting with lots of back and forth, screenshots and voice notes.
Onboarding and implementation
Conversations that run for days, with documents, contracts and setup.
Collections and renegotiation
Sensitive conversations where the agent needs time, not a stopwatch.
Consultative sales
Quotes, proposals and several rounds of questions before closing.
How to get started
- 01Measure the average business messages per conversation in each queue.
- 02Start with one queue, like technical support or onboarding.
- 03Adjust the invite text to explain the benefit to the customer.
- 04Compare resolution time and satisfaction, then extend to other queues.
FAQ
Questions about moving WhatsApp chats to Web Chat
What customers and support teams usually ask before turning it on.
Still have questions? Write to support@talqui.com
Does the customer need to install an app or create an account?
No. They tap the link and Web Chat opens in the phone's browser. The customer arrives already identified, with no form, and sees the recent messages of the conversation.
Is the link safe for customer data?
The link uses HTTPS and a random single-use token that expires in 24 hours and only works for that contact, that conversation and your workspace. The data that identifies the conversation travels in the URL fragment, which browsers don't send to servers, so it doesn't appear in logs, proxies or analytics tools.
What if the customer doesn't tap the link?
The conversation goes on over WhatsApp, with the same agent. The link is valid for 24 hours; if it expires, the agent sends a new one in one click.
Does the agent lose the conversation or its history?
No. The Web Chat conversation stays with the same agent and in the same inbox, and Talqui moves the agent to it in real time. If the conversation was still in the queue, it stays in the queue. The customer sees the recent messages at the top of Web Chat.
What can the customer send on Web Chat?
Text, photos, audio, PDF and Office documents, spreadsheets and videos up to 12 MB per file, and they can reply to specific messages, just like on WhatsApp.
Do I have to move every conversation to Web Chat?
No. You choose how the invite goes out. With the automatic reply on in the official WhatsApp connection, every new conversation gets the invite on its first message. Without it, the agent decides when to send it, in the queues and conversation types where it makes sense. Short exchanges can stay on WhatsApp.
Can the invite be sent automatically?
Yes. In the official WhatsApp connection settings, turn on the automatic reply and the Suggest a channel switch option, picking Web Chat as the destination. The first message of every new conversation gets the automatic reply with a button that takes the customer to Web Chat, with no one on the team having to act. Agents can still send the invite by hand.
How do reports handle the channel handoff?
The WhatsApp conversation is closed with a channel handoff reason, without a goodbye message to the customer, so your reports can tell a handoff apart from a resolution.
What do I need to use it?
WhatsApp and Web Chat connected to Talqui. The invite lists only your company's active channels and also works in other directions, like inviting a Web Chat visitor to continue on WhatsApp, Telegram or Instagram.