Ticket Statuses currently cannot be used as conditions or actions in Company Rules - they can only be used in Workspace Rules. This means the rules need to be duplicated for every workspace to apply to all inboxes. This is a time-consuming, manual...
Improve visual difference between comments and messages
With the new redesign, particularly for SMS and WhatsApp channels, the internal comments vs actual messages are visually very similar and difficult to distinguish. This is particularly true for our SMS and WhatsApp channels.
Customer wants the ability to embed their public-facing KB to their website, and then be able to search articles directly in their website. If the public API included search functionality, this would be doable
The limit is set to 2000 characters currently, it would be nice if this could be increased to avoid needing to send multiple messages or direct the customer to another form of communication i.e. email when dealing with a more complex inquiry.
Ability to set a Primary Email & Phone for our Front Contacts
This would help our team set up our customers with their preferred email & phone number for certain communication. This would still allow us to still have additional emails and phone numbers available for our team to better help our customers....
API: Support multiple recipients on custom channels
I'm building an integration with an external SMS provider, which supports group conversations. Right now, Front's Receive custom messages and Sync inbound message API endpoints do not allow me to receive a message from a sender which was addressed...
When snoozing a conversation in an Intercom channel in Front, this is synced to Intercom as "Archived" which is not intended. Request is to support Snooze activities fully in both systems. https://developers.intercom.com/docs/references/rest-api/a...