As of 13 August 2026, AI can only partly set up an email automation for your small business.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open your email platform or CRM and record its name, the sender address, the available contact fields and the event that should start the automation.
   2. Gather the approved email list or audience definition, the exclusion and suppression lists, the consent information you hold, the offer, the current price list and the links you are allowed to use.
   3. Paste those details into the prompt, then ask the chatbot to produce the workflow, email copy, field map and platform-specific setup steps without activating or sending anything.
   4. Open the automation builder in your platform and create the trigger, entry conditions, exclusions, delays, branches and exit conditions from the drafted workflow.
   5. Paste the drafted emails into the message editor and compare every factual claim, price, link, sender detail and call to action against your current business materials before saving.
   6. Use test contacts to exercise each branch, including an excluded contact, an unsubscribed contact, a missing name and a failed link, then check the rendered emails on desktop and mobile.
   7. Ask a colleague to approve the audience, copy, consent handling and stop conditions, then activate the automation only after removing test contacts and confirming reply handling.

   Prompt

   Design an email automation for my small business and give me an implementation-ready setup plan.
   
   Business: [what the business sells and who it serves]
   Email platform or CRM: [platform name]
   Automation goal: [for example, welcome new subscribers, recover abandoned enquiries, or follow up after purchase]
   Trigger: [the event that starts the automation]
   Audience: [who may enter]
   Exclusions: [who must not enter]
   Number of emails: [number]
   Timing constraints: [when messages may be sent]
   Offer or call to action: [details]
   Brand voice: [plain description]
   Approved facts and links: [paste only verified information]
   Available fields: [for example, first name, product, enquiry date]
   Consent and unsubscribe rules already configured: [describe them]
   
   Produce:
   1. A plain-English workflow showing the trigger, entry conditions, exclusions, delays, branches, exit conditions and suppression rules.
   2. The full email copy for every message, with a subject line, preview text, body, call to action and a clear unsubscribe instruction where appropriate.
   3. A field-mapping table showing exactly which customer data each message uses.
   4. Platform-specific setup steps for [platform name]. If you do not know a platform feature, say so instead of inventing it.
   5. A test plan covering a new subscriber, an excluded contact, an unsubscribed contact, a missing name, a failed link and each branch.
   6. A launch checklist covering permissions, consent records, suppression lists, links, sender details, reply handling and approval.
   
   Use only the approved facts and links. Invent no customer details, claims, results, prices or legal conclusions. Do not activate the automation, import contacts or send anything. Mark every item I must confirm before launch.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.