Support employees with accountable access and troubleshooting requests.
Internal IT teams receive account-access questions, configuration problems and requests for help with everyday business software. A focused helpdesk gives each employee request a clear owner and preserves the public conversation alongside the technical investigation. The service team can apply agreed priority and response targets without introducing field dispatch or a live contact-center platform.
Map verified employee principals to their customer records before enabling portal access. An address imported from an HR system supplies a reference, not authority to impersonate that employee. Staff see their own requests and permitted files while agents retain the internal diagnostics needed to investigate.
Use categories and queue skills to distinguish straightforward account questions from work requiring an application or infrastructure specialist. Capacity-aware assignment keeps a busy specialist from receiving unlimited work, and an unresolved routing exception remains visible to the support manager.
Agree on the business calendar and what waiting on an employee means for the clock. An internal note or an automated receipt does not count as the first public agent response. Reopened work retains its earlier service episode and any prior breach.
Link maintained troubleshooting notes or approved wiki references to the ticket. Keep these links internal and review the explanation before sharing a public response with the employee. A common article is guidance for investigation, not permission to make an unrelated account change.
Review resolution time, recurring categories and explicit employee feedback together. A request closed without a survey response remains a nonresponse. Use the actual ticket evidence to decide whether a queue, note or upstream application needs attention.
Employee identity · Internal guidance
Feedback and improvement
Specialist routing
Service windows
Same records, same gates. The configuration changes how the process runs for this team.
Support Manager: Approve submitted SLAPolicies prepared by another actor
Approval waits for the support manager.
Owns staffing, queue health and service policy within assigned teams.
Works assigned support requests and escalates specialist questions.
Works specialist assignments and accepts escalations in the assigned team.
Uses a lightweight portal to open and follow their own requests.
Let customers follow their own requests with clear updates.
Give agents useful internal answers close to the ticket.
Track response and resolution against the agreed service policy.
Keep the customer conversation with the request.
Route each request to someone who can take responsibility.
Move difficult or urgent requests to the right level of support.
Median, p75 and p95 elapsed UTC minutes from each ServiceEpisodes.StartTime to that episode ResolvedAt, grouped by PriorityAtStart and CategoryAtStart. Count distinct resolved episodes; unresolved windows stay separately visible. Elapsed duration includes waiting time; business-calendar SLA target arithmetic is separate.
Report first-response and resolution obligations separately for closed episodes. First response applies only to Episode 1 and becomes eligible once answered or its deadline has passed; resolution uses each closed episode. Success requires an eligible completion timestamp on or before the retained deadline. Group by frozen policy, PriorityAtStart, TeamAtResolution and AgentAtResolution with explicit missing buckets. Retain every breach and show not-yet-eligible obligations separately.
Average explicit 1-5 responses by response period and the linked closed episode TeamAtResolution/AgentAtResolution. Each SurveyKey counts once. Show responded, unanswered and eligible invitation counts; exclude missing scores from the average. Later assignment changes cannot move historical scores between staff.
Use connected email, portal or web forms and authorized system events. Agents can manually record phone requests. Live chat, telephony and social aggregation are separate products.
Related questionCustomers see only their own permitted public ticket fields, replies and files. Internal notes, article links and diagnostic history remain private, including through direct downloads.
Related questionAn allowed reopen creates a new service episode and returns the request to work. Earlier targets, responses and breaches remain in history.
Related questionIt includes internal notes, macros and links to approved knowledge sources. Public article publishing and customer-facing knowledge search belong to a separately configured product.
Related questionThe configured queue strategy selects eligible staff and reserves capacity atomically. Requests without a safe destination remain visibly unassigned for the manager.
Related questionNo. Acknowledgment records the review and reason; the original missed target remains part of historical attainment.
Related questionSupport employees with accountable access and troubleshooting requests.
Coordinate customer questions across first-line and specialist teams.
Give shared-service requests a visible owner and resolution path.
