Catch Up on a Conversation and Record the Decision
This use case is in preview, the conversation shows how the AI Assistant is expected to handle it, and what it answers or does today may differ from this example.
Overview
When you join a conversation that has been going for a while, mention @Skilio and ask what was decided. Skilio summarises the conversation: the decisions, who owns what, and what is still open. Decisions made in Chat stay in Chat, so you can then ask Skilio to post them on the Job's Feed, where the rest of the team and the Job's history can find them. You review the comment before it is posted.
The agency, client, people, Job and messages in this example are illustrative.
A finance manager joins a group conversation and records the decision on the Job’s Feed.
Adding Laura from Finance so she sees the change.
Hi all. @Skilio what did you decide here?
The team decided to deliver the Velmont Christmas campaign website a week early:
- The client moved the delivery from 22 to 15 December. Ana Costa confirmed it on the call.
- Sofia Marques takes over as Executor on Campaign Website. Rui Santos added her to the team.
- An in-store poster was added as a new Job, Velmont Christmas 2026 – In-store Poster (1058), due on 10 December.
Still open: whether the earlier delivery has a rush fee for the client. Nobody has confirmed it.
Thanks. There is a rush fee in their contract. @Skilio post this decision on the Campaign Website Feed, say the rush fee applies, and mention Ana so she tells the client.
- Job
- Velmont Christmas 2026 – Campaign Website
- Mentions
- Ana Costa
- Comment
- Delivery moved from 22 to 15 December at the client’s request. Sofia Marques is now the Executor. The contract’s rush fee applies to the earlier delivery. Ana, can you let Velmont Bakery know?
The comment is on the Job’s Feed. Ana was notified.