Workspace Configuration
Configure your workspace settings to optimize Voxvaani for your organization’s communication needs. Workspace configuration involves setting up the core infrastructure — voice providers, AI models, email servers, integrations, and team access — that powers every campaign and automation you run.
Overview
A properly configured workspace is the foundation of a successful Voxvaani deployment. Without it, voice calls cannot be placed, emails cannot be sent, and AI features remain inactive. This guide walks you through every required configuration step in the recommended order.
What You’ll Need
Gather the following credentials before you begin. Keeping them on hand will let you complete the entire setup in one session.
| Credential | Where to Get It | Required For |
|---|---|---|
| SIP Credentials (username, password, host, port) | Your voice provider dashboard (SignalWire, Plivo, or Indian Route) | Outbound and inbound voice calls |
| SMTP Settings (host, port, username, password) | Your email service provider or IT administrator | Email campaign delivery and transactional emails |
| OpenAI API Key | OpenAI Platform | Conversational AI agents, smart chatbots, enhanced IVR flows |
| Gemini API Key | Google AI Studio | Alternative AI provider for agents and chatbots |
| Truecaller Credentials | Truecaller developer account | Contact enrichment and caller ID lookups |
| Meta Business Account | Meta Business Suite | WhatsApp messaging and campaign delivery |
Configuration Order
Follow this numbered sequence. Each step depends on the ones before it — skipping ahead without completing prerequisites will cause configuration failures.
- Voice Provider — Must be configured first. Voice is the primary communication channel, and campaign creation depends on an active SIP trunk.
- SMTP Server — Configure second. Email delivery is required for campaign notifications, password resets, and bulk mail dispatches.
- AI API Keys (OpenAI / Gemini) — Add after voice and email are working. AI agents depend on these keys to power conversational flows.
- WhatsApp Connection — Requires a functioning Meta Business Account. Connects via OAuth and depends on organization settings being complete.
- Truecaller Integration — Add last. Contact enrichment enhances your existing contact database but is not a dependency for other services.
- Team Invitations — Once all services are verified, invite team members so they can begin working with the fully configured platform.
Skipping the dependency order can lead to silent failures. For example, adding an AI key before configuring voice means any IVR agent you create will have nothing to connect to when placing calls.
Voice Provider Configuration
When you first access voice features, you will be prompted to configure your calling provider. Voxvaani supports three providers with distinct strengths.
Provider Comparison
| Provider | Best For | Supported Regions | Notes |
|---|---|---|---|
| SignalWire | US and international calling | Global | Reliable SIP trunking, competitive international rates, strong API |
| Plivo | Global reach, high volume | Global | Strong API, supports SMS alongside voice, carrier-grade infrastructure |
| Indian Route | Domestic Indian calling | India | Optimized for Indian phone numbers and regulatory compliance |
Required Credentials by Provider
All three providers use the same SIP credential format. Enter these in Settings under the voice section:
| Field | Example | Notes |
|---|---|---|
| SIP Username | your_account_sid | The account identifier assigned by your provider |
| SIP Password | •••••••• | The authentication credential from your provider dashboard |
| SIP Host | sip.signalwire.com | The server address; different for each provider |
| SIP Port | 5060 | Standard SIP port; change only if your provider specifies otherwise |
Setup Steps
- Choose your provider from the dropdown menu
- Enter your SIP Username — the account identifier from your provider
- Enter your SIP Password — the authentication credential from your provider
- Enter your SIP Host — the server address (e.g.,
sip.signalwire.com) - Set the SIP Port — typically
5060for standard SIP - Click Save and then Test Connection to verify
WhatsApp Connection
WhatsApp integration connects your Meta Business Account to Voxvaani through an OAuth flow. See the complete Connect Meta (WhatsApp) guide for detailed setup instructions, template management, and webhook configuration.
Email Configuration
Configure your SMTP server in Settings to enable email sending.
| Field | Recommended Value | Notes |
|---|---|---|
| Host | smtp.gmail.com (example) | Your SMTP server address |
| Port | 587 (TLS) or 465 (SSL) | Use TLS unless your provider requires SSL |
| Username | Your SMTP account email | Authentication credential |
| Password | Your SMTP password or app-specific password | Do not use your regular email password for services that support app-specific passwords |
| From Email | [email protected] | The sender address recipients will see |
| From Name | Your organization name | The display name next to the sender address |
After saving, use the Test SMTP button to send a verification email and confirm your settings are correct.
AI API Keys
Add your OpenAI or Gemini API key in Settings to unlock conversational AI agents, smart chatbots, and enhanced IVR flows. Both providers can be configured simultaneously — the system will use the provider you select when creating each AI agent.
Testing Your Configuration
After completing each step, run the corresponding test to catch misconfigurations before they affect production campaigns.
| Service | How to Test | Expected Result |
|---|---|---|
| Voice Provider | Click Test Connection next to SIP credentials | ”Connection successful” toast message |
| SMTP Server | Click Test SMTP next to email settings | Receive a test email in your inbox within 60 seconds |
| OpenAI API Key | Create a test AI agent and send a prompt | Agent responds with coherent text |
| Gemini API Key | Create a test AI agent with Gemini selected | Agent responds with coherent text |
| Send a test message to your own number | Message delivered to your WhatsApp app | |
| Truecaller | Enrich a known contact | Contact record displays additional data fields |
Always test each configuration after saving it. A misconfigured SIP host or an expired API key can silently break your campaigns. Use the built-in Test buttons next to each configuration section to validate your settings before relying on them in production.
Verification Checklist
After completing all configuration steps, confirm every item below:
- Voice provider test connection passes
- SMTP test email received
- AI agent responds to test prompts
- WhatsApp test message delivered
- Truecaller enrichment returns data
- Team members can log in and access their dashboards
Troubleshooting Common Setup Errors
| Symptom | Likely Cause | Resolution |
|---|---|---|
| ”Connection failed” on SIP test | Incorrect host or port, or firewall blocking SIP traffic | Verify host and port against provider dashboard; confirm port 5060 is open on your network |
| No test email received | Wrong SMTP port, blocked by spam filter, or authentication failure | Check spam folder; try port 587 instead of 465; verify credentials and use app-specific password if applicable |
| AI agent returns error | Invalid or expired API key, or insufficient API quota | Regenerate key from provider dashboard; check usage limits on OpenAI/Gemini console |
| WhatsApp OAuth fails | Meta Business Account not fully set up or missing permissions | Complete Meta Business verification; confirm whatsapp_business_messaging permission is granted |
| Truecaller returns no data | Invalid credentials or API rate limit reached | Regenerate credentials in Truecaller dashboard; check rate limit tier |
Best Practices
- Complete the full checklist before launching any campaign — partial configuration leads to failed deliveries
- Use separate API keys for development and production to limit the blast radius of a compromised key
- Document your configuration — maintain an internal record of which providers, ports, and accounts are in use
- Test after every change — even a minor SMTP port update can break email delivery