WeavrCRMAgree on the service before the interval
Define the maintenance scope, eligible condition, vehicle, location, and pricing basis. Then choose an interval that suits the customer's use and the service outcome.
Do not imply that a maintenance visit includes unlimited recovery work. Explain how a vehicle that falls outside the agreed condition will be assessed and quoted.
Related resource: Design a Detailing Maintenance Plan Customers Understand
Document the series defaults
Have any subscription, automatic renewal, or advance-payment terms reviewed professionally before selling them. A repeating calendar entry is not automatically a subscription contract.
Customer and vehicle: Normal service and price basis: Visit interval and preferred window: Location and access: Start date and review date: Rescheduling process: Payment arrangement: How either party changes or ends the arrangement:
Related resource: A Weather Rescheduling Process for Mobile Detailers
Separate one-visit changes from series changes
If the customer postpones next Tuesday, decide whether only that visit moves or the whole pattern changes. If an add-on is sold once, do not silently add it to every future appointment.
When changing the series, preserve completed history. A future default should not rewrite what was performed or paid on earlier visits.
Related resource: Create a Clear Detailing Deposit Policy
Keep billing deliberate
A recurring job does not necessarily mean the customer is invoiced through WeavrCRM. Platform invoicing must be explicitly enabled on the appointment or series, with the required business Stripe setup.
Confirm the customer-facing payment arrangement separately. Do not describe a generated invoice or link as a completed payment, and do not imply automatic recurring card charges unless that specific payment arrangement exists.
Review whether the pattern still works
A useful recurring system reduces repeated decisions while retaining a clear exception path. It should not become a calendar full of stale assumptions.
- Are access and timing reliable?
- Has vehicle use changed?
- Is the purchased scope still appropriate?
- Do actual durations fit the route or bay?
- Does the customer understand upcoming commitments?
The practical takeaway
Use series defaults for consistency and occurrence-level decisions for real-world exceptions.
Explore the relevant WeavrCRM workflow · Review integrations and requirements