From request to a trackable outcome
This page explains your role, the robot’s decisions and the conditions for continuing. The diagram describes the designed workflow; capability availability and evidence are reviewed separately.
Decisions and stop conditions
Choose a diagram stage to jump to its explanation.
- Customer request
- Enough details?
No → ask and wait, then check details again
- Plan & skills
- Valid authority?
No authority → stop and request required approval
- Authorised action
- Clear outcome?
Unknown → read back the same action; do not blindly repeat sending or payment
- Receipt & follow-up
Customer request
Identify the goal and request through an admitted channel.
Enough details?
Check required information and clarify ambiguity.
Plan & skills
Define steps, skills, permitted knowledge, responsibility and timing.
Valid authority?
Check authority, recipient, content and cost before real effects.
Authorised action
Act through an admitted API, browser or software tool; report blockers.
Clear outcome?
Read the same operation back from its destination; unknown is not success.
Receipt & follow-up
Separate receipt, recipient acceptance and business outcome; follow up.
Ask and wait
Ask a focused question and wait for missing information.
Read back the same action
Read back the same attempt before retrying any send or payment.
Wait for approval / stop
Stop without authority; continue only under valid approval.
REQUEST → PLAN → ACTION → FOLLOW-UP
Example: handling a customer request
Example: handling a customer request. Select a stage to see the robot’s work, your decisions and the output.

Robot: work within authority ↔ Your panel: configure, approve and supervise
Receive request
The customer makes a request through conversation, phone, web or a configured schedule. The robot must identify the desired outcome.
“Please contact me about the product.”
- Output
- Topic, permitted contact route and desired outcome
- To continue
- Only connected, authorised channels in that customer’s configuration.
Canonical data stays on the customer’s system. Each task’s online or offline availability depends on configuration and admitted connections. This illustration does not establish that every stage is live; review recorded capability status on the capabilities page.
Get started in three steps
1. Choose your use
Review product uses and base prices. For organisational workflows, explore bespoke services.
2. Explore a demo and evidence
Try a relevant demo and read recorded status and limits on the capabilities page.
3. Define delivery scope
Clarify data, connections, authority and acceptance criteria before real execution.