Integration

Send from your own mailboxes, without handing over your inbox

E-mail steps go out from the mailboxes your team already uses, so the conversation and the sender reputation stay yours. Demander asks only for permission to send. Replies reach it through a reply subdomain you point at Demander, and each human answer lands back in the sender’s mailbox, threaded under the original.

Reviewed 2 October 2026

Fig. 01 Gmail, Microsoft 365 and SMTP mailboxes and the reply subdomain start as separate boxes, then pull into one loop, and their sends and replies flow into one record in the middle.

Three ways to connect a mailbox

MailboxHow it connectsWhat Demander can do
Gmail and Google WorkspaceSign in with Google; the grant is gmail.send plus your addressSend as you, with each message in your Sent folder. There is no read scope, so no access to your inbox.
Microsoft 365 and OutlookSign in with Microsoft; the grant is Mail.Send plus offline accessSend as you, saved to Sent Items. There is no Mail.Read. Tenants that block user consent need an admin to approve Demander once.
Any other provider (SMTP)Host, port, user and password, stored encryptedSend through your own server. Demander checks that the host is public and pins the connection to the address it checked.

Each mailbox is its own connection. Plans include 3 mailboxes on Starter, 15 on Growth and 50 on Scale; see pricing.

How replies come back: the reply subdomain

  1. One DNS record per sending domain

    You add an MX record for a reply host such as reply.yourdomain.com that points to Demander’s inbound mail. Demander checks the record daily and can send a round-trip test message to prove the route.

  2. Signed reply addresses

    Every message carries a Reply-To address on that host, signed for that one message, and a one-click unsubscribe address. Guessed or forged addresses are ignored, and threading headers still match replies that arrive another way.

  3. Replies handled there

    Demander classifies the reply, stops the sequence, records unsubscribes and creates the sales task. Out-of-office and other automatic replies are recorded and never stop a sequence.

  4. Forwarded to the sender

    Human replies are forwarded to the sending mailbox, threaded under the original, with Reply-To set to the prospect, so the conversation carries on in your normal inbox.

  5. Without a reply host

    In live mode first messages still go out, while follow-up steps from that mailbox wait. Demander retries every 12 hours and alerts you once a day per mailbox.

Warm-up, limits and health

  1. 01

    Warm-up

    A new mailbox starts at 5 messages a day and ramps to its daily limit over about 21 days. The default limit is 30 a day, and you set your own per mailbox.

  2. 02

    Send windows

    Messages go out between 08:00 and 17:00 on weekdays in the recipient’s time zone, paced through the window.

  3. 03

    Health

    A bounce rate above 3 percent or a complaint rate above 0.3 percent pauses the mailbox; warnings start at 2 percent and 0.1 percent. A mailbox in poor health sends less, and below a health score of 0.5 it sends nothing.

  4. 04

    Domain checks

    Demander checks SPF (with nested includes), DKIM and DMARC on each sending domain against the Gmail, Yahoo and Outlook.com bulk-sender rules, and shows what to fix.

What every message carries

A footer with your sender identity and postal address, and an RFC 8058 one-click unsubscribe (https in live mode). Links to your own domain carry campaign-level UTM parameters for the sequence and step. There is no open-tracking pixel, and nothing in a link identifies the recipient.

Before every send Demander checks the recipient’s country against cold e-mail law: consent where it is required (Germany, Austria, Czechia and Poland, and consumers everywhere), legitimate interest with an opt-out where that is allowed. See cold e-mail rules by country and e-mail outreach.

Provider approvals and limits

  1. 01

    Google

    gmail.send is a sensitive scope, so Demander’s OAuth app goes through Google’s verification for it. It needs no CASA security assessment, which applies only to the restricted read scopes Demander does not request.

  2. 02

    Microsoft

    Demander’s app registration is multitenant. Many organisations allow user consent only for verified publishers or selected permissions; otherwise an administrator grants consent once for the tenant.

  3. 03

    Provider sending limits

    Google Workspace allows 2,000 messages a day per user and Exchange Online 10,000 recipients a day per mailbox at 30 messages a minute. A default onmicrosoft.com domain is capped at 100 external recipients a day, so send from your own domain.

Questions people ask

Will the messages show in my Sent folder?

Yes for Gmail and Microsoft 365, which send through your own account. With SMTP it depends on your mail server.

What if we cannot add an MX record?

First messages still send in live mode. Follow-up steps wait until a reply host is active, because without one Demander cannot tell who has replied and would risk following up on a reply.

Can we send outreach from a separate domain?

Yes. Each mailbox belongs to a sending domain, and each sending domain gets its own DNS checks and its own reply host. Keep a clear sender identity on whichever domain you use.

Does Demander track opens?

No. There is no open pixel, and Apple Mail Privacy Protection makes opens meaningless anyway. Demander counts clicks to your own domain and replies.

See the plan for your own product

Enter the website. In about a minute you get the profile, two personas, the messaging, the funnel and three creatives. Keep the rest by signing up.

Free, no card. Demander reads the public pages, then shows your personas, messages, funnel and first creatives. Sign up to keep the full plan.