List of emails WorkZerk sends

Mail leaves your account in two directions, and they behave differently. Some goes to the people you onboard, and you mostly control the wording. Some comes to you, about your own account, and you do not. This article maps both, says who each one comes from, and covers what to do when something does not arrive.

Who the email comes from

Everything WorkZerk sends, to you or to your people, comes from WorkZerk, at [email protected]. When one of your people replies to an email about their portal (an invite, a reminder, a rejection or a status update), the reply goes to your account's email address. Replies to emails WorkZerk sends to you go to our support inbox at [email protected].

Two exceptions. The welcome series comes from [email protected], because it is the only marketing mail we send. Billing receipts come from our payment provider, Stripe.

Mail to the people you onboard

Most of it is either a system email or one of your own rules, and both are edited in Automations. The short list:

The portal invite with somebody's private link.
The requests completed receipt once everything required is in.
The expiry date prompt, when you click Prompt on the Requests screen.
The upload rejected notice, carrying your reason.
The self-registration confirmation, when somebody joins through a self-registration link.
The document approved confirmation, once you approve a file.
Five reminders. The outstanding requests reminder is switched on: it emails 7 days after the invite and again at 14, until they finish. The other four are off until you turn them on: document expiring, document expired, a rejected upload nobody has replaced, and a document with no expiry date that is due to be asked for again.
Any email one of your own rules sends.

Two more are sent from the portal rather than from Automations:

A status update, when you move somebody's status and choose to tell them. It carries the wording you gave that status and copies you in, so both sides hold the same record. Where the portal has the option on, it also carries their private link. A link you revoked stays revoked, and the email goes out without one. See Statuses.
A please sign the updated terms email, when you ask the people on an older version of your terms to sign the current one. Its wording is fixed. See Terms and conditions.

If somebody says the wording of an invite or reminder is wrong, blunt, or missing something, it is yours to fix in Automations.

Mail to you, about your account

These are not editable, and none of them go to anyone you onboard. Knowing they exist matters mostly so a real one is not mistaken for phishing.

Your verification code. A six-digit code, sent when you sign up. Until you enter it, every send you press a button for is refused: single invites, bulk invites, rejection notices, status updates, terms requests. If your people are getting nothing, check this first. Automations keep running regardless.
Reset your password. Sent only when somebody asks for it. The link lasts 24 hours.
Changing your email address. A confirmation link goes to the new address, so a typo cannot lock you out, and a notice goes to the old one saying a change was asked for. Nothing changes until the link is clicked.
An invitation to somebody's account, when a colleague shares their account with you. See Sharing your account.
A seat was added or removed, to the account owner, with the new seat count and what the subscription now costs.
You're now above 25 active people, the first night you go over the number your plan includes, again if you climb back over after a week or more under, and again each time your count reaches double the number in the last email. Your account credit has run out follows if the prepaid credit behind those extra people drops below zero. See What counts as an active person.
Billing. Receipts and payment failures, from Stripe.
Our support team accessed your account, every time a support agent opens it to help you.
Two-factor authentication was reset, if 2FA on your account is turned off through support.
Your account will be deactivated. Four of them, at 60, 30, 7 and 1 day out, if a long-dormant account starts the removal process, then a fifth saying it has been deactivated and how long you have to restore it. See Inactivity and automatic deletion.
Your account is scheduled for deletion, when you delete your account, saying when it happens (about 48 hours later) and how to stop it. See Deleting your account.
An automation could not create tasks, when a rule is due to apply a workflow that has since been deleted.
A test email, when you click Send test to me in the automation editor. It goes to you, marked [Test].
A short welcome series over your first few weeks. Unsubscribing stops it and affects nothing else.
Help tickets. An acknowledgment when you open one, and our replies. See Getting help.

Three more come from automations pointed at you: invite not opened, upload not reviewed, and everyone has finished. Invite not opened is switched on from the start; the other two are off until you switch them on. All three are yours to reword. Automations covers them.

The weekly summary is a digest of what is outstanding across your portals. It is off by default. When you switch it on you pick the day and hour and one address to send it to. See Weekly summary email.

When an email does not arrive

Work down this list. It is roughly in order of how often each one turns out to be the answer.

Check the log first. Emails, Activity tab, tells you whether the message was sent, delivered, bounced, or stopped before it left. That answer decides everything else. See Email tracking & log.

"Not sent" means it never left. The usual causes are an unverified account address, which blocks every email the account sends, automations included, and a used-up monthly allowance. See Monthly email allowance. If an automation should have sent it, when an automation does not send has its own checklist, because several of those skips leave no record at all.

A bounce usually means the address is wrong. Correct it on the contact and send again. An address that bounces permanently, or whose owner marks one of our emails as spam, is blocked from then on so we stop sending to it. A temporary bounce (a full mailbox, a server that is down) does not block it. If a blocked address is actually fine, email us to clear it.

Delivered but not seen is nearly always a spam folder or a corporate filter. Ask them to check, and to mark it as safe. If a whole company is filtering you, their IT can allow mail from mail.workzerk.com.

Nothing at all in the log means the send was never triggered. The commonest reason is a reminder that is switched off. Most of them start off; only the outstanding requests reminder and invite not opened start on.

The log cannot always tell you whether an email was read. Opens and clicks are recorded where the recipient's mail client allows it, and plenty do not.

Getting help

If a message is missing from the log entirely, or the log says delivered and the recipient is certain nothing arrived, email [email protected] with the person's address and roughly when it should have gone. We can see further into the delivery record than the Activity page shows.