All ideas
Sort by:
Trending
Status:
Showing 2067
3
VOTE
Allow multiple people assigned to one conversation
We are a large organization where we have multiple teams working in parallel with multiple stakeholders, there are times when two individuals from two different teams have to be responsible and responding on the same ticket. Understand there is th...
5
Backlog
3
VOTE
5
VOTE
Don't require signature to set sender info
Currently, in order for the sender's name to appear in an email to the recipient, a signature must be used. It would be nice to pull the sender's name from their Front profile or allow it to be set elsewhere without the need to create a signature....
2
Backlog
5
VOTE
Add 'Draft Created' as a Trigger for Rules
When a large customer is using the API with a singular custom channel to create drafts in batches, there is a manual triage component in terms of routing the Draft to the correct place. If Front could look at the content on the draft and take acti...
0
Backlog
1
VOTE
Utilise Ticket Statuses in Company Rules
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...
0
Backlog
1
VOTE
4
VOTE
7
VOTE
2
VOTE
Allow auto-installed apps to be disabled
Certain applications (e.g. those with only a channel type) appear "enabled" in the app store and have no way to disable them. This makes it hard to understand what external services have access to Front data. There should be a way to remove these ...
0
Backlog
9
VOTE