01 / The problem
What was getting in the way
We create recurring service plans in Zoho FSM because that is where the schedule, service details, and billing setup belong. But Zoho can miss the first visits when a new plan starts inside its scheduling window.
Someone had to calculate those missing visits and create them by hand. The work was easy to miss, hard to review, and risky to retry because a second attempt could create duplicate or partial records.
A missing visit can let down a customer and cause scheduling or payroll problems. A careless repair can be just as harmful if it creates the same work twice.
02 / Our approach
The decisions we made first
My roleI decided that Zoho should continue to own the recurring plan. We focused on the one gap Zoho did not solve and built a preview-first repair process with confirmation, duplicate checks, and clear results.
Keep the recurring plan in Zoho
We rejected the idea of rebuilding scheduled maintenance in Whiteboard. Operators still create the recurring plan in Zoho, where the service and billing setup belongs.
Show the repair before creating anything
We calculate the missing dates and show the operator exactly what we plan to create before changing any work order or appointment.
Make retries safe and reviewable
We identify each planned visit, check earlier repair attempts, look for existing records, and verify the result so a retry does not depend on memory.
03 / What we built
How the solution came together
Start with the real plan
We read the schedule pattern, timing rules, service template, and related setup from the existing Zoho recurring plan.
Find only the missing visits
Date rules identify which early visits Zoho will not generate and where Zoho's normal recurring schedule will take over.
Create only what was approved
Before writing, we recalculate the preview and check earlier runs and existing appointments. We create only the visits the operator approved.
Check the result in Zoho
After creation, we read Zoho again and record whether the repair is complete or still needs an operator's attention.
04 / How it works
The process from start to finish
-
01
Create plan
The operator creates the recurring service plan in Zoho FSM.
-
02
Find the gap
We calculate which early visits Zoho will not generate.
-
03
Review
The operator checks the dates, warnings, and possible duplicates.
-
04
Repair
We create only the confirmed missing work orders and appointments.
-
05
Verify
We record the results and check the new records in Zoho.
We may use AI to help investigate or explain a problem. Fixed rules control the expected dates, repair scope, duplicate checks, and record creation.
05 / The result
What improved
Business value
- We created a repeatable way to repair missing recurring visits.
- We reduced the need to calculate and monitor early visits by hand.
- We kept Zoho as the official source for the recurring service plan.
- We made duplicate checks and partial-result review part of the normal process.
Safeguards we kept
- Zoho remains the official source for the recurring plan.
- We recalculate the preview before creating records.
- We detect changed requests and stale previews.
- We skip visits that already exist or were already repaired.
- The operator confirms the proposed repair before creation.
- We keep failures and warnings visible for follow-up.
What this demonstrates
Commercial judgment backed by operating depth.
Capabilities
- Operational problem solving
- Customer implementation
- Reliable workflows
- Exception management
- Operator-friendly controls
- Connected process design
Systems used
- Zoho FSM
- PostgreSQL
- Employee OS
- Scheduled functions
- Zoho Cliq