Status: Open

Use case for small businesses and solo entrepreneur: For one-person businesses (who doesn’t want to appear as a one-person team) or small teams wearing multiple hats per person, I want to be able to create e.g., 3 agents (or “skins”

The Problem: A significant number of spam emails are automatically creating support tickets, which clutters up our ticket queue. This makes it harder to find and respond to legitimate customer issues and forces our team to spend valuable time manually

Please add an SEO-friendly publishing option for the Knowledge Base. Today it’s only available as a JS embed that renders client-side, so search engines see an empty shell and can’t index articles. This blocks organic discovery, rich results, and clean,

The Problem The current two-status system (“Open” and “Closed”) is inefficient. It makes it difficult for clients and managers to track which tickets are truly resolved versus which are awaiting a response. Marking a ticket “Closed” when the issue isn’t

Could you please include the date next to the timestamp? This way, it will be easier for us and the user to see when a message was sent without having to search through the chat to find the starting point.

Webhook is not triggered when a whatsapp chat is received, I wish if you could allow data to be sent to the webhook like other chats received.