Orchestration · for COOs, sales and CX — Assigning the work and setting its order shouldn't take up the manager's day. At Olie, the rule coordinates people, AI agents, areas and systems.
Today, the priority changes in a voice note in the WhatsApp group, and someone spends the day asking for the status of each request. At Olie, the request reaches the right person through the rule, the priority changes in the funnel (the process and its steps) and everyone sees it, the same project crosses the areas without being recreated, and people step in where the decision requires human judgment.
- Distribution by rule or by AI agent
- Overflow: the same project in several funnels, not duplicated
- Human approval via WhatsApp
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 piles up work 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 was told.
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's account.
“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 can also ask ChatGPT or Claude, connected to Olie through MCP (the AI assistant connector).
Every request that comes in becomes a project, with an owner and a deadline.
Today, requests arrive by email, WhatsApp and in the hallway, and some of them get lost. At Olie, every request that comes in is born as a project in a funnel, with an owner set by the rule and a deadline. The calendar shows everything due each month, per funnel.
- Single entry pointPublic form, request catalog by role, WhatsApp and API: everything becomes a project.
- Owner set by the ruleDraw, AI agent or the step's role: assignment follows a defined criterion.
- The rule does the chasingThe deadline chases the owner and then escalates to the manager. How it works is in Algorithmic management.
- Calendar per funnelForecast and next step of each project, month by month.
RevenueR$ 184,000
Forecast09/26
OwnerAna Lima
Won on 09/26RevenueR$ 61,000
Forecast09/29
Next steptoday 15:00
Forecast todayRevenueR$ 27,500
Forecast10/08
OwnerDiego Alves
In progressRevenueR$ 9,000
Forecast10/15
Postponements2
In progressRevenueR$ 42,000
Forecast11/12
OwnerBruno Reis
In progressThe rule or an 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 rating) and assigns the request. If the deadline is missed, the rule replaces the owner and notifies whoever needs to know.
- Assignment by AI agentAnalyzes the people and chooses who gets the request, with the reason recorded.
- Reassignment by deadlineOnce the deadline passes, the request goes to another person and the previous one is notified.
- Distribution by draw or by roleWithout an AI agent, the rule splits new requests among the step's team.
- Decision with a reasonThe agent records why it chose each person. The full statement is in Governance.See traceability
| 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: that is Overflow.
- 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.
Overflow: the same project in several funnels. Not duplicated, with a single history.
Today, each area gets its part through a different channel and nobody sees the whole. At Olie, Overflow makes the same project run in several funnels at the same time, without being duplicated: one code, one history, and each area with its own steps. When the order needs to be split, the 4-level hierarchy (root, child, grandchild, great-grandchild) creates one child per department, and the parent only closes when the children finish.
- One project, several funnelsOne code, one history, several areas; the status per funnel shows where each part stands.
- Children per departmentA conditional form generates one child per area, through the automation.
- Tag that calls another areaThe "legal" tag takes the project to the legal funnel.
- Chat per projectMessages, audio, files and logs on the timeline.
This project has no linked parent project
One agent qualifies, another writes, another classifies. The person steps in where the decision requires human judgment.
This is what is called human-in-the-loop: a person in the loop, at the points the company chooses. The agent acts with the permission it was given, at the step where it is; a decision that requires a person goes to them, and they approve through WhatsApp; and, when the AI fails, the route returns the project to someone. Every run is recorded.
- 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‑1086 | 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‑1087 | 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 orchestrate?
Who does what, in what order, across people, AI agents, areas and systems, inside the same project. Every request that comes in becomes a project with an owner. The rule or an AI agent assigns the request and reassigns it when the deadline is missed. A form answer takes the request to several funnels, and Overflow makes the same project run in several areas without being duplicated. The 4-level hierarchy splits the order by department, and human approval arrives through WhatsApp. Outside systems connect through webhook, REST API and MCP.
Updated on · Source: Olie technical base · Guide to the 77 features
Who does what, in what order. Designed once.
Execution that doesn't depend on people: the request reaches whoever should do it, crosses the areas and stops at a person only where the decision requires one. In the next tab, see how governance protects the operation.
Next step: 30 minutes to see your process on screen; then, a diagnosis with your leadership.