In ServiceNow FSM, what is the order for determining the appointment time zone?

• A. Location of the service, current user, system time zone
• B. Current user, location of the service, system time zone
• C. System time zone, location of the service, current user
• D. Location of the service, system time zone, current user

Answer: (A)

The time zone used for an appointment in FSM is determined by a precedence that starts with the most context-specific source and falls back to a default. First, the system checks the location of the service; if that location has its own time zone defined, that value is used to schedule and display the appointment. If the service location doesn’t specify a time zone, the system then looks at the current user’s time zone preference and uses that. If neither the location nor the user provides a time zone, the system time zone is used as the fallback.

This order makes sense because where the service actually happens is the most relevant for timing. The user’s time zone matters next, as the person handling or viewing the appointment may be in a different locale. Only if neither of these has a time zone defined does the system default come into play, ensuring there’s always a consistent time reference.

Choices that prioritize the user first or rely solely on the system time zone would ignore the on-site context or default to a single global time, which could lead to incorrect scheduling for cross-region field service.