An internal AI assistant can tell authorized employees who is scheduled to work today when it retrieves current data from Microsoft Teams Shifts through a secured connector or workflow. It should not answer from an exported spreadsheet, an old posted schedule or a manager’s message. Shifts remains the system of record. Maisy can make the schedule conversational, but the underlying schedule, permissions, time zone and publication status determine whether the answer is reliable.
A Work Schedule Is Live Operational Data
Questions about today’s staffing require current operational records. The answer can change whenever a manager publishes a revised schedule, approves time off, fills an open shift or accepts a swap request.
Microsoft Teams Shifts Stores the Schedule
Microsoft Teams Shifts allows managers to create schedules, organize workers into groups, assign shifts, publish schedules and manage requests. The Microsoft Teams connector documentation shows that shift records can include the assigned user, start and end times, scheduling group, activities, notes and publication state.
Published and Draft Shifts Must Remain Separate
A manager may prepare next week’s schedule before publishing it. The assistant should report the shared schedule employees can rely on, not an unpublished draft that may still change.
Time Zones and Overnight Shifts Create Edge Cases
Questions containing today, tonight or tomorrow require precision. A schedule may have its own time zone, and overnight shifts cross calendar dates. The assistant should use the configured time zone and state it when confusion is possible.
Example: Finding the On-Call Technician
A properly configured workflow identifies the relevant team, retrieves the published shifts covering the current evening, filters for the on-call activity and returns the employee’s name and coverage period. Maisy can then retrieve the approved escalation procedure from SharePoint.
Schedule Data Does Not Prove Attendance
Teams Shifts can show who is scheduled. It does not necessarily prove who is physically present. Confirming attendance may require time-clock data, a check-in system or manager confirmation.
Permissions and Privacy Still Matter
Some employees should see only their team or location. The assistant should not reveal private time-off reasons or sensitive assignments.
Changing the Schedule Requires Stronger Controls
Reading a published shift is lower risk than changing one. Requests to offer a shift, claim an open shift or approve a swap should use controlled connector actions and defined approval rules.
The assistant should not hear “I probably cannot work Friday” and remove the employee from the schedule. Otherwise, chaos walks into the building wearing a name badge.
Where Pixeldust and Maisy Fit
During the Pixeldust knowledge-hub implementation process, employee questions are separated into questions answered from approved knowledge and questions requiring live operational data.
The Microsoft 365 Knowledge Hub architecture allows SharePoint, Teams, Copilot Studio, Power Automate and connectors to serve distinct roles.
Shifts establishes who is scheduled. SharePoint explains scheduling policies, coverage rules and escalation requirements.
