Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (217 biz days late)
Active: 238 biz days
Paused: 34 biz days
🕐 Clock stopped: Completed (Feb 5, 2026)
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸34d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Feb 3, 2026
34 business days (not counted)
▶ Clock Running
Status: Assigned
Feb 3 → Feb 3, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Feb 3 → Feb 4, 2026
1 business day (counted)
Running total: 237 of ? biz days used
▶ Clock Running
Status: Tech On Site
Feb 4 → Feb 5, 2026
1 business day (counted)
Running total: 238 of ? biz days used
Created: Jan 2, 2025Completed: Feb 5, 2026
Show SLA Clock Detail (5 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Feb 3
Ready for Release
⏸ Paused
34
—
Feb 3 → Feb 3
Assigned
▶ Running
0
236
Feb 3 → Feb 4
Scheduled
▶ Running
1
237
Feb 4 → Feb 5
Tech On Site
▶ Running
1
238
Holding271.2d (excluded)
Coordinators1.4d
Field Work0.9d
Billing17.5d
✗ SLA Missed
Holding(excluded from total)
271.2 days
Coordinators
1.4 days
Field Work
0.9 days
Billing
17.5 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Feb 5, 2026 (329 days early)
📅
271.8 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
8 transitionsStatus Changes
⚠️
16.4d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
5 linesWork Details
🏠
1 visitOn-Site Trips
👤
Self-ScheduledScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed with significant delays
Invoiced • 426 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay16.4 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
236.5d
Ready for Release
34.7d
Assigned
0.0d / 0.5d SLA
Scheduled
1.4d / 2.0d SLA
Tech On Site
0.9d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
17.4d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
Technician Findings upon arrival: Unit is due for PM. Unit is operational.
What caused the issue: WO for PM required
Actions Taken/Work Performed: Performed testing & PM maintenance
Final Resolution: All Functions are Working as Intended
Returned unit to service
🔍Technician Findings
Technician Findings upon arrival: Unit is due for PM. Unit is operational. Spoke with Josh
What caused the issue: WO for PM required
Actions Taken/Work Performed: Performed testing & PM maintenance
Final Resolution: All Functions are Working as Intended
Returned unit to service
⚠️Problem Description
Please Perform PM: PM Checklist can be found as a link in the work order under WO actions
If Kiosk is not on the Sales floor request to speak to a manager to find out if kiosk is being stored in the back room or if it was disposed. Offer to help bring the kiosk to the salesfloor or advise that EMSAR can replace a disposed kiosk. If store does not want to bring the kiosk out of storage or if kiosk was disposed, close out work order with Repair code '37 Store intervention required' and document who you spoke with and outcome of conversation. Labor line shall be a trip charge.
***Important: Please make sure to document if kiosk is disposed or in storage***
If kiosk fails a PM, checklist is still required to be completed. Please use Code 35 - Follow up needed and detail in the Tech Findings, Work Performed and Final condition the result and cause for a follow up. Close out the work order. Dispatch will create a follow up repair work order to send parts.