Next step · What to do next

Send confirmation emails (order, booking, sign-up)

What you may see

Customers should receive an email after they order or book

Why this step

A clear confirmation lowers worry and questions; it must be sent reliably, from your own domain, in the customer's language.

Before you start

Do you have a verified sending domain, and which email service will send?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Send confirmation emails (order, booking, sign-up)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
A clear confirmation lowers worry and questions; it must be sent reliably, from your own domain, in the customer's language.

DO THESE STEPS, IN THIS ORDER
1. List the events that need an email, and for each: who gets it, what it says, and which language (use the customer's choice).
2. Build the emails as simple, readable HTML with a plain text version, right-to-left for Arabic, with the order details, a clear next step, and a way to ask questions.
3. Send from the server after the action is saved, log each send with its result, retry on failure, and never block the order if email fails.
4. Use the site address setting for links (never localhost) and test in Gmail and another provider on a phone.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A test order produces one correctly formatted email in each language, with working links.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not include sensitive data like full card numbers or passwords.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

List the events that need an email, and for each: who gets it, what it says, and which language (use the customer's choice).
Build the emails as simple, readable HTML with a plain text version, right-to-left for Arabic, with the order details, a clear next step, and a way to ask questions.
Send from the server after the action is saved, log each send with its result, retry on failure, and never block the order if email fails.
Use the site address setting for links (never localhost) and test in Gmail and another provider on a phone.

Do not do this

Do not send the same email twice.
Do not include sensitive data like full card numbers or passwords.

Try another entry