The structure most people land on is a recurring job for the visits, a tag or custom field for the plan, and the renewal date typed in somewhere. That part works fine. The problem is none of those three talk to each other, so nothing tells you when something is about to go wrong.
D_LHerbier's second point is the one nobody answered and I think it's the bigger one. If the visit is scheduled a year out, the schedule is never going to remind you in time to actually reach the customer and move it. The reminder has to fire weeks ahead of the visit, not at it.
Renewals have the same shape. Once the agreement has lapsed it is too late to sell the renewal and you are just having an awkward conversation about price instead.
And if an agreement includes more than one visit a year, how many have been used versus how many are left is not something Jobber will surface for you. That is usually where the money goes. Somebody pays for four, takes two, and renews anyway. Or takes six and nobody notices.
For what it's worth I don't run a service business, I build integrations, so weigh the operator side of this accordingly. Those are just the three things that kept coming up when I looked at how people track this.
