Who can be e-mailed, by country
The legal matrix is part of the code and runs for each recipient, at enrolment and again at send.
| Rule | Countries | What Demander does |
|---|---|---|
| Consent required, B2B included | Czechia, Poland, Germany, Austria, Switzerland, Belgium, Spain, Italy, Portugal, Denmark, Norway, Hungary, Romania, Canada, Australia | Sends only with recorded e-mail consent, or to existing customers where the country allows a soft opt-in. Everyone else is reached through ads, content and tasks for your team. |
| Opt-out allowed for business contacts | Slovakia, France, Netherlands, Ireland, Sweden, Finland, United Kingdom, United States, India | Sends to business addresses under legitimate interest once the workspace has a completed legitimate interest assessment and a privacy notice linked from the first message. |
| Any other country | Not in the matrix, or unknown | Treated as consent required. |
Free-mail addresses count as private persons and need consent inside the GDPR area. The matrix is a conservative reading of each country’s law and is not legal advice: the workspace owner confirms it. The detail is in cold e-mail rules by country.
Sending from your own mailboxes
-
01
Gmail, Microsoft 365 or SMTP
Google connects with send-only access, Microsoft 365 through Graph, and any other provider over SMTP. Demander never reads the mailbox. Messages appear in your Sent folder and recipients reply to your address. See mailboxes.
-
02
Domain checks
SPF, DKIM and DMARC on each sending domain are checked against the bulk-sender requirements of Gmail, Yahoo and Outlook.com.
-
03
Warm-up
A new mailbox starts at 5 messages a day and ramps to its daily limit over about 21 days.
-
04
Circuit breakers
A bounce rate above 3 percent or a complaint rate above 0.3 percent pauses the mailbox. Warnings start at 2 and 0.1 percent.
-
05
Identity in every message
Sender name, company and postal address in the footer (English, Czech or German), one-click unsubscribe to RFC 8058, and for prospected contacts the source of their data.
How a sequence runs
-
Enrol
Enrolling contacts is a proposed action. It waits for your approval by default and can run on its own only from autonomy level 4. The country check runs first.
-
Pace
Every 15 minutes due messages are spread across your mailboxes, 2 to 7 minutes apart per mailbox, on weekdays between 08:00 and 17:00 in the recipient’s time zone (from their country, else your workspace’s). Messages that miss the window wait for the next one.
-
Cap
Each mailbox stays under its warm-up limit, scaled down when its health drops. The workspace has a daily cap across all mailboxes, 200 by default.
-
Check again at send
Country rules and suppression are checked again. A step whose copy still reads as machine-written is held, with one review task per step, and resumes when you fix the e-mail.
-
Stop on a reply
Any reply from a person stops the sequence for that contact. Steps can be e-mails, waits, tasks for your team, or LinkedIn and X messages that a person sends.
Replies, opt-outs and the reply subdomain
Each sending domain gets a reply host, such as reply.yourdomain.com, with one MX record pointing to Demander. Every message’s Reply-To is a signed address on that host, tied to the one message it answers, so guessed or forged addresses are ignored. Replies reach Demander there, without any access to your inbox.
Replies are classified: positive, meeting request, referral, question, not now, not interested, unsubscribe, out of office or bounce. A reply from a person is forwarded to the sending mailbox, threaded under your original. Positive replies, meeting requests, referrals and questions become a follow-up task for sales, due within four hours. Unsubscribes and hard bounces suppress the address at once, and when someone else answers with “please remove us”, their address too. Automatic replies are recorded but never stop a sequence.
In live mode, follow-up steps wait until the mailbox’s reply host is active. First messages still go out.
Assisted first touches on LinkedIn, X and Reddit
LinkedIn and Reddit have no public API for one-to-one messages and both ban automating them, and X allows messages only after the person writes first. So Demander prepares these first messages and a person sends each one.
-
Review in bulk
Drafts arrive as cards. With review first, on by default, you edit them and approve or skip them in bulk. A draft that still reads as machine-written cannot be approved.
-
Caps per sender
Approved cards get a send time within each sender’s caps: LinkedIn 20 a day and 80 a week, X 20 a day, Reddit 5 a day.
-
One batch a day
By default each working day’s cards fall due together at one time (09:30 unless you change it), so the day’s messages go out in one sitting. Drip spreads them through working hours instead.
-
A send session
The web app walks through the due cards. Enter copies the text and opens the conversation (pre-filled on X), you press Send on the platform, and Enter marks it sent. A reminder e-mail tells you when messages fall due.
Questions people ask
Can I e-mail prospects in Germany or Czechia?
Only contacts who gave e-mail consent, or existing customers where the soft opt-in applies. Both countries require prior consent for marketing e-mail to businesses. Those accounts are reached through ads, content and tasks for your team.
Does Demander need access to my inbox?
It needs send access only. Google connects with the send-only scope, and replies come back through the reply subdomain’s MX record, so nothing in your mailbox is read.
How many mailboxes can I connect?
Starter connects 3, Growth 15 and Scale 50. Sandbox mailboxes never count. See pricing.
Will Demander send LinkedIn messages for me?
A person sends every LinkedIn, X and Reddit first message. Demander drafts them, paces them under the caps and lines them up in a send session that takes a few keystrokes per message.