All ideas

We can't manually configure chat messages to refresh for the end-user. If someone sends us a message and we solve their problem, there's no way to manually make the chat history clean up/mark it as resolved so they can send us another message. Thi...

When chatting with a customer, have the ability to see their current geographic location. This is important for businesses who have to comply with export restrictions.

Load balancing rule conditions are checked when a conversation *enters* the queue, but not when Front tries to assign. Ex: - Rule says "when inbound, if in inbox A, then assign load balance" - Conversation comes in inbox A, no teammate capacity, g...

The current jira integration rule to add a comment to a jira ticket does this as an external comment so everyone subscribed to the Jira ticket can see. It would be great to edit the built in rule so you can choose if the comment is left as interna...

AI features should come to individual inboxes as well. It seems like all the features are for the shared inboxes but we have most of our interactions coming through individual mailboxes.

Similar to how users can tag an email while composing a new one, users should have the ability to tag a discussion while composing one, especially since you can do it after the fact anyway.

To be able to set it to dd-mm-yy or mm-dd-yy

Each time we send a message to the customer, a notification sound should alert them. This will enhance our ability to offer effective support, enabling them to respond promptly to our messages.

Provide an overview off all message templates when doing housekeeping and auditing. This could be a global export and/or per-Workspace.