Shared chat, guided setup, and workflow draft control

Teams can now collaborate in shared chats, guide new self-serve users through a first-run setup, and manage workflow changes with more control.

Collaborate in shared chat

Teams can now work in the same chat thread instead of splitting work across separate conversations. Shared chats are visible across the organization, active participants can be seen from the chat list, and messages show who said what when more than one person joins. If someone starts an action that needs confirmation, that confirmation stays with the person who started it.

Guide first-time users to a review

New self-serve organizations can now start with a skippable walkthrough that helps them add a sample chart or their own PDF, ask a question with citations, add a sample policy or import one, and run a first review. This is limited to organizations created through sign-up. For those organizations, some features remain locked, and usage limits apply to chat, policies, and reviews.

Keep multiple workflow drafts

Workflow builders can now keep more than one named draft for the same workflow. You can create drafts, switch between them, discard a draft, publish one without losing the others, and revert while keeping alternate drafts available. Draft names must stay distinct even when capitalization or extra spaces differ, which helps prevent near-duplicate versions during review.

Start workflow edits from chat

You can now begin a workflow change from chat and continue it in the workflow builder with the same request carried over. The builder opens the work as a draft, shows a confirmation step before applying proposed changes, and asks for confirmation again before publishing. This gives teams a clearer path for updating an existing workflow without starting over.

Smaller improvements

• Desktop chat now matches more of the web chat experience, including chat search, shared header actions, and My or All history controls for admins.

• The Usage page now includes chat credits and updated contact flows. Availability remains turned on per organization.

• Organizations with desktop beta access can now find a download page, and people without access see a clear not-available-yet message.

• Admins can turn on a nested inbox view for split child documents so related items stay grouped under a parent. It starts off by default and does not apply when grouping by patient.