Skip to content

Update exotel-chatbot outbound README #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markbackman merged 1 commit into from
Dec 21, 2025
Merged

Update exotel-chatbot outbound README #136

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 3 additions & 31 deletions exotel-chatbot/outbound/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,21 +64,6 @@ cp env.example .env
# Edit .env with your API keys
```

## Environment Configuration

The bot supports two deployment modes controlled by the `ENV` variable:

### Local Development (`ENV=local`)

- Uses your local server or ngrok URL for WebSocket connections
- Default configuration for development and testing
- WebSocket connections go directly to your running server

### Production (`ENV=production`)

- Uses Pipecat Cloud WebSocket URLs automatically
- WebSocket connections route through Pipecat Cloud infrastructure

## Local Development

### Configure Your Bot Number in App Bazaar
Expand Down Expand Up @@ -176,27 +161,14 @@ Replace:

Follow the [quickstart instructions](https://docs.pipecat.ai/getting-started/quickstart#step-2%3A-deploy-to-production) to deploy your bot to Pipecat Cloud.

### 2. Configure Production Environment

Update your production `.env` file with the Pipecat Cloud details:

```bash
# Set to production mode
ENV=production

# Keep your existing Exotel and AI service keys
```

### 3. Deploy the Server
### 2. Deploy the Server

The `server.py` handles outbound call initiation and should be deployed separately from your bot:

- **Bot**: Runs on Pipecat Cloud (handles the conversation)
- **Server**: Runs on your infrastructure (initiates calls, serves WebSocket connections)

When `ENV=production`, the server automatically routes WebSocket connections to your Pipecat Cloud bot.
- **Server**: Runs on your infrastructure (initiates Exotel calls)

### 4. Update Your Bot Number's App Bazaar Configuration
### 3. Update Your Bot Number's App Bazaar Configuration

Update your bot number's Voicebot Applet configuration for production:

Expand Down