Skip to content
plugboard.appRequest a demo

Reference

Email templates

Edited under Settings, Notifications. All are plain text.

Nothing sends until an email connector is configured and enabled.

KeyNameTriggerAudienceCan disable
repair.submittedRepair receivedSomeone lodges a repair through the client portalThe person who lodged itYes
repair.readyCollection reminderA technician presses Email client on a repairThe person who lodged itYes
repair.ready.tutorReady for collection (tutor)A repair is ready and the student has a tutor on fileThe student’s tutorYes
repair.readyForCollection.studentReady for collection (student)A repair is marked ready for collectionThe studentYes
repair.readyForCollection.parentReady for collection (parent)A student’s repair is marked ready for collectionThe student’s parents and guardiansYes
repair.readyForCollection.staffReady for collection (staff)A staff member’s repair is marked ready for collectionThe staff memberYes
loan.dueSoon.studentLoan due soon (student)The morning a loan device is due back within three daysThe studentYes
loan.dueSoon.parentLoan due soon (parent)The morning a student’s loan device is due back within three daysThe student’s parents and guardiansYes
loan.dueSoon.staffLoan due soon (staff)The morning a staff member’s loan device is due back within three daysThe staff memberYes
loan.due.studentLoan due today (student)The morning a loan device is due backThe studentYes
loan.due.parentLoan due today (parent)The morning a student’s loan device is due backThe student’s parents and guardiansYes
loan.due.staffLoan due today (staff)The morning a staff member’s loan device is due backThe staff memberYes
loan.overdue.studentLoan overdue (student)The morning after a loan device was due backThe studentYes
loan.overdue.parentLoan overdue (parent)The morning after a student’s loan device was due backThe student’s parents and guardiansYes
loan.overdue.staffLoan overdue (staff)The morning after a staff member’s loan device was due backThe staff memberYes
ticket.acknowledgedTicket receivedA ticket is raised with somebody to send it toThe person who raised itYes
ticket.replyTicket replyThe desk replies in public. Internal notes never sendThe person who raised itYes
ticket.closedTicket closedA ticket is closed and the requester has an email addressThe person who raised itYes
purchase.receiptPurchase receiptA student buys something and a parent address is on fileThe parent or guardianNo
licence.expiringSoftware contract renewalA software contract approaches its term endThe configured software renewal recipientsYes
monitor.downMonitor alertA monitored service has been unreachable long enough to alertStaff who can view monitorsYes
backup.failedBackup failedA scheduled backup does not completeStaff who can manage backupsNo
parent.loginParent sign-in linkA parent asks for a link to the parent portalThe parent who askedNo
plan.changedPlan changedA licence is activated or removed and entitled modules changeStaff who can manage billingNo
report.scheduledScheduled reportA scheduled report is deliveredWhoever the schedule namesYes
digest.dailyDaily digestEach morning, to staff who opted inStaff with the digest turned onYes
visitor.arrivedVisitor arrivedA visitor or contractor signs in to see somebody, and host notification is onThe staff member being visitedNo
visitor.wwccReminderContractor WWCC renewalA contractor’s Working With Children Check is about to expire, or hasThe visitor register’s reminder recipientsNo

Four are mandatory because switching them off would hide something a person needs to know or act on:

purchase.receipt. A receipt to a parent for money taken. Switching it off leaves you with no record when a parent queries a charge.

backup.failed. An alert about your own data protection failing. If it can be switched off, eventually somebody will, and find out during a restore.

parent.login. The mechanism a parent uses to reach the portal. Off, the portal has no entry.

plan.changed. Modules should not appear or disappear without explanation.

The two visitor register messages cannot be switched off here for a different reason: each already has its own switch. Host notification is turned off in the register’s settings, where the change is audited and every sign-in records it. WWCC reminders stop going by email when the register’s recipient list is empty. A second, unaudited switch in this editor would undo that.

Written {{likeThis}}. The editor lists the ones each message carries, with a description and a realistic sample.

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, rather than rendering blank in production. Otherwise a template containing {{studentName}} on a message that never had a student would first show up in what a parent receives.

Every send in the product is plain text. An HTML editor would mean deciding how to escape a school’s own data inside it, and we have not made that decision.

The editor renders your wording with 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.

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

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

Repair received. Set a timing expectation if you have one.

Ticket received. Say whether replying to the email works. It does not by default.

  • Internal notes, ever.
  • Anything with no recipient address on file, which is skipped without an error.
  • Anything while the email connector is in demo mode, which logs instead.