GenAI Integrations¶
Overview¶
GenAI Integrations lets an account use its own OpenAI and Google Gemini API keys for the AI features of QVOICE Platform, instead of the platform's default keys. Usage is then billed to the customer's own OpenAI / Google account.
The screen is optional. If both fields are left empty, every AI feature keeps working with the platform defaults, as long as the platform operator has configured them.
Where to Find It¶
The same screen is reachable from two places:
- AI → AI Agents → GenAI Integrations
- Config → Integrations → AI Transcription → GenAI Integrations
Functionality¶
| Field | Description |
|---|---|
| OpenAI API key | The customer's OpenAI key (sk-...). |
| Google Gemini API key | The customer's Google Gemini key. |
Speech-to-text credentials (Deepgram) are not set here. They belong to AI Transcription. ElevenLabs voices use the platform's ElevenLabs credentials; there is no field for an account-level ElevenLabs key.
Click Save to store the keys. Cancel discards unsaved changes. To go back to the platform defaults, clear a field and save.
Features that use these keys¶
| Feature | OpenAI key | Gemini key |
|---|---|---|
| AI Agents (Personas): live calls, voice preview, prompt assistant, flow diagram generation | ✓ | ✓ |
| AI Agents memory and frustration detection | ✓ | |
| AI Assistant | ✓ | |
| Meeting summaries in the web client | ✓ | |
| CRM email analysis (lead classification, intent, summary, disposition suggestion) | ✓ |
How It Works¶
Each time one of the features above calls OpenAI or Gemini, the key is resolved in this order:
- The account's key from GenAI Integrations, when set.
- Otherwise, the platform's default key.
The voice AI agent caches the resolved keys for a short time, so a changed key takes effect on new calls within minutes.
flowchart LR
F[AI feature] --> R{Account key set?}
R -- yes --> T[Customer's OpenAI / Gemini account]
R -- no --> P[Platform default key]Configuration¶
| Requirement | Details |
|---|---|
| Who can edit | Reseller administrators and platform super-administrators. Administrators of a regular (non-reseller) account do not see this screen. |
| Menu visibility | In the AI menu, the user's role must also grant at least one of the Personas, Knowledge or Memory permissions. |
| Keys | Created by the customer in their OpenAI / Google AI Studio accounts. The key must be allowed to use the models selected in the personas. |
Use Cases¶
Customer-paid AI usage. A reseller sells AI Agents to a large customer who wants AI costs on their own cloud bill. The reseller enters the customer's OpenAI key on the customer's account. From then on, that customer's persona calls, AI Assistant queries and meeting summaries are billed to the customer's OpenAI account.
Model access. A customer wants a persona on a Gemini real-time model that the platform key is not entitled to. They add their own Gemini key, and the persona model list and live calls use it.
Limitations¶
- Keys are not validated when saved. A wrong key only shows up when a feature fails to call the provider.
- The same key is used by every feature listed above. It cannot be chosen per feature or per persona.
- If neither the account nor the platform has a key, the features that need it fail.