the Forecasted vs Actual report often shows 0% or 100% forecasted SLA, even when actual SLA is somewhere in between. This makes it nearly impossible to model SLA risk, especially for email channels or queues with long SLA windows (e.g., 24+ hrs). Assembled should more accurately calculate forecasted SLA, including factoring in: • Backlogged cases (created prior to the day, still open and breaching SLA) • Non-zero forecasted SLA based on staffing + productivity inputs • Real-time reflection of service level performance, not just tickets created today Right now, we’re seeing mismatches between FvA and Realtime Overview, and some tickets that missed SLA still appear as met (or vice versa). This impacts our ability to triage, report accurately, and forecast requirements.