# How to Send Automatic Registration Confirmations and Receipts

> Which emails Laces sends after registration, what each contains, who receives it, and what really happens when an address is mistyped or an email bounces.

Source: https://laces.run/blog/how-to-send-automatic-registration-confirmations-and-receipts (HTML version of this page)

To send registration confirmations and receipts automatically, use a system where confirming the payment and sending the email are one step, tied to one record. On Laces, there's nothing to set up: each confirmed registration triggers a ticket and receipt by email. The harder question is what happens when that email never arrives, so this guide covers that too.

[Create your event](https://laces.run/app): Each confirmed registration gets a ticket and a receipt by email, with nothing for you to send.

## Why not just use a form and a mail merge?

You can. A form, a mobile money number and a mail merge can send everyone a message. The trouble is the step between them, because somebody has to look at a payment, match it to a name and press send. Once you do that by hand:

- A "confirmed" email can go to someone whose payment didn't land.
- A real payment can sit unconfirmed until someone finds it.
- Your receipt numbers and your actual money can drift apart.

Whatever tool you use, the rule is the same: send the confirmation from the payment result, not from a person's reading of a screenshot.

## What Laces sends, and when

| Email | Goes to | Sent when | What's in it |
| --- | --- | --- | --- |
| **"You're in"** confirmation | The buyer | The registration is confirmed | Order code, ticket QR, PDF receipt, what was paid, calendar buttons, your contact details |
| **"You're registered"** | Another attendee, if the buyer gave that person's email | With the confirmation above | Their own ticket details, QR note, when and where. No prices |
| **Organizer's copy** | Your owner, plus admins, event managers and finance members | The registration is confirmed | Who registered, how to reach them, what they paid |
| **Payment didn't go through** | The buyer | A payment attempt fails | What happened, and how to continue that same order |
| **Your spot is still waiting** | The buyer | You tap Nudge on an unfinished order | A friendly way back to that order. One per order |
| **Event reminder** | Paid participants and your team | Two days before the event | Event name, date and place |

For an order of more than one ticket, the buyer's email carries a combined PDF, and usually one PDF for each ticket, so one can be forwarded on its own. Very large orders get the combined PDF only.

These are sent as email only. **Laces doesn't send tickets by SMS or WhatsApp.** You also can't edit the wording of these emails. They use your event's details and colours, so what you put on the event page matters. If people need to know about parking or what to bring, put that in the event description, then repeat it yourself nearer the day.

## What makes a good receipt

Even if you use another system, check that a receipt has these:

- The event name, date and place
- The buyer's name and an order reference
- What was bought, ticket by ticket
- The amount, the currency and any service fee as its own line
- Who to contact with a question

The Laces PDF and printable page carry these, and a person's receipt also opens at `/o/` with their order code. Participants pay the service fee at checkout, and it's shown before they pay. To see it for your country, check the pricing page for [Uganda](https://laces.run/pricing/ug), [Kenya](https://laces.run/pricing/ke), [Ghana](https://laces.run/pricing/gh), [Rwanda](https://laces.run/pricing/rw) or [Zambia](https://laces.run/pricing/zm).

If your organization needs its own tax invoices, ask your accountant. Laces' receipts are a record of the order, and we don't promise they meet a specific tax rule in your country.

## Emails come from Laces, so tell people to expect them

The emails are sent on your behalf from a Laces no-reply address. They name you as the organizer and carry your contact details, so questions about your event should come to you, not to Laces.

So put a real contact on your organization profile, and make sure someone checks it.

Also tell people, in your poster and your messages, that their ticket comes by email from Laces, and to check spam and promotions. A short line prevents a surprising number of "where's my ticket?" messages. Keep a reply ready. Our [participant guide to registering](https://laces.run/blog/how-to-register-on-laces) is a useful page to send them.

## What really happens when an email fails

This is where people assume more than is true. A failed email doesn't affect the ticket. The registration is valid, it's on your list, and it can be scanned or found at the gate. Only the message failed. There are three different failures.

**The send itself failed.** The email service refused the message or returned an error. Laces records it and retries automatically, unless the failure is one that retrying can't fix. Your copy of the order also changes: the subject starts "Entry not delivered", and the body tells you to check the address for a typo and pass on the order code. In this case, you are the backup.

**The email was accepted, then bounced.** This one catches people out. The address looks fine, the service accepts it, then the receiving server refuses it. At that point you've already had a normal copy, so **Laces doesn't send you a later warning**. It doesn't retry that email either, and the participant gets no alert. You'll only find out when they contact you.

**The email arrived but nobody saw it.** It's in spam or promotions, or the person mistyped an address that belongs to someone else. Nothing can detect this.

So never treat silence as delivery. Laces asks for the email twice at registration, which cuts down typos, but it can't stop all of them.

## How to help someone with no ticket

Save these steps for your support person:

1. **Ask for their order code.** It's shown on screen right after payment. If they have it, they can open their ticket at [Find your ticket](https://laces.run/o), with no email needed.
2. **If they have no code, find them.** Search your people list in the app by name or phone. You'll see their order, or you can find it in the organizer's copy in your inbox. Then pass on the code.
3. **If the email address is wrong,** ask them to write to support@laces.run with their order code to get it corrected.
4. **If they're at the gate already,** staff can type the order code, or search by name or phone. Nobody needs the email itself to get in.

Don't ask anyone to register again. That creates a second order and possibly a second charge. If a payment seems stuck, they should stay on the payment page and tap Check again, then send the prompt again or change the number there.

[Talk to the team](https://laces.run/contact): Tell the team what's happening, with the order code, and we can help you sort it out.

## Test the whole chain before you share the link

Do this once for each event type you run, from a phone that isn't yours:

1. Register for a ticket, using an address you can open. Once your organization is cleared, a free ticket lets you test this with no money involved.
2. Note how long the email takes, and which folder it lands in.
3. Open the PDF on a phone. Check the name, date, venue and order code.
4. Open your order code at `/o/`, as someone who has lost the email would.
5. Scan the ticket with the app.
6. Check that your organizer's copy arrived, and that it went to the right people on your team.

Remember that a new organization needs payment clearance before any registration opens, including free tickets. Build that into your timeline. See [what you need to create a registration form](https://laces.run/blog/create-online-event-registration-form).

## Frequently asked questions

### Do I need to set up confirmation emails on Laces?

No. They're sent automatically when a registration is confirmed. There's nothing to switch on, and you can't change the wording.

### Does Laces send confirmations by SMS or WhatsApp?

No. Tickets go by email and on the ticket page. You can share your event link on WhatsApp, but the ticket itself comes by email.

### Can I see which emails bounced?

Not in a complete way. If the send fails outright, your copy of the order says "Entry not delivered". If the email is accepted and bounces later, you won't get an alert.

### Is the participant still registered if the email fails?

Yes. The registration stands. They can use their order code at [Find your ticket](https://laces.run/o), and your gate staff can find them by name or phone.

### Can participants get a new copy of the receipt?

Yes. With the order code, they can open their entry and printable receipt online at any time.
