Appearance
An automatic email went wrong, or did not go
A family got an email you did not know Xperios sent, or did not get one you were counting on, or the wording was not yours. Automatic emails have three separate parts - whether they are sent at all, what they say, and who they come from - and each is set in a different place, so the first job is working out which part is wrong.
Step 1 of 8
Automatic emails belong to the service type
Nearly every automatic email is a property of the service type the activity is on, not of the system as a whole. Open the service type and its Email area carries the From address those emails are sent from, a Reply address for where answers should land, and the switches for the ones you can choose about. Two services can behave completely differently - one sending a new application email and the next not - which is why "does Xperios email parents about this?" has no single answer.
So when somebody reports an email, find out which activity it was about first. The answer is on that activity's service type, and looking at a different one will tell you the wrong thing.
Use the arrow keys to move between steps.
Why this one is worth knowing
The thing that makes these confusing is that "the email" is really three decisions taken in three places. Whether it goes is the service type. What it says is a message template. Who it is from and where replies go is the service type again, but a different pair of fields. A complaint about an email is rarely a complaint about all three, so the first move is to work out which one you are being told about.
The second is to stop guessing about delivery. The journal is a record of what was sent to whom, so "we never told them" and "they never got it" are different findings with different answers, and you can tell them apart in about twenty seconds.
And it is worth knowing which emails have no switch. They are the ones that follow an action somebody here took — an application received, a child placed in a lesson, money taken — and they are deliberate. A service that needs families not to hear about something is usually a service that needs to change when it does it.
The same ground, as reference
- Message Content Templates — the wording, and what an override replaces
- Service Types fields — every field on a service type, the Email area among them
- What the payer was told about a payment — the notice, failure and success emails behind one payment
- Emailing a lot of people at once — the other kind of email, the ones you send yourself
- A parent cannot sign in — when the address on the record is not the address they use
