Question 1

What is pool service automation?

Accepted Answer

Pool service automation is software that carries out the routine follow-up around a service route without anyone remembering to do it: the text after a completed stop, the review request, the receipt when an invoice is paid, the second attempt at a quote that went quiet. In Pool Runs this is called Workflows. You choose an event that happens in your business, stack up the steps that should follow it, and the system runs them for every customer it applies to.

Question 2

Do I need Zapier or another automation tool for this?

Accepted Answer

No. That is the main difference. General automation platforms are built to connect separate apps, so before you can write a single message you are choosing connectors, mapping fields, and maintaining webhooks. Pool Runs workflows start from events that already exist inside your account: a work order is completed, an invoice is paid, a lead submits a form, a customer texts back. There is nothing to connect because the data was never in a different system.

Question 3

What can trigger a workflow?

Accepted Answer

Nine events: work order completed, invoice paid, form submitted, chat started, customer replied, contact created, tag added, pipeline stage changed, and opportunity won. You can also enroll people directly, either one at a time or in bulk from a filtered list, which is how seasonal campaigns usually start.

Question 4

Will it text my customers at eleven at night?

Accepted Answer

Not unless you tell it to. Each workflow has a send window: the hours and the days of the week when outbound messages are allowed. If a step comes due outside that window the message is held and queued for the next time the window opens. The window is evaluated in the customer's own timezone when Pool Runs knows it, which matters if your route crosses a timezone line.

Question 5

What happens when a customer replies or opts out?

Accepted Answer

A workflow can be set to stop the moment a contact replies, so nobody gets an automated nudge after they have already answered you. You can also use a Wait for reply step, which pauses the sequence until they respond or a timeout you set elapses. If a customer texts STOP they are opted out, and the engine checks that status before every send, so no workflow can message them again.

Question 6

Can I try a workflow before turning it on?

Accepted Answer

Yes, and it is worth doing. Every template installs as a draft, and there is a test run that executes the whole workflow against a single contact and shows you the result of each step in order. Be aware that a test run is a real run: the texts and emails actually send to that contact, so use your own number.

Question 7

Can I put my existing customer list into a workflow?

Accepted Answer

Yes. Bulk enrollment lets you pick an audience by customer status and tags, or by a saved Smart List, and shows a live count of how many people match before you commit. Anyone already enrolled in that workflow is skipped rather than double-messaged. A single bulk enrollment is capped at 5,000 contacts, so a very large list needs to be narrowed or run in passes.

Question 8

Can I stagger a big campaign so it does not all send at once?

Accepted Answer

Yes. Turn on drip pacing and set a batch size and an interval, for example fifty contacts every fifteen minutes, and Pool Runs tells you roughly when the last batch will go out. This keeps a winterization blast from putting three hundred replies into your inbox inside one minute.

Question 9

How do I know a workflow is actually working?

Accepted Answer

The builder has a Stats view that puts a run count on every step, so you can see how many contacts reached each one and where they stopped. Alongside it there is an execution history listing each contact and each step with its outcome: succeeded, skipped, or failed. If a template is sending but not converting, the drop-off is usually visible at a specific node.

Question 10

Is Workflows part of the standard Pool Runs plan?

Accepted Answer

No. Workflows is part of the Engage add-on at $50/month, which also covers sales pipelines, lead capture forms, the self-booking page, the website chat widget and review requests. Engage comes with its own dedicated number, two-way texting and unified inbox, plus 1,000 text segments a month, so the workflows have somewhere to send from without a second add-on. If you also want the AI Voice Agent answering your calls, add Communications and the two are $80/month together on top of your base plan.

Pool Service Automation With Nothing to Connect

General automation tools have never heard of a work order

Sixteen steps, and none of them are “call an API”

A commercial lead should not get the residential text

Nine automations, already written for a pool office

New lead instant response

Quote follow-up nurture

Review request after service

Review request with reminders

Welcome new customer

Win back lapsed customers

Seasonal winterization campaign

Payment thank-you

Text reminder opt-in

Automated texting goes wrong in predictable ways

Send windows in the customer's timezone

STOP is honored everywhere

Review requests are throttled

Everything starts as a draft

Test against a real contact

Per-step counts and full history

Put your winterize list into a workflow in one pass

Workflow Automation FAQ

Why pool companies get stuck automating follow-up

Workflows Run on the Rest of Pool Runs

Customer Management

Invoicing

Lead Generation

Further reading

Stop Remembering the Follow-Up