Appearance
Notifications
Every automated message the product sends has a template you control — the subject, the body, and whether it goes at all.
Templates
Each template is tied to a trigger — the thing that causes it to send. Booking sent for signature, signature completed, invoice sent, invoice overdue, task due, document rejected, deposit return due, and so on.
Per template:
| Field | Notes |
|---|---|
| Type | Email, SMS, or in-app |
| Subject | Email only |
| Body | With merge tags |
| SMS body | A shorter version for text |
| Active | Turn a message off entirely |
| Notify team | Send your team a copy as well as the recipient |
Merge tags
The same idea as contract templates. Renter name, booking title, dates, invoice number, amount due, due date, the link, your account details. The editor lists what is available for each trigger.
Branding
Every email uses your branded layout with your logo and account details from Settings → General. You are editing the content, not the wrapper — the wrapper is consistent so your renters recognize it.
Defaults
The product ships with a working set. They are reasonable and you can leave them alone.
The ones worth reading in your own voice:
- Booking sent for signature — the first thing a new renter receives from you
- Invoice sent and invoice overdue — tone matters; the overdue one especially
- Document rejected — this one lands badly if it reads like a machine. Say what was wrong and what to send instead.
Recipient preferences
Recipients can set their own preferences per trigger, choosing email, SMS, or nothing for messages that are not essential.
In-app notifications
Staff get an in-app bell for things needing attention: signatures completed, payments received, documents awaiting approval, tasks overdue.
The email log
Every message the account sends is recorded in Email Log with the recipient, the subject, and the status — so "we never got that" has an answer.