Inbox links, deep links, and reconnect prompts that work
Inbox context-panel links are now real and correctly encoded, the open thread stays in the URL so deep links and the back button work, and expired connectors prompt a clear reconnect.
Working from the inbox should feel like the rest of the web — links you can click, a back button that works, and clear errors when something needs your attention. Three things were not living up to that: dead links in the thread context panel, deep links and the back button that did not behave, and cryptic failures when a connector's access had quietly expired. Small as each one sounds, together they made the inbox feel slightly broken in ways that were hard to put your finger on.
What was happening
The context panel beside an inbox thread showed the campaign, connector and team it related to, but those were not real links — there was nothing to click through to, and where links did exist they could be malformed by improper encoding. The open-tracking tooltip showed up even in cases where open tracking did not apply, which was misleading. The inbox also did not keep the page URL in sync with whichever thread you had open, so you could not share a direct link to a conversation, and the browser's back and forward buttons did not move you between threads the way you would expect. Expired connector access is a routine event — tokens do not last forever — but when a Google or Microsoft connector's access expired, the error it produced looked like a serious malfunction rather than a two-click fix, giving no hint that the answer was simply to reconnect.
What we fixed
In the thread context panel, the campaign, connector and team references are now real, clickable, correctly-encoded links that take you straight to the right place. The open-tracking tooltip only appears when open tracking actually applies to that thread. The inbox now keeps the page URL in sync with the thread you are viewing, so deep links point to the exact conversation and the browser back and forward buttons move between threads as expected. And when a Google or Microsoft connector's access has expired, you now see a clear message telling you to reconnect, instead of an opaque failure.
Why it matters
The inbox now behaves the way you expect a web app to. You can jump from a thread straight to the campaign that produced it, the connector that is sending it, or the teammate who owns it — without copying identifiers or hunting through other screens. You can share a link that lands the recipient on the exact conversation, and you can use the browser back and forward buttons to move through threads without losing your place. The open-tracking tooltip only appears when it is actually telling you something true. And when a connector needs reconnecting, the message says so plainly — so you spend a few seconds reconnecting instead of puzzling over an error that never explained itself.