A bot is the voice agent that talks to your customers. You build one in the Ori console using a guided, multi-step wizard. This page explains how the wizard works, what every button in the wizard header does, and every field on the Identity and Behavior steps. The other steps each have their own dedicated page:

Prompts & policy

Instructions and Policy steps — system prompt, dynamic runtime prompt, post-call analysis, QC, auto dispositions, and the policy engine.

Voice pipeline

Speech-to-Text, the language model, and the voice (Text-to-Speech) engine.

Tools & integrations

End call, transfer, voicemail detection, custom tools, pre-call fetch, and post-call push.

Before you start

Have these ready so you can fill the wizard in one pass:
  • The bot’s name and the exact opening line you want customers to hear.
  • Any customer data fields (CRM or call variables) you plan to reference in the greeting.
  • Your call window: which days and hours the bot should accept calls, and in which timezone.

How the wizard works

Open Bots in the left navigation and click Create Bot. This opens the creation wizard at a fresh, blank bot. The wizard has six steps, shown in order along the top:
  1. Identity
  2. Instructions
  3. Policy
  4. Voice Pipeline
  5. Behavior
  6. Tools & Integrations
This page covers the wizard header and steps 1. Identity and 5. Behavior. The remaining steps are linked in the cards above.
The same wizard is used to edit an existing bot. When you open a bot and choose to edit it, you see these identical steps pre-filled with the bot’s current settings. Everything below applies to both creating and editing.

The step indicator

Across the top of the wizard is a numbered stepper bar — a row of circles, one per step, joined by connectors.
StateWhat it looks likeMeaning
Future stepLight circleYou have not reached this step yet.
Active stepCircle in the primary brand colorThis is the step you are on now.
Completed stepCheckmark inside a primary-color circleYou have moved past this step.
The connectors between circles fill in with the primary color as steps are completed, so you can see your progress at a glance.
You can click any step circle to jump straight back to an earlier step — handy for fixing something without clicking Previous several times. Your entries on the steps you skip past are kept.

Wizard header buttons

These controls move you through the wizard and submit (or abandon) the bot.
ButtonWhat happens when you click itNotes
PreviousMoves back one step.Disabled while you are on the first step (Identity), since there is nothing before it.
ContinueMoves forward one step.Available on steps 1 through 5.
Create BotSubmits the whole bot. Appears on the final step (Tools & Integrations). On success, you are taken to the new bot’s detail page.See the validation note below.
CancelAbandons the wizard and returns you to the previous page. Nothing is saved.Available throughout.
When you click Create Bot, the platform validates every step, not just the one you are on. If a required field is missing or invalid anywhere in the wizard, you see an error message and are taken to the first step that contains a problem so you can fix it. The bot is not created until all validation passes.
There is no separate Save button mid-wizard. A new bot is committed only when you click Create Bot on the last step. If you click Cancel or leave the page before then, your work is discarded.

Identity step

The Identity step is where the bot gets its name and its first spoken line, plus optional behavior for handling silent customers.

Fields

FieldWhat to enterRequiredDefault / validation
Bot NameA clear, unique name for the bot, for example My Voice Bot. Use a name your team will recognize in lists and reports — client, use case, and language are all helpful.YesLength limit enforced by the backend.
Opening MessageThe first thing the bot says when a call connects, for example Hello! How can I help you today?. Keep it short and natural. You can include customer variables (see below).YesRequired fields are marked with an asterisk.
Re-engagementA toggle. Turn it on if you want the bot to nudge a customer who has gone quiet before the call is given up. Off by default.NoWhen off, the fields below are hidden.
When Re-engagement is enabled, these additional fields appear:
FieldWhat to enterRequiredDefault
MessagesOne or more short lines the bot can say to coax a silent customer back into the conversation. A line is picked at random on each attempt — add two or more for variety.No
First Attempt GapSeconds of silence to wait before the first re-engagement nudge, for example 8.No8 seconds
Subsequent GapSeconds of silence to wait before the next attempt; after this the call is disconnected, for example 5.No5 seconds
Max RetriesHow many times the bot will nudge before hanging up.No2

Re-engagement message buttons

The Messages list is built one line at a time.
ButtonWhat it does
Add messageAdds a new, empty re-engagement message line you can type into.
RemoveDeletes that message line from the list.
Add at least two re-engagement messages. Because a line is chosen at random each time, varied wording stops a silent-but-listening customer from hearing the exact same sentence twice and sounds more natural.

Writing the opening message

The opening message is the customer’s first impression, so make it warm and brief. You can drop in customer-specific values using variables in double curly braces:
Namaste {{CUSTOMERNAME}}, main aapki kaise madad kar sakti hoon?
If you use a variable such as {{CUSTOMERNAME}}, make sure that field is actually supplied — by the campaign data, the dialout request, or a pre-call fetch. A variable with no value will read out awkwardly or be skipped.
The Re-engagement section is collapsed by default. If a required field fails validation, the error message appears inline directly under that field.

Behavior step

The Behavior step controls how the bot listens, how long calls can run, and when the bot is allowed to take calls. It also lets you add subtle background sound so the bot feels more lifelike.

Listening sensitivity (voice activity detection)

These four sliders tune how the bot detects when the customer is speaking versus silent. Each slider shows its current value as you drag it.
FieldWhat it controlsRange / step
VAD ConfidenceHow certain the system must be that it is hearing real speech before it reacts.0 to 1, step 0.05
VAD Start SecsHow long the customer must be speaking before the bot treats it as the start of speech.0 to 1, step 0.05
VAD Stop SecsHow long the customer must be silent before the bot decides they have finished talking.0 to 2, step 0.1
VAD Min VolumeThe minimum audio loudness that counts as speech, which helps filter out background noise.0 to 1, step 0.05
VAD Stop Secs should stay low (around 0.2 seconds). Setting it too high makes the bot wait too long after the customer stops talking and can cause speech to be missed. If soft-spoken customers are not being heard at all, lower VAD Min Volume rather than raising the stop time.

Interruptions

FieldWhat to enterRange / step
Min Words to InterruptThe number of words the customer must speak before they are allowed to cut the bot off mid-sentence. A higher number stops the bot from being interrupted by short noises like “hmm” or “okay”.1 to 10, step 1

Call duration and timezone

FieldWhat to enterRequiredDefault
Max Call DurationThe longest a single call may run, in seconds, before the bot automatically hangs up. This is a safety cap against runaway calls.No600 seconds (10 minutes)
TimezoneThe timezone identifier used for all timestamps the bot reports after a call, for example UTC or Asia/Kolkata. Set this to match the customer base so post-call times read correctly.NoUTC

Active hours

FieldWhat to enterRequiredDefault
Active HoursA toggle. Turn it on to restrict the hours during which the bot will accept calls. Calls that arrive outside the window are rejected immediately.NoOff
When Active Hours is enabled, these fields appear:
FieldWhat to enter
Start TimeThe time the call window opens, in HH:MM 24-hour format, for example 09:00.
End TimeThe time the call window closes, in HH:MM 24-hour format, for example 18:00.
Active DaysWhich days of the week the bot accepts calls.
The Active Days picker is a row of day buttons (Mon through Sun).
ButtonWhat it doesState
Day button (Mon–Sun)Click a day to switch it on or off.A selected day shows the primary brand color background with matching text; an unselected day shows a light background with muted text.
The Start Time, End Time, and Active Days controls only appear once Active Hours is switched on. The window and day rules are evaluated using the Timezone you set above.

Background ambience

A small amount of background sound can mask the brief pauses while the bot thinks, making it feel more like a real call center.
FieldWhat to enterRequiredDefault
Background AmbienceA toggle. Turn it on to mix a subtle ambient sound under the bot’s voice.NoOff
When Background Ambience is enabled, these fields appear:
FieldWhat to enter
Sound TypeChoose the ambience: Office (keyboard and air-conditioner hum), Café (soft chatter and cups), or Comfort Noise (a minimal background hiss).
VolumeHow loud the ambience plays, as a percentage from 1% to 30%. The slider shows the current percentage.
Keep the ambience volume low. The aim is to take the edge off silent gaps, not to compete with the bot’s voice. Start around the lower end of the range and listen to a test call before raising it.

Save and test

Once you reach the final step and click Create Bot, the bot is created and you land on its detail page. Before pointing real campaigns at it:
1

Run a test call

Use the test call control on the bot detail page and confirm the bot speaks the right opening message.
2

Check variables render

Make sure any {{...}} variables in the opening message fill in with real values.
3

Check listening behavior

Speak softly and pause to confirm the bot hears you, waits the right amount of time, and re-engages if you go quiet.
4

Confirm the call window

If you set Active Hours, test that calls inside the window connect and that the bot rejects calls outside it.
5

Review the call afterward

Open the call detail and inspect the transcript, recording, and timestamps to confirm the timezone reads correctly.
Fix the bot’s configuration here before building campaigns around it.