What happens to unsent composer text when you navigate around Team

When you're writing a message in Team and need to check another conversation before finishing it, it helps to know how that unsent text behaves.

How it works

The composer keeps whatever you've typed in the box while you keep navigating inside Team — for example, if you open another Space or a Direct Message to check something and come back. This is local to the current browser tab: it isn't automatically saved to the server and it doesn't sync to another device.

When the text is lost

• If you reload the page or close the tab, unsent text is gone.
• If you leave Team for another part of Omnifox (like the customer Inbox) and come back, the composer starts empty.
• If you log out, it's lost just like any unsaved text field.

Recommended steps for a long message

1. When possible, finish writing the message before switching conversations.
2. If you have to stop mid-draft, copy the text (Ctrl/Cmd + C) before navigating away — especially before reloading the page or switching tabs.
3. When you come back, paste it (Ctrl/Cmd + V) into the composer to pick up where you left off.

Example

An agent is drafting a long message in a Space and needs to check a detail in a Direct Message before finishing it. They switch to the DM, confirm the detail, and come back to the Space: the text they'd already written is still there, ready to finish and send.

Tips

• If the message is important but not ready yet, consider using Schedule send (when available in your composer) instead of leaving it half-written for a long time.
• Avoid reloading the Team page while you have a long unsent message.

Troubleshooting

• I lost a message I was writing: if you reloaded the page, switched sections, or logged out, the text isn't kept — there's no way to recover it after that.
• My composer still has text from another conversation: this is expected if you typed something and switched Space/DM without sending or clearing it — double-check the content before hitting send so it doesn't go to the wrong conversation.