All ideas

This feature is available with twilio SMS, but it would be very useful to send the same text message to many clients and have each one sent separately in a different conversation. Similar to the way sequences work, but with text. We run a service ...

When you have an OOO reply on, Front thinks the email that was sent in is read. It would be better to remain unread since it is just an automatic reply.

Ability to choose the trigger: archive or move, but not both as is the case today.

The ability to set a global inactivity period for all inboxes. At present Close conversation segment if inactive for can only be set on a per inbox basis. Creates a massive manual lift if a company needs to mass update all their inboxes.

Currently it's not possible for team's to update their Account SID or Auth Token within the channel settings of their Twilio SMS channel. To update their credentials they have to reach out to the Support team which can take some time for a respons...

At the moment, our Analytics paradigm is that you report based on context at event time (or events happening within the Analytics segment). After that segment is closed you cannot update that data anymore. For instance, you cannot add a tag and re...

Directly unsubscribe a user from a conversation via rules (for example unsubscribe the teammate that assign the conversation to another teammate) at this time.

Mass changes for large teams in shifts are difficult to adjust in the product. Uploading via CSV would reduce the time needed to take these actions.

It seems to me like counting throttled API calls against our API call limit is punitive and the root cause for these snowballing outages. This is compounded by the fact that we are relying on Zapier for these api calls and can't finely control the...