← Back to the changelog
FeatureWeb App

Move chats to another project

You can now send one chat or a batch of them into a different project, with their messages and active share links coming along.

You start a chat in one project and later realize it belongs somewhere else. Until now, copying the content across by hand was the only way out.

Move to project

Pick a chat, or select several, and choose Move to project. A modal lists the other projects in your organization, and you can search by name or sort by most recent or create date. If the right project does not exist yet, create one from inside the modal without losing your selection.

Each project in the list shows its description, when it was created, and who created it, so you can tell similar projects apart before you commit.

What travels with the chat

Messages and active share links move with the chat. Project knowledge and integrations the chat referenced stay in the original project, and the modal says so before you confirm.

Confirmation and next step

After the move, Chief confirms how many chats landed in the destination and offers to take you there. Stay where you are, or jump straight into the destination project.

Some chats cannot be separated from what they belong to. A chat attached to a live session, a transcription, or an automation action stays put, and you get a message explaining why rather than a silent failure.

Open a chat's menu to try it on the next one that ended up in the wrong place.