Sending infrastructure
SendCopilot drafts replies to the email a local service business already receives — pricing questions, scheduling, “do you cover my street” — and sends them only after the business owner has read and approved that exact message. Nothing leaves on its own.
This domain carries client mail only. Every business sends
from its own authenticated subdomain — business.sendcopilot.com —
so one sender’s reputation is never pooled with another’s.
“Hi — do you service the east side of the valley, and what’s the call-out fee for a leaking water heater?”
Drafted reply
Hi Dana — yes, we cover the whole east valley, no travel surcharge.
Our call-out is $95, credited against the repair if you go ahead on the day. For a leaking water heater we’d usually want to see it same-week. Would Thursday morning suit?
Illustration only. Not a real customer, business, or message.
Mail goes to people who wrote to the business first. No campaigns, no lists, no cold outreach — ever.
SPF, DKIM and DMARC are published for each subdomain before it is allowed to send a single message.
Approval is a person reading one specific draft. There is no bulk approve, and no scheduled autopilot.
How mail leaves here
The order matters more than the technology. Everything upstream of step three is a suggestion; only step three creates mail.
At the address that business gave them. Nothing enters the system that a customer did not send to a business directly.
It sorts the message into a small fixed set of everyday categories and writes an answer from that business’s own published details — services, hours, service area, prices. Urgent and unclassifiable mail is never drafted; it goes straight to the owner untouched.
Send it, edit it first, or throw it away. A draft nobody approves is a draft that never becomes an email. This boundary is structural, not a setting — there is no configuration that turns it off.
Signed, and threaded to the original message, so the customer’s reply lands back in the inbox the business is already watching — not in a no-reply void.
Acceptable use
The second list is not a policy waiting to be enforced. Those things are outside what the software is built to do — there is no code path that performs them.
Sending practices
Written out because a sending domain should be legible to the mailbox providers, blocklist operators and email vendors who have to make a judgement about it.
In-Reply-To, References and Reply-To headers, so the conversation stays in one thread and the customer’s answer reaches a monitored inbox.If you received one
That means a local business you contacted uses SendCopilot to answer its email. The reply came from that business, not from us — a person there read it and approved it before it was sent.
Just reply as normal. Your answer goes straight back to the business’s own inbox. If you would rather they didn’t email you again, say so in that reply and it will be honoured. If the message looks like something a business would not send, tell us at abuse@sendcopilot.com — that is a real address, read by a person.
Contact
No autoresponders, no ticket wall. Abuse reports and postmaster enquiries are answered ahead of everything else.
Report abuse
abuse@sendcopilot.comUnwanted mail, a message that misrepresents a business, or anything that looks like a compromised sender. Include full headers if you have them.
Deliverability
postmaster@sendcopilot.comFor mailbox providers, blocklist operators and email vendors. Authentication questions, feedback loops, and anything about this domain’s sending.
General
support@sendcopilot.comEverything else, including businesses using the platform and anyone who wants to know what this domain is.