Email automation.

Every lap at your venue is a reason to get in touch. Someone beat your customer's time; they set a personal best; they have not been in for a month; it is their birthday. Multitap writes and sends these emails on its own, in your brand colour, with your logo, to drivers who registered with an email address and agreed to hear from you. Every lap email quotes your own leaderboards exactly as your TVs show them, and links to the board. It sends your guests their booking confirmations and reminders too. There is no mailbox to connect: the emails go out in your venue's name, and replies come straight back to you.

Two switches

The Email page has four tabs: Setup, Templates, Notifications and Queue & Logs. Two switches on Setup decide what goes out at all.

Your own weekly venue summary follows neither switch. It has its own tick box on the Notifications tab, starts switched on, and reaches you as soon as email is working.

Save email settings sits at the bottom of the Setup tab and again at the bottom of Notifications. Either one saves both tabs. The template editor has its own Save template button.

Setup

The Setup tab opens on a status card. Its first line says in one sentence whether your email is working, with a coloured dot, and the line under it says what to do, if anything. Below that is a checklist with one row for each thing that matters. A green tick means done, an amber mark means it needs you, and a grey mark means optional or waiting.

The checklist

Driver emails and your postal address

Marketing email law in the United States requires a postal address in every commercial message, so the driver switch waits until you enter one under Postal address. Multitap prints it in the footer of every driver email.

Under the address, one line tells you who you can actually reach, for example Lap emails can reach 27 of 859 drivers. The second number counts every driver with an email address who agreed to hear from you and has not unsubscribed. The first counts those whose in-game name is also linked to their record, which Time Beaten, Session Summary and Milestone emails need because they are about laps. Linking names on the Drivers page closes the gap.

Require email consent to register makes the email consent box on your public registration page compulsory. Leave it off if any of your customers are in the UK, the EU or Canada, where consent has to be optional.

Who sends your emails?

The card below the checklist has two choices.

While either switch is on, your own server can't be saved without its address and a From address. The page tells you which is missing, or you can choose Multitap instead.

Sending a test

The test uses what is on the screen, saved or not, so you can try a mail server before you save it. Type an address, press Send test, and the answer appears under the button: Sent to [email protected] at 16:42. Check your inbox., or what went wrong and how to fix it. The test reads as your venue and says where your emails come from and where replies go. After a test gets through, the row remembers it, for example Last test sent 2d ago.

Through Multitap you can send ten tests an hour. A test that gets through also clears a Last email failed status, so after you fix a problem, a test is how you confirm it.

The status line and the dashboard

The first line of the Setup card always shows one of six states.

Your dashboard's System Health shows the same state in a few words, such as Email: sending as Demo Lounge <[email protected]>, last email 3m ago or Email: waiting on Multitap, and clicking it opens this page. Needs Attention lists the two states you can fix yourself: Email: finish your mail server setup and Email: last email failed.

Notifications

Nine cards, each with a checkbox and an eye icon that opens a preview. They go out only while the driver switch is on.

Driver emails greet each driver by first name and name everyone else as your boards do, such as K. Ito. Only valid laps count, and if your boards hide laps by drivers who aren't registered, so do the emails. Positions always come from your own leaderboards, ranked exactly as their TVs rank them. A lap on a track no board covers is ranked against the same class on that track instead, for example in GT3 at Imola, with no board link.

Under Behavior Settings you tune the rules: whether Time Beaten fires only when a driver leaves the top ten or on any drop; a cooldown per driver per board (24 hours by default); a cap on emails per driver per day (5); the visit timeout (60 minutes); the comeback threshold and its minimum gap (30 days each); the digest weekday; and the birthday message.

The same section holds the Weekly venue summary for you rather than your drivers: on the weekday you pick, an email to your account email (or any address you enter) with laps, unique drivers, active days, seat time, top tracks and cars, the week's fastest laps, the busiest days, and how the mail system performed. A line under the tick box tells you when it last went out and when it goes next, for example Last sent Monday, Sep 21. Next: Monday, Sep 28, to [email protected]. Send now queues one straight away without changing the weekly schedule (three times an hour at most). The summary appears in Queue & Logs like every other email.

Templates

The look and previews

Every email shares one clean layout: a white card on light grey, a header bar in your Primary Color with your logo, real buttons in the same colour, and a footer that says why the email came. The colour and the Venue Logo come from your Settings page, so there is nothing to choose here; change them there and every email follows. On a very light colour the button text turns dark so it stays readable. Each email also carries a plain-text version for mail apps that prefer it.

The Template Previews buttons render each email, the weekly summary included, with sample data in your own colour, logo and postal address, so you see what your drivers and guests will get.

Editing the content

The Template Editor lets you rewrite the body of any email type, including the Booking Confirmation and Booking Reminder your guests receive. Choose the type, edit the subject and the HTML content, and use the variable chips listed under the editor, such as {first_name} and {board_name}, wherever the real value should appear. A type you have not customised opens with the built-in email, with those variables already in place, so you can change one sentence and save without touching the rest. Parts that change from one email to the next, such as the subject, the button or a booking's details, are single variables like {subject} and {button_html}, so a saved template still fits every case. The header, footer and legal block are always added around your content.

Queue and logs

Emails are queued and sent in small batches by a background worker. This tab shows what happened.

An empty log says No emails sent yet., and a filter that hides every row says No emails match this filter. A message that fails three times is marked failed and waits for you here. Booking confirmations and reminders travel through the same queue and appear in the same log.