Email Overview

​

What it does

Email sits alongside texting in the same account, on the same wallet, with the same organizations, permissions, and reporting. You get:

• Sending domains. Prove a domain you own by publishing DNS records, then send from it.
• Sender identities. A From address on a verified domain, carrying the physical mailing address and paid-for-by disclaimer that go in every footer.
• Lists. Uploaded, segmented, or synced from WinRed and Anedot, each with a recorded consent attestation. Optional paid validation cleans a list before you send to it.
• Suppressions. Opt-outs held at the organization, sender identity, or list level, honored automatically.
• Campaigns. Compose, test, schedule, send, and report, with warm-up limits and deliverability breakers applied for you.
• Templates, drafted for you if you want. A reusable design library, plus Draft with Lincoln: describe the email and the platform’s AI agent writes the design, $3.00 per draft, charged only when one comes back.
• Link tagging. Donation links to WinRed and Anedot are tagged with a refcode, source code, and UTM parameters, so the committee can attribute the gift in their own portal.

​

What it deliberately does not do

Knowing the boundaries up front saves a wasted afternoon:

• There is no inbox. We do not receive inbound email. Replies go to the reply_to address you configure, in whatever mailbox you already use. There is no inbound email webhook.
• There is no A/B testing. One campaign is one message to one audience.
• We never write your DNS. Every record is published by you, in your own zone. See Sending domains and DNS.
• There is no open-tracking webhook. Open rates appear in reports, but email.opened is not an event you can subscribe to: a tracking pixel is approximate and, at campaign volume, would be by far the noisiest event we could send.

​

How setup goes

Only the first step needs someone with DNS access; everything after it happens in the app. The one thing to plan ahead for is warm-up. A brand new domain starts at 500 messages a day and climbs from there, so a large send tied to a deadline means starting the domain well before the deadline, not the week of. See Campaigns and deliverability.

​

What it costs

Email sending is **$1.50 per 1,000 recipients** ($0.0015 each). Optional list validation is $0.02 per address**, charged only when you run it. A Lincoln email draft is **$3.00, charged only when a draft comes back ready. The optional dedicated sending add-on is $15.00 per month. Sending domains, sender identities, and hosted unsubscribe pages are free. Charges appear in your ledger under the Email family, alongside your texting usage on the same wallet, so there is one balance and one invoice rather than two. Lincoln drafts are billed under the AI family, since that is what they are. Sub-organization charges roll up to the parent. When a sub-organization sends, every organization above it in the hierarchy is charged at its own price, exactly as texting works today. A funded sub-organization is still blocked if an organization above it cannot cover its share, so fund the organization that actually ran short. See Billing. Test sends and seed addresses are real sends and are billed at the same per-recipient rate. They are excluded from campaign statistics and never fire webhooks, because they are our traffic rather than your audience’s.

​

Over the API

Everything above is available programmatically under /v1/email: domains, senders, lists, suppressions, campaigns, and templates. Five outbound webhook events cover the results: email.delivered, email.bounced, email.complained, email.unsubscribed, and email.clicked. Request and response shapes, authentication, and error codes are in the API reference. These help pages cover the product; the reference covers the contract.

​

Where to go next