Until now your assistant only replied when someone wrote to it. With **Jobs** and **Flows**, your assistant can also **act on its own**: check something tomorrow, send a summary every Monday, run a chain of steps when a new contact comes in… The work doesn't end when the conversation ends. - **Jobs** is the queue of everything your assistant has pending, in progress, or already resolved — a one-off task, whether it's a single occurrence or a repeating one. - **Flows** is where you chain several steps into a single process, with the possibility for the process itself to **take one path or another** depending on what happens (a decision, not just a plain list of steps in sequence). Every step the assistant runs — what it saw, what it decided, what it sent — is logged with a date and time in a **step-by-step history**, visible right on the task's or flow's own record. You never have to trust blindly what it did. > **Note — Requirements** > > Anyone on the team can see the screens in this manual. Creating, editing, activating or deleting tasks and > flows is exclusive to the Admin and Editor roles.