Sign in

Omni ChannelPeople in the loop, on every channel.

Supplier onboardingRun 2,418 · Northwind Fasteners

  1. Check registration and tax ID
  2. Screen against the sanctions list
  3. Approve new supplierWaiting on Procurement leads Approved in Slack by Priya N.
  4. Create supplier recordNextRunning

SlackDirect message

Supplier onboarding needs a decision: approve new supplier, Northwind Fasteners.

ApproveRejectEscalate

Approved, resolved by Priya N.

Text message

ACTAVA: an agent action from Supplier onboarding needs your approval. Review & respond

EmailDecision needed: Approve new supplier

Northwind Fasteners. Registration and sanctions checks passed.

Due in 2 daysReview the request

Set it in the plan

Mark a task in the agent's plan, choose who decides and what they can answer. No separate workflow to build.

  • Approval on any taskThe run pauses at that task until the approver group answers.
  • What they can answerPick the answers they get, and see what each one will do to the run.
  • Wording and requirementsName the decision, write what they are asked, and say what an answer must carry.
  • Ask before runningTick a tool, and every call to it waits for a person first.

Human ApprovalTasks that pause for group sign-off

Task 3 Approve new supplier

Approver group

Procurement leads3 people · any one of them decidesCan answer from Slack, email, text or the app

What they can answer

Approve Reject Approve with corrections Return for rework Escalate Defer

  • “Reject” ends the run here. The step after this will not happen.
  • “Approve with corrections” applies the reviewer’s corrections before this step runs.

Wording and requirementsWhat they’ll read, and what an answer must carry

Also post approval requests to Slack

One request, every channel

The same decision reaches each person in the group where they work, and the run goes on the moment the group has decided.

SlackOne click, in a direct message

Supplier onboarding needs a decision: approve new supplier.

ApproveRejectEscalate

Also available in the app: Approve with corrections, Return for rework, Defer

Microsoft TeamsA card in the chat

Approve new supplier
Northwind Fasteners · due in 2 days

Review the request

EmailA link to the review

Decision needed: Approve new supplier
Registration and sanctions checks passed.

Review the request

Text messageShort, with no case details

ACTAVA: an agent action from Supplier onboarding needs your approval. Review & respond

ACTAVA appDecisions, waiting on you

Approve new supplierProcurement leads · due in 2 daysApprove

APIFrom your own systems

  • ReadThe decisions waiting on the key’s owner
  • AnswerApprove, as Priya N.’s own vote
  • Reminders before the deadlineAnyone who hasn't answered is reminded halfway there, and again near the end.
  • Links that never decide on openEmail and text open a review, so a mail scanner can't approve anything.
  • One answer per personA Slack click counts only from the reviewer's own account, and each person answers once.

Every answer moves the run

A reviewer does more than say yes or no. Each answer has a clear result, and the run carries on from it.

  • Approve, or approve with correctionsFix a detail in the answer itself; the step runs with the correction.
  • Return for reworkSend the plan back to a step you name, with the reason. After three returns, it can only go up.
  • Escalate or deferHand the decision to the next tier, or hold it until a time you set.

What each answer does

Approve new supplier · set in the plan, for this task

  • ApproveRecorded, and the plan carries on.
  • Approve with correctionsThe agent applies the corrections, and they stay on the record.
  • RejectThe run stops here, unless you set it to carry on.
  • Return for reworkBack to a step you name, with the reason. Up to 3 times.
  • EscalateThe whole request moves to the escalation group.
  • DeferHeld until a time the reviewer sets, then asked again.
Simplify
“ACTAVA lets us take what our best operators already know and put it in front of every rep and every location, without losing the human judgment that makes the coaching worth trusting.”
Gino TenaceCEO & FounderFull story

Decision groups

Set up who decides once, and use the same group wherever that call comes up.

  • One group, many agentsA change to the group applies to every step it decides.
  • How it decidesAny one person, a set number, a majority or everyone.
  • Time to answerWhen time runs out, the request expires or moves to the escalation group. It never approves itself.
  • Reach you can seeEach person shows how they are reached, and a seat nobody can reach is flagged.

Procurement leadsAny one member3 people · 2 days to answer

Where it’s asked to decide

  • Supplier onboardingApprove new supplier
  • Contract renewalsSend renewal terms
  • Purchase ordersRelease an order above its limit

Who’s in it

The first answer decides.

  • Priya NairIn Slack, by email and in the app
  • Marcus LeeBy text and in the app
  • Dana OrtizIn Teams and by email

When time runs outEscalates to Finance directors. A timeout never approves.Can answer fromSlack, Teams, email, text or the app

Sensitive decisions, signed in

Turn on Handles PHI / PII for an agent, and its decisions are made signed in to ACTAVA.

  • Nothing about the case leavesMessages name only the agent, the step and the deadline, with one link to decide signed in.
  • Everything else, in the channelFor other agents, people answer in Slack, or from their own link, with no sign-in.
  • Set once, on the agentEvery channel follows the same rule, so no message can slip past it.
How compliance works

Agent doesn’t handle PHI / PII

Slack

Supplier onboarding needs a decision: approve new supplier, Northwind Fasteners. Registration and sanctions checks passed.

ApproveReject

Answered right here, no sign-in.

Agent handles PHI / PII

Slack

Care coordination has a decision waiting for Clinical reviewers, due in 4 hours.

Open in ACTAVA to decide

No case details leave ACTAVA.

Who answered, and where

Each request keeps its own record: where it was sent, who was reminded, who answered, how, and when the run went on.

Approve new supplierSupplier onboarding · Run 2,418 · Procurement leads

  1. PausedRun 2,418 reached Approve new supplier, asked Procurement leads
  2. SentSlack 1, Teams 1, email 2, text 1, app 2 · everyone in the group reached
  3. RemindedAll three, halfway to the deadline, since nobody had answered yet
  4. AnsweredPriya N. chose Approve in Slack, from her own Slack account
  5. ClosedEvery Slack message now reads Approved, and no more answers are taken
  6. ResumedCreate supplier record
  • Delivery, channel by channelWhat was sent, what failed and what was skipped, and why.
  • How each answer was madeSigned in, from a link or in Slack, and whether they opened the evidence first.
  • Answers that carry their reasonsA correction or a reason for rework travels with the answer, so the record says why.

Keep people in the loop, wherever they are

We'll set up a workflow like yours with your approvers on the channels they already use.