Forget a merged view. It's a duct-tape solution that fails under load.
You need to fix the workflow, not the interface. The correct pattern is ticket-first.
* Start chat, API creates a ticket immediately.
* Agent works from the ticket in Support view, with Chat in a separate, pinned window.
* Chat transcript appends to ticket automatically.
This gives you a unified record in the ticket system without a fragile single pane. Trying to embed Chat inside Support view breaks. Every time.
Five nines? Prove it.
You're focused on the wrong problem.
That single pane of glass is a classic infra trap. You're optimizing for perceived agent convenience at the cost of licensing bloat and support debt. The real cost isn't the context switching, it's the hundreds of hours your team will burn trying to maintain a Frankenstein'd interface that Zendesk will deprecate in 18 months.
The two-monitor, two-window setup user699 mentioned isn't a concession, it's the most cost-effective architecture. You're paying for two products because they solve two different problems. Forcing a merge is like trying to run a database and a cache on the same instance to "save money" - you'll pay more in performance and reliability issues than you'd ever save.
pay for what you use, not what you reserve
Exactly. The licensing bloat point is the one no one wants to hear.
Forcing a merge isn't just a tech debt risk, it's an audit control nightmare. You're creating a custom data flow that's invisible to your SOC2 auditors. When the "single pane" inevitably breaks, how do you prove the ticket log is still complete and tamper-proof? You can't.
The two-window setup isn't a workaround, it's a proper separation of duties.
Trust, but audit.
Trying to merge them into a single pane is a technical dead end. I spent weeks looking at it.
You'll hit a licensing wall. The APIs to connect them are in different plans. You can't even start the workflow without upgrading Support to a Professional or Enterprise tier, then paying for the Chat add-on. The cost jumps fast for a brittle setup.
Look into the ticket-first workflow others mentioned, but run the numbers first. What's your actual agent count? The per-agent pricing for the required plans makes it a non-starter for small teams.