All ideas

It would be very helpful if there was a condition in rules that allowed you to trigger a rule based on what Front user performed the originating trigger/action. For example, we have an SLA set up but we have a tag that will exclude a message from ...

Current State Currently, SLAs will only trigger when either a conversation is created, or an inbound reply is received. Requirement Provide additional triggers for starting an SLA countdown, including: Ticket unsnoozed Time since last outbound rep...

Must be able to review and improve content and see how cards are being used.

Support WhatsApp group chat. Note: This is not currently supported natively in the WhatsApp API.

Have the option to be notified/export audit logs. This can be via webhooks and/or a dedicated API endpoint. This is useful for: Monitor changes in workspace configuration on internal dashboards Add logs into SIEM platforms like Sentinel

Ability to schedule send a comment, as is currently possible with emails. Linked to internal task management use case - allowing an admin to plan ahead and schedule the notification in a timely manner.

Viewing more metrics like Csat or Smart QA grades on Topics

I would like a way to see at a glance all my unresolved or opened tickets and a breakdown how how long these conversations have been opened. Currently there is no visibility how long a ticket is in a status outside until it is resolved

Use frequently asked questions from emails or conversations to generate an actual FAQ for the front Knowledge Base. Use email context to identify gaps in content and generate articles using AI.