Email deliveries and sender domains
Customizing the lead email a buyer receives, and sending it from your own domain instead of leadmove.io.
An email delivery method sends one email per lead. You control the recipient, the subject and the body; the address it comes from is set once for your whole account, with an optional override per buyer.
Edit the template on the delivery method's page, under Email template.
The template
- To — leave empty to use the buyer's own email address. Fill it in to send somewhere else (a shared inbox, a CRM drop address).
- Subject and Body — plain text with
{variable}placeholders. A new email method starts with a working subject and body already filled in, so you can send leads before touching anything.
Click any variable button to insert it: the fields declared in Expected fields, the fields of the pipelines wired to this buyer, and the system variables {lead_id}, {timestamp}, {source}, {campaign}, {buyer}, {quality_score}, {quality_grade}.
A variable with no value is removed from the sent email, and the line it leaves empty is cleaned up — so an optional field never produces a dangling Zip: line. The editor warns you about variables that match nothing at all (usually a typo, or a field missing from Expected fields).
Show Preview renders the email with sample data. Test email sends a real message — to the buyer's address if you set one, otherwise to your own.
Sender domains
Until you verify a domain, lead emails go out from leads@leadmove.io. Buyers see LeadMove, not you.
Add your own in Settings → Sender Domains (account owners). You add a domain, publish the DNS records it gives you (DKIM, SPF, MX), and it becomes usable once verified — pending or failed domains are visible but can't be selected. Set one as the default: every email delivery uses it unless overridden.
To use a different domain for one buyer, open the buyer's edit page and pick it under Sender Domain. Leave it on "Use organization default" for everyone else.
The number of sender domains you can hold depends on your plan — see Plans and quotas.
Why this matters
Buyers filter aggressively, and lead emails look exactly like the mail spam filters distrust: automated, repetitive, sent to an address that never replies. A verified domain you own gives those messages an authenticated sender, which is what inbox providers check first. It also means the buyer sees your brand in the From line, and can reply to an address you control.
Common questions
Do I need a sender domain to start?
No. Deliveries work from day one on leads@leadmove.io. Verify your own domain before you scale volume with a buyer who filters hard.
A buyer says my leads land in spam. Verify a sender domain and set it as default, then ask the buyer to allowlist that address. Sending from a domain you own is the part LeadMove can fix; the allowlist is the part they can.
Can I send HTML with images and buttons? No. The body is plain text with variables; line breaks are preserved. Keep it scannable — most buyers copy the values straight into their own system.
What happens if I delete a domain that a buyer uses?
That buyer falls back to the organization default, and to leads@leadmove.io if there isn't one. Deliveries never stop for a missing domain.
Webhook deliveries
Posting leads to a buyer's API — URL, headers, the standard payload, custom body templates with merge codes, and what a failure looks like.
Retries and deferrals
What happens between "routed" and "delivered" — automatic retries on failure, deliveries held outside a buyer's hours, and how to cancel one.