Copy a Week's Schedule into Zenoti
Availability: AI Employee Scheduler is in Beta. Your center is enrolled automatically by Zenoti β there is no separate join or enable step required.
After you have reviewed the suggested schedule in the Schedule Grid and are satisfied with the recommendations, use Copy all to write the week's shifts into the live Zenoti schedule. This is the only way AI Scheduling changes the live schedule β nothing reaches the live schedule until you initiate Copy all.
Audience: Managers who review and publish provider schedules for their center.
Before you begin
- Your center must be enrolled in AI Employee Scheduler (Beta).
- The suggested schedule for the week must exist and must not require regeneration. If settings or scheduling rules have changed since the schedule was generated, Copy all is replaced by Regenerate β run a recompute first.
- Any user who can edit the employee schedule can use Copy all. No separate permission is required for AI Scheduling.
- Review all suggested changes in the Schedule Grid before copying. After a successful copy, the week becomes read-only in AI Scheduling.
Steps
Open the Schedule Grid for the week
- In the Zenoti toolbar, select AI Scheduling.
- On the Demand based Scheduling page, confirm that the correct calendar week is selected. To switch weeks, see Review scheduling runs by calendar week.
- Review the Schedule Grid. Confirm that each provider row shows the recommended changes you expect. To make edits before copying, see Manage the suggested schedule.
Copy the week into Zenoti
In the Schedule Grid rail, select Copy all.
Note: If the rail shows Regenerate instead of Copy all, the displayed schedule was generated using settings or rules that have since changed. The label shown is "Regenerate first - shown schedule uses old settings". Run a recompute before copying. See Run an on-demand recompute.
In the confirmation dialog, read the message:
This will write this week's approved schedule into Zenoti. Existing shifts will be updated in place.
Confirm the dialog β labeled Approve and copy to the main schedule? β to start the copy.
Wait for the result message. A successful copy reports: "Approved {n} shift change(s) into Zenoti." where n is the number of shift changes written.
Worked example: A manager reviews a six-provider week. After confirming the dialog, the system reports "Approved 14 shift change(s) into Zenoti." Four rows show In Zenoti, one shows Skipped, and one shows Not applied with the reason "split shift not supported yet (retry may help)". The manager navigates to the Employee schedule to add that provider's two shifts manually.
Understand each provider's copy outcome
After the copy completes, each provider row in the Schedule Grid shows one of the following outcome labels:
| Label | Meaning |
|---|---|
| In Zenoti | The shift was written to the live schedule successfully. |
| Removed | A shift that previously existed was removed from the live schedule. |
| Skipped | No action was needed for this provider; the row was not changed. |
| Changed | The provider's shift was edited after it was last approved, so the copy reflects the edited version. |
| Not applied | The shift could not be written. See the reason shown on the row. |
If one or more rows were not applied, the rail summarizes the partial result as:
{approved} approved, {notApplied} not applied - review
Handle rows that were not applied
When a row shows Not applied, the row also displays a specific reason. Reasons fall into two categories:
Retry may help β The issue may be transient. You can attempt to copy again after addressing the underlying condition.
| Reason | What to do |
|---|---|
| Missing schedule ID | Verify the provider exists and has a valid schedule record in Zenoti, then retry. |
| Unresolved times | Check the provider's shift times in the suggested schedule for conflicts, then retry. |
Cannot be applied β The row cannot be written by Copy all. Make the change directly in the Employee schedule instead.
| Reason | What to do |
|---|---|
| Split shift not supported yet | See Split shifts β what cannot be copied below. Add the provider's shifts manually in the Employee schedule. |
| Nothing to remove | The shift AI Scheduling intended to remove was not found in the live schedule. No action is needed. |
| Dropped shift left unchanged | A shift that was dropped from the suggestion could not be removed automatically. Remove it manually in the Employee schedule. |
Split shifts β what cannot be copied
Split shifts are not supported by Copy all yet.
When a provider has two shifts on the same day, Copy all reports that row with the reason "split shift not supported yet". The row is marked (retry may help) β however, until split shift support is added to Copy all, the reliable path is to add that day's shifts directly in the Employee schedule.
Understand error states
If Zenoti rejects the entire copy before writing any shifts, the Schedule Grid rail shows:
Zenoti rejected the schedule (nothing was written).
No shifts were changed. Review the Schedule Grid for data issues and try again, or make corrections in the Employee schedule.
If the copy starts but does not finish, the rail shows:
Zenoti passed the check but the write did not complete (some rows may not be saved).
In this case, check each provider row for its outcome label. Rows that show In Zenoti were saved; rows without that label may not have been written. Verify the affected rows in the Employee schedule and correct any missing shifts manually.
After a successful copy
Once the copy completes, the week is read-only in AI Scheduling. The Schedule Grid displays:
This week was copied to Zenoti {when} and is read-only. Changes are no longer possible here.
The rail also shows:
This week is already copied to Zenoti.
Any further changes to that week's shifts must be made directly in the Employee schedule in Zenoti.
Important: AI Scheduling does not contact providers about new or changed shifts. After copying, it is your responsibility to notify affected providers of any schedule changes.
Tips
- Review all Not applied rows immediately after copying. A partial copy is summarized in the rail β do not assume all rows were written successfully.
- For any provider with a split shift on a given day, plan to add both shifts manually in the Employee schedule. Split shifts are not supported by Copy all yet, and waiting will leave that provider without a schedule for the day.
- If the Schedule Grid rail shows Regenerate instead of Copy all, do not try to work around it β regenerate the schedule first so that the copy reflects your current settings and rules.
- Check the week's day-level coverage summary before copying. Days marked with an unresolved coverage state may benefit from a manual edit before you commit the week to Zenoti. See Review the day-level coverage summary.
- The copy is the final step of your weekly scheduling workflow. Once complete, the week is locked in AI Scheduling, so make sure you have reviewed and edited all provider rows first. See Manager review for the full review checklist.
Troubleshooting
The Copy all button is not visible β I see Regenerate instead.
Settings or scheduling rules changed after the displayed schedule was generated. The rail shows "Regenerate first - shown schedule uses old settings". Run an on-demand recompute to generate a new schedule against your current settings, then Copy all will become available. See Run an on-demand recompute.
The copy completed but several rows show "Not applied".
Check the reason shown on each Not applied row. Rows marked "(retry may help)" may succeed on a second attempt after you address the stated condition. Rows marked "(cannot be applied)" β including any row with the "split shift not supported yet" reason β must be resolved manually in the Employee schedule. The rail summarizes the partial result as "{approved} approved, {notApplied} not applied - review".
The Schedule Grid shows "Zenoti rejected the schedule (nothing was written)."
The entire copy was rejected before any shifts were written. Nothing in the live schedule changed. Review the provider rows for data issues such as unresolved times or missing schedule IDs, make corrections, and try Copy all again. If the issue persists, make the affected changes directly in the Employee schedule and submit in-product feedback. See Send in-product feedback.
The Schedule Grid shows "Zenoti passed the check but the write did not complete (some rows may not be saved)."
The copy started but did not finish. Some rows may have been written and others may not. Check each provider row for its outcome label β In Zenoti confirms a row was saved. For any row without that label, verify the shift in the Employee schedule and add it manually if it is missing.
The week is showing as read-only but I need to make a change.
Once a week is copied to Zenoti, it is read-only in AI Scheduling. The rail shows "This week was copied to Zenoti {when} and is read-only. Changes are no longer possible here." All further edits to that week must be made directly in the Employee schedule in Zenoti.