ai calling Logo / Documentation

App Settings

The Settings page allows you to configure branding, API integrations, email, scheduling, and payment settings for your workspace or white-label instance. Proper configuration ensures all features work correctly and your application reflects your brand identity.

Common Use Cases

White-Label Branding

Customize your application with your logo and app name. Create a branded experience for your clients or end users.

API Integration Setup

Connect your Twilio, VAPI, and Cal.com accounts to enable calling, AI assistants, and appointment scheduling features.

Email Configuration

Configure SMTP settings to send email templates, appointment confirmations, and notifications through your own email server.

Payment Setup

Configure Stripe for subscription billing and wallet refills. Enable secure payment processing for your users.

Key Benefits

Centralized Configuration

Manage all application settings from one place. No need to edit configuration files or access server settings directly.

Secure Storage

API keys and sensitive credentials are encrypted at rest. Your credentials are protected with industry-standard encryption.

Brand Customization

Customize your application's appearance with your logo and app name. Create a professional, branded experience.

Access Control

Some settings (like Stripe) are restricted to Super Admins only. Control who can access sensitive configuration options.

Branding

Customize your application's appearance with your logo and app name. This branding appears in emails, invoices, and throughout the application interface.

App Name

Set your application name to customize how your brand appears throughout the system:

  • Enter your desired app name in the App Name field
  • The app name appears in email templates (via {company} variable), invoices, and system notifications
  • Use a clear, professional name that represents your brand

Logo Upload

Upload your company logo to display throughout the application:

Logo Requirements

  • Format: PNG format only
  • File Size: Maximum 2 MB
  • Recommended: Transparent background PNG for best appearance
  • Dimensions: Square or rectangular logos work best (e.g., 200x200px or 400x100px)

Where Logo Appears: Your logo is displayed in emails, invoices, and can be used in templates via the {company} variable context.

API Settings

Configure API credentials for third-party services that power your application's features. These credentials are encrypted and stored securely.

Twilio Configuration

Twilio powers voice calls and SMS messaging. Configure your Twilio credentials:

Twilio SID

Your Twilio Account SID. Found in your Twilio Console dashboard. Format: ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Twilio Token

Your Twilio Auth Token. Found in your Twilio Console dashboard. Keep this secret and never share it publicly.

Getting Twilio Credentials: Sign up at twilio.com, then find your Account SID and Auth Token in the Console dashboard. These are required for making calls and sending SMS.

VAPI Configuration

VAPI (Voice API) powers AI assistant conversations. Configure your VAPI token:

VAPI Token

Your VAPI API token. Found in your VAPI dashboard. This token enables AI assistant functionality for voice conversations.

Cal.com Configuration

Cal.com enables appointment scheduling. Configure your Cal.com API key:

Cal.com Key

Your Cal.com API key. Found in your Cal.com account settings. This key enables appointment scheduling and calendar integration.

Cal.com Settings

Configure time zone and event types for appointment scheduling integration with Cal.com.

Time Zone

Select your time zone to ensure appointments are scheduled in the correct time zone:

  • Choose your time zone from the dropdown menu
  • This ensures appointment times are displayed and scheduled correctly
  • Common time zones: America/New_York, America/Los_Angeles, Europe/London, etc.

Event Types

Select which Cal.com event type to use for appointments:

  • Choose an event type from the dropdown (populated from your Cal.com account)
  • Event types define the duration and settings for scheduled appointments
  • Click Refresh Event Types to reload available event types from Cal.com

Refresh Event Types: If you create new event types in Cal.com, use the "Refresh Event Types" button to update the list in Settings. This ensures you can select newly created event types.

Mail Configuration (SMTP)

Configure SMTP settings to send email templates, appointment confirmations, and notifications through your own email server.

SMTP Settings

Mail Driver

Select your email provider (e.g., smtp, sendmail, mailgun). Most users will use "smtp".

Mail Host

Your SMTP server hostname (e.g., smtp.gmail.com, smtp.mailgun.org, mail.yourdomain.com).

Mail Port

SMTP port number. Common ports: 587 (TLS), 465 (SSL), 25 (unencrypted).

Mail Username

Your SMTP username (usually your email address or SMTP account username).

Mail Password

Your SMTP password or app-specific password. For Gmail, use an app password, not your regular password.

Mail Encryption

Encryption method: TLS or SSL. Match this with your port (587 = TLS, 465 = SSL).

From Address & Name

Configure the sender information that appears in outgoing emails:

From Address

The email address that appears as the sender (e.g., noreply@yourdomain.com, support@yourdomain.com).

From Name

The display name that appears as the sender (e.g., "Your Company Name", "Support Team").

Gmail Users: If using Gmail, you'll need to generate an "App Password" in your Google Account settings. Regular passwords won't work with SMTP. Enable 2-factor authentication first, then create an app password.

Stripe Settings (Super Admin Only)

Configure Stripe for payment processing, subscription billing, and wallet refills. These settings are restricted to Super Admins only for security.

Stripe Mode

Select whether to use test or live mode:

Test Mode

Use test API keys for development and testing. No real charges are processed. Use test card numbers from Stripe docs.

Live Mode

Use live API keys for production. Real charges are processed. Only switch to live mode when ready for production use.

Stripe API Keys

Publishable Key

Your Stripe publishable key (starts with pk_). Safe to use in frontend code. Found in Stripe Dashboard → Developers → API keys.

Secret Key

Your Stripe secret key (starts with sk_). Keep this secret! Never share or commit to version control. Found in Stripe Dashboard → Developers → API keys.

Webhook Secret

Your Stripe webhook signing secret (starts with whsec_). Used to verify webhook requests from Stripe. Found in Stripe Dashboard → Developers → Webhooks.

Security Warning: Stripe secret keys and webhook secrets are highly sensitive. Only Super Admins should have access to these settings. Never share these keys or commit them to version control.

Security Best Practices

Follow these security practices to protect your API keys and sensitive configuration data.

API Key Management

  • Rotate Regularly: Periodically rotate API keys, especially if you suspect they may have been compromised. Update keys in Settings and test functionality.
  • Never Share: Never share API keys in templates, prompts, documentation, or public channels. Treat them like passwords.
  • Use Test Keys First: When setting up new integrations, use test keys first to verify configuration before switching to live keys.
  • Monitor Usage: Regularly check your API provider dashboards for unusual activity or unexpected usage.

Access Control

  • Restrict Settings Access: Only grant Settings access to trusted administrators. Payment settings (Stripe) are automatically restricted to Super Admins.
  • Review Permissions: Regularly review who has access to Settings and remove access for users who no longer need it.
  • Use Environment Variables: For sensitive values, consider using environment variables where applicable (if your deployment supports it).

Data Protection

  • Encryption: API keys and sensitive credentials are automatically encrypted at rest. The system handles encryption/decryption transparently.
  • Secure Transmission: Always use HTTPS when accessing the Settings page. Never configure settings over unencrypted connections.
  • Backup Security: If backing up settings, ensure backups are encrypted and stored securely. Don't store unencrypted API keys in backups.

Troubleshooting

Calls failing or not connecting

Checklist:

  • Twilio credentials: Verify Twilio SID and Token are correct. Check for typos or extra spaces.
  • Twilio account status: Ensure your Twilio account is active and has sufficient balance.
  • VAPI token: If using AI assistants, verify the VAPI token is correct and valid.
  • Number capabilities: Check that your phone numbers have voice capabilities enabled in Twilio.
  • Test credentials: Try making a test call from Twilio Console to verify credentials work independently.
Appointments/bookings not syncing with Cal.com

Checklist:

  • Cal.com key: Verify the Cal.com API key is correct and has proper permissions.
  • Event type: Ensure the selected event type exists in your Cal.com account and is active.
  • Refresh event types: Click "Refresh Event Types" to reload available event types from Cal.com.
  • Time zone: Verify the time zone setting matches your Cal.com account time zone.
  • Cal.com account: Check that your Cal.com account is active and accessible.
Emails not sending

Checklist:

  • SMTP settings: Verify all SMTP settings (host, port, username, password, encryption) are correct.
  • Port and encryption: Ensure port matches encryption (587 = TLS, 465 = SSL). Try different combinations if needed.
  • Credentials: Verify username and password are correct. For Gmail, use an app password, not your regular password.
  • Firewall/network: Check if your server can connect to the SMTP server. Some networks block SMTP ports.
  • Provider logs: Check your email provider's logs for authentication errors or blocked attempts.
  • From address: Ensure the "From Address" is valid and matches your SMTP account (some providers require this).
  • Test email: Try sending a test email from your email provider's interface to verify credentials work.
Stripe payments not working

Checklist:

  • Stripe mode: Verify you're using the correct mode (test vs. live) and matching API keys for that mode.
  • API keys: Ensure Publishable Key and Secret Key are correct and match the selected mode.
  • Key format: Verify keys start with correct prefixes (pk_ for publishable, sk_ for secret).
  • Webhook secret: If using webhooks, verify the webhook secret is correct and matches your Stripe webhook configuration.
  • Stripe account: Check that your Stripe account is active and in good standing.
  • Test mode: Test with Stripe test card numbers first to verify configuration before using live mode.