Login and register emails for your contacts

Two emails let a contact into your loyalty programme. The login email carries the link or code they sign in with, and the register email is what they get right after they sign up. Both are system emails, so they go out on their own and all you decide is what they say and how they look.

Both are shared. The contacts portal, the loyalty widget on your website and the Leat API all send the same login email, and the portal and the widget both send the same register email.

You'll find both in your account settings: click the gear icon at the top right of the dashboard to open Settings, then click Contact touchpoints under Communication. Only admins see Contact touchpoints. They're in the Login emails and Register emails sections. Until your account uses the contacts portal, each section shows an empty state instead of a list.

It goes out whenever a contact asks to sign in and we have to prove it's them. That happens from 3 places:

the contacts portal, when a contact enters their email address on the Login page
the loyalty widget on your website, when a contact requests a code
your own integration, through the contact verification call on the Leat API

Wherever the request came from, it's the same email, so an edit here changes what all 3 send.

The contact has to exist already. If the address doesn't belong to one of your contacts, nothing is sent. The portal still shows its usual message that an email is on its way, so that nobody can use your login page to find out who your contacts are.

When the register email is sent

It goes out once, right after a contact signs up on the portal's Sign up page or through the loyalty widget. It confirms the sign-up and carries the same login link or code, so they can go straight in.

When the Sign up page is switched off in the portal editor, sign-ups on the portal are refused, so no register email goes out for them.

When someone signs up on the portal or through the widget with an address that already belongs to one of your contacts, they get the login email instead, and they see the same message a new sign-up gets.

These emails only work because of what's in them, so one of 2 merge tags has to be present:

Login link, which signs the contact in when they click it. Put it in the URL field of a button.
Login code, which prints the code they type on the portal's Login code page. Put it in a text block.

Either one is enough, and you can use both. When neither is in the design, Publish refuses the email and tells you which tags are missing. Publishing also needs your account to be approved for sending.

Both emails offer the same tags, so a register email can hand a new contact a working login link without you setting anything else up.

The Login link tag is also available in your other emails to contacts. Adding it there lets contacts go straight to the portal without requesting a login email first.

You still need a working login email, because it's what goes out whenever a contact asks to sign in.

Editing one

Go to Settings → Contact touchpoints and click the email in Login emails or Register emails.
The Information tab shows the name, the subject, the sender name and address, and a preview of the design. Webview, in the ⋮ menu next to Edit email, opens the email in a browser tab.
Click Edit email to open the editor.

The editor has 2 tabs. Content is the drag-and-drop design, with the Tags panel on the left to search for and copy a tag. Information holds the name, the subject and the sender profile. After you change one, click Submit to save it.

Under Actions you can replace the design with a template (Replace design) and send yourself a test email (Send a test email). Finish later leaves the editor without publishing. Press Publish when you're done.

Marketing subscriptions don't apply

Both emails are functional. A contact gets one because they asked to log in or just signed up, not because they opted in to anything, so they're sent whatever the contact's subscriptions say. That's why neither email has a subscription type to choose.

Checking what went out

The Recipients tab on an email lists every send: the address, the status, opens, clicks and when it was created. Statuses run from Created and Awaiting sending through Processed, Sent and Delivered, with Deferred, Bounced, Dropped and Spam report for the ones that didn't land.

You can filter the list by contact, by status and by date, and the menu at the end of a row opens the contact's profile.

When a contact says the email never arrived

Look them up on the Recipients tab first. Bounced or Dropped points at the address or at their mail server, not at your design.
Delivered with nothing in their inbox usually means spam, so ask them to check it.
Not on the list at all usually means the address isn't one of your contacts, so nothing was sent even though the portal said it was. Check the spelling, or ask them to sign up first.
If the email itself is missing from your account, nothing can be sent. For a login or a portal sign-up we email your account admins when that happens. Contact support to have it restored.