Email Integration

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.

💡

Email integration is currently in beta. To enable this feature for your account, contact support@chipp.ai and request access.

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!

Open Email Configuration

Go to your app and click Share in the navigation. Select the Deploy tab and find the Deploy to Email card. Click Add Deployment.

Review Your Email Address

Chipp automatically generates an email address for your app using the shared domain. It will look like:

yourappname-123@mail.chipp.ai

This is both your inbound address (where users send emails) and from address (where responses come from).

Set Display Name

Enter a From Display Name - this is what recipients see in their email client (e.g., "Sales Assistant" or "Support Bot").

Enable the Deployment

Toggle on Enable Email Deployment at the top of the dialog.

Configure Whitelist

By default, whitelist protection is enabled. You must add at least one email address to the whitelist before your AI will respond to anyone.

Click Manage Whitelist to add allowed email addresses.

Save Configuration

Click Save Configuration to activate your email deployment.

Email Whitelist

The whitelist controls who can email your AI.

Adding Emails to Whitelist

In the email configuration dialog, click Manage Whitelist
Enter email addresses (one per line or comma-separated)
Click Add to Whitelist

You can whitelist:

Individual emails: john@example.com
Domain patterns: @company.com (allows anyone from that domain)

Disabling Whitelist

⚠️

Disabling whitelist protection means anyone can email your AI. This may result in increased AI usage costs and potential spam.

To disable whitelist protection:

Go to the Whitelist tab
Toggle off Email Whitelist Protection

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.

Create Postmark Account

Verify Your Domain

In Postmark:

Go to Sender Signatures > Domains
Add your domain and verify DNS records

Configure MX Records

Set up MX records for your inbound email subdomain to point to:

inbound.postmarkapp.com

Get Your API Token

In Postmark, go to your server > API Tokens and copy your Server API Token.

Configure in Chipp

In the email configuration dialog:

Change the email addresses to use your custom domain
Enter your Postmark Server API Token
Save the configuration

Set Up Webhook

After saving, go to the Webhook tab in the dialog. Copy the webhook URL and configure it in Postmark:

Go to your Postmark server > Message Streams > Inbound
In Settings, paste the webhook URL from Chipp
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:

Go to Chats in your app
Use the Source filter to select Email
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

Check whitelist: Ensure sender is on the whitelist (if enabled)
Verify deployment is active: Toggle must be on
Check spam folder: AI responses may be filtered by recipient
For custom domains: Verify Postmark webhook is configured

AI Not Responding to Whitelisted Users

Verify the email address is exactly as whitelisted
Check for typos in the whitelist entry
Domain patterns must start with @ (e.g., @company.com)

Slow Response Times

Check your AI model - faster models respond quicker
Reduce system prompt complexity
Complex custom actions may add latency

Threading Issues

Keep subject lines consistent - don't change mid-conversation
Use reply, not new email, to continue conversations
Some email clients may break threading

Custom Domain Not Working

Verify DNS: Domain must be verified in Postmark with correct DNS records
Check MX records: Must point to inbound.postmarkapp.com
Test webhook: URL must be accessible and correctly configured
Check API token: Ensure token has correct permissions