Organization Settings
Configure your organization’s core infrastructure — voice providers, email servers, AI API keys, and contact enrichment services. Proper configuration of these settings is required before you can use voice calling, email sending, or AI-powered features.
Navigate to Settings from the sidebar. The Voice Provider, SMTP, and AI API Keys sections are all on the main Settings page at /dashboard/settings.
Configuration Checklist
Complete these steps in order before launching your first campaign:
- Set your voice provider — Choose SignalWire, Plivo, or Indian Route based on your calling region. Click Test Connection to verify credentials.
- Configure SMTP — Enter your email server details. Click Test SMTP to send a verification email.
- Add AI API keys — Configure OpenAI and/or Gemini keys to enable conversational AI agents and chatbots.
- Set up Truecaller (optional) — Enable caller identification and spam detection for incoming contacts.
All settings are scoped to your organization — changes apply to every user within your workspace.
Voice Provider
Configure your calling provider to enable voice campaigns and IVR calling:
| Field | Description |
|---|---|
| Provider | SignalWire, Plivo, or Indian Route |
| SIP Username | Your SIP account username from the provider dashboard |
| SIP Password | Your SIP account password from the provider dashboard |
| SIP Host | Provider’s SIP server address (e.g., sip.signalwire.com) |
| SIP Port | Connection port (usually 5060 for standard SIP) |
Voice Provider Comparison
| Feature | SignalWire | Plivo | Indian Route |
|---|---|---|---|
| Best For | US and international calling | Global high-volume campaigns | Domestic Indian calling |
| Max Concurrent Calls | Depends on account tier | Depends on account tier | Depends on account tier |
| International Reach | Strong | Excellent | Limited (India-focused) |
| SMS Support | Yes | Yes | No |
| API Quality | Good REST API | Excellent REST API | SIP-only |
| Setup Complexity | Medium | Medium | Low |
| Pricing Model | Per-minute | Per-minute | Per-minute |
| Compliance | US and international regulations | Global regulations | Indian TRAI regulations |
| Requires | SignalWire account + SIP credentials | Plivo account + SIP credentials | Provider credentials |
Choose Indian Route for campaigns targeting Indian phone numbers. This provider is optimized for Indian telecom compliance and typically offers better answer rates on domestic Indian calls. Choose SignalWire or Plivo for international campaigns or when you need SMS capabilities alongside voice.
Troubleshooting Provider Connections
| Symptom | Likely Cause | Fix |
|---|---|---|
| Test Connection fails immediately | Wrong host, port, or credentials | Double-check SIP Host and Port; verify credentials are not expired |
| Connection succeeds but calls drop | Codec mismatch or network firewall | Check provider dashboard for supported codecs; ensure SIP port (5060) is open |
| Calls go straight to voicemail | SIP registration issue | Re-enter credentials and re-test; contact provider to confirm account is active |
| One-way audio on calls | NAT/firewall blocking RTP | Ensure UDP ports 16384-32768 are open for RTP traffic |
SMTP Configuration
Configure your email delivery server to enable transactional and bulk email sending:
| Field | Description |
|---|---|
| Host | SMTP server address (e.g., smtp.gmail.com, smtp.sendgrid.net) |
| Port | SMTP connection port — see port recommendations below |
| Username | SMTP authentication username (often your full email address) |
| Password | SMTP authentication password or app-specific password |
| From Email | Default sender email address that recipients see |
| From Name | Default sender display name (e.g., your organization name) |
| Security | Transport encryption — TLS or SSL |
Port Quick Reference
| Port | Protocol | Encryption | When to Use |
|---|---|---|---|
| 587 | SMTP submission with STARTTLS | Opportunistic (starts plain, upgrades to TLS) | Recommended for most providers. Industry standard. |
| 465 | SMTP with implicit TLS | Mandatory (TLS from connection start) | Use if your provider requires implicit SSL on connect (legacy, but still supported by some providers) |
| 2525 | SMTP submission (alternative) | Configurable | Fallback if 587 is blocked by your network |
| 25 | Plain SMTP relay | None or STARTTLS | Generally blocked by ISPs and cloud providers. Do not use for production. |
Port 587 with TLS is the industry standard for modern SMTP submission. If your provider supports it, use 587. Port 465 is legacy but still supported by Gmail, Yahoo, and some shared hosting providers. Port 25 is the traditional SMTP relay port — virtually all cloud providers and ISPs block it for email submission to prevent spam.
Testing SMTP
After configuring SMTP, use the Test SMTP button to send a verification email to your registered email address. Check your inbox (and spam folder) for the test message. If the test fails:
- Verify the hostname and port match your provider’s recommended settings.
- Confirm the username/password are correct — some providers require app-specific passwords rather than your account password.
- Check that your SMTP provider allows connections from Voxvaani’s IP range (some providers require IP whitelisting).
- Try the alternate port if your provider offers one.
AI API Keys
Configure AI provider keys to enable conversational AI agents, smart chatbots, and AI-assisted campaign features:
| Provider | API Key Field | Purpose |
|---|---|---|
| OpenAI | API Key | Powers conversational AI agents, smart IVR responses, and chatbot interactions |
| Gemini | API Key | Alternative AI backend for agents and chatbots (Google AI) |
Both providers can be configured simultaneously. AI features will use the provider you select when creating an AI agent.
API keys grant programmatic access to paid AI services. Anyone with your key can make requests on your behalf, potentially incurring charges. Store keys securely and never commit them to version control or share them in plain text. Rotate keys immediately if you suspect they have been exposed.
Truecaller Integration
Enable Truecaller to enrich incoming contact data with caller identification and spam detection:
- Obtain your Truecaller API credentials from the Truecaller developer portal.
- Enter your credentials in the Truecaller section of Organization Settings.
- Toggle the integration to Active.
- Contacts imported or scraped through the platform will now include Truecaller enrichment data.
Configuration Best Practices
| Practice | Recommendation |
|---|---|
| Test before using | Always use the built-in Test buttons to verify each configuration |
| Use separate credentials for dev/prod | Maintain different API keys for development and production environments |
| Rotate keys regularly | Change API keys and SMTP passwords every 90 days |
| Document your setup | Keep an internal record of which providers and ports are configured |
| Monitor usage | Check the dashboard periodically to ensure no unexpected API consumption |