Skip to main content
An automation pack is a named set of automations built to work together: a salon’s Salon Growth System books appointments, cuts no-shows and brings clients back, using several automations that each do one job. You add the whole pack to a channel in one go. Everything arrives paused, so nothing reaches a customer until you have looked at it and switched it on. A pack is a shortcut, not a different kind of automation. What it adds are ordinary automations on your list, published and paused, and from then on they are yours to edit like any other.

​
Find the packs

1

Open the gallery

Go to Automations and select New automation. The Templates picker opens on the Automation packs tab. The other tab, Single automations, is the template library for adding one automation at a time; see Start from a template.
2

Check the channel

A pack is added to the channel you are on, and the picker judges every automation in it against that channel. To add a pack to a different WhatsApp number, Page or account, switch to that channel on the Automations page first.
3

Pick one

Each card shows the pack’s name, what it is for, its first few automations and how many it holds. Search packs matches a pack’s name and summary and the names of the automations inside it, so searching “birthday” finds the pack that sends one. A card marked All added has nothing left to add on this channel.
The Automation packs tab only appears when at least one pack is available on the channel you are on. If your workspace is managed by an agency, you may also see packs your agency made for you, listed first, or only theirs.

​
DMLY’s packs

Open a pack to see exactly which automations it holds today.

​
Preview a pack

Select a card to see What’s inside: every automation in the pack, in the order the pack lists them, with its trigger and a short description. Two small labels may sit beside a name:
  • A.I. agent: the automation answers with an A.I. Reply step.
  • Optional: worth having, but not something to switch on on day one. Unmarked automations are the pack’s core.
On the right of each automation is a pill saying what Add will do with it on this channel. The preview runs the same checks the install does, so the pill is what will happen. Needs setup has two causes, and the amber line tells you which:
  • Something the automation depends on. Needs a service or product to sell before it can go live. The things a pack automation can wait for are a service or product to sell, your working hours, your booking page set up, a payment method connected, at least one contact, and an approved WhatsApp template. Only what is still missing is listed: if you already sell a service, you are not told this needs one.
  • An integration that is not connected, such as your store or a payment provider. The line starts To use this template, and names it.
An A.I. step on its own never makes an automation Needs setup. Without a provider key of your own it answers on the shared A.I., as described in A.I. templates.

​
Add the pack

Select Add 5 automations (the number is however many will be added). When there is nothing new for this channel the button reads Nothing to add on this channel and can’t be selected. You land on your Automations list, narrowed to that pack, with a line saying what happened:
Anything left out is named with the reason, after Skipped:: already on this channel, not available on this channel, not included in your plan, no longer available, or could not be installed. Each automation is added published and paused. Open any of them in the flow builder to change the wording, the tags or the branches before you switch it on.
Already added goes by where an automation came from, not by its name. A pack automation you have renamed is still recognised, so adding the pack again doesn’t add a second copy. An automation you built yourself never blocks the pack’s one, even under the same name: both end up on your list, the pack’s one paused. Two packs that share an automation from DMLY’s library add it only once per channel.
You can add a pack as often as you like, on as many channels as you like: each time, only what is not on that channel yet is added. That also brings back a pack automation you deleted. Adding a pack never changes or replaces an automation that is already there.

​
Work with a pack’s automations

Every automation that came from a pack shows the pack’s name as a small label under its own name in the list. Select the label to narrow the list to that pack. The list then shows Automations from and the pack’s name at the top, with Show all to go back to everything. The status, type and search filters still work inside the pack.

​
Switch on paused

When some of the pack’s automations on this channel are paused, the banner offers Switch on paused with the number in brackets. Select it, read Switch on this pack?, and select Switch on. Each paused automation from the pack goes through the same checks as its own On/off switch in the list: your plan’s cap on active automations per channel, anything it still needs set up, whether it is published, and whether another active automation already answers the same messages. The ones that pass go Active. The ones that don’t stay paused, and the result names them:
followed by each automation that stayed off and the first sentence of why. One refusal never stops the rest. The most common reason is expected rather than a fault. Only one automation can answer every message on a channel, so if you already have a live welcome or catch-all bot, the pack’s own catch-all stays off beside it. Pause one of the two, or give one of them keywords, then switch on the other. See Triggers.
You don’t have to switch the whole pack on at once. Each automation also has its own On/off switch in the list, which runs the same checks. Start with the core automations and add the optional ones later.

​
Steps you fill in yourself

A pack your agency made can include automations they first built for another business. Anything in those that belonged to that business is left blank for you, because only you know which of yours to use: a WhatsApp template, a pipeline stage, a teammate, the service a booking link offers, the product or plan a step sends, a web address it calls. A step that acts on “the appointment” or “the invoice” needs nothing from you: it works on the one the automation is running for. The automation’s row in the list carries an amber Needs setup label; hover it to see each blank, for example the WhatsApp template in the “Send template” step. It stays off until every blank is filled: open it in the flow builder, fill in each named step, and Publish. Publishing the filled-in draft is what clears it. Switching it on before then is refused with <name> needs <what is missing> before it can be switched on. The same amber label appears on any pack automation that is still waiting for something, such as a payment method. For those, the refusal takes you to the page where you set it up.

​
Who can do what

  • Adding a pack needs the Create & edit automations permission (automation.create).
  • Switch on paused needs Activate / publish automations (automation.activate). Without it the button is hidden; the pack can still be added.
See Roles and permissions.

​
Your first pack is added for you

When you connect your first channel, DMLY adds the pack for the business type you chose at sign-up, paused, in the way described above. It happens once per workspace, and unlike adding a pack yourself, it leaves out anything you already have under the same name. If your workspace is managed by an agency, the agency decides which pack you start with, and it may be none. The Get started checklist then asks you to Turn on your starter automations; see Set up your workspace.

​
Changes to a pack don’t reach your copies

Adding a pack copies its automations into your workspace. If the pack is later changed, renamed or withdrawn, the automations you already added stay exactly as they are, and still show the pack’s name. Your edits never change the pack either.

​
What to do next

Publishing and turning on

What the checks at switch-on look for, and how to clear them.

Flow builder

Edit an automation the pack added.

Start from a template

Add a single automation instead of a whole pack.

Triggers

Why only one automation answers a given message.