Triggers & Automation
Triggers are automated rules that fire when something happens in ServCraft — usually a status change. They send emails and SMSes using templates, optionally attaching the relevant documents. Properly configured triggers reduce manual communication overhead significantly.
What Is a Trigger?
A trigger is a rule with three parts:
- Event (Trigger Rule) — What happened? e.g., "Job status changed to Closed"
- Conditions — When should it fire? e.g., "Only for Job Type = Installation"
- Actions — What should happen? e.g., "Send email to the customer's primary contact using the Invoice Reminder template"
Multiple triggers can be configured. When the event fires, all matching triggers execute.
Accessing Triggers
Settings → Templates → Triggers
Permission required: Super Admin (the same permission that opens every item under Templates)
Supported Events (Trigger Rules)
Every trigger belongs to one Trigger Module, and the module decides which Trigger Rule options appear. There are six modules: Job Card, Quote, Invoice, Query, Purchase Order and Customer Zone. Jobs and job cards are the same module.
Most rules are events: they fire the moment something happens. Three rules are time-based reminders: Job Status Reminder, Quote Reminder and Invoice Reminder. ServCraft checks these in the background, and they fire once a set amount of time has passed.
| Trigger Module | Trigger Rule | Kind | Fires when... |
|---|---|---|---|
| Job Card | Job Status Change | Event | A job moves to one of the chosen statuses |
| Job Card | Job Employee Allocated | Event | An employee is assigned to a job |
| Job Card | Job Employee Unallocated | Event | An employee is removed from a job |
| Job Card | Job Status Reminder | Time-based reminder | An open job has stayed in one of the chosen statuses for longer than the time set on the trigger. It fires once each time a job enters that status |
| Quote | Quote Status Change | Event | A quote changes to the chosen status |
| Quote | Quote Reminder | Time-based reminder | A set time after the quote date (After Quote Date), or a set time before the quote expires (Before Expiry Date) |
| Invoice | Invoice Status Change | Event | An invoice changes to the chosen status |
| Invoice | Invoice Reminder | Time-based reminder | A set time after the invoice date (After Invoice Date), or a set time after the due date (After Invoice Due Date) |
| Query | Query Status Change | Event | A query changes status |
| Query | Query Employee Allocated | Event | A query is saved by an employee other than the one assigned to it, for example when a manager assigns it to a technician. See the note below the table |
| Query | Email to Query Create | Event | An inbound email creates a new query. It has no conditions to set |
| Purchase Order | Purchase Order Status Change | Event | A purchase order changes status |
| Customer Zone | Customer Zone Message | Event | A customer sends a message in the Customer Zone |
| Customer Zone | Customer Zone Feedback | Event | A customer leaves a job rating or feedback in the Customer Zone |
Quote Reminder and Invoice Reminder
Both are set up under Settings → Templates → Triggers. Pick the Quote or Invoice module, choose the reminder rule, then choose the Quote Reminder Type or Invoice Reminder Type and the Time.
A Quote Reminder only goes out for quotes that are Approved, have been sent to the customer, have not yet expired and are less than 6 months old. Use it to chase customers who have not accepted a quote.
An Invoice Reminder only goes out for invoices that are Unpaid or Overdue and have been sent to the customer. The invoice date must be within the last 6 months and on or after the day the trigger was created, so older invoices are never chased by a new trigger. Use After Invoice Due Date for overdue payment reminders.
Each reminder fires once per quote or invoice. To send a second reminder, create a second trigger with a longer time.
Triggers from the job status screen
On Settings → Jobs → Statuses, selecting a status shows a Triggers button with a count, for example "Triggers (2)". It lists the triggers that watch that status. A trigger added from that button is always a Job Status Change trigger for that status. To add a reminder for a status, use Settings → Templates → Triggers and the Job Status Reminder rule described below.
Job Status Change — The Most Used Event
This is the workhorse trigger. Common uses:
- Send customer confirmation when job status moves to "Work in Progress" ("We're on our way")
- Send customer notification when job is "Complete", attaching the sign-off document
- Send internal alert when job moves to "Quote Awaiting"
- Email the office when a job reaches "Closed"
Job Status Reminder — Jobs Sitting in a Status Too Long
Use this rule when the office wants to hear about jobs that have not moved, for example jobs still waiting for parts after three days. It is the only time-in-status reminder in ServCraft, and it exists only for jobs. Query triggers have no reminder rule; their rules are Query Status Change, Query Employee Allocated and Email to Query Create.
Jobs on hold for several days. This is the rule to use. ServCraft has no built-in on hold flag. On hold is whichever status your workflow uses for it. Choose that status under Job Status, set Time to the number of days, and pick an employee as the recipient. If the job is still in that status when the time runs out, the reminder is sent.
To set it up:
- Go to Settings → Templates → Triggers and create a new trigger.
- Set Trigger Module to Job Card.
- Enter a Trigger Name, for example "Awaiting parts – 3 days".
- Set Trigger Rule to Job Status Reminder.
- Choose the Workflow, then one or more Job Status values. Job Type is optional; leave it empty to cover all job types.
- Set Time, the length of time a job may stay in the status before the reminder fires. It can be entered in minutes, hours, days, weeks or months, and cannot be more than 6 months.
- Add the communication action (recipient, email or SMS, message template) and save.
How it behaves:
- It only looks at open jobs. Once a job is closed it is no longer reminded about.
- The clock starts when the job entered the status. If the job moves to another status before the time is up, nothing is sent.
- It sends one reminder per visit to the status. If the job leaves the status and later comes back, the clock starts again and it can fire again.
- It only counts status changes made after the trigger was created. Jobs already sitting in the status when you create the trigger are not picked up.
- It ignores status changes older than 6 months.
The other Job Card rules are Job Status Change, Job Employee Allocated and Job Employee Unallocated.
Available Actions
Each trigger action has an Action Type:
| Action type | What it does |
|---|---|
| Communication | Sends an email and/or SMS using a chosen message template |
| Property Set | Sets a value on the record — used to stamp the SLA start and end date/time on jobs |
There is no "create task" or "reassign employee" action — triggers communicate and stamp SLA times; they don't change who a job is assigned to.
Communication actions
For a communication action you choose:
- Notification Type / Recipient — who receives it. Options include the customer's contacts, the customer's primary contact, the contacts linked to the specific record, a specific employee, the employees on the record, all employees, the customer's primary accounting contact, and (for allocation events) the employee who was just allocated or unallocated
- Send Email and/or Send SMS — at least one must be on. There is also Send SMS If No Email, which falls back to SMS only when the recipient has no email address
- Message Template — the template to use (Settings → Templates); templates can be created and edited right from the trigger screen
- Attachments — for job, quote, invoice, and purchase order triggers, tick which generated documents to attach (e.g., the job card, sign-off document, quote, invoice, or purchase order PDF)
Trigger Conditions
Conditions narrow when a trigger fires. The conditions available depend on the trigger rule:
| Condition | Example |
|---|---|
| Job Type | Only fire for "Installation" jobs |
| Workflow | Only fire for jobs in Workflow A |
| Status | The specific job / quote / invoice / purchase order / query status the rule watches |
| Priority | For query triggers |
| Time | For Job Status Reminder, Quote Reminder and Invoice Reminder: how long to wait before the trigger fires |
Adding job type conditions is recommended when you have multiple job types with different workflows — otherwise a "job completed" trigger fires regardless of job type.
Template Configuration
Triggers that send emails or SMSes need templates. Templates are configured in Settings → Templates → Messages.
Template features:
- One template holds a Subject, an Email Template and an SMS Template. Rich text is used for the email.
- Each template belongs to one module (Job, Invoice and so on), chosen when the template is created and not changeable afterwards.
- Replacement tags insert live data. They are written in double curly braces, such as
{{Link}}, and the Insert Replacement Tag button on the template lists the tags that module accepts. A tag the module does not know stops the template saving with "Please fix the following replacement tag(s)". - System templates (pre-built) vs User templates (custom)
Creating a trigger-ready template:
- Go to Settings → Templates → Messages and click Add Template.
- Enter the Name of the template and the Module, then continue to the template page.
- Fill in the Subject, the Email Template and the SMS Template, using Insert Replacement Tag for personalisation.
- Save.
- Go back to Settings → Templates → Triggers and reference this template in your trigger.
Example Trigger Configurations
"Notify customer when technician is on the way"
| Part | Value |
|---|---|
| Event | Job Status Change |
| Status | Work in Progress |
| Condition | Job Type = Service Call (optional) |
| Action | Communication — Send Email |
| Template | "Technician En Route" template |
| Recipient | Customer primary contact |
"Alert office when a job is completed — needs invoicing"
| Part | Value |
|---|---|
| Event | Job Status Change |
| Status | Complete |
| Condition | None (all job types) |
| Action | Communication — Send Email |
| Template | "Job Ready to Invoice" template |
| Recipient | A specific employee (e.g., the accounts person) |
"Send invoice payment reminders"
Use the Invoice Reminder rule, which fires a set time after the invoice date or due date:
| Part | Value |
|---|---|
| Trigger Module | Invoice |
| Event | Invoice Reminder |
| Invoice Reminder Type | After Invoice Due Date |
| Time | e.g., 7 days |
| Action | Communication — Send Email |
| Template | "Payment Reminder" template |
| Recipient | Customer primary accounting contact |
It goes out once per invoice, and only while the invoice is Unpaid or Overdue, so paid invoices are left alone. Invoices dated before the trigger was created are not chased.
"Alert the office when a job is stuck in a status"
| Part | Value |
|---|---|
| Event | Job Status Reminder |
| Condition | Workflow + the job status(es) being watched + Time (e.g., 3 days) |
| Action | Communication — Send Email |
| Template | "Job Stuck" template |
| Recipient | An employee or all employees |
The time is set on the trigger itself. When an open job has been in a watched status longer than that, the trigger fires once for that job.
"Tell the office every time a quote is accepted"
| Part | Value |
|---|---|
| Trigger Module | Quote |
| Event | Quote Status Change |
| Quote Status | Accepted |
| Action | Communication — Send Email and/or Send SMS |
| Template | "Quote Accepted" template |
| Recipient | Notification Type Employee, then the person to tell |
It fires when the customer accepts the quote in the Customer Zone and when a staff member changes the status to Accepted by hand. The Quote Status list offers Draft, Approved, Accepted, Declined, Cancelled and Invoiced, and each trigger watches one of them. Use Add Another Action on the same trigger to notify more than one person.
Every new trigger needs a Trigger Name, whatever the module. The name field shows the hint "Leave blank to auto generate from condition" for status and reminder rules, but leaving it blank stops the trigger from being created with "Name is required".
Common Trigger Issues
"The trigger is firing but the customer isn't receiving the email"
- Check the customer's contact record — does the primary contact have a valid email?
- Check the trigger's Notification Type — is the recipient the contact you expect (primary contact vs all contacts vs employees)?
- Check spam filters — automated emails sometimes land in promotions or spam
- If "Send SMS If No Email" is on, the message may have gone out as an SMS instead
"The trigger is firing too often (every status change, not just the right one)"
Add conditions to narrow the trigger:
- Specify the exact job type(s) this trigger should apply to
- If multiple workflows exist, specify the workflow in the condition
"We set up a trigger but it's not firing at all"
- Confirm the trigger is Active (Is Active = true on the trigger record)
- Check that the status being transitioned to matches the trigger's configured status exactly
- If using workflow conditions, confirm the job is using that workflow
- Check that the email template exists and is active
"We want different messages for different job types"
Create separate triggers with job type conditions. One trigger for "Installation Complete" (one template), another for "Service Call Complete" (different template).
Trigger vs. Manual Communication
Triggers handle expected, routine communications automatically. They're not a replacement for manual follow-up.
| Use triggers for | Do manually for |
|---|---|
| Confirmation emails (job booked, tech en route) | Complex or personalised conversations |
| Stuck-job alerts | Negotiating overdue invoices |
| Status-based notifications | Sales/upsell conversations |
| Routine invoice reminders | Dispute resolution |
Related Topics
- Job Settings
- Company Settings (email from address used by triggers)
- The Job Lifecycle