Sessions and continuity

Know when to continue an Agent session and when to start a new one.

Use one session for one coherent outcome.

Continue when the job is still the same

Keep working in the same session when you are refining, correcting or completing the same task. The existing conversation, files and activity are useful context.

Start a new session for a new outcome

Start fresh when the work changes to a genuinely different job.

You do not need to keep one enormous conversation alive just to preserve how your organisation works. Project context, Skills and Memory can carry useful information across sessions.

Give the current task the context it needs

A new session still needs the specific case information that matters now: the relevant customer, order, file, time period or exception.

Persistent context should reduce repetition, not make the Agent guess which case you mean.

Slack and Teams

The same principle applies in Channels: keep related work together and start a new thread or conversation for unrelated work.

For channel routing and Project scope, see Agent in Slack and Agent in Microsoft Teams.