Channels and volume
Voice, chat, email and the rest of the digital surface, inbound and outbound. How many conversations a month, how they peak, and which queues you want Orvera's AI agents to carry.
How an Orvera deployment is scoped
Orvera builds, deploys and runs the platform on the customer's behalf, so the shape of an engagement follows the work in front of it. Two contact centers with the same headcount can sit a long way apart once you look at their channels, their volumes and the systems their agents have to reach. This page sets out what moves that shape and how to get a figure for yours.
What shapes it
Six things a scope turns on
Each of these moves the shape of a deployment, and a scoping call works through all six.
Workflows and outcomes
Which conversations you want carried all the way to an outcome, and what that outcome is in your own system of record. A booked appointment, a filed claim status, a resolved billing question.
Integrations
Which systems the AI agents read from and write back to. CRM, ticketing, order management, telephony, scheduling and your knowledge base. Orvera holds 500+ integrations, and the published directory is a sample of them.
Languages
More than 80 languages across every channel, and which of them your customers actually call in.
Governance and compliance
SOC 2 Type II certified, HIPAA compliant, GDPR compliant. In a regulated vertical the review that decides the deal is usually about evidence, so the scope covers what you have to show a regulator on every conversation.
The human-agent layer
Agent Assist for live guidance during complex calls, AI Quality Management scoring every conversation, and Voice of Customer reading the themes out of all of them.
What the deployment involves
From the first call to a live floor
Orvera does the build, the integration and the run. The scope is set at the first stage on this list.
- 01
Scoping conversation
Your queues, your monthly volume, the systems the AI agents have to reach, and the compliance review the work has to pass. This is the call that produces a scope.
- 02
Build
Orvera does the build. Conversation design, workflow execution and governance, and contextualization models custom-trained on de-identified data.
- 03
Integration
Orvera connects the platform to the stack you already run, so the AI agents work inside the systems of record your team already uses.
- 04
Go live
3 to 6 weeks, against a customary 6 to 9 months for a program of this shape.
- 05
Run
Orvera runs the system it deploys. Full reporting and observability, transcripts and summaries on every interaction, quality scored across 100% of conversations, human-handled and AI-handled.
How to get a figure
A scoped call, and what to bring to it
A figure comes out of a scope, and a scope comes out of one conversation with the people who run your floor. Bring four things and the call does the rest of the work.
- The queues you want carried end to end
- Monthly conversation volume, and how it peaks
- The systems the AI agents have to read and write
- The security and compliance review the work has to pass
Orvera comes back with the scope of the deployment it would run for you, and the figure that sits against it. Book a demo to start that conversation, or read the security and architecture detail your reviewers will ask for first.
Bring us your queues. We will scope the rest.
One call about your channels, your volumes and the systems you run, and you get the shape of the deployment back.