AI Outreach Email Workflow
Prepare and review relevant partnership emails one at a time, test delivery, and keep accurate reply and opt-out records.
Use AI to draft a short partnership email after you establish that the contact is eligible and the offer is relevant. Keep a preview before sending, send the first test to yourself, and track replies, bounces, and opt-outs so the next action comes from the record.
Scott’s Cohort 1 workshop shows four individually drafted messages for a sample list. The demo stops before delivery. It lets you inspect the proposed messages and the checks without contacting the people represented in the sample. Open the outreach demo
What belongs in the contact record?
Keep the source, contact status, reason for reaching out, and whether the address is on a suppression list. A publicly listed business address is a source to document. Whether you can contact it depends on the context, applicable requirements, and your sending provider’s rules. A record with no clear source or eligibility belongs in review.
For US commercial email, start with the FTC’s guidance on sender information, accurate subject lines, opt-out handling, and mailing address requirements. Check the rules for your recipients before a campaign. FTC CAN-SPAM compliance guide
How do you draft an email someone can answer?
- Give the assistant a specific business reason to contact that person, plus one verified observation about their work.
- Ask for a short note that connects that observation to a real offer.
- Read the draft and verify the observation. Remove generic praise, unsupported details, and any claim about a relationship that does not exist.
- End with a request that takes one answer, such as whether the recipient wants a short brief or sample information.
If three drafts differ only in their names, the assistant needs better inputs. A good test is to read the middle paragraph without the name and see whether the specific reason for contacting that person remains clear.
How do you test the sending workflow?
Use a domain you control and follow the sending provider’s documented verification. Prepare a dry run that saves the message previews and suppression decisions. Then send an approved test message to an address you control and confirm the sender, reply address, links, and opt-out behavior. Keep the first contact batch small enough to review by hand. Resend domain verification documentation
What should you record after delivery?
| Signal | Useful next action |
|---|---|
| Reply | Respond to the actual question and update the contact record |
| Hard bounce | Suppress the address and check the source record |
| Opt-out | Apply suppression across future sends |
| Delivered | Confirm the receiving system accepted the message |
| Open or click | Treat it as a supporting signal, since clients and security tools can affect the measurement |
A review report should make clear who replied, who needs a response, and who should receive no further messages. Keep the sample contacts and message approval separate from the real send queue. SCT Camp Cohort 2