Skip to content
plugboard.appRequest a demo

Configuration

Email messages

Settings, Notifications (/admin/notifications).

Thirteen messages ship with default wording. Most schools change two or three.

The editor shows what triggers each message, who receives it, the variables it can use, and a live preview filled with sample values.

An email connector has to exist and be enabled. Until then nothing on this page sends. Set it up and send yourself a test before you change any wording.

MessageSent whenToCan be switched off
Repair receivedSomeone lodges a repair through the client portalThe person who lodged itYes
Ready for collectionA repair is marked readyThe person who lodged itYes
Ready for collection (tutor)A repair is ready and the student has a tutor on fileThe student’s tutorYes
Ticket receivedA ticket is raised with somebody to send it toThe person who raised itYes
Ticket replyThe desk replies in public. Internal notes never sendThe person who raised itYes
Ticket closedA ticket is closed and the requester has an email addressThe person who raised itYes
Purchase receiptA student buys something and a parent address is on fileThe parent or guardianNo
Monitor alertA monitored service has been unreachable long enough to alertStaff who can view monitorsYes
Backup failedA scheduled backup does not completeStaff who can manage backupsNo
Parent sign-in linkA parent asks for a link to the parent portalThe parent who askedNo
Plan changedA licence is activated or removed and the entitled modules changeStaff who can manage billingNo
Scheduled reportA scheduled report is deliveredWhoever the schedule namesYes
Daily digestEach morning, to staff who opted inStaff with the digest turned onYes

Purchase receipt. A receipt to a parent for money taken. Without it you have no record to point at when a parent queries a charge.

Backup failed. An alert that your own data protection has stopped working. You find out during a restore otherwise.

Parent sign-in link. The mechanism a parent uses to reach the portal. With it off, the portal has no entry.

Plan changed. Notification that your entitlements changed. Modules appearing or disappearing without a message is confusing enough to be worth a mandatory email.

Each message has a subject and a body. Every message the product sends is plain text.

Variables are written {{likeThis}}. The editor lists the ones each message carries, with a description and a sample value.

Common ones:

VariableHolds
{{name}}Who the message is about or to
{{deskName}}What your service desk calls itself, from branding
{{trackingUrl}}The person’s private repair status link
{{repairType}}What kind of repair, when known
{{deviceSuffix}}The serial in brackets, or nothing when unknown
{{loanLine}}A line about the loan device, when one was issued

A variable that does not exist on a message is rejected when you save, so {{studentName}} on a message that never had a student is caught here rather than in the email a parent receives.

The preview renders your wording with realistic sample values, so you see the message as a parent would. Wording that reads fine in the editor often reads oddly once the variables fill in.

Four messages benefit from local detail:

Ready for collection. Say where. “Ready to collect from the ICT office, opposite the library” saves your desk a lot of questions.

Purchase receipt. Say what to do if something is wrong, and who to contact.

Repair received. Set an expectation about timing if you have one. “Most repairs take two to three school days” prevents the follow-up email tomorrow.

Ticket received. Same, and say whether replying to the email works. A reply joins the ticket only when the desk has a ticket mailbox address and its mail is delivered back to Plugboard, for example through Microsoft 365 Email intake. Without that, say so in the message.

Internal notes. A note on a ticket is internal by design and is never emailed to the requester. Only a public reply sends. Say so to your team before somebody writes something in a note that they would not write in an email.

Anything with no address on file. A message with no recipient is skipped without raising an error.

Anything while an email connector is in demo mode. Demo mode logs instead of sending.

The complete list with default wording and every variable is in email templates.