PR-4105 · Live
Member Sync
When the Membership Coordinator suspends, cancels, or reactivates a membership, Member Sync handles the schedule side of that decision. It finds the visits already on the books for that customer and brings them into agreement with the new status. It cancels the upcoming visits when a membership is paused or ended, rebuilds them when it comes back, and creates the first block when someone new signs up. On every job it touches, it writes the same cancel reason, memo, and tags the office already uses, so dispatch and billing see a clean picture. The Coordinator gets a short summary of what changed and goes back to the work that needs a person.
The promise
When a membership's status changes, the schedule stays correct on its own. The forward visits are cancelled or rebuilt to match. The reasons and tags are written the way the office expects, and the dispatch board stays accurate, all without the Coordinator opening each job by hand. The minutes that used to go to cleanup go to the customers who actually need a call.
How it works
The path from input to value.
- 01
Watches the membership book
Member Sync watches the field service management system for membership status changes, new sign-ups, and recurring-service edits.
- 02
Holds for a moment, then gathers the visits
When a membership changes, it waits a short buffer the Coordinator sets so a mistaken edit can be undone, then gathers the upcoming visits tied to that membership.
- 03
Brings the schedule into agreement
It cancels the upcoming visits when a membership is paused or ended, rebuilds them when it comes back, and creates the first block for a new sign-up. On each one, it writes the matching reason, memo, and tags.
- 04
Shows what changed
It posts a short summary of every change for the Coordinator to review and sends anything it could not finish to an exceptions list.
The day before. The day after.
Same moments. Lived differently.
A customer cancels their plan. The Coordinator changes the status, then opens each upcoming visit one by one to cancel it, type the reason and memo, and add the tags dispatch filters on.
9:00 AMA customer cancels their plan. The Coordinator changes the status and moves on. Member Sync cancels the upcoming visits, writes the reason, memo, and tags, and posts a short summary of what changed.
9:00 AMBefore
A customer cancels their plan. The Coordinator changes the status, then opens each upcoming visit one by one to cancel it, type the reason and memo, and add the tags dispatch filters on.
After
A customer cancels their plan. The Coordinator changes the status and moves on. Member Sync cancels the upcoming visits, writes the reason, memo, and tags, and posts a short summary of what changed.
A paused member reactivates. Now the Coordinator has to rebuild the visits they cancelled weeks ago, recreating each one from the plan template by hand.
11:30 AMA paused member reactivates. The forward visits rebuild from the plan template on their own. The Coordinator checks the summary and keeps going.
11:30 AMBefore
A paused member reactivates. Now the Coordinator has to rebuild the visits they cancelled weeks ago, recreating each one from the plan template by hand.
After
A paused member reactivates. The forward visits rebuild from the plan template on their own. The Coordinator checks the summary and keeps going.
A technician calls in from a driveway. The customer paused last month, but the visit was never cleared off the board. The Coordinator apologizes to the customer and reroutes the tech.
2:15 PMNo driveway call comes in. The visits for paused customers came off the board when the status changed, so no technician is sent to an inactive account.
2:15 PMBefore
A technician calls in from a driveway. The customer paused last month, but the visit was never cleared off the board. The Coordinator apologizes to the customer and reroutes the tech.
After
No driveway call comes in. The visits for paused customers came off the board when the status changed, so no technician is sent to an inactive account.
They set aside time for the weekly reconciliation pass, combing the board for visits that no longer match a membership's status.
4:45 PMThere is no reconciliation pass to run. The board already matches the membership book, and the time goes to the customers who need a call.
4:45 PMBefore
They set aside time for the weekly reconciliation pass, combing the board for visits that no longer match a membership's status.
After
There is no reconciliation pass to run. The board already matches the membership book, and the time goes to the customers who need a call.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Does not optimize routes, plan drive time, or assign technicians by skill or zone.
- ×Does not handle membership renewals or win-back outreach.
- ×Does not score accounts for churn risk or run retention offers.
- ×Does not text or email the end customer about a cancelled or rescheduled visit.
- ×Does not run membership billing; it writes a tag the office can filter on.