Airgentic Help
This module covers voice interaction capabilities in Airgentic. Read this when your service has voice mode enabled or when you're planning to enable it.
When voice mode is enabled:
Voice and text can be mixed freely — users aren't locked into one mode.
Voice mode uses the same:
- Agents and routing
- Knowledge sources and search
- Functions and capabilities
The main difference is how responses are phrased — voice responses may be adapted for spoken delivery.
Voice settings are found in Service Configuration → Voice Mode.
Toggle voice mode on or off. When disabled, the microphone button doesn't appear.
A block of instructions prepended to every voice interaction:
What to include:
- Language and accent preferences
- Tone adjustments for spoken delivery
- Instructions to keep responses concise
- Guidance on pronunciation or terminology
Example:
Speak in Australian English with a friendly, conversational tone.
Keep responses brief and easy to follow when spoken aloud.
Avoid long lists; summarise instead.
The preamble ensures consistent voice personality across all interactions.
The initial prompt for voice sessions — defines the greeting and initial behaviour:
What to include:
- How to greet the user
- What to offer or ask
Example:
You are a helpful assistant for {{title}}. Greet the user warmly and ask how you can help them today.
The {{title}} substitution inserts your service name.
Voice responses often need different phrasing:
| Text | Voice |
|---|---|
| Long, detailed answers | Shorter, summarised answers |
| Bullet lists | Numbered or flowing sequences |
| Exact URLs | "I'll show you a link" (since URLs are in the text too) |
| Technical precision | Plain language explanations |
The AI naturally adapts when in voice mode, but you can guide this further in your preamble.
Some content works better in text:
- Long lists of options
- Detailed specifications
- Step-by-step instructions with many steps
Consider how your content will sound when spoken. Very technical or list-heavy content may be harder to follow in voice.
Voice interactions feel more personal. The AI should sound like a helpful colleague, not a document being read aloud.
When testing in Admin Chat:
- Enable voice mode
- Actually speak your test questions
- Listen to the responses
- Check if they sound natural and helpful
Voice may be particularly useful for:
- Mobile users
- Accessibility needs
- Hands-busy scenarios
- Users who prefer speaking to typing
Not every service needs voice. Enable it when it adds value for your users.
Back to: Optional Deep-Dives