# Email Integration
Let users interact with your AI chatbot via email for support tickets, inquiries, and automated responses.
---
Deploy your Chipp AI as an email responder. Users can email questions and receive AI-powered responses automatically. Perfect for support tickets, sales inquiries, and customer service.
> **Note:** Email integration requires a **Studio plan** or higher. It's self-serve: just open **Launch → Share → Deploy → Email** inside your app to configure it. No approval step is needed.
## How Email Integration Works
| Feature | Description |
|---------|-------------|
| **Inbound emails** | Users email your AI, get automated responses |
| **Conversation threading** | Multi-turn conversations via email replies |
| **Whitelist protection** | Control who can email your AI |
| **Custom domains** | Use your own email domain (optional) |
## Quick Start (Shared Infrastructure)
The fastest way to get started is using Chipp's shared email infrastructure. No Postmark account needed!
**1.**
Open Email Configuration
Go to your app and open **Launch → Share** in the navigation. Select the **Deploy** tab and click the **Email** card.
**2.**
Review Your Email Address
With **Use Shared Infrastructure** on (the default), Chipp pre-fills an address on the shared domain based on your app's name. It will look like:
```
yourappname@agents.chipp.ai
```
The **Inbound Email Address** (where users send emails) and **From Email Address** (where responses come from) both start with this value. You can edit either one.
**3.**
Set Display Name
Enter a **From Name** - this is what recipients see in their email client (e.g., "Sales Assistant" or "Support Bot").
**4.**
Save and Continue
Optionally turn on **Enable Sender Whitelist** (under Security), then click **Save & Continue**. Your email deployment is now active.
**5.**
Configure Whitelist
The next step lets you manage allowed senders. When the whitelist is enabled, your AI only responds to listed addresses, so add at least one address before testing. Click **Finish Setup** when you are done.
## Email Whitelist
The whitelist controls who can email your AI.
### Adding Emails to Whitelist
1. In the email configuration dialog, click **Manage Whitelist**
2. Enter one email address (for example `john@example.com`)
3. Click **Add**, and repeat for each address
To allow everyone from a domain, set an **Allowed Domain** in **Launch → Access** (for example `company.com`). Senders from that domain pass the email whitelist too.
### Disabling Whitelist
> **Warning:** Disabling whitelist protection means anyone can email your AI. This may result in increased AI usage costs and potential spam.
To disable whitelist protection:
1. In the email configuration dialog, click **Manage Whitelist**
2. Toggle off **Enable Whitelist**
Only disable this if you have other protection measures in place.
## Custom Domain (Advanced)
Want to use your own email domain like `support@yourbrand.com`? You'll need a Postmark account.
**1.**
Create Postmark Account
Sign up at [postmarkapp.com](https://postmarkapp.com) and create a server for your email integration.
**2.**
Verify Your Domain
In Postmark:
1. Go to **Sender Signatures** > **Domains**
2. Add your domain and verify DNS records
**3.**
Configure MX Records
Set up MX records for your inbound email subdomain to point to:
```
inbound.postmarkapp.com
```
**4.**
Get Your API Token
In Postmark, go to your server > **API Tokens** and copy your Server API Token.
**5.**
Configure in Chipp
In the email configuration dialog:
1. Turn off **Use Shared Infrastructure**
2. Change the email addresses to use your custom domain
3. Enter your **Postmark Server API Token**
4. Click **Save & Continue**
**6.**
Set Up Webhook
After saving, the dialog shows the **Configure Postmark Webhook** step with a **Webhook URL** and a **Webhook Token**. Configure it in Postmark:
1. Go to your Postmark server > **Settings**
2. Under Inbound, paste the webhook URL from Chipp with `?token=YOUR_TOKEN` added
3. Save and test with a sample email
## Email Behavior
### Response Format
Your AI responds to emails maintaining conversation context:
- **Subject line**: Preserved for threading
- **Reply format**: Clean text response
- **Threading**: Email clients group conversations automatically
### Conversation Memory
Each email thread maintains context:
- Previous messages are included in AI context
- Users can have ongoing conversations
- Context resets after extended inactivity
## Use Cases
### Customer Support
Handle support tickets automatically:
```
System prompt addition:
You are a support agent for [Company]. When users email:
1. Acknowledge their issue
2. Provide helpful solutions
3. Escalate complex issues to human support
4. Include ticket reference numbers
```
### Sales Inquiries
Qualify leads via email:
```
System prompt addition:
You are a sales assistant. When prospects email:
1. Answer product questions
2. Gather their requirements
3. Offer to schedule a demo
4. Collect contact information for follow-up
```
### Information Requests
Provide automated information:
```
System prompt addition:
You are an information assistant. Respond to emails with:
1. Accurate information from your knowledge base
2. Links to relevant resources
3. Suggestions for related topics
```
## Monitoring Email Conversations
View email conversations in your Chipp dashboard:
1. Go to **Insights → Conversations** in your app
2. Use the source filter to select **Email**
3. View full email threads and AI responses
## Best Practices
### Clear Auto-Replies
Set expectations in responses:
```
System prompt addition:
Start each response with a brief acknowledgment like
"Thanks for reaching out!" and end with "Reply to this
email to continue our conversation."
```
### Set Boundaries
Prevent misuse:
```
System prompt addition:
If asked to perform actions outside your scope (like
making purchases or accessing external systems), politely
explain your capabilities and suggest alternatives.
```
### Professional Tone
Maintain email etiquette:
```
System prompt addition:
Respond professionally with proper email formatting.
Use appropriate greetings and sign-offs. Keep responses
concise but complete.
```
## Troubleshooting
### Emails Not Being Received
1. **Check whitelist**: Ensure sender is on the whitelist (if enabled)
2. **Verify deployment is active**: Toggle must be on
3. **Check spam folder**: AI responses may be filtered by recipient
4. **For custom domains**: Verify Postmark webhook is configured
### AI Not Responding to Whitelisted Users
1. Verify the email address is exactly as whitelisted
2. Check for typos in the whitelist entry
3. Domain-wide access comes from **Launch → Access → Allowed Domain** (e.g., `company.com`), not from the whitelist
### Slow Response Times
1. Check your AI model - faster models respond quicker
2. Reduce system prompt complexity
3. Complex custom actions may add latency
### Threading Issues
1. Keep subject lines consistent - don't change mid-conversation
2. Use reply, not new email, to continue conversations
3. Some email clients may break threading
### Custom Domain Not Working
1. **Verify DNS**: Domain must be verified in Postmark with correct DNS records
2. **Check MX records**: Must point to `inbound.postmarkapp.com`
3. **Test webhook**: URL must be accessible and correctly configured
4. **Check API token**: Ensure token has correct permissions
### Does renaming my app or changing its URL affect email?
No. Your email inbound address is stored independently of your app's name or URL slug. Renaming the app, changing the vanity URL (e.g. `your-app.on.chipp.ai`), or connecting a custom domain has no effect on email routing: inbound messages sent to your configured address will continue to reach the app.
If you want to change the **email address itself** (e.g. pick a different local part on the shared `agents.chipp.ai` domain), open **Launch → Share → Deploy → Email** and update the Inbound Email Address field. The old address stops receiving messages once you save.
## Using with MCP
You can manage email deployments programmatically using the Chipp MCP Server.
### Available Tools
| Tool | Description |
|------|-------------|
| `get_email_deployment` | Get email channel configuration |
| `update_email_deployment` | Update email settings (from name, etc.) |
### Example Prompts
```
"Show me the email configuration for my support bot"
"Update the from name to 'Customer Support'"
"Is email enabled for my app?"
```
### Workflow: Email Configuration
```
You: Show me the email setup for my support bot
AI: [Calls get_email_deployment]
Email Deployment for Support Bot:
- Status: Enabled
- Email Address: support-123@agents.chipp.ai
- From Name: "Support Team"
- Whitelist: Enabled (12 addresses)
- Last email received: 3 hours ago
You: Change the from name to "Acme Support"
AI: [Calls update_email_deployment]
Updated from name to "Acme Support". New emails will use
this display name.
```
> **Note:** MCP server access requires a Studio plan or higher. See the [MCP Setup Guide](/docs/guides/mcp/setup) to get started.