Specify Regions

Sub Banner

When a ticket is created, in addition to an SLA Plan assignment to determine the amount of time an agent is given to complete an event (e.g. an initial response or resolution of a ticket), a Region should be assigned to the ticket (see Creating and Maintaining Regions).

A Region is used to determine which set of Working Hours and Public Holidays apply and the regional Timezone upon which the event due date/time calculation should be based.

Regional Timezones

In order to accurately calculate by when each event must be completed, it will be necessary to determine the timezone within which the submitter of a ticket is located.

The Timezone is used together with the Working Hours and Public Holidays to determine exactly when work will take place on the ticket and so by when the completion of the event is due.

For example:

  • You might have contracts in place with a customer based on the US West Coast and a second customer based on the US East Coast, both of which include an SLA for an initial response within 1 hour between 9am and 5pm
  • If a ticket is submitted by US West Coast based customer at 10am PST (1pm EST) then the due date/time will be calculated as 11am PST
  • If a ticket is submitted by US East Coast based customer at 1pm EST (10am PST) then the due date/time will be calculated as 12pm EST
  • If a ticket is submitted by the US West Coast based customer at 7am PST (10am EST) then the due date/time will be calculated as 10am PST
  • If a ticket is submitted by  the US West Coast based customer at 3pm PST (6pm EST) then the due date/time will be calculated as 4pm PST
  • If a ticket is submitted by  the US East Coast based customer at 6pm EST (3pm PST) then the due date/time will be calculated as 10am EST the next working day

Timezones in the Agent Interface

The calculated due date/time is recorded against the ticket in Zendesk and displayed in the SLA Assistant based on the TimeZone associated with the Region assigned to the ticket.

In ideal circumstances the ticket would be assigned to an agent based in the same timezone and operating within the associated Working Hours.

However, depending upon the agreed Working Hours it is possible that the ticket might be assigned or reassigned to an agent working in a different timezone at some stage.

Although the agent should receive a warning of an impending breach of SLA your agents should be mindful of the timezone displayed against the due date/time.

Overriding the Region Defaults

There might be certain rules or circumstances under which the default Working Hours and/or Public Holidays associated with a Region don't always apply.

For example a ticket with an urgent priority might be covered by 24x7 working hours.

See Refine SLA Plans for further details.

Specify Regions

Sub Banner

Specify Regions

When a ticket is created, in addition to an SLA Plan assignment to determine the amount of time an agent is given to complete an event (e.g. an initial response or resolution of a ticket), a Region should be assigned to the ticket (see Creating and Maintaining Regions).

A Region is used to determine which set of Working Hours and Public Holidays apply and the regional Timezone upon which the event due date/time calculation should be based.

Regional Timezones

In order to accurately calculate by when each event must be completed, it will be necessary to determine the timezone within which the submitter of a ticket is located.

The Timezone is used together with the Working Hours and Public Holidays to determine exactly when work will take place on the ticket and so by when the completion of the event is due.

For example:

  • You might have contracts in place with a customer based on the US West Coast and a second customer based on the US East Coast, both of which include an SLA for an initial response within 1 hour between 9am and 5pm
  • If a ticket is submitted by US West Coast based customer at 10am PST (1pm EST) then the due date/time will be calculated as 11am PST
  • If a ticket is submitted by US East Coast based customer at 1pm EST (10am PST) then the due date/time will be calculated as 12pm EST
  • If a ticket is submitted by the US West Coast based customer at 7am PST (10am EST) then the due date/time will be calculated as 10am PST
  • If a ticket is submitted by  the US West Coast based customer at 3pm PST (6pm EST) then the due date/time will be calculated as 4pm PST
  • If a ticket is submitted by  the US East Coast based customer at 6pm EST (3pm PST) then the due date/time will be calculated as 10am EST the next working day

Timezones in the Agent Interface

The calculated due date/time is recorded against the ticket in Zendesk and displayed in the SLA Assistant based on the TimeZone associated with the Region assigned to the ticket.

In ideal circumstances the ticket would be assigned to an agent based in the same timezone and operating within the associated Working Hours.

However, depending upon the agreed Working Hours it is possible that the ticket might be assigned or reassigned to an agent working in a different timezone at some stage.

Although the agent should receive a warning of an impending breach of SLA your agents should be mindful of the timezone displayed against the due date/time.

Overriding the Region Defaults

There might be certain rules or circumstances under which the default Working Hours and/or Public Holidays associated with a Region don't always apply.

For example a ticket with an urgent priority might be covered by 24x7 working hours.

See Refine SLA Plans for further details.

Specify Regions

Sub Banner

When a ticket is created, in addition to an SLA Plan assignment to determine the amount of time an agent is given to complete an event (e.g. an initial response or resolution of a ticket), a Region should be assigned to the ticket (see Creating and Maintaining Regions).

A Region is used to determine which set of Working Hours and Public Holidays apply and the regional Timezone upon which the event due date/time calculation should be based.

Regional Timezones

In order to accurately calculate by when each event must be completed, it will be necessary to determine the timezone within which the submitter of a ticket is located.

The Timezone is used together with the Working Hours and Public Holidays to determine exactly when work will take place on the ticket and so by when the completion of the event is due.

For example:

  • You might have contracts in place with a customer based on the US West Coast and a second customer based on the US East Coast, both of which include an SLA for an initial response within 1 hour between 9am and 5pm
  • If a ticket is submitted by US West Coast based customer at 10am PST (1pm EST) then the due date/time will be calculated as 11am PST
  • If a ticket is submitted by US East Coast based customer at 1pm EST (10am PST) then the due date/time will be calculated as 12pm EST
  • If a ticket is submitted by the US West Coast based customer at 7am PST (10am EST) then the due date/time will be calculated as 10am PST
  • If a ticket is submitted by  the US West Coast based customer at 3pm PST (6pm EST) then the due date/time will be calculated as 4pm PST
  • If a ticket is submitted by  the US East Coast based customer at 6pm EST (3pm PST) then the due date/time will be calculated as 10am EST the next working day

Timezones in the Agent Interface

The calculated due date/time is recorded against the ticket in Zendesk and displayed in the SLA Assistant based on the TimeZone associated with the Region assigned to the ticket.

In ideal circumstances the ticket would be assigned to an agent based in the same timezone and operating within the associated Working Hours.

However, depending upon the agreed Working Hours it is possible that the ticket might be assigned or reassigned to an agent working in a different timezone at some stage.

Although the agent should receive a warning of an impending breach of SLA your agents should be mindful of the timezone displayed against the due date/time.

Overriding the Region Defaults

There might be certain rules or circumstances under which the default Working Hours and/or Public Holidays associated with a Region don't always apply.

For example a ticket with an urgent priority might be covered by 24x7 working hours.

See Refine SLA Plans for further details.

Specify Regions

Sub Banner

Specify Regions

When a ticket is created, in addition to an SLA Plan assignment to determine the amount of time an agent is given to complete an event (e.g. an initial response or resolution of a ticket), a Region should be assigned to the ticket (see Creating and Maintaining Regions).

A Region is used to determine which set of Working Hours and Public Holidays apply and the regional Timezone upon which the event due date/time calculation should be based.

Regional Timezones

In order to accurately calculate by when each event must be completed, it will be necessary to determine the timezone within which the submitter of a ticket is located.

The Timezone is used together with the Working Hours and Public Holidays to determine exactly when work will take place on the ticket and so by when the completion of the event is due.

For example:

  • You might have contracts in place with a customer based on the US West Coast and a second customer based on the US East Coast, both of which include an SLA for an initial response within 1 hour between 9am and 5pm
  • If a ticket is submitted by US West Coast based customer at 10am PST (1pm EST) then the due date/time will be calculated as 11am PST
  • If a ticket is submitted by US East Coast based customer at 1pm EST (10am PST) then the due date/time will be calculated as 12pm EST
  • If a ticket is submitted by the US West Coast based customer at 7am PST (10am EST) then the due date/time will be calculated as 10am PST
  • If a ticket is submitted by  the US West Coast based customer at 3pm PST (6pm EST) then the due date/time will be calculated as 4pm PST
  • If a ticket is submitted by  the US East Coast based customer at 6pm EST (3pm PST) then the due date/time will be calculated as 10am EST the next working day

Timezones in the Agent Interface

The calculated due date/time is recorded against the ticket in Zendesk and displayed in the SLA Assistant based on the TimeZone associated with the Region assigned to the ticket.

In ideal circumstances the ticket would be assigned to an agent based in the same timezone and operating within the associated Working Hours.

However, depending upon the agreed Working Hours it is possible that the ticket might be assigned or reassigned to an agent working in a different timezone at some stage.

Although the agent should receive a warning of an impending breach of SLA your agents should be mindful of the timezone displayed against the due date/time.

Overriding the Region Defaults

There might be certain rules or circumstances under which the default Working Hours and/or Public Holidays associated with a Region don't always apply.

For example a ticket with an urgent priority might be covered by 24x7 working hours.

See Refine SLA Plans for further details.