Recurring service

Recurring service is work that repeats on a rhythm the customer agreed to: a cleaner every other week, a lawn route, a maintenance membership, a pest visit each quarter. The sale is not one job. The sale is the next visit still happening, and the one after that. Losing a recurring customer quietly is more expensive than losing a one-off quote, because the future visits disappear with them.

The record has to know the rhythm. Frequency, the last visit, and the next one belong on the customer, not in a tech's memory. When someone cancels, the reason belongs there too, in a sentence, so you can see whether you are losing people over quality, schedule, or silence. A list of "active" with no next date is how routes decay. You discover the gap when the customer calls to ask why nobody came.

Recurring work still starts as a lead. The first call, the missed call, and the form are the same top of the funnel as a one-time repair. A CRM earns its place by getting that first yes onto a schedule you will actually run. The route itself, stop order, and chemical tracking may live in a dedicated tool. Puffly does not build routes. It holds the customer, the agreement to come back, and the task to confirm the next visit.

Confirmation is the unglamorous part. A text before the visit cuts no-access stops and "I forgot you were coming" complaints. One message, with the day and a way to reschedule, is enough. Do not turn the reminder into a newsletter.

Invoice the agreement from whatever tool you already use. Review the list of recurring customers monthly: who is overdue for a visit, who has gone quiet, who just finished a visit and should be asked for a review. That review of the list is the business. The software only makes the list true.