Status and tag sync between Front and Gmail/Office365
If you connect your Gmail or Office365 account in Front and utilize both tools alongside one another, you might experience a situation where you archive, delete, or tag a conversation within Front, but the same conversation doesn't reflect the change in Gmail/Office365 - or vice versa, the action you take in Gmail/Office365 is not reflected in Front.
Puzzled? 🤔 You're not the only one.
Front has specific behaviors that are unique to our platform and may not translate over into Gmail or Office365. Here are some of the unique behaviors that will sever the sync between your conversation in Front and that same conversation in Gmail or Office365:
- Moving a conversation to an inbox where the initial message was not received from. (i.e. a message was sent to email@example.com and a user moves that message to the sales inbox - that will sever the connection).
- Replying to a conversation from a different Gmail or Office365 account, other than where the message originated from. (i.e. a message was sent to firstname.lastname@example.org but you reply with your own email address, email@example.com).
- Changing the threading mode in Front so that the messages thread according to a Front logic instead of the native Gmail or Office365 logic, in which case the sync must stop in order to respect the new Front threading.
Note: While most status changes made in Gmail will sync to Front, Gmail snoozes are not compatible with Front.
You should not have the same account open in Gmail/Office365 and in Front. Navigating through Gmail/Office365 may trigger actions you do not intend to within Front, such as unarchiving conversations. To have the optimal experience, only utilize Front to handle the email channels you've connected.