This map is part of the workforce schedule exceptions guide, which covers the renewal inventory. It answers a narrower question: where each record lives and how they join.
Five systems, one exception day
A schedule exception rarely lives in one tool. The plan is in the WFM platform. The demand that broke it is in the telephony or contact platform. The cause is in ticketing. The money and hours are in HR and payroll. And in many operations, the approval itself happened in team chat or email.
Each system counts differently. WFM counts by interval and queue; telephony counts by contact; ticketing counts by ticket and tag; payroll counts by employee and pay period. The joins are therefore not one shared ID but a combination: time plus queue plus a ticket reference plus an employee identifier.
The system map
| System | Record | Linking key | Owner |
|---|---|---|---|
| WFM platform | Published forecast and intraday reforecast versions | Queue or workstream name, interval start, publish time | WFM team |
| WFM platform | Schedule change requests and overrides | Interval, queue, reason code, approver, ticket number in the note | Workforce director |
| WFM platform | Adherence and service level by interval | Interval, queue, published schedule version | Customer operations |
| Telephony or contact platform | Contact records with queue and timestamps | Contact ID, initial contact ID, queue, timestamp | Telephony administrator |
| Ticketing system | Incident and release tickets, tags | Ticket number, created timestamp, tag | Product and support |
| HR and payroll | Overtime approvals and adjusted time cards | Employee ID, date, approver | HR |
| Team chat or email | Informal approvals and context | Timestamp, channel, ticket number if quoted | Varies; often nobody |
Two rows do the hardest work. The override row carries the reason and the approver, which are what make the record a decision. The contact record row supplies the actual demand: in Amazon Connect, for example, a transferred call creates a new contact record that points to the previous one and to the initial contact, so demand can be counted once per customer rather than once per leg.
Amazon ConnectWhere each linking key breaks
Every key above has a known failure mode, and most of them happen quietly during renewals and reorganizations.
- Time. Interval start in WFM, created timestamps elsewhere. Time zones and daylight saving shifts move one side by an hour. Ask which zone each system stores.
- Queue. Queues get renamed, merged and split. Zendesk documents that historical WFM report data reflects the configuration active when it was recorded, so a renamed workstream appears as a break in history rather than a correction.
- Schedule. Zendesk also documents that WFM schedules do not sync automatically with Zendesk schedules or business hours. Two systems can each hold a "schedule" that disagrees.
- Plan version. Adherence is calculated against the published schedule (Amazon Connect documents this). If only the latest version survives, old adherence figures lose their reference point.
- Reason. An override note that says "spike" with no ticket number cannot be joined to its cause.
- Authority. Approvals given in chat never reach the schedule change record.
ZendeskThe same issue shows up in manufacturing, where a production schedule change log needs its reason codes and versions kept for the same reasons.
One joined case: the 10:20 override (Illustrative)
Fictional and invented for this page. The 410-person support operation from the worked firmware release case cancels a training block for 14 agents at 10:20 after a release at 10:05. Here is what a fully joined record of that single decision looks like, field by field.
| Link | System | Field value (Illustrative) |
|---|---|---|
| Cause | Ticketing | Incident ticket opened 10:11, tag "firmware", linked to release ticket |
| Plan before | WFM | Forecast version published 06:00: 125 calls for the 10:30 interval, voice queue |
| Plan after | WFM | Reforecast version published 10:18: 340 calls for the same interval |
| Decision | WFM | Schedule change 10:20: training block canceled for 14 agents, reason code "volume event", note cites the incident ticket |
| Authority | WFM | Approved by the workforce manager at 10:21 |
| Demand | Telephony | 365 contacts offered in the 10:30 interval on the voice queue, counted by initial contact |
| Hours | HR and payroll | No overtime; training hours recoded as phone time on 14 time cards |
| Outcome | WFM | Service level 31% at 10:30, 44% at 11:00 after a second action |
Read down the right-hand column. Every row shares the same interval and queue, and the cause, decision and authority rows share the ticket number. That is what "fully joined" means. Remove the ticket reference from the note and the decision loses its reason; overwrite the 06:00 forecast and the gap that triggered it disappears.
Testing the map with the WFM manager, at metadata level
A partner can test each link in one conversation without seeing any record. Ask, and write down yes, partly or no:
- Which time zone does each system store, and has it changed?
- Have queues or workstreams been renamed or merged, and when?
- Do override notes cite a ticket number, and since which year?
- Is the approver recorded on schedule changes, or only in chat or email?
- Are earlier forecast and schedule versions kept, or replaced?
- How many years does each system hold, and which ones change at the next renewal?
The answers go into the referral brief template. Never ask for exports, screenshots or logins. Contact center advisors may also find the telephony side covered in call transfer recovery, and closures or sales of a center in call center closing and selling a call center business.
Qualification and unknowns. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Whether the joins hold in practice, what employee data must be removed, buyer interest and any offer stay unknown until SourceX reviews the opportunity. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application. More record types are on the industries hub.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the WFM manager answers yes to most of the six questions and the history spans several years, register as a partner, check the company against who qualifies and read the program terms before you introduce the workforce director.