VOICEComplaints intake
Capture the issue, dates, people involved and requested outcome before routing it to the correct human owner.
SPECIALIST VOICE
When the boundaries matter as much as the conversation.
Specialist Voice is for multilingual, complaint, welfare, safeguarding-aware and operational intake journeys where the system must know exactly what it may capture, what it may explain, and when it must stop and involve an accountable person.
WHAT CUSTOMERS GET
A controlled intake layer, not an autonomous decision-maker.
Safeguarding-aware capture
Collect approved factual information and immediately follow the organisation's defined escalation route when a threshold is reached.
Welfare workflows
Use controlled check-in questions and escalate exceptions, concerning answers or non-response.
Multilingual journeys
Supported languages are confirmed only after the selected speech and transcription configuration is tested for the use case.
Operational intake
Structure incident, service or field information for allocation or connected systems where verified.
Named escalation
Use explicit routes for live transfer, urgent alert, callback or accountable human review.
CONTROL MODEL
Human first. Human last. Automation in the controlled middle.
01
Listen
Establish the reason and relevant facts.
02
Check
Apply approved rules and thresholds.
03
Capture
Record structured information without interpretation creep.
04
Escalate
Stop routine automation when the threshold is reached.
05
Human
An accountable person makes the judgement or decision.
ILLUSTRATIVE EXAMPLE
A concern is captured without letting the system decide what it means.
ARIA
I'm going to take the key information and make sure the appropriate person receives it. If someone is in immediate danger, please contact the emergency services.
CALLER
I'm worried because I haven't seen my neighbour for two days and this is unusual.
ARIA
I can capture what you've observed and the contact details for the human team. I won't make a safeguarding decision.
Result: factual concern captured; automation stops at the defined point; named human route receives the information.
HUMAN HANDOVER
Potential welfare concern · human review
- Reporter
- Contact details captured
- Observation
- Neighbour not seen for two days; unusual according to caller
- System action
- Concern intake recorded and escalated
- Decision
- Not made by ARIA
- Owner
- Configured accountable person/team
NON-NEGOTIABLE BOUNDARIES
Where Specialist Voice stops.
No safeguarding judgement
ARIA may identify a configured trigger and escalate; it does not decide whether a statutory safeguarding threshold is met.
No clinical or legal decision
Clinical, legal, financial and regulatory conclusions remain with appropriately authorised people.
Not an emergency service
Emergency instructions and routes must be explicit; ORVIA Voice is not a replacement for 999 or statutory emergency arrangements.
No unsupported language promise
Language capability is scoped and tested before being offered for a live specialist journey.
OPERATIONAL CONNECTIONS
Specialist calls can feed a wider controlled workflow.
Where specifically built and verified, Voice can create a structured record or notification for another ORVIA or customer system. Planned connections are never described as live merely because they are technically possible.
BEST FIT
For environments where routine automation needs explicit stop points.
Care & health services
Routine reception plus clear human routes for concerns, welfare and sensitive information.
Complaints teams
Consistent initial capture without the system deciding whether the complaint is upheld.
Operational services
Structured incident or field intake where the receiving team needs facts, priority indicators and ownership.
Design the boundary before automating the conversation.
Tell us the use case, risk points, escalation route and systems involved.