When an agent is composing a reply to a conversation and a new inbound message arrives from the customer before the agent sends, Front currently has no mechanism to alert the agent that their reply is no longer responding to the latest message in the thread.
This creates a risk of:
Sending a reply that doesn't address the customer's most recent message
The new inbound message being silently archived along with the conversation if Send & Archive is used
Missed customer messages going unnoticed
A fail-safe mechanism similar to the one built into Outlook would resolve this. In Outlook, when a user attempts to reply to a message that is not the latest in the thread, a warning is displayed along the lines of "you are not replying to the latest message".
The requested feature: A pre-send intercept or warning prompt that alerts the agent when a new inbound message has arrived on the conversation they are currently composing a reply to, giving them the opportunity to review the new message before sending.
Why this matters: For teams managing high volume, time sensitive client communications, missing a client message due to a timing issue is a meaningful operational risk. This is a standard safeguard in Outlook that agents are accustomed to and its absence in Front is a genuine workflow gap.
Current workaround suggested by Front support: Using Send instead of Send & Archive and manually checking for new messages before archiving. This is not a reliable safeguard as it still allows agents to send replies that don't address the latest message.
Your idea is now live and open for voting.