Summary: ◀▼
You can import existing schedules using a CSV template that requires exact agent name and email matches. Imported schedules overwrite shifts starting the same day but don't remove overlapping overnight shifts or existing time off. You can also export schedules by selecting date ranges and agents, receiving the export via email. Ensure schedules exist for the chosen date range to avoid empty exports.
You can import existing schedules into Zendesk Workforce Management (WFM) from a CSV file. This helps you move schedule data from another system or update schedules for multiple agents at once.
You can also export schedules as a CSV file. Use the exported file to review schedule data, make bulk updates, or save a copy of your schedules.
This article contains the following topics:
About importing schedules
You can import a schedule in two ways: use a simplified import to define the intraday variant and WFM generates intraday tasks based on the forecast, or use an advanced import to define each task manually.
Using a simplified import (recommended)
With a simplified import, you specify each agent's working time and the intraday variant that applies to their shift. WFM generates the shift from the selected intraday variant and its configured tasks. The start time in the CSV determines when the shift begins.
When you select this option, two template files can be downloaded:
- The intraday field keys, that contains the list of all your locations, shift names, intraday variant names, and intraday variant IDs.
- The simplified import template, that contains an example of how your CSV should be formatted.
Use the Intraday field keys to complete the simplified import template. See example below.
| Location | Shift Name | Intraday Variant Name | Intraday Variant ID |
| Lisbon | Automatic shift1 | Morning shift | 01234567-c4e1-4eb1-56gt09-fr45609kiuo |
Then upload the Simplified import CSV file. See example below.
| agentName | agentEmail | intradayVariantName | intradayVariantId | startTime | timeZone | date | endDate |
| Anna Noah | a.noah@myemail.com | P1 | 01234567-c4e1-4eb1-56gt09-fr45609kiuo | 09:00 | Europe/Warsaw | 2025-12-31 | 2026-01-31 |
The following table lists the fields to include in the Simplified import CSV file. The first row of the CSV file must be the header row and must match the template exactly.
| Field | Requirement | Description |
agentName |
Optional | For reference only. |
agentEmail |
Required | The agent's email address. |
intradayVariantName |
Optional | For reference only. |
intradayVariantId |
Required | The ID of the intraday variant to apply. |
startTime |
Required | The shift start time. |
timeZone |
Optional | The shift time zone. If blank, WFM uses the time zone of the agent's shift
location. If provided, use a standard format such as UTC+01:00 or
GMT-02:00. |
date |
Required | The shift start date in YYYY-MM-DD format. |
endDate |
Optional | The final date in the shift date range. WFM creates a shift at the specified
start time for each day from date through
endDate. If blank, WFM creates a shift only on the date in the
date field. |
Using an advanced import
With an advanced import, you import a schedule by manually defining each task.
When you select this option, two template files can be downloaded:
- The Intraday field keys contain a list of all your tasks and their IDs,
including:
- Workstreams
-
General tasks or unified agent statuses (both listed as
generalTask) - Time off
- The Advanced import template, that contains an example of how your CSV should be formatted.
Use the Intraday field keys to complete the Advanced import template. See example below.
| agentName | agentEmail | taskType | taskId | taskName | timeOffType | startTime | endTime |
| Anna Noah | a.noah@myemail.com | generalTask | 303733 | Lunch | 2025-06-20T16:45:00+02:00 | 2025-06-20T17:45:00+02:00 |
The following table lists the fields to include in the Advanced import CSV file. The first row of the CSV file must be the header row and must match the template exactly.
| Field | Requirement | Description |
agentName |
Optional | The agent's name. This field is for reference only. |
agentEmail |
Required | The agent's email address. |
taskType |
Required | The type of scheduled task. Supported values are
workstream, generalTask, and
timeOff. |
taskId |
Required for workstreams and general tasks | The unique ID of the workstream or general task. |
taskName |
Optional | The workstream, general task, or time-off type name. This field is for reference only. |
timeOffType |
Required for time-off tasks | The time-off type to apply when taskType is
timeOff. Leave this field blank for workstreams and general tasks. |
startTime |
Required | The task start date and time in ISO 8601 format, including the time zone offset. |
endTime |
Required | The task end date and time in ISO 8601 format, including the time zone offset. |
Shifts remain unpublished after import. To publish them, see Publishing the schedule.
Note the following key information before you import a schedule:
- WFM removes all shifts that start within the imported date range for each agent to prevent duplicates. All shifts are overwritten if they start on the same day UTC.
- WFM doesn't overwrite imported time off when you import a schedule, which can result in two or more layers of time off in the same period.
- If overnight shifts overlap, the import doesn’t delete the previous day’s schedule and might create overlapping shifts.
-
TimeOffTypeaccepts onlyfull-dayandpartialvalues. - When completing the Import template, ensure that the agents' names and email addresses match exactly in Zendesk WFM. All fields are case-sensitive and each agent must be active. To ensure accuracy, consider exporting your current list of agents.
- When multiple CSV rows define shifts for the same agent on overlapping
dates, later rows in the CSV override earlier rows.
For example, if the CSV includes:
- January 1 to 10: Template 2
- January 2 to 4: Template 4
- January 1 to 2: Template 3
The resulting schedule is:- January 1 to 2: Template 3
- January 3 to 4: Template 4
- January 5 to 10: Template 2
- The imported CSV file size limit is 5 MB.
- You can import schedules up to two years in the future and up to 30 days in the past.
- The CSV shift start time applies to each day in the selected date range. The intraday template, referenced by ID, provides only the shift duration and task configuration. WFM ignores the intraday template’s start time and uses the CSV value instead.
- The agent and intraday variant must belong to the same location.
Importing a schedule
Importing a schedule permanently replaces the existing schedule. Make sure your CSV files use the same structure as the template files.
To import a schedule
- In Workforce management, click
Scheduling in the sidebar, then select Schedule. - Click the CSV icon.
- Select Import schedule.
- Select an import method:
- Upload your CSV file.
- Click Import schedule.
Once uploaded, your file is validated and processed in the background. You'll receive a notification confirming whether the import succeeded or failed. If validation fails, WFM rejects the file and highlights specific row-level errors so you can fix them and re-upload.
Exporting a schedule
Make sure the date range you export includes a draft or published schedule. If no schedule is entered or published, the export contains no data for the selected date range and users.
To export a schedule
- In Workforce management, click
Scheduling in the sidebar, then select Schedule. - Click the CSV icon.
- Select Export Schedule.
- Select whether to export the Published schedule or Draft version.
- Select a Date range.
- Click the Agents tab, then select the agents whose schedule you want to export.
- Click Export schedule.
When the export is complete, WFM sends the file to your email address.