01
Scope
Define the conversations, intent classes, service rules, operating hours, and outcomes the workflow owns.
TRUST · CONTROL · EVIDENCE
Trust is designed into the workflow.
Concierge runs configured routine work autonomously, keeps the operating trail visible, and brings people in when an exception crosses the boundary you set.
Company-led controls for real operations — without borrowed badges or vague promises.
Control model
Autonomy with explicit operating boundaries.
The workflow decides and acts inside the scope you configure. Its permissions, exception paths, and evidence are part of the design — not an afterthought.
02
Permissions
Enable only the connected tools, data lookups, dispatch routes, and post-call actions required for that workflow.
03
Autonomous routine work
Concierge can resolve intent, match a configured rule, act, dispatch, follow through, and record the result autonomously within configured boundaries.
04
Exceptions
When confidence, authority, permissions, or a visible failure requires review, Concierge can pause and prepare the available context for the right person.
Operational evidence
See what the workflow decided and did.
A trustworthy agentic workflow leaves an operational trail your team can inspect, continue, and improve.
Action records
Configured tool calls and completed actions stay attached to the conversation and case.
RECORDEDDispatch trail
Resolved intent, matched rule, owner, retry state, and follow-through remain visible together.
TRACEABLEVisible failures
A failed connection or blocked action becomes an explicit state that can be reviewed and continued.
NEEDS ATTENTIONReview context
When a person is required, the available conversation, decision, and action context travels with the handoff.
PREPAREDData and privacy
The data boundary follows the configured workflow.
Before live use, we agree what information the workflow needs, which connected systems it may use, which records it should create, and where a person must review the result.
We publish what is confirmed, and label what is still in progress as exactly that. Formal compliance work continues alongside the product, and nothing on this page borrows certification language or implies a control we have not implemented.
Read the privacy policyCompliance and human oversight
Nothing is decided by the system alone.
Human oversight and escalation are built into the architecture — which is also how we meet NDPA Section 37. Handover to a person is a designed step, logged and auditable, not a failure mode.
Human handover is architectural
Escalation rules are configurable per workflow and per sensitivity level, and every handover is recorded.
Auditable end to end
Interactions are logged and timestamped, so an incident can be reviewed rather than reconstructed.
PII redaction
Personal data is redacted where the workflow allows, and what is stored is agreed with you before go-live.
Retention you control
Retention is configurable down to metadata only. Recording is off by default and enabled per line by you.
Callers keep their rights
Anything held about a caller can be viewed, exported or erased on request.
Current status
NDPC registered
Registered with the Nigeria Data Protection Commission.
Pilot validation
Prove the workflow before live traffic.
A pilot turns the operating boundary into testable scenarios, so autonomy and exceptions are understood before customers depend on them.
- 01Agree one workflow, its outcomes, and its exception paths.
- 02Configure the lines, rules, permissions, tools, dispatch routes, and records it needs.
- 03Run representative scenarios, including blocked actions and failures.
- 04Confirm the live boundary and commercial terms before go-live.
Bring one workflow. Define the controls together.
Show us the customer request, the decisions Concierge should make, the systems it should use, and the exceptions your team needs to own.