How it works
From a first sign-in to a voice of their own
How an owner’s voice and persona are made, checked and handed back to them for review, and where Ovance’s own console fits.
Onboarding at a glance
Scroll to see how it flows
Step 1:Two doors, one engine
- Your app
- Your sign-in
- Owner
- App
- Console
Owners sign in to the app they already use. Ovance’s own console is a separate door, for Ovance’s administrators only.
- Owners never see Ovance. The app keeps its own sign-in and its own brand. Its server speaks to Ovance on the owner’s behalf.
- Same engine behind both. Every onboarding step below works the same way whichever door it is reached through.
Step 2:An account of its own
- Platform API
- App
- API
- Data
The first sign-in creates an account and the person inside it. From that moment the account’s data is sealed off from every other.
- Platform, account, person. An app is a platform; each customer is an account; the voice belongs to one person in it.
- Its own key. A key is created for the account alone. Everything personal is encrypted under it.
- Safe to retry. A repeated request never creates a second account.
- Database. The database itself refuses to show one account’s rows to another.
- Key vault. One key per account. Destroying it is how an account is deleted for good, backups included.
Step 3:What they would say
- About ten minutes
- Owner
- App
- API
- Model
A written conversation that learns how the owner greets people, where their boundaries are, and what they do when they don’t know.
- A conversation, not a form. Every answer can earn a follow-up. It stops when the ground is covered, not when a list runs out.
- Kept word for word. Answers are stored exactly as written. They are evidence, and the persona must quote from them.
- Never asked twice. Anything already answered aloud is credited, so the owner is not asked for it again.
Step 4:The voice sample
- About two minutes
- Owner
- Voice
- Speech
- Data
About two minutes of speech. The audio goes straight from the owner’s browser to the voice engine, never through the app.
Step 5:A spoken interview, if wanted
- Optional
- Owner
- Voice
- Model
Optional. An AI interviewer talks with the owner to hear how they really sound: their stories, their laugh, their way of closing a call.
- Typed or spoken. The same interview can be typed or held aloud.
- It asks about what they wrote. Questions build on the questionnaire, which draws out real speech instead of performed speech.
- Never holds onboarding up. With today’s voice it is not required. It sits under "More you can do".
Step 6:Building the persona
- Grounded in their own words
- API
- Model
- Data
What the owner wrote and said becomes a description of how they talk and decide. Nothing in it may be invented.
Step 7:The owner has the last word
- Nothing hidden
- Owner
- App
- API
Before it ever speaks for them, the owner sees what it learned and can keep, change or reject each point.
- Review what it learned. Each thing it believes about the owner is shown with the words it came from.
- Never say. A list of things the double must never say aloud. Once saved, even the owner’s app cannot read them back.
- The result, as it will be used. The owner can read the persona exactly as the double will follow it.
Step 8:Ready for calls
- A number and its rules
- Owner
- App
- API
- Voice
A number, the people who may reach it, and a rule for each. Then a test call, to hear it for themselves.
- A shield number. A second number, chosen by area code, that the double answers.
- Contacts and rules. For each person: answer, take a message, pass it on, or politely decline.
- Try it. A call from the browser, straight to the voice engine, before any real caller rings.
The console, and what stands behind onboarding
Everything onboarding touches is lit.
Cyan edge below: used in onboarding
Sign-in
- Owners Sign in to their app. Ovance never holds their password.
Data
- Database Accounts, evidence, personas, consent, review items.
- Key vault One key per account; destroying it is the deletion receipt.
- File storage Voice samples and recordings. Biometric data, reachable only through the API.
Models
- Interviewer Leads the questionnaire and the interview, and judges when enough is covered.
- Persona builder and verifier One model writes; a different one decides what stands.
- Voice The cloned voice. The consent text names everyone who holds it.
Our services
- Platform API Accounts, onboarding, personas, numbers, contacts.
- Voice engine Recording, the spoken interview, test calls.
- Console For Ovance’s administrators.
Promises we keep
- Consent first No voice is made without recorded consent, and it can be withdrawn.
- Deleted means deleted Closing an account destroys its key, so its data can’t be read again, and its voice is removed from every provider that holds it.
- It won’t make things up Every line of the persona traces back to the owner’s own words.