Warpflow
Signals

Connect email

Connect your Google Workspace or Microsoft 365 email so inbound emails flow into the Signals pipeline alongside SMS and voice.

What email integration gives you

Once connected, email becomes a full channel in your Signals pipeline:

  • Inbound emails are processed through classification, scoring, and routing, just like SMS and voice
  • Outbound email: reply to customers directly from the Work Queue with threading, aliases, and rich text
  • Thread tracking: email conversations are grouped into threads and displayed alongside SMS and voice in the conversation timeline
  • Alias discovery: Signals auto-discovers email aliases on your domain from inbound traffic

Prerequisites

  • A Signals account on any plan
  • A Google Workspace or Microsoft 365 email account
  • Email is not available for HIPAA-enabled tenants (the email integration does not include a BAA)

Step 1: Navigate to email settings

Go to Voice & Channels → Email in the sidebar.

Email settings, before connection

Step 2: Connect your email account

  1. Click Connect Email Account
  2. Choose Google Workspace or Microsoft 365
  3. Complete the OAuth authorization flow (you'll be redirected to Google or Microsoft to grant access)
  4. Your credentials are handled securely by the email provider, not stored by Warpflow

Email settings, connected

Step 3: Verify the connection

Once connected, inbound emails begin flowing into the pipeline automatically. You'll see:

  • A connected status badge on the Email settings page
  • New emails appearing in the Work Queue conversation thread
  • Email messages interleaved with SMS and voice in the Conversations timeline

Sending email

When replying to a customer via email from the Work Queue:

  1. Click Reply on an email message in the conversation thread
  2. Choose your from address if you have multiple aliases
  3. Compose your reply using the rich text editor
  4. Click Send

Email compose with alias selector

Replies are threaded: the customer sees your response as a continuation of the original email thread, not a new message.

Email draft approval

When AI routing generates an email reply, it goes through the same approval gate as SMS drafts:

  • If auto-send is on and confidence meets the threshold, the email sends automatically
  • If held for review, the draft appears in the Work Queue with the email subject, from-alias, and thread context
  • Agents can approve, edit, or dismiss the draft before it sends

Alias discovery

Signals automatically discovers email aliases from inbound traffic. As emails arrive addressed to different aliases on your domain, those aliases become available as "from" addresses when composing replies. No manual configuration needed.

Email in the conversation timeline

Email threads appear as cards in the conversation timeline alongside SMS messages and call records. Each email shows the subject line, sender, and a content preview.

Email thread in conversation view

Bulk sync (optional)

After connecting, Signals processes new inbound emails in real-time. If you want to import historical emails, contact your account admin (bulk sync is available but optional).

Limitations

  • HIPAA tenants: Email integration is not available. The email provider does not include a Business Associate Agreement (BAA). HIPAA tenants will see a restriction banner on the Email settings page.
  • One email account per tenant. Connect your primary business email. If you need multiple mailboxes, contact support.

Tips

  • Connect email early. The sooner you connect, the sooner email flows through your routing rules and AI classification.
  • Use aliases strategically. If your business uses info@, support@, and sales@, all three become available for outbound replies after discovery.
  • Check the conversation timeline. Email, SMS, and voice are all visible in one place, giving you the complete history of every customer interaction.

On this page

We use cookies to understand how you use our site and improve your experience. Privacy Policy