3.4The service desk

When users run into trouble, never making them wonder where to turn—that is the service desk's first value. The service desk is the single point of contact (SPOC) for users, centralizing the entry point for incidents, requests, and inquiries. After confirming this SPOC role, this section covers the design judgment of which structure (local, centralized, virtual, or follow-the-sun) to choose given constraints such as site distribution, language, the need for 24-hour coverage, and cost.

3.4.1The SPOC role as a single point of contact

• The service desk is the single point of contact (SPOC) for users, receiving incident reports, service requests, and inquiries in a unified manner. Users never have to wonder "where should I contact?", and the status of handling can be tracked in one place.
• The service desk is not a mere relay; it resolves at first contact (using known errors and the KEDB), acts as the starting point for functional and hierarchical escalation, keeps users informed of status, and maintains user satisfaction. A distinctive point is that not only technical skill but communication and user satisfaction are evaluation criteria.

3.4.2Structural patterns

Suppose a service manager designs the service-desk structure for a company with three domestic sites and two overseas sites. The requirements are: (1) users at any site receive the same quality of support; (2) 24/7 coverage is needed, including the overseas sites; and (3) securing night-shift staff is difficult and cost must be contained. As a fundamental premise, the single point of contact (SPOC) for users must be maintained—if contact points differ by site, users get confused and the status of handling cannot be tracked in one place. From the standpoint of (1) uniform quality and consolidating staff and tools alone, a centralized service desk is a strong candidate; but trying to meet (2) 24-hour coverage with a single centralized site inevitably requires night-shift staff, contradicting (3) and inflating costs. This is where follow-the-sun is effective. Operating time-zoned overseas and domestic sites in relay lets each site work only during its own daytime, while globally achieving 24-hour coverage without night shifts. Furthermore, even though each site's staff are physically dispersed, unifying them with common tools and knowledge (the KEDB) so that they appear to users as a single desk combines with the virtual service desk concept, allowing dispersed operation while preserving the SPOC. On the other hand, if the requirement were "a single site, daytime only, where face-to-face support in the local language matters most," a local service desk would be appropriate and follow-the-sun would be overkill. "Without breaking the SPOC principle, choose the structural pattern from the constraints of site distribution, the need for 24-hour coverage, and night-shift cost"—this is the service manager's judgment in service-desk design.

3.4.3Section summary

• The service desk is the users' single point of contact (SPOC), centralizing communication so users are not left wondering, and handling first-line resolution, escalation, and user satisfaction
• Structures include local, centralized, virtual, and follow-the-sun; do not confuse centralized (consolidated into one site) with virtual (dispersed but tool-unified)
• Choose the pattern from constraints of site distribution, language, the need for 24-hour coverage, and night-shift cost; follow-the-sun is a means of achieving 24-hour coverage without night shifts