AI Agent Management
Settings
Configure workspace, chatbot, billing, notification, security, and usage options.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available QwryAI pages before exploring further.
Configuration
Settings are split between workspace-level controls and chatbot-level controls. Workspace settings affect team access, billing, security, and usage. Chatbot settings affect a specific assistant's behavior and deployment.
- General workspace details
- Security and access controls
- Notifications and team alerts
- Usage and plan limits
- Billing provider status
- Chatbot-specific behavior and appearance
- Check workspace-level settings separately from chatbot settings.
- Billing, security, and team access affect the whole workspace.
Instruction example
Role:
You are a QwryAI customer support assistant for an ecommerce store.
Behavior:
- Answer only from approved source content.
- Keep answers concise and specific.
- Ask one clarifying question when the request is ambiguous.
- Escalate to a human agent when the customer needs account-specific help.
Unavailable answer:
If the answer is not in the source content, explain that you do not have enough information and offer the support handoff path.Recommended Setup
Voice usage example
If a voice-enabled agent receives a long customer call, review call duration, message requests, transcription behavior, and model usage together instead of looking at only one metric.
| Component | What to review |
|---|---|
| Call duration | How long the customer stayed connected. |
| AI requests | How many assistant turns were generated during the call. |
| Voice settings | Transcriber language, silence threshold, provider, voice speed, and stability. |
| Plan limits | Daily sessions, concurrent sessions, recordings, and available credits. |
- Review workspace name and account details.
- Invite the team members who need access.
- Confirm notification preferences.
- Review usage limits and billing status.
- Configure security options.
- Return to the chatbot and test before deployment.
- Confirm the subscription is active.
- Upgrade before important limits block live support.
| Setting area | Review before launch |
|---|---|
| General | Workspace and chatbot names are clear for the team. |
| Team access | Only the right teammates can change production settings. |
| Notifications | Support alerts go to monitored inboxes or channels. |
| Billing and usage | Plan, credits, and limits can handle expected traffic. |
| Security | 2FA, developer keys, and access controls match your risk level. |
| Agent setting | What to configure |
|---|---|
| Instructions | Tone, answer boundaries, URL behavior, examples, and unavailable-answer handling. |
| Model and temperature | Accuracy, creativity, latency, and cost tradeoffs for the support use case. |
| Voice | Transcriber language, silence threshold, noise sensitivity, voice provider, speed, stability, and session messages. |
| Limits | Daily sessions, concurrent sessions, call duration, recordings, and voice credit usage. |
| Security and webhooks | Allowed domains, webhook destinations, and sensitive-event routing. |