Enable Voice Input in Your AI Hub
Your users can speak their answers instead of typing and review the text before submitting. Enable Voice input in Hub Settings → Customize, confirm Turn on, then select Save Pending Edits.
Your users can now speak their answers instead of typing them. OBIE turns each recording into text they can review and edit before submitting. To enable it, open Hub Settings → Customize, set Voice input to On, confirm Turn on, then select Save Pending Edits.
Speak your answer, then make it yours
Sometimes it's easier to explain an idea out loud than to type it. Voice input gives your users another way to work through your journeys and conversations without changing how they submit their answers.
It isn't a live voice conversation. Users record what they want to say, OBIE converts it to text, and they decide when to submit it. Typing is still available.
Turn on voice input for your AI Hub
Voice input is Off by default, including in existing hubs. Creators choose whether to make it available.
1. Open Your AI Hubs and select Settings from your hub's ⋯ menu.
2. Open Customize.
3. Find Voice input and choose On.
4. In the Turn on voice input? dialog, review the token-use notice and select Turn on.
5. Select Save Pending Edits to apply the change to your live hub.
This enables voice input in steps and conversations that follow the AI Hub setting. Anything you've explicitly set to Off stays off.
Important: Turning recordings into text uses your AI Hub's tokens. The confirmation dialog explains this before you enable the feature.
Choose where users can speak
You don't have to enable voice input everywhere. You can control it for an individual step or conversation.
Open that step's or conversation's settings, choose Customize, and find Voice input. You'll see three options:
- Use AI Hub setting (On) or Use AI Hub setting (Off): Follow the hub's setting. The value in parentheses shows the current hub setting. This is the default.
- On: Enable voice input here, even if it's off for the hub.
- Off: Disable voice input here, even if it's on for the hub.
If your change turns voice input on, confirm Turn on when prompted. Then select Save Pending Edits.
For example, you can leave voice input off for your hub and turn it on for a step where users describe their goals. Or you can enable it across the hub but keep a particular step text-only.
To turn it off later, choose Off and save your pending edits. Remember that a step or conversation explicitly set to On won't follow a hub-wide change to Off.
Where the microphone appears
When voice input is enabled, users can record in:
- Short-answer and long-answer question fields.
- The Other text field in choice questions.
- A step's Refine chat.
- Conversation chat inputs.
It isn't available in timeline session fields. Deliverable steps don't have a voice input setting because they don't ask users to enter answers.
How users record an answer
1. Select the Voice input microphone button in a supported text field.
2. Allow microphone access if the browser asks.
3. Speak your answer. A Recording indicator shows the time remaining.
4. Select Stop recording when you're finished. Recordings stop automatically after five minutes.
5. Wait while OBIE transcribes the recording. The text is added to the field, alongside anything you've already typed.
6. Review the text, make any changes, then continue or send your message as usual.
Recording doesn't submit an answer automatically. While a recording is running or being transcribed, some input and navigation controls are temporarily unavailable. Wait for the text to appear before continuing.
After saving your settings, use Preview as User to check that the microphone appears in an eligible field.
Frequently asked questions
- Why can't a user see the microphone?
- Check that voice input is enabled and that you've selected Save Pending Edits. An individual step or conversation may be set to Off, even when the hub is on. The microphone also won't appear in unsupported fields or browsers that don't support recording.
- What if microphone access is blocked?
- Allow microphone access for the hub's website in the browser's site permissions, then try again. Users can still type their answers if they don't want to grant access.
- What if a recording won't transcribe?
- Speak clearly near the microphone. If OBIE reports that no speech was detected or that transcription failed, record again or type the answer.
- Does voice input change how OBIE responds?
- Voice input turns speech into text. Users review and submit that text through the same question or chat field they'd use when typing. It doesn't turn the experience into a live audio call.
Related help articles
Customize Your Hub
Open **Hub Settings** to control your hub's name, appearance, content, emails, AI behavior, access, login experience, domains, and analytics. **General** holds the logo and background; **Customize** holds the layout, theme, style, labels, badge, and default content colors.
Read moreEdit Steps and Questions
Open a step to choose its type, edit its name and prompt, add questions, and control visibility. OBIE supports Regular, Fixed Guidance, Timeline, Option, and Deliverable steps, plus six question types.
Read moreUse Conversations in Your Hub
Use Page Settings to control the whole Conversations section, and open an individual Conversation to control its prompt, documents, prerequisites, and visibility. Prerequisites depend on required steps; Visibility rules support broader conditions such as tags, offers, dates, and progress.
Read more