Sending protections and verification

Every pplCRM newsletter leaves through a shared sending infrastructure, so one bad sender can hurt everyone’s deliverability. These protections keep spammers out — and for a legitimate organization they cost a few minutes, once.

Before your first send

1. 1Verify your sending domainUnder Workspace → Domains, add the domain you send from. You’ll get a checklist of 4 required DNS records to add at your domain provider (GoDaddy, Namecheap, Cloudflare, and similar); use the copy buttons so nothing gets mistyped, then select Check DNS records. Changes usually appear within minutes but can take up to 48 hours. A fifth record, DMARC, is recommended but optional; it never blocks verification. Once verified, set a default From address on that domain under Workspace → Communications. Mail authenticated with your own domain lands in inboxes; unauthenticated mail lands in spam.
2. 2Verify a mobile number (Free plan)Under Workspace → Communications → Sending phone verification, enter a mobile number and confirm the 6-digit SMS code. One number per workspace, one time.

The Free-plan warm-up

For the first 7 days, a Free workspace can send up to 100 newsletter emails per day. If a send is larger than the day’s remaining allowance, you’ll be told before anything goes out — narrow the audience or wait a day. After the first week the normal plan limits apply.

Automatic pauses

• If a send’s hard-bounce rate passes 5%, sending is paused automatically — a bounce rate that high almost always means the list contains addresses that never opted in. Even a send already in progress stops.
• If a send’s spam-complaint rate passes 1%, the account is suspended pending a human review.

Plan-gated features

Some features are enforced by plan: forms, donations, automations, lists and volunteer management (teams and events) need Grassroots or higher; canvassing, deliveries and companion volunteer access need Movement. See your options under Workspace → Billing.