IntelligenceOverview
Operational Intelligence
Watch what happens in your business systems, and let AI Workers act on it, with a person approving where it matters.
Operational Intelligence watches the events coming out of your business systems, such as a payment failing, an invoice going overdue or a lead going quiet. It tells the right people, and lets AI Workers take the next step. A person approves what they do until you trust them to act on their own.
Approve: send a payment reminder to Acme Ltd
- Invoice 1042 entered the "overdue 7 days" segment
- Drafted a payment reminder
- Posted it for approval in the finance channel
Approved by Peter, and the reminder was sent.
How it works
| Step | What it is |
|---|---|
| Sources | The systems that send events in: your payment processor, CRM or your own app. |
| Segments and stages | Who needs what: groups of customers or records in a given state, kept up to date as events arrive. |
| Triggers | Rules that react to an event, such as alerting a channel or starting a worker. |
| AI Workers | Workers that take the next step for each item that enters a segment. Start from a preset, such as dunning, a KYC document chaser or lead follow-up. |
| Channels | Where alerts and approvals go, so the right team hears about them. |
People stay in control
- Proposes only, to start. New workers propose actions, and a person chooses Approve, Send my edit or Reject from the link in your channel.
- Dry runs. Run dry-run shows what a worker would have done against past events, with nothing sent.
- Acts on its own, when you’re ready. Switch a worker over once you trust it.
- Budgets and guardrails. Each worker has a monthly budget, and Handoff guardrails limit how many messages a person receives.
- A full record. Every item has a Run history with every step the worker took.
Start here
- Operational Intelligence quickstart Your first worker, in about 15 minutes
- Organization Intelligence Your policies and SOPs, verified