Useful answers before you commit.
Only capabilities that are actually configured and verified should be treated as live.
Is ARIA a real person?
No. ARIA is an automated ORVIA Voice Assistant. She should identify herself appropriately and work within the customer-approved configuration.
What happens if somebody needs a human?
The deployment defines the appropriate human handover or escalation route. ARIA can capture context so the person taking over does not start from zero.
Can I keep my existing phone number?
Often an existing number can remain through diversion or routing, but the current provider and safest cutover method must be confirmed before this is promised.
Can Voice work outside office hours?
Yes, out-of-hours handling can be scoped. The exact route depends on what the organisation approves and which human escalation paths must remain available.
What happens when a call is urgent?
Urgent routes are customer-specific. ORVIA Voice is not an emergency service. The organisation must maintain appropriate emergency and authorised escalation arrangements.
Can it take quotation enquiries?
Yes, a configured journey can capture the information needed for a quote request and route it for human follow-up. It should not invent or approve pricing outside the agreed rules.
Can it arrange callbacks?
It can capture a callback request and route it to the appropriate person or team. Any direct calendar or booking action is only described as live where it has been connected and tested.
Can it integrate with our current systems?
Specific integrations can be assessed. The current website enquiry journey routes into Monday.com. Other platforms are customer-scoped and only treated as live after end-to-end verification.
What information does it store?
The exact fields depend on the customer-approved deployment. Website enquiries currently collect the information shown on the form so the team can follow up.
Where is data held?
The exact suppliers, locations and processing arrangements depend on the configured deployment and must be documented during onboarding. This website does not make a universal hosting claim for every future configuration.
How is personal information protected?
ORVIA Oversight Ltd is ICO registered under ZC152311. Access, retention, recording/transcription and recipients are defined for the deployment, not assumed from a generic template.
Can we decide what ARIA is allowed to do?
Yes. The customer approves the business information, journeys, boundaries and escalation contacts used for its deployment.
Can we change scripts and workflows?
Yes, within the controlled configuration process. Changes should be reviewed and tested rather than silently pushed into live handling.
Is every business given the same setup?
No. The point is to configure around real call reasons and operating needs rather than force every customer through the same script.
How quickly can we launch?
That depends on complexity, telephony, integrations, approvals and testing. ORVIA does not publish a blanket launch-time promise that may be unsafe or unrealistic.
What happens after I buy or request discovery?
We map your current calls, define boundaries, configure routing and escalation, test real scenarios, approve the journey, go live and then review actual behaviour.
Does ORVIA Voice replace staff?
No. Its purpose is to carry repetitive communication and administration around people, not remove human judgement, care or accountability.
Can it make safeguarding or clinical decisions?
No. It can capture and route approved information, but safeguarding findings, diagnosis and other consequential decisions remain with authorised humans.
What does it cost?
Current starting points are Essential £495/month, Business £695, Growth £995, Professional £1,495, Command £2,495 and Enterprise bespoke. Final scope reflects usage, telephony, integrations and implementation.