Skip to main content
An email address normally routes to an agent. Set its handler to demo and it does something else instead: mail containing a company website builds a demo AI voice agent for that company in your organization, and the requester — plus everyone CC’d — is emailed twice, once on receipt and once when the demo is live. No agent, no conversation, no reply drafting. A demo-builder address is a build request inbox.

​
How it flows

1

Create the address

Create an email address as usual, with handler set to demo. Any agent you pass alongside it is ignored — a demo address has no agent to pin.
2

Someone emails it a company URL

The subject line is the documented way to ask (Demo https://acme.com), but the body is checked too. Bare domains work — acme.com is normalized to https://acme.com.
3

They get an acknowledgment

Sent as a threaded reply the moment the request is accepted, with everyone from the original thread CC’d.
4

They get the demo

When the build finishes, a second reply lands in the same thread with the company name, the demo link, and a phone number if you enabled one.

​
Configuration

Demo options live in handler_config on the address:

​
What is and isn’t answered

A demo address applies the same guards as an agent address:
  • Auto-generated mail — anything carrying List-Id, List-Unsubscribe, or X-Auto-Response-Suppress — never builds anything.
  • Another platform agent as the sender is ignored, so two Anyreach addresses can’t build demos at each other.
  • Opted-out senders are skipped. STOP / START still manage the org-wide unsubscribe ledger; they never trigger a build.
  • No company URL gets a short “how to request a demo” reply instead of a build. Addresses in signatures don’t count as the company — a message whose only domain is jo@gmail.com is treated as having no URL.
The auto-generated guard only stops well-behaved senders. If another automated mailer can end up on the same thread — a second demo bot, a helpdesk autoresponder — add it to ignore_senders. A bot that doesn’t stamp Auto-Submitted will otherwise read the company URL out of the acknowledgment email, build its own demo, and reply, which this address would then build from again. The loop is unbounded and each cycle costs a full demo build.

​
Duplicate protection

Each request is keyed on the provider’s message id, which is unique. A redelivered webhook loses that key and is acked without starting a second build, so the same email can never produce two demos.

​
Tracking requests

Every request is recorded with its requester, CC list, company URL, status, and resulting demo link. Read them from GET /core/demo-email-requests (scopes email_addresses:read or email_addresses:manage), or in the dashboard under Email → Demo Requests. A request is only finished once the requester has actually been told the outcome. If email delivery fails, it is retried with backoff rather than abandoned — and a failed delivery is never reported to the requester as a failed build.