- log in and find your way around the console
- create bots the same way every time
- test before calling real customers
- monitor retries, callbacks, and failures
- know what is yours to fix and when to escalate to engineering
You do not need any technical or coding knowledge to use the console. Everything in this manual is point-and-click. Engineering handles the servers, telephony plumbing, and anything that breaks at runtime.
Who owns what
The platform is split between two teams. Knowing the boundary saves time: it tells you what you can fix yourself and what to hand off.| Area | Operations owns | Engineering owns |
|---|---|---|
| Bot setup | Bot name, opening message, prompt/policy, voice pipeline choices, tools, CRM mapping, test calls | Provider keys, runtime bugs, transport failures |
| Campaign setup | Bot selection, outbound number pool, contact upload, concurrency, time window, retry rules | Dialler health, fleet capacity, SIP trunk health |
| Monitoring | Campaign status, failed calls, attempt reports, obvious bad data | Stuck states, infrastructure failures, provider outages |
| CRM integration | API key handoff, variable names, post-call mapping checks | Endpoint failures, authentication bugs, webhook retries |
Logging in
The console lives at your team’s Ori web address. Open it in a browser and you land on the Login screen. The login page is split into two halves. The left side is a welcome panel with the Ori logo, a headline, and a short list of platform highlights — there is nothing to click there. The right side is the sign-in form you use every day.Enter your email
Type the email address your administrator created your account with (for example,
you@company.com).Enter your password
Type your password. It is hidden behind dots by default. Use the eye icon at the end of the field to reveal or re-hide it if you want to check what you typed.
Login fields
| Field | What to enter | Required |
|---|---|---|
Your account email address in standard email format (name@company.com). | Yes | |
| Password | Your account password. Hidden as dots by default; use the eye icon to reveal it. | Yes |
Login buttons
| Button | What it does |
|---|---|
| Sign in | Submits your email and password. Shows Signing in… and is disabled while it checks your details. On success it opens your dashboard. If the details are wrong, it stays on this page and shows an error message at the top of the screen. |
| Eye / Eye-off (password toggle) | Switches the password field between hidden dots and plain text so you can confirm what you typed. The icon flips between the two states. It does not submit anything. |
The console shell
Once you are signed in, every page sits inside the same frame. A navigation sidebar runs down the left on desktop; on a phone or narrow window the sidebar is hidden behind a menu button at the top. The middle of the screen is where each page loads.Sidebar navigation
These are the links in the sidebar. Some links only appear for certain roles — those are marked below. If a link is not in your sidebar, your account does not have access to it; that is expected, not a fault.| Link | Where it takes you |
|---|---|
| Overview | The dashboard home page with your key metrics and recent calls. |
| Bots | The bot management area, where you build and edit voice agents. |
| Knowledge Base | Manage knowledge documents that bots can search during a call. |
| Call Logs | Call history, with full details and transcripts for each call. |
| Campaigns | Campaign management — set up and run outbound calling lists. |
| Reports | Analytics and reporting across calls and campaigns. |
| Carriers | Telephony carrier configuration. Super admin only. |
| Users | Team member management — invite and manage console accounts. |
| Fleet | Fleet and server status for the calling backend. |
| API Keys | Manage keys that let your CRM trigger calls programmatically. |
| Release Notes | Version history and recent changes to the platform. |
| Settings | System-wide configuration. Super admin only. |
The sidebar groups these links into sections (main, Telephony, Team, System). Empty sections are hidden automatically, so what you see depends on your role. Some accounts are restricted to a “calls-only” view and will see only Call Logs and Campaigns — this is set up intentionally by your administrator.
Profile card and shell controls
At the bottom of the sidebar is a small profile card showing your initial, your display name (or email), and your role. Two icons live here, plus a menu control on mobile.| Control | What it does |
|---|---|
| Profile (gear icon, in the profile card) | Opens the Profile modal, where you can change your display name and password. |
| Sign out (logout icon, in the profile card) | Logs you out immediately and returns you to the login screen. |
| Menu (hamburger icon, mobile only) | Opens and closes the sidebar on a phone or narrow window. The icon turns into an X while the sidebar is open. |
Profile modal
The Profile modal is where you manage your own account. Open it from the gear icon in the sidebar profile card. It has two independent sections separated by a divider: Display Name at the top and Change Password below. The two sections save separately — changing one does not touch the other.Profile fields
| Field | What to enter | Required |
|---|---|---|
| Display Name | The name shown for your account across the console (for example, Jane Doe). Pre-filled with your current name. | No |
| Current Password | Your existing password, used to confirm it is really you before a change. | Yes (when changing password) |
| New Password | The new password you want to set. | Yes (when changing password) |
| Confirm New Password | Type the new password again. It must match New Password exactly. | Yes (when changing password) |
Profile buttons
| Button | What it does |
|---|---|
| Save Name | Saves the Display Name field. Shows Saving… and is disabled while it works. On success it updates your name across the console and shows a success message. If it fails, it shows an error message. |
| Change Password | Saves a new password. It first checks that New Password and Confirm New Password match. On success it clears all three password fields and shows a success message. If your current password is wrong (or anything else fails), it shows an error message. The button is disabled while saving. |
| Close (X icon, top-right) | Closes the modal without saving anything still in progress. You can also close it by pressing Escape or clicking outside the modal. |
The password checks happen before anything is saved: if the two new-password fields do not match, you will be told before the change is attempted. Each section has its own save button, so you can update just your name, just your password, or both in one visit.
Day-to-day flow
Once you are comfortable signing in and finding your way around, a normal working day follows this shape.Sign in and scan the Overview
Log in and check the dashboard home page for active bots, today’s call volume, and fleet availability.
Build or update a bot
Use the bot builder to set identity, instructions, policy, voice pipeline, behaviour, tools, knowledge, and CRM mapping.
Test the bot
Run a test call. Confirm the opening message, customer variables, response style, tools, recording, transcript, analysis, and CRM push all work.
Create a campaign
Choose the bot, the outbound numbers, the contact list, the time window, concurrency, and retry rules.
Escalate to engineering when
Some problems are not yours to fix. Hand these to engineering rather than retrying them yourself:- The fleet shows no capacity but workers should be free.
- Campaign calls stay stuck in a dialling or in-progress state far longer than expected.
- Many calls fail at once with the same error.
- Recordings are missing or playback returns an access error.
- A bot’s configuration fails to load for a valid, active bot.
- A CRM push is set up correctly in the console but keeps failing at runtime.
Next steps
Console tour
A guided walk through the sidebar and every section of the console.
Create a bot
Build your first voice agent step by step.