Customers ask.
Your business acts.
Actum's AI operators handle customer conversations and the tasks behind them. Writes to business systems wait for permission checks and human approval. CRM, calendar, email, and payment connections are not connected yet.
Policy levels
3
Writes
Gated
Connections
Pending
Front Desk
Example conversation
Ledger
3 facts
Tool
calendar
Policy
confirm
How a workflow moves through Actum
RunningConversation
Customer asks for a Thursday service slot
Permission
create_booking requires confirmation
Action
Calendar step · no external write
Audit
Audit view · example data
Every message becomes
a governed signal
Channels feed the agent. Policy decides. Writes wait for approval before any connected tool runs, and every step leaves a record you can follow.
- Web, WhatsApp, and voice channels (WhatsApp and phone not connected yet)
- Front Desk routes intent to the right tools
- Writes only land after permission clears
Conversation is the control layer.
Action is the product.
Channels, orchestration, and the action engine stack as one operating system — the same path every request takes.
Move across the stack — depth responds to your pointer.
Try the same loop yourself
Pick an example and watch the policy flow. No external action runs.
Example workflow
Ask for an outcome your staff would complete
Customer
Book a service for my VW Golf next Thursday morning.
Policy path
- 1
Understand
Waiting for request
- 2
Decide
Select agent + tools
- 3
Permission
Policy check
- 4
Action
MCP invocation
- 5
Result
Audit + response
Permission before
every material write
Each action is assigned a policy level: automatic, confirmation, or protected. Writes at the confirmation and protected levels wait for a person.
Policy engine
Automatic
Connect the systems
your operators write to
Tools are discovered and granted with explicit permissions. CRM, calendar, email, and payment connections are not connected yet.
Record the work once.
Run it the same way every time
Tasks are recorded as steps and reviewed before they run again. Computer-use execution and live system connections are not connected yet.
How the work becomes a skill
Record it once. Run it the same way.
Record
Share the screen. Talk through the real work.
Atomic steps
Every action, nested with what-ifs, in order.
Run
An agent replays it with computer use.
Share
Department or organisation — same every time.
Atomic steps
Break the huge task until every step knows what comes next.
Open the period
Payroll
Not a chatbot builder.
An operator platform.
Typical assistant
- Explains how to fill a form
- Collects a lead and stops
- No governed tool access
- Transcript is the only memory
- Hard to measure real outcomes
Actum
- Prepares the booking, quote or CRM update for approval
- Least-privilege MCP tools with three policy levels
- Human approval at meaningful boundaries
- Structured requirements + durable workflows
- Audit and analytics designed in
Built for businesses that
cannot afford invisible autonomy
One business brain
Shared knowledge and requirements across channels
MCP capability layer
Discover tools once, grant them with policy
Least privilege
Three permission levels on every material write
Durable workflows
Long-running work with audit at every step
Templates for measurable outcomes
Example configurations of tools, channels, and policy. External connections are not connected yet.
Horizontal platform.
Concrete templates.
Ship a governed operator
this week.
Explore agents, connections, and approval flows. External integrations are not connected yet.