Zscaler help desk and second level

Resolve more tickets at first line. Use specialist time where it matters.

User Support Center gives the help desk roughly 70 relevant user-related data points with role limits and without broad Zscaler admin rights. Unified Support Center adds the detail needed for genuine specialist analysis.

User Support Center: Capture the user, device, access and relevant service signals in a role-based search.
First diagnosis

User Support Center

Capture the user, device, access and relevant service signals in a role-based search.

Unified Support Center: Review rules, includes, excludes, profiles, apps, tunnels and available experience data together.
Extended context

Unified Support Center

Review rules, includes, excludes, profiles, apps, tunnels and available experience data together.

Connectivity Triage Map: Prioritize available signals and state source context, confidence and the next check.
Root-cause context

Connectivity Triage Map

Prioritize available signals and state source context, confidence and the next check.

Log Verdict: Structure ZCC logs by finding and severity and prepare concrete technical checks.
Client evidence

Log Verdict

Structure ZCC logs by finding and severity and prepare concrete technical checks.

In the support workflow

Each role gets the context it actually needs.

Routine cases stay where they can be resolved quickly. Complex cases reach specialists with a prepared and understandable finding.

First line

Move from symptom to finding

Connect user, device, access and available experience signals without full console permissions.

Second level

Begin with analysis, not data collection

See detailed user, policy, application and tunnel context in the same case.

Administration

Connect context and action

Prepare approvals or supported ZCC control actions when role, tenant and package allow them.

Handover

Pass on a prepared case

Keep the finding, sources, status and next action together for ITSM and specialist review.

From ticket to classification

Diagnosis, decision and permission follow one clear path.

The help desk can answer more questions directly and escalate the cases that need additional authority with the relevant context attached.

01

Understand the case

Connect the user, device, application and visible symptom.

02

Identify the likely cause

Assess connection, device, policy and Zscaler service information with its source context.

03

Continue deliberately

Offer self-service, resolve the case or prepare a controlled request and handover.

Access Review Desk with request status, reason and responsible role
Access Review Desk: Access Review Desk: a prepared handover for the responsible decision role.
Access Review Desk

Turn a first finding into a clear decision record.

When a case needs approval or a change, the responsible role receives the requested action together with its reason, status and relevant user context.

  • Keep finding and requested action together.
  • Make approval status visible to support and requester.
  • Record the decision and target-system result.
Help desk and administration team reviewing an access case
Faster together

A good first finding accelerates both teams.

Help desk and administration start from the same factual basis while permissions and responsibility remain distinct.

Next step

Review a help desk workflow

Bring one recurring operating situation. We will map the roles, required context and appropriate demo path.

Frequently asked questions

Direct answers for Zscaler support teams.

Can the help desk analyze Zscaler cases without admin rights?

Yes. User Support Center provides the approved user, device and access context without giving first-line staff broad rights in the Zscaler consoles.

What is the difference between User Support Center and Unified Support Center?

User Support Center provides the fast baseline view. Unified Support Center adds deeper identity, application, policy, tunnel and available experience context for second level and administrators.

What information is available to second level?

Depending on connected services and permissions, the view includes user and device data, rules, includes, excludes, profiles, apps, tunnels and available experience signals.

Can actions be started from the same context?

Yes, where role, tenant configuration and package allow it. The tenant policy controls the approval path and successful writes require target-system effect and read-back.