Status: Open

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.

The customer’s WhatsApp number is not visible in the main chat window. However, I can see it when I view their contact card. Please fix this so the number appears directly in the chat section.

I have a concern regarding the deletion process of conversations/tickets. What happens to them once they are deleted? Permanently deleting them immediately might cause issues, especially if the deletion was accidental. Could we consider archiving these items for at least

The Automated Response should only be sent the first time the customer sends us an email (ticket) not on every reply by them. Thanks