Approval Authority
A payment, discount, refund, access change or other action requires authority that the agent does not hold.
Controlled automation
AI should know when the work belongs to a person.
Answer in brief
Design AI-human handoffs that preserve context, ownership, approval state and workflow continuity with MicroPlatform.
MicroPlatform treats human handoff as a designed workflow state, not an automation failure. The system can pause, transfer context and ownership, wait for the human action and resume when the next step becomes automatable again.
Handoff lifecycle
Pause with context. Resume with state.
The goal is to prevent the common pattern where AI and staff operate as separate conversations and the customer or employee must explain everything twice.
1. AI workingThe agent handles tasks inside the configured knowledge, tool and permission boundary.
2. Boundary reachedThe workflow detects missing authority, uncertainty, policy restriction, exception or specialist need.
3. Structured transferIssue summary, relevant context, evidence, actions already taken and recommended next step are packaged for the person.
4. Human ownsAutomation pauses where necessary and ownership becomes explicit.
5. Human actionThe person decides, approves, communicates or performs the step that requires human responsibility.
6. ResumeMicroNerve records the updated state and automation can continue from the correct point.
When to hand off
Low Confidence
The available evidence is incomplete or conflicting and the workflow should not guess.
Sensitive Customer Case
The issue is high-value, emotional, contractual, legal or reputational and needs human judgement.
Policy Boundary
The requested action is outside the configured agent permissions or automation rules.
Specialist Expertise
The case requires technical, financial, operational or domain knowledge that should remain with a specialist.
Exception Workflow
A document, transaction or system state does not meet the normal acceptance path.
Handoff payload
Give the person the work, not just the transcript.
A useful handoff is structured for action. It should reduce the time a person spends reconstructing what happened before they can help.
SummaryWhat happened and what outcome is required.
IdentityCustomer, account, document, order, vehicle, ticket or other primary record.
EvidenceRelevant approved information gathered by the workflow.
ActionsSteps already completed, attempted or blocked.
Decision neededThe precise human approval, judgement or specialist action required next.
Resume conditionWhat state or result allows the automated workflow to continue.
Handoff assessment
Design the point where AI stops before deploying the AI.
Share the automated task, human responsibilities, approval boundaries and what context staff need when they take over.