Orchestration — Distributing, reprioritizing and chasing shouldn't be the manager's whole day. At Olie, the rule orchestrates people, AI and systems.
Today, the manager spends the day deciding who takes what, redoing priorities in the WhatsApp group and asking where each thing stands. At Olie, the request reaches the right person through the rule, the priority changes in the funnel and everyone sees it, and each executor's data stays in the project, not in each person's spreadsheet.
Half the day goes into organizing the work. Not into doing the work.
- 58%
of the workday goes to “work about work”: searching for information, switching tools, tracking status.
Asana, Anatomy of Work 2022, 10,624 people - 25%
of teams' time is spent searching for answers and information in order to get work done.
Atlassian, 2025, 12 thousand professionals - 56%
need to ask someone or schedule a meeting to get the information they need.
Atlassian, 2025 - No. 1
Uncertainty about priorities is the main cause of missed deadlines, cited by 22%.
Asana, Anatomy of Work 2022
“Who takes this request?”
Today The manager distributes it in the group. The fastest one grabs it, the overloaded one sinks and nobody knows who is free.
At Olie The rule or an AI agent chooses based on each person's queue and goal, and reassigns if the deadline is missed.
“The priority changed and nobody knew.”
Today Reprioritizing means sending a voice message, rescheduling a meeting and hoping everyone heard.
At Olie Moving the card to another column in the funnel changes everyone's queue; the new deadline starts chasing on its own.
“The data lives with each executor.”
Today The spreadsheet is on one person's computer, the conversation on another's phone, the file in a third person's email.
At Olie Form, conversation, files and history stay in the project, recorded in the company.
“Where does it stand?”
Today Three meetings a week to find out what moved, what stopped and why.
At Olie The project shows step, owner, deadline and history; the director asks the assistant through MCP.
The AI agent chooses who does it. Deadline missed, the rule swaps the owner.
Today, distributing depends on who is watching the group. At Olie, an AI agent analyzes the people at the step (each one's queue, what they have delivered and their score) and assigns the request. If the deadline is missed, the rule replaces the owner and notifies whoever needs to know. And each person is measured by the goals you set: quantity, quality and value, with a target and a limit.
- Assignment by AI agentAnalyzes the people and chooses who gets the request, with the reason recorded.
- Reassignment by deadlinePast the limit, the request goes to another person and the previous one is notified.
- Goals per person and per teamQuantity done, quality delivered and value generated, with a target and a limit.
- Everything in the statementEach agent decision is recorded: why it chose, when and how much it cost.
| Person | In queue | Monthly goal | Score | Decision |
|---|---|---|---|---|
| Júlia | 2 | 31 of 40 | 9.4 | Chosen |
| Diego | 5 | 35 of 40 | 8.7 | Backup |
| Bruno | 9 | 38 of 40 | 7.9 | — |
One form answer takes the request to several funnels. People, AI agents and integrations at the same time.
The request moves through its origin funnel and, depending on one answer or a set of answers in the form, is distributed to other funnels or to hybrid actions: one part goes to a person, another to an AI agent, another to the ERP through the integration. The rule knows who is involved and communicates with everyone, from the internal team to the customer and the supplier.
- Single answer or a set“Need credit?” sends it to Finance; “credit + another city” also opens Logistics.
- Several funnels without duplicatingThe same project runs in parallel in each area, each with its own steps.
- Hybrid actionsPerson, AI agent and integration (webhook, API) in the same rule. The entry and exit doors are in Integrations.
- Everyone notifiedInternal mention, email and WhatsApp for those outside, with each one's deadline.
One order generates children per department. The parent only closes when the children finish.
Today, each area gets its part through a different channel and nobody sees the whole. At Olie, the hierarchy has 4 levels (root, child, grandchild, great-grandchild). The same project goes through sales, finance and operations without being recreated. The "legal" tag takes the project to the legal funnel; the status per funnel shows where each part stands.
- Project in several funnelsOne code, one history, several areas.
- Create hierarchy by automationA conditional form generates one child per area.
- Tag that calls another areaChanges funnel through the tag.
- Chat per projectMessages, audio, files and logs on the timeline.
This project has no linked parent project
Pipeline: one agent qualifies, another writes, another classifies. The person steps in where the decision calls for a human.
Real human-in-the-loop: the agent acts with the permission you gave it, at the step where it is; approval is human and arrives through WhatsApp; the failure route returns the project to a person. Every run in the statement.
- Agent pipelineChained by the automation, each at its own step.
- Human approval via WhatsAppThe director replies on WhatsApp, with free text, a button or a form, and the project moves forward.
- Route when the AI failsThe project goes to a person.
- Briefing agentSummarizes the project for whoever joins midway.
| Assistant | Status | Project | Form result | AI answer | Date |
|---|---|---|---|---|---|
| Lead qualifier | Success | PD‑1041 | Score: 8 · Size: large | ok | 09/28 18:47 |
| AI follow-up · tracking | Success | PD‑1043 | — | ok | 09/28 17:46 |
| Lead qualifier | Success | PD‑1050 | Score: 5 · Size: medium | ok | 09/28 16:45 |
| Request distributor | Success | CS‑212 | Owner: Júlia M. | ok | 09/28 15:44 |
| AI follow-up · tracking | Success | PD‑1055 | — | ok | 09/28 14:45 |
| Contract reader | Success | PD‑1041 | Penalty clause: yes | ok | 09/28 08:28 |
What does Olie Flow AI orchestrate?
The distribution, reprioritization and follow-up of work, together with APIs, AI agents and people inside the same project: an AI agent assigns the request and the rule reassigns it when the deadline is missed, a form answer takes the request to several funnels, the 4-level hierarchy connects the areas, the agent pipeline chains the AI, human approval arrives through WhatsApp and the webhook, the API (~200 endpoints) and MCP connect outside systems. It is a composable platform: funnels, steps, forms, automations, agents and channels are blocks you combine without coding, with advanced syntax when needed.
Updated on · Source: Olie Flow AI technical base · Guide to the 77 features
Who does what, in what order. Designed once.
30-minute meeting: your process built on screen and the price for your team. Then, see how the rule ensures the process is followed.