Time Management Tools
The Time Management actions let an AI clock people in and out, record and correct shifts, lock them for payroll, delete a shift, pull hours-and-pay reports for your whole team, and see which devices and places your team clocks in from.
Overview
From Yaplet, the assistant inside your dashboard, or a connected AI app, an AI can do what you'd normally do on the My Shifts and All Shifts pages — clock in and out, record a shift for a teammate, fix times, change one shift's pay rate, finalize shifts for payroll — and get the Shift reports page's hours and pay totals in a single call. It can also report which devices, networks and countries your team clocks in and out from, and — where activity recording is on — which devices they were active on during their shifts. It looks the actions up with find_actions and runs each one with the run tool for its kind (see MCP Server).
In the dashboard this feature is called Shifts, and it sits under a menu group called Team — look for Team → Shifts, with My Shifts, All Shifts, Shift Types and Shift reports inside it. Behind the scenes it goes by Time Management: the permission is spelled Time Management, the action names start with shifts., and the web addresses say /dashboard/time-management/….
Shift data is also readable through the Data Access Tools — list_records and get_record accept shifts and shift_types as resource types.
Actions
| Action | Level | What it does |
|---|---|---|
shifts.report | Read | Hours and pay over a date range — per agent, per shift type and in total, optionally day by day. Needs the Reports sub-permission. |
shifts.device_report | Read | Which devices, networks and countries agents clocked in and out from over a date range — phone use, switches during a shift, and, where activity recording is on, which devices they were active on and for how long. Needs All Shifts. |
shifts.clock_in | Change | Clocks you in now on the shift type you name. While activity recording is on, the answer carries a notice ("While your shift runs, Yaplet notes which device you're active on.") that the AI passes on to you. |
shifts.clock_out | Change | Clocks you out now. With All Shifts it can also end a teammate's running shift. |
shifts.create | Change | Records a shift for any agent — finished, or still running — for example one someone forgot to track. Needs All Shifts. |
shifts.update | Change | Changes a shift's start, end or note; with All Shifts also its pay rate and whether it is finalized. |
shifts.delete | Delete or send | Permanently deletes one shift, together with its shift log. |
Key Concepts
Finalization is a lock
A finalized shift is payroll — it refuses every change. The single exception: a shifts.update that does nothing but switch finalization off unlocks it again. Deleting a finalized shift also requires unlocking it first. Finalizing needs the All Shifts sub-permission and a shift that has actually ended.
How pay is calculated
Every shift's pay is hours × the shift type's rate multiplier × the hourly rate recorded on the shift when it was created. Changing a member's rate later doesn't rewrite old shifts — someone with All Shifts can change the rate on an individual shift instead. A shift that is still running has no pay yet.
One running shift at a time
Clocking in is refused while you already have a running shift, and agents can only clock into the shift types they've been granted. Clocking in is always for the person the connection runs as — to put a shift on someone else's record, the AI uses shifts.create, which is not limited by the type grants.
Correcting a shift
Only the fields the AI sends are changed. Time and pay-rate corrections flag the shift as edited, which shows as a warning marker in the dashboard. Setting the first end time of a running shift counts as clocking out, not as a correction. A shift can be at most 31 days long.
Deleting a shift
A delete needs the Read, change, delete and send access level. Along with the shift, the AI must give the shift's start date (for example 2026-09-30), and nothing is deleted unless it matches — so a wrong or made-up shift is never removed. The date is counted in UTC (Coordinated Universal Time): for a shift that started shortly after midnight in a time zone ahead of UTC, it is the previous day's date. If the date doesn't match, the AI is told the right one.
The shift report
shifts.report gives the same figures as the Shift reports page, without paging through raw shifts:
- Per agent: shift count, total hours, average hours per shift, total pay, plus how many shifts are still running, manually edited, or finalized.
- Totals: agents, shifts, hours and pay across the whole range.
- Per shift type: shifts, hours and pay for each type.
- Per day (when asked for): summed man-hours next to covered hours — overlapping shifts merged, so you can see whether someone was on duty, not just how much total time was logged. Days are split at UTC midnight.
Shifts that are still running are counted separately and add no hours or pay. Pay amounts are plain numbers — the dashboard shows them with a dollar sign. One report covers at most 400 days.
Clock-in devices and locations
shifts.device_report answers questions such as "who works from their phone?" or "who clocked in from another country?" from the shift log, the same record the dashboard's shift log shows:
- Per agent: the kinds of device they clocked in and out from — system and browser, such as Windows · Chrome or iPhone · Safari — with how often each was used, how many shifts involved a phone or tablet, how many shifts switched device, network or country between clock-in and clock-out, and the countries they clocked in from.
- Shifts one by one, newest first, up to 500: by default the flagged ones — a phone, a device switch, a network switch or a country switch. The AI can also list every shift, only one kind of flag, or none.
- Activity during the shift, where the organization has activity recording switched on (the Record activity during shifts switch on the All Shifts page): each listed shift shows its active minutes, how many minutes after the start the first activity came, any minutes not recorded before the clock-in or after the clock-out, and for each device its first and last activity, its active minutes and — when it was already in use before the clock-in — since when. Per agent, the report adds how many shifts had activity, the active hours, and how many shifts were clocked in from a phone or tablet with a computer used later, with the median minutes until the computer's first activity. The phone, device, network and country flags still look only at clock-ins, clock-outs and edits.
A few things shape the answer:
- A device is a kind, not one machine. Two Windows laptops running Chrome look the same, and a browser update is not a switch.
- Only the agent's own actions count. When a manager edits someone's shift, the log shows the manager's device, so it is left out. What an agent used between clock-in and clock-out is known only when they edited the shift in the meantime, or from the activity notes where recording is on.
- A clock-out typed in later is a correction. A clock-out entered more than 15 minutes after the end time it sets is shown, but kept out of the phone and switch checks — fixing a forgotten clock-out from your phone the next morning is not working from your phone.
- Networks are compared by IP address with its last part blanked. Older shift log entries often have no usable address, and those shifts are simply not compared.
- Active time is a floor, not a stopwatch. It is 10 minutes for every 10-minute slot with at least one key press, click, tap or scroll in Yaplet or the Yaplet app, counted only between the shift's current start and end. Minutes "not recorded" mean the start or end was moved beyond the running clock — never that the agent was idle. Clocking in or out through Yaplet never counts as activity.
One report covers at most 400 days. Reading a single shift with get_record gives its log without the activity notes, plus an activity summary — only for people with All Shifts. get_account_state says whether activity recording is on.
What an AI cannot do here
- Change a member's own hourly rate — the rate new shifts start with. Members' pay rates are human-only in every connection: change it on the team page (account menu → Manage team).
- Create, change or delete shift types, or choose who may clock into each type. Manage shift types under Team → Shifts → Shift Types, and assign them to members on the team page (account menu → Manage team).
- Clock a teammate in "now". Clocking in is only for yourself; for anyone else the AI records the shift with a start time instead.
- Delete several shifts in one go. Each delete names one shift and its date.
- Switch activity recording on or off. A person does it with the Record activity during shifts switch on the All Shifts page.
Example Prompts
- "Clock me in for chat duty."
- "I forgot to clock out yesterday — set my shift's end to 6 PM."
- "Record an 8-hour shift for Anna last Tuesday."
- "How many hours did each agent work last month, and what do we owe them?"
- "Run July's shift report, show me any shifts that aren't finalized yet, and finalize the ones that look complete."
- "Who clocked in from their phone last month, and did anyone switch devices or countries during a shift?"
- "Who clocks in by phone and reaches the PC much later?"