Skip across the chapter
Quota Playbook

Response-time lines: 4 published figures to check

Quota Playbook Editorial Team · Published · 9 min read

Before a seller names a support response time, verify whether its clock runs on business hours or calendar hours. According to Freshdesk, you must choose whether the SLA is calculated using Business hours you have set or Calendar hours (24*7). This distinction determines how the timer runs during the operational period.

Key takeaways

  • Confirm whether the SLA uses business hours or calendar hours before a seller names any time.
  • Quote only a time that appears in a published line for the exact product and plan tier.
  • Check region support for Dynamics 365 SLAs before promising one.

What to check before a seller names a support response time

The manager’s role is to confirm the specific calculation method before the seller speaks. A response time is not a single number; it is a duration measured against a defined clock. If the seller quotes a five-minute response, the buyer needs to know if that five minutes counts only during business hours or includes nights and weekends. The source documentation explicitly requires this choice to be made under operational hours.

When coaching a seller, ask them to identify which clock their current plan uses. If it uses Calendar hours, the timer runs continuously. The seller must understand this difference to avoid promising a speed that the system does not track.

If you cannot find the clock type setting, do not let the seller name a time. Instead, tell the seller to describe the support process without a specific number. It is better to be vague than to be wrong. Your job is to ensure the seller’s words match the system’s settings.

Four published time lines from Freshdesk, Zendesk, and Zoho CRM

Before a seller tells a buyer how fast support will answer, the manager must verify which specific time lines are actually published by the vendors. These figures come directly from vendor documentation and serve as the baseline for what can be accurately stated.

Freshdesk and Freshdesk Omni

Freshdesk lists a five-minute line for both response and resolution times, across all priorities. This applies to the standard Freshdesk product. For the Freshdesk Omni product, the same source states that you can set the SLA as low as 30 seconds for both response and resolution times. The documentation specifies precise 15-second increments for these settings, such as 15s, 30s, 45s, and 60s. The manager should note that the 5-minute line and the 30-second line belong to different product tiers within the Freshdesk ecosystem.

Zendesk

Zendesk defines a minimum target time that you can set at 15 seconds. This is the floor for any SLA policy configuration. The same page includes a sentence stating that you can define an agreement where you respond to urgent tickets in 10 minutes. The source gives this 10-minute figure only as an example, not a minimum requirement. When coaching a seller, it is critical to distinguish between the 15-second minimum setting capability and the 10-minute illustrative example. The 10-minute figure does not represent a standard or required response time; it is merely a demonstration of how an agreement might be structured.

Zoho CRM

Zoho publishes a support-plan row that lists initial response times of 8 hours, 3 hours, 1 hour, and 30 minutes. These four times correspond to different support plan tiers. The source also describes a specific plan feature as priority issue resolution with an initial response time of 30 minutes. The manager should use these four specific times when discussing Zoho CRM support options. The 30-minute line is the fastest initial response time listed in the published row.

Reference table

The table below summarizes the published time lines by publisher. Each row is sourced directly from the vendor’s documentation.

Publisher Product/Service Published Time Line Qualifier
Freshdesk Freshdesk 5 minutes Response and resolution, across all priorities
Freshdesk Freshdesk Omni 30 seconds Minimum setting, 15-second increments
Zendesk Zendesk 15 seconds Minimum target time you can set
Zoho Zoho CRM 8 hours, 3 hours, 1 hour, 30 minutes Initial response time by plan tier

When reviewing these lines with a seller, confirm that the time they plan to quote matches the specific product and plan tier listed. If the seller intends to quote a time not present in these published rows, they must not do so. The manager’s role is to ensure the seller’s promise aligns exactly with the vendor’s published documentation. Verify the product name and the specific time value before the seller speaks to the buyer.

Where Dynamics 365 says an agreement can and cannot be turned on

Before a seller quotes a support speed, the manager must know if the platform even allows an agreement to run in that specific environment. These limits are not about the speed of the answer, but about the structural availability of the feature itself.

The first constraint is geographic. According to Microsoft, the SLA feature isn't supported in Singapore. You cannot turn on an agreement in that specific location.

The second constraint is related to the application type within the environment. The source states that you can create SLAs only in environments that have customer engagement apps such as Customer Service. It notes that SLAs are available by default in these apps. This means the feature is tied to specific customer engagement applications. If the environment does not include these specific apps, the SLA capability is not present. The manager should verify which apps are active in the environment before assuming the feature is available.

Constraint Type Dynamics 365 Rule Source Qualifier
Geographic Limit The SLA feature isn't supported in Singapore. Microsoft
Application Requirement You can create SLAs only in environments that have customer engagement apps such as Customer Service. Microsoft

The documentation also describes how work hours are handled within the SLA structure. You can define work hours and pause and resume SLAs at the SLA KPI level and SLA item level. This capability helps track SLA items for different work hours based on priority and criteria. When coaching a seller, explain that pausing an SLA is a configuration action related to work hours. The pause function manages the tracking of items during non-work hours.

How to read an example on the page without adopting it

Vendor documentation often mixes hard configuration limits with illustrative examples. A front-line manager must distinguish between a setting that defines the boundary of a system and a sentence that merely demonstrates how a feature might be used. If a seller quotes a number from a documentation page, the manager needs to know whether that number is a fixed rule or a flexible suggestion. The following table breaks down three specific configuration parameters from the Freshdesk support page to show how these distinctions appear in practice.

Setting Type Published Range or Rule Editorial Note
Seconds field visibility Removed if SLA is greater than 5 minutes A conditional rule based on the configured time
Reminder window 5 minutes to 4 hours A defined range for one specific reminder type
Long reminder window Immediately (5 minutes) to 1 month A defined range for a different reminder type

The first row addresses the visibility of the seconds field in the SLA configuration. Freshdesk states that the seconds field is removed if the SLA configured is greater than 5 minutes. This is a structural rule within the interface. It does not suggest that 5 minutes is a target response time for customer support; rather, it defines when a specific input field disappears from the screen. A seller should not interpret this as a promise to answer tickets in 5 minutes. It is a UI behavior tied to the magnitude of the time value entered.

The second row concerns the reminder window for SLA policies. The same source notes that you can set the reminder from 5 minutes to 4 hours. This establishes a minimum and maximum for a specific alert function. The 5-minute figure here is a lower bound for setting a reminder, not a guarantee of how quickly an agent will respond to a ticket. The 4-hour figure is the upper limit for this particular setting. If a seller mentions "5 minutes" in a sales call, the manager should verify whether they are referring to this reminder setting or a different metric entirely. The documentation presents this as a configurable range, not a fixed service level.

Check the seller's notes before the next call. If they have written down a time from the documentation, ask them to explain which setting that time belongs to. If they cannot explain it, remove the number from their talking points. This ensures that any time mentioned to a buyer is a true service commitment, not a misread configuration limit.

Illustrative example: checking a 10-minute promise

A seller wants to promise urgent tickets in 10 minutes. Before the call, the manager asks three questions. Is the timer set to business hours or calendar hours? Is 10 minutes a configured target, or only sample wording from a vendor page? Does the published row for the buyer’s product and plan show a response time that matches? If any answer is unclear, the seller describes the process without a number.

Check the time your own plan states

Today, note the response time your own public support page states, or note that none is published. Check the Freshdesk documentation to understand how SLA policies function. You can add up to 1000 SLA policies and 500 Business Hours according to that source. If your plan does not explicitly state a response time, do not invent one. The seller must only quote what your public documentation actually says.

Response-time FAQ

Which sentence states Freshdesk's 5 minutes?

The Freshdesk support documentation lists "5 minutes for both response and resolution times, across all priorities." This specific line defines the standard SLA policy for that product. It applies to both the initial response and the final resolution clock.

Which sentence states the 30-second floor, and for which product?

The Freshdesk page identifies "Freshdesk Omni" as the product allowing settings as low as 30 seconds. The text notes you can use "precise 15-second increments" for both response and resolution times. This distinction separates the Omni product from the standard Freshdesk line mentioned earlier.

What is the Zendesk minimum, and what is only an example?

The Zendesk help article states the "minimum target time you can set is 15 seconds." A separate sentence on the same page offers a 10-minute response time for urgent tickets.

What four times are in the Zoho CRM row?

The Zoho support plans page lists four initial response times in a single row. These times are 8 hours, 3 hours, 1 hour, and 30 minutes.

What does the Dynamics 365 page say about Singapore?

The Microsoft documentation for Dynamics 365 Customer Service states the SLA feature "isn't supported in Singapore." This limitation applies specifically to the Singapore region.

Sources

  1. Check 5 task fields before the next coaching 1:1
  2. Work-hour rules: 4 checks before a coaching 1:1
  3. Sales manager handover: 5 steps for a rep's first 1:1
  4. Pump break paid time
  5. New-seller onboarding time

More plays