Skip to main content
Tawked Chat is the inbox of the WhatsApp number connected to your application. It opens on its own when the number is connected, at chat.tawked.com and in the Tawked Chat app for phones. Your team answers customers there; your code does not.

​
What developers need to know

  • It has no API. Your code sends template messages with Tawked Notifications. Customers’ replies are read and answered in Tawked Chat, by people.
  • Your sends appear in the conversations. Every message your code sends through POST /v1/whatsapp/messages shows in the customer’s conversation, so the person who answers sees what the customer received. The code of an authentication template shows as ••••••.
  • Replies do not reach your webhook. The webhooks carry the status of what you sent (message.sent, message.delivered, message.read, message.failed), never what a customer writes.
  • STOP is handled for you. A customer who writes STOP to your number is opted out of the application’s marketing, and marketing sends to them answer 422 consent_opted_out. See Marketing and opt-outs.
  • One number, one inbox. An application has one number, so a second inbox is a second application with its own number.

​
Who answers

The account owner always has the inbox. Everyone else is added on the application’s Chat → Support team page, by mobile number, with one of two roles: The inbox roles are separate from the console’s roles on Members: someone can answer customers in Tawked Chat without opening the console, and a developer in the console does not see the inbox unless they are on the support team.
Last modified on October 6, 2026