Skip to content
Companionby MetaControl
Admin panel

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.

Work algorithmYour panel: configure & approve · Robot: act & follow up
Customer request workflowRequest, check details, plan, check authority, act, verify and follow up. Missing information leads to a question; missing authority leads to a stop; an unknown effect leads to readback.Customer requestEnough details?Plan & skillsValid authority?Authorised actionClear outcome?Receipt & follow-upAsk and waitRead back the same actionWait for approval / stopYesNoYesYesUnknownRevise approach
  1. Customer request
  2. Enough details?

    No → ask and wait, then check details again

  3. Plan & skills
  4. Valid authority?

    No authority → stop and request required approval

  5. Authorised action
  6. Clear outcome?

    Unknown → read back the same action; do not blindly repeat sending or payment

  7. Receipt & follow-up
Solid line: main pathDashed line: clarification, readback or revisionSent ≠ received ≠ business outcome

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.

Six stages of the work
Companion product with a screen showing a robot at work

Robot: work within authority ↔ Your panel: configure, approve and supervise

Designed process illustration · educational example, no operations executed

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. 1. Choose your use

    Review product uses and base prices. For organisational workflows, explore bespoke services.

  2. 2. Explore a demo and evidence

    Try a relevant demo and read recorded status and limits on the capabilities page.

  3. 3. Define delivery scope

    Clarify data, connections, authority and acceptance criteria before real execution.