The simplest way is a recurring weekly invoice in GoHighLevel for every client on a fixed plan, a Payment Received trigger that tags each client Paid, and reminders that go only to clients without the tag. The bottom line: Friday billing runs on a schedule, and the follow up runs on the tag, so you chase only the clients who have not paid.
What dog walkers put in their policies
Published policies from small businesses show the range. One requires payment for regular services in advance of the scheduled walks and a deposit or full payment 24 hours ahead for one time walks, and does not confirm a service until payment arrives. Another bills at the end of each week, Friday to Sunday, with a $30 late fee for every seven days overdue and $20 for three days late, and payment by Venmo, Zelle, or PayPal. A third sends invoices on Mondays for the previous week, with payment expected by the end of that week. A 24 hour cancellation rule is common. Your policy sets the schedule, so write it before you build.
Two billing styles
| Style | How |
|---|---|
| Same walks every week | Recurring invoice from a template, sent every Friday |
| Walks vary by week | Create each week's invoice from your walk log, then let the reminders run on the tag |
The recurring invoice action bills from a template, so it fits fixed plans best. Confirm in your account how to handle weekly amounts that change.
Build it in GoHighLevel
- Connect Stripe, create invoice templates for your plans, and add each client with a card on file after a first paid invoice.
- Build a workflow that starts the Send Recurring Invoice action on a weekly schedule, sent on Friday.
- Build a workflow with the Payment Received trigger that adds the tag Paid this week and removes the tag Unpaid.
- Build a Saturday workflow that adds the tag Unpaid to every client, sends a friendly reminder to clients who do not have the Paid tag, and waits.
- Add a Monday reminder that includes your late fee policy, and a task to call anyone still unpaid on Tuesday.
- Build a Payment Failed workflow that texts a link to update the card.
GoHighLevel's help page on recurring invoices says the Send Recurring Invoice workflow action needs an invoice template created under Payments, then Invoices, and a gateway connected under Payments, then Integrations. It says the action is currently supported for Stripe connected sub accounts, that card details are stored only after the first invoice is paid manually, that a Payment Failed trigger can retry and notify the customer, and that conditional branches can send different templates by contact attributes. The Payment Received trigger page says it fires for payments from forms, manual payments, memberships, Text2Pay links, and subscription charges.
A third party setup guide describes Text2Pay as a payment icon in the message composer: you pick a product or enter an amount, and the contact receives a secure Stripe checkout link. The same guide lists separate triggers for invoice sent, viewed, paid, and partially paid, and for payment failed events. Confirm the exact trigger names in your workflow builder.
What the workload looks like
For example, 80 clients billed every Friday is 80 invoices a week, or about 4,160 a year (80 times 52). If 10 percent pay late, that is 8 reminders a week (80 times 0.1), and the tag keeps the other 72 from getting any.
Mistakes to avoid
- Reminding clients who already paid. Use the Paid tag.
- A late fee that is not in the client contract. State it up front.
- Billing after the walks with no card on file. Collect payment in advance where you can.
- Forgetting sales tax rules. Some states tax pet care.
How this was handled before
Dog walkers collected cash, checks, and Venmo, and kept a spreadsheet of who owed what. That works for 15 clients and breaks at 80. A scheduled invoice and a paid tag replace the spreadsheet, and reminders reach only the people who owe.
What to measure after launch
Track percent paid by Saturday, percent paid by Tuesday, and total overdue dollars each Monday. If the Saturday number is low, move the invoice earlier or collect payment in advance for new clients.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Clients often want reminders by text, so ask which number to use for billing. This is general information, not legal advice.
Questions people ask
Can I bill 80 clients with one workflow?
Yes, for fixed plans, using the Send Recurring Invoice action on a weekly schedule.
How do I avoid reminding clients who paid?
Tag them Paid when the Payment Received trigger fires, and send reminders only to clients without the tag.
What late fees do dog walkers use?
One published contract charges $30 for every seven days overdue and $20 for three days late. Use your own policy.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.