Part 1: From your name, at your address
Verify your domain and mail goes out as you. That is the difference between an email people open and one that reads as a forward from a stranger.
Your brand
The email arrives days after the sale. It should still look like it came from you.
Verimly derives every customer email from your storefront theme, so the confirmation, the e-ticket, a cancellation and a refund notice all carry your colours, fonts and logo without being designed separately. You can send from your own address with a verified domain, and set a reply-to that reaches the person who should answer.
The numbers on the screen above mark the parts that do the work. Here is what each one is.
Verify your domain and mail goes out as you. That is the difference between an email people open and one that reads as a forward from a stranger.
The palette, fonts and logo come from the same place as your shop. There is no second design job and no way for the two to drift apart.
A QR code the door can scan, with the event, the date, the ticket type and the seat, so nobody has to log in to find their ticket at the gate.
Confirmation, ticket access, cancellation and refund. The ones nobody enjoys sending are the ones that most need to look official.
Set where replies land. A buyer answering the confirmation reaches your inbox, not a no-reply address.
You set your colours, fonts and logo once for the storefront. The emails read the same settings, so the message that lands in an inbox three weeks later matches the page the buyer bought from. Nobody has to remember to update a second template when the branding changes.
Add your domain, publish the records shown, and Verimly sends as your address once verification passes. Buyers see your name in their inbox, replies reach you, and the mail is authenticated properly so it lands in the inbox rather than the spam folder.
The ticket travels in the email: a QR code the door can scan, with the event, the date, the ticket type and the seat next to it. It works when the venue has no signal, when the buyer never made an account, and when they forward it to the friend who is actually going.
A cancellation or a refund is when your brand matters most, because the buyer is already unhappy. Those messages are in the same set and carry the same branding, with the specifics of what was refunded and why, so they read as a business handling it rather than as an automated shrug.
What you actually do, in order, the first time.
Logo, colours and fonts in the storefront editor. The emails follow.
Publish the DKIM records shown in email settings.
The name buyers see, and the inbox that receives their answers.
Buy a ticket on your own shop and read what arrives before your audience does.
| Styling | Derived from your storefront theme — palette, fonts, logo |
|---|---|
| Sender | Your own from-name and address, with domain verification |
| Authentication | DKIM records provided; status shown until verified |
| Reply-to | Set separately, so replies reach a person |
| Messages | Order confirmation, ticket access, cancellation, refund |
| E-ticket | QR code with event, date, ticket type and seat |
| Overrides | Accent colour and button shape, if the theme is not quite right |
| Rendering | Table-based with inline styles, so it survives every mail client |
No. They are derived from your storefront theme. If you want a different accent colour or button shape, both can be overridden.
Yes. Add the domain in email settings and publish the DKIM records shown. Until verification passes, mail is sent from a working default so nothing breaks.
The email carries your branding and, once your domain is verified, your address. Verimly is the tooling behind it, not the sender.
Yes. The QR code is in the email. Buyers do not have to create an account or install anything to get through the door.
Ticket access can be sent again from the order, to the same address, without reissuing the ticket.
They are built as tables with inline styles rather than modern CSS, which is what makes them survive the mail clients that are still stuck in 2003.
Get started
No subscription, no setup fee, nothing to cancel. Build the whole thing, and decide at the end whether to publish it.