Problem Message templates only save body content, so users must manually add recurring recipients (To, CC, BCC) each time. Request Allow message templates to include pre-filled To, CC, and BCC recipient fields.
Problem When viewing a long conversation, there's no quick way to jump back to the beginning. Request Provide a keyboard shortcut or button to jump to the first message in a conversation.
Problem Admins cannot enforce consistent email signatures across the organization — users can set any signature, leading to inconsistent branding. Request Allow admins to define and enforce company-wide email signature templates, with optional per...
Keep subject line visible in composer and message view
Problem The subject line is hidden or collapsed in the composer and individual message view, making it hard to review or edit. Request Always display the subject line in the composer and when viewing individual messages.
Localize the chat widget for non-English languages
Problem The chat widget is English-only — all UI text (buttons, prompts, chatbot flow labels) cannot be translated for non-English customers. Request Support localization of the chat widget, including the customer details form, 'Start new conversa...
Problem Managers can't see how conversation volume in their team's backlog is changing over time, making it hard to understand workload trends. Request Show how many conversations were in each status (Open, Snoozed, custom status) at specific poin...
Problem We need to programmatically access CSAT scores and survey data from external systems for analytics and reporting. Request Expose API endpoints (e.g., GET /analytics/csat) to retrieve CSAT scores with structured data including score, review...
Problem There is no centralized place to see all conversations where you were @mentioned — mentions are scattered across inboxes and easy to miss. Request Add a notification center or activity view that aggregates all @mention activity for the cur...
Request Create rules triggered by CSAT scores, with filtering by score range (e.g., 1–3) and submitter type (human or AI). Make the score and submitter info accessible via dynamic variables.