> For the complete documentation index, see [llms.txt](https://docs.shortcutco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shortcutco.com/readme/automations/automations-list-+-triggers-exact.md).

# Templates and starts

Every automation template and what it does, every way an automation can start, every event it can start from, and what your older built-in automations start on.

This page is the reference for starting an automation: the templates on the **New automation** page, the four kinds of start, every event an automation can start from, and what the older built-in automations start on. [Open Automations →](https://shortcutco.com/settings/automations)

For how to build and publish, see [Build and publish an automation](https://docs.shortcutco.com/readme/automations/build-and-publish-a-campaign.md). For steps and variables, see [Steps, message options, and variables](https://docs.shortcutco.com/readme/automations/steps-and-variables.md).

## Templates

Click **New automation** on the Automations list. Under **Templates** (*Proven flows, grouped by what they get you*), each row has the template's name, one line on what it does, and **Use template**. Starting from a template, like building from scratch, needs the **Optimize** plan.

* Type in **Search templates** to find one by name, description, or step.
* Click a chip to see one kind: **All**, **Get paid faster**, **Close more estimates**, **Welcome new leads**, **Confirm visits**, **Win back quiet customers**, or **Keep work moving**.

**Use template** opens a new, unsaved automation with that flow filled in. Nothing is live until you start it, and you can change everything first. Templates that message customers mostly wait for a 9:00 AM–6:00 PM sending window first. Tasks a template creates are unassigned, and notifications go to company admins, until you change **Assign to** or **Notify**.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-7f78152154d64f865776ddb21a476790abd38543%2Fautomations-templates-tab.png?alt=media" alt="The Templates list on the New automation page, filtered to Get paid faster, with each template&#x27;s name, one-line description, and Use template button"><figcaption><p>Filter templates by what they get you, then click Use template.</p></figcaption></figure>

### Get paid faster

| Template                     | What it does                                                                                             |
| ---------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Invoice due soon**         | Reminds the customer three days before an unpaid invoice is due.                                         |
| **Overdue invoice recovery** | Reminds customers about an overdue invoice and hands ones that stay unpaid to your team.                 |
| **Payment failed**           | Emails the customer when a payment fails, then texts them if the invoice is still open three days later. |
| **Expired card on file**     | Asks active customers whose saved card has expired to add a new one, at most every 60 days.              |
| **Invoice paid receipt**     | Sends a receipt email when an invoice is paid.                                                           |
| **Partial payment reminder** | Reminds the customer of the balance still open three days after a partial payment.                       |
| **Autopay suggestion**       | Suggests autopay, once, to a customer who pays by hand with a card on file.                              |
| **Card added thank-you**     | Thanks the customer for adding a card and explains autopay.                                              |
| **Card removed follow-up**   | Gives your team a task and alerts an admin when a customer's saved card is removed.                      |

**Overdue invoice recovery** in detail: it starts for invoices that are sent or overdue, 7 or more days past due, with a balance left. It emails during a Mon–Fri 9:00–17:00 sending window, waits a week, and if the invoice still has a balance creates the task *Review overdue invoice*, due the next day. It runs at most once every 14 days per invoice and ends as soon as the invoice is paid or voided.

### Close more estimates

| Template                         | What it does                                                                                |
| -------------------------------- | ------------------------------------------------------------------------------------------- |
| **Estimate follow-up**           | Emails customers whose estimate is still pending, then creates a task for larger estimates. |
| **Estimate approved next steps** | Confirms an approved estimate by email and gives your team a task to schedule the work.     |
| **Declined estimate win-back**   | Sends one win-back email a month after an estimate is declined.                             |
| **Estimate voided or expired**   | Tells the customer when an estimate is voided or expires, once per estimate.                |
| **Estimate expiring soon**       | Reminds the customer three days before a pending estimate expires.                          |

**Estimate follow-up** in detail: three days after an estimate is sent, it waits for a 9:00–18:00 sending window (every day) and emails the customer if the estimate is still pending. Estimates of $1,000 or more that are still pending three days after that get the task *Follow-up high-value estimate*. It runs at most once every 7 days per estimate.

### Welcome new leads

| Template                         | What it does                                                                                                                                                                |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New lead welcome**             | Welcomes a new lead by email, and creates a call task if they're still a lead two days later.                                                                               |
| **Website inquiry auto-reply**   | Confirms a website inquiry to the customer straight away and notifies an admin to respond.                                                                                  |
| **New customer welcome**         | Sends a one-time welcome email when a customer account is created.                                                                                                          |
| **Priority customer follow-up**  | Notifies company admins when a new lead comes in or a customer gets a tag, if they're a lead, prospect, or active customer. An example of two starts sharing one follow-up. |
| **Quiet lead check-in**          | Checks in with a lead who has gone quiet for a week, then gives someone a task to call.                                                                                     |
| **Tag onboarding sequence**      | Sends two onboarding emails, three days apart, when a customer gets a tag. Pick the tag in the start conditions.                                                            |
| **Dismissed lead re-engagement** | Sends one check-in email 90 days after a lead is dismissed, if they're still a lead.                                                                                        |

### Confirm visits

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-7693e328529e1cdf0f4842f14d864af25da38799%2Fautomations-templates-confirm-visits.png?alt=media" alt="The Templates list on the New automation page filtered to Confirm visits, from Day-before service reminder down to Missed visit reschedule, Skip or cancel notice by reason, Call-ahead text and Call-ahead phone call, each with Use template"><figcaption><p>The Confirm visits templates, including the skip/cancel and call-ahead ones.</p></figcaption></figure>

| Template                            | What it does                                                                                                                                                                       |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Day-before service reminder**     | Combines tomorrow's visits into one reminder email per customer, listing the visit date and services.                                                                              |
| **Visit reminder**                  | Texts a separate reminder the day before each visit, using the visit's current date.                                                                                               |
| **Visit scheduled confirmation**    | Emails the customer when a visit is scheduled.                                                                                                                                     |
| **Visit date changed**              | Emails the new date whenever a visit is rescheduled.                                                                                                                               |
| **Visit canceled notice**           | Emails the customer when a visit is canceled.                                                                                                                                      |
| **Visit completed thank-you**       | Sends a thank-you email after a completed visit, at most once a week per customer.                                                                                                 |
| **Skipped visit follow-up**         | Gives your team a task and notifies admins when a visit is skipped or needs rescheduling, without messaging the customer. If nothing happens within a day, it notifies them again. |
| **Treatment complete**              | Texts the customer the products applied when a treatment visit is completed.                                                                                                       |
| **Team arrival text**               | Texts the customer when the team marks itself arrived at their property.                                                                                                           |
| **Missed visit reschedule**         | Every time a visit is skipped or needs a new date, whatever the reason, emails the customer and gives your team a task to rebook it.                                               |
| **Skip or cancel notice by reason** | When a visit is skipped or canceled, the reason picked decides what happens: the customer gets an email saying why, or your team gets a task to review it.                         |
| **Call-ahead text**                 | The day before each visit for customers tagged **Call ahead**, texts them the date and service. If they can't be texted, your team gets a task to call instead.                    |
| **Call-ahead phone call**           | The day before each visit for customers tagged **Phone ahead**, gives your team a task to phone them. Sends nothing to the customer.                                               |

* **Day-before service reminder** sends through the grouped day-before reminder, which only one automation can own. See [The grouped day-before reminder](https://docs.shortcutco.com/readme/automations.md#the-grouped-day-before-reminder).
* **Skip or cancel notice by reason** emails the customer for the reasons **Customer asked to skip**, **Grass not growing / not needed**, **Weather**, and **Couldn't access the property**. The email names the reason. Other reasons, including ones your company added, give your team the task *Review skipped visit for \[customer]* instead. To email for another reason, add it to the template's **Branch** condition. A customer gets at most one of these emails a day. Reasons are set in **Settings → Operations → Visit reasons**; see [Skip or cancel one visit](https://docs.shortcutco.com/readme/jobs-and-scheduling/skip-or-cancel-a-visit.md#your-list-of-reasons).
* **Call-ahead text** and **Call-ahead phone call** go by tag name. Add a tag called **Call ahead** (or **Phone ahead**) to the customers who need it; until a customer has the tag, the automation starts for nobody. If your tag has another name, change that one condition. Both run once per visit, alongside your day-before reminder, and wait for 8:00 AM–6:00 PM before texting or creating the task. The call task is due four hours later. To text on the morning of the visit instead, change the start's timing to 0 days after the visit's date.
* A call-ahead goes out only for visits Shortcut saw before the start time. A customer tagged, or a visit booked, after that is covered from their next visit. A visit moved after its call-ahead went out doesn't get a second one.
* **Visit reminder** only reaches visits scheduled after you start it. The text goes only if the visit is still scheduled and its service isn't paused. A visit booked for tomorrow before 6:00 PM still gets its reminder that day; one booked later that evening, or for the same day, doesn't.
* **Treatment complete** only sends for visits with a completed chemical record, and only once you share application records with customers in **Settings → Operations → Chemicals**.

### Win back quiet customers

| Template                      | What it does                                                                                                                                   |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Seasonal service offer**    | Between September 1 and November 30, emails customers who've had service before and have nothing upcoming.                                     |
| **Customer reactivation**     | Emails customers who've had service before, with no visit completed in 90 days and nothing upcoming. Logins and notes don't count as activity. |
| **Paused service check-in**   | Checks in by email when a service paused by hand has stayed paused for 30 days. A season pause never starts it.                                |
| **Spring pre-booking**        | Every March 1, invites past customers with nothing on the calendar to book the coming season.                                                  |
| **Canceled service win-back** | Sends one win-back email 30 days after a service is canceled, if nothing else is booked.                                                       |
| **Churned customer survey**   | Two days after a customer is marked churned, asks one question by email: what could we have done better?                                       |
| **Customer anniversary**      | Sends a yearly thank-you email on each active customer's anniversary.                                                                          |

**Seasonal service offer** and **Customer reactivation** run at most once every 90 days per customer. **Customer reactivation** also reaches customers you've deactivated; add **Customer account status** **is** **active** to its conditions if you don't want that.

### Keep work moving

| Template                        | What it does                                                                                                                                                                                                                                                                 |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Estimate sent**               | Emails and texts the estimate link as soon as an estimate is sent, on the channels ticked for that send. Every new company already has this one running. See [The Estimate sent automation](https://docs.shortcutco.com/readme/automations.md#the-estimate-sent-automation). |
| **Delivery evidence follow-up** | Notifies company admins when an automation email is confirmed delivered. It fires for **every** delivered automation email, so it's best kept to small automations.                                                                                                          |
| **Bounced email fix**           | Gives your team a task to fix the address and alerts an admin when an automation email bounces.                                                                                                                                                                              |
| **Failed text follow-up**       | When a text from any automation fails or the carrier refuses it (a landline or a wrong number), gives your team a task to call the customer instead.                                                                                                                         |

## Ways an automation can start

Pick one in the start's **Start kind**. The **On a date or schedule** card on the New automation page opens **On a schedule**; switch it to **Around a date** if that's what you need.

| Start kind                          | What it does                                                                                                                                                     |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **When something happens**          | Starts when one of the events below happens after the automation starts.                                                                                         |
| **When customers match conditions** | Keeps checking your rules and starts for each customer or record that newly matches. Existing matches are only included if you choose that on the first publish. |
| **Around a date**                   | **A date relative to a record** (before or after a date field, optionally **Repeat every year (anniversary)**), or **A specific date**.                          |
| **On a schedule**                   | **Daily**, **Weekly**, **Monthly**, or **Yearly** (one date or several dates each year) at a set time, with optional **Starts on** / **Ends on**.                |

## Events you can start from

The **Event** picker groups them like this:

**Visits**

* Day before service (grouped per customer)

**Customers**

* Customer created · Customer account status changed · Customer marked as churned · Customer account became active
* Lead created · Public intake submitted · Lead lifecycle stage changed · Lead source changed · Lead dismissed · Lead marked lost

**Invoices & payments**

* Customer autopay setting changed
* Invoice record created (including drafts) · Invoice sent · Invoice created and sent at once (no draft) · Invoice paid · Invoice became overdue
* Invoice payment attempt failed · Invoice payment recorded (partial or full)
* Card added on file · Card details updated · Card removed from file

**Estimates**

* Estimate created · Estimate sent · Estimate accepted · Estimate declined · Estimate expired · Estimate voided

**Services & visits**

* Service record created · Service status changed · Service scheduled · Service paused · Service paused for the season · Service resumed · Service canceled · Service assigned team changed
* Visit scheduled · Visit date changed · Visit completed · Visit canceled · Visit skipped · Visit skipped or canceled · Visit needs rescheduling · Team arrived at visit · Devices skipped on a visit · Visit team override changed

**Tags & fields**

* Customer tag added · Customer tag removed
* Customer field value added · Customer field value changed · Customer field value cleared

**Staff work**

* Task created · Task completed · Task reopened

**Messages**

* SMS received
* Automation message accepted · Automation message delivered · Automation email bounced · Automation message failed
* Automation email open reported · Automation email link click reported

A few notes:

* **Invoice sent** is for a draft invoice that you then send. **Invoice created and sent at once (no draft)** is for an invoice that goes out the moment it's made. To catch every invoice that reaches a customer, add both as starts.
* **Service scheduled** happens once per service when it's put on the schedule, not once per visit. Resuming a paused service counts too. For every visit, use **Visit scheduled**.
* **A season pause doesn't start Service paused or Service status changed.** A pause for the season is planned, so customers aren't told their service is paused the night their season ends. To act on season pauses, start from **Service paused for the season**.
* **Visit skipped or canceled** is one start for both. Add a condition on **Why this visit was skipped or canceled** to act only for some reasons.
* **Devices skipped on a visit** is for companies that track bait stations and traps: a finished visit left some unchecked.
* **Automation message failed** also happens when the carrier refuses a text outright, for example to a landline.
* **Lead marked lost** happens when a lead who declined an estimate is marked lost.

{% hint style="info" %}
"Open reported" and "click reported" are what the email provider tells us. They are not proof a person read the email. Some mail apps open messages automatically.
{% endhint %}

The event also decides which kind of email the automation sends. That matters for customers who've turned some kinds of email off:

* **Billing:** **Invoices & payments** events, except **Customer autopay setting changed**
* **Service:** **Day before service**, and the **Estimates**, **Services & visits**, and **Staff work** events, and **SMS received**
* **Marketing:** all other events

See [Which kind an automation email is](https://docs.shortcutco.com/readme/finances-invoices-and-payments/customer-email-preferences.md#which-kind-an-automation-email-is).

## Steps

| Group        | Steps                                                                                                                                                                     |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Messages** | **Email**, **Text message**                                                                                                                                               |
| **Timing**   | **Wait**, **Sending window**, **Wait for a date**                                                                                                                         |
| **Actions**  | **Task**, **Notify team**, **Internal note**, **Tag**, **Field**, **Copy into a field**, **Update lead stage**, **Create a job**, **Webhook**, **Stop other automations** |
| **Paths**    | **Branch**, **Wait for a condition**, **Wait for a reply**                                                                                                                |

What each one does, and every setting on it, is on [Steps, message options, and variables](https://docs.shortcutco.com/readme/automations/steps-and-variables.md).

## Older built-in automations

Companies that used Automations before the current editor had a set of built-in automations. They were upgraded in place, kept their names, and start on these:

| Automation              | Starts on                                                                                                                                                                                                 |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New Lead Welcome**    | **Lead created** (or **Customer created**, depending on how it was set up)                                                                                                                                |
| **Proposal Sent**       | **Estimate sent**. Its email and text follow the channels ticked when the estimate is sent. This is what delivers your estimates.                                                                         |
| **Proposal Reminder**   | **Estimate sent**, then a 3-day wait, and it only sends while the estimate is still pending. It came over **stopped**, because the old version never actually sent. Check it and start it if you want it. |
| **Proposal Voided**     | **Estimate voided** or **Estimate expired**                                                                                                                                                               |
| **Job Scheduled**       | **Service scheduled** (once per service, not per visit)                                                                                                                                                   |
| **Job Rescheduled**     | **Visit date changed**                                                                                                                                                                                    |
| **Job Canceled**        | **Visit canceled**                                                                                                                                                                                        |
| **Day-Before Reminder** | **Day before service (grouped per customer)**. If it was on, it owns the grouped day-before reminder.                                                                                                     |
| **Visit Completed**     | **Visit completed**                                                                                                                                                                                       |
| **Invoice Paid**        | **Invoice paid**                                                                                                                                                                                          |
| **Invoice Overdue**     | **When customers match conditions**: invoices past due by the number of days it was set to, with a balance left                                                                                           |
| **Payment Failed**      | **Invoice payment attempt failed**                                                                                                                                                                        |

Automations your team built or copied on the old engine moved over the same way. A few older starts became: *User status change* → **Lead lifecycle stage changed**, *New message* → **SMS received**, *Estimate accepted* / *Estimate rejected* → **Estimate accepted** / **Estimate declined**, *Invoice created* → **Invoice sent** and **Invoice created and sent at once (no draft)**, and *New inquiry from webform* → **Public intake submitted**.

New companies don't get these. They start with **Estimate sent** only, and can add any of the templates above.

<details>

<summary>Still stuck?</summary>

Email **<hello@shortcutco.com>** with the template or automation name and a screenshot.

</details>
