Actions that break the sync between Front and Gmail/Office 365

If you connect your Gmail or Office 365 account in Front and utilize both tools alongside one another, you might experience a situation where mark a conversation as spam, but the same conversation doesn't reflect the change in Gmail/Office 365. Or vice versa, the action you take in Gmail/Office 365 is not reflected in Front. This may happen if a specific action breaks the spam status sync between Gmail/Office 365 and Front.

Front has specific behaviors that are unique to our platform and may not translate over into Gmail or Office 365. Here are some of the unique behaviors that will sever the sync between your conversation in Front and that same conversation in Gmail or Office 365:

1. Moving a conversation to an inbox where the initial message was not received from, e.g., a message was sent to marketing@front.com and a user moves that message to the Sales inbox.

2. Replying to a conversation from a different Gmail or Office 365 account, other than where the message originated from, e.g., a message was sent to marketing@acme.com but you reply with your own email address, sophia@acme.com.

3. Changing the threading mode in Front so that the messages thread according to a Front logic instead of the native Gmail or Office 365 logic, in which case the sync must stop in order to respect the new Front threading.

4. Splitting a conversation into separate threads.

5. Merging conversations. Merging can occur automatically through a smart merge or can be triggered manually.

You should not have the same account open in Gmail/Office 365 and in Front. Navigating through Gmail/Office 365 may trigger actions you do not intend to within Front. To have the optimal experience, only utilize Front to handle the email channels you've connected.