ZenotiHelp

Custom Metric β€” Average Service Time

ZTZenoti Docs Team Updated September 20, 2026 6 min readGuide

The Average Service Time metric in ezPulse measures how long your team spends delivering services to guests. Use this metric to monitor service efficiency, identify trends across time periods, and set meaningful goals for your center.

Audience: Business owners and center managers who monitor service performance in the ezPulse metrics dashboard.

Before you begin

  • You must have an active ezPulse account and a valid Zenoti authentication session. For login steps, see Authentication & Session Management.
  • Your organization must have the Average Service Time metric enabled in the metric configuration. For setup, see Metric Configuration.
  • To view metrics on the metrics dashboard, you need access to the ezPulse web app at https://ezpgateway.zenoti.com or the ezPulse mobile app.
  • Center-level goals using this metric require that a center-level goal has been created. See Goal Creation.

Steps

Understand the Average Service Time metric definition

Before using this metric in goals or reviewing it on the metrics dashboard, understand how the value is calculated.

What it measures:

Average Service Time is the total time from when a service starts to when it is marked completed or checked out β€” whichever occurs first β€” divided by the number of service clients in the selected time period.

Formula:

Average Service Time = Total service time (minutes) Γ· Number of service clients

Key behaviors:

  • The result is expressed in minutes, rounded up to the nearest integer. For example, if the calculated average is 32.1 minutes, the displayed value is 33 minutes.
  • The denominator uses the same definition as the Number of Service Clients metric β€” the count of clients who received a service in the selected time period.
  • Both the total service time and the service client count accumulate from the start of the selected time period through the selected date.

Supported time periods:

The metric supports all standard time periods available in ezPulse:

Time period What it covers
Today The current calendar day
WTD (Week to Date) From the organization's configured week start day through today
MTD (Month to Date) From the first of the current month through today
QTD (Quarter to Date) From the first of the current quarter through today
YTD (Year to Date) From January 1 of the current year through today

Note: The WTD time period respects your organization's week start day setting. This setting is configured at the organization level and applies to all centers. For details, see Organization Settings.

View Average Service Time on the metrics dashboard

  1. Sign in to ezPulse at https://ezpgateway.zenoti.com or open the ezPulse mobile app.
  2. Navigate to the Metrics Dashboard.
  3. Select the center you want to review from the center selector.
  4. Locate the Average Service Time metric card.
  5. Use the time period selector to switch between Today, WTD, MTD, QTD, and YTD views.
    • The displayed value updates to reflect the accumulated total for the selected time period.
  6. Review the displayed value, which appears as a whole number of minutes.

Note: Metric values reflect the most recent data refresh. Data is refreshed by the backend on a scheduled basis β€” there is no manual refresh option.

Use Average Service Time in a center-level goal

  1. Sign in to ezPulse and navigate to the Goals section.
  2. Select Create Goal to open the goal creation wizard.
  3. Set Goal Level to Center.
  4. In the metric selection step, choose Average Service Time from the metric list.
    • The metric appears under the Performance category.
  5. Set the Target Value β€” enter the number of minutes you want the center to achieve as its average service time.
  6. Select the Time Period for the goal: Week, Month, Quarter, or Year.
    • For weekly goals, the start date aligns automatically to the organization's configured week start day.
  7. Complete the remaining goal definition fields and review the goal summary.
  8. Save the goal as Draft or publish it directly.
    • A goal in Draft status is visible only to administrators.
    • A Published goal is visible to the team on the metrics dashboard.

Important: Once a goal is published, the allowed status transitions are: Published β†’ Draft and Published β†’ Deactivated. Review the goal definition carefully before publishing. For status change steps, see Goal Status Management.

For a full walkthrough of the goal creation wizard, see Goal Creation.

Use Average Service Time in an employee-level goal

  1. Sign in to ezPulse and navigate to the Goals section.
  2. Select Create Goal to open the goal creation wizard.
  3. Set Goal Level to Employee.
  4. In the metric selection step, choose Average Service Time.
  5. Set the Target Value for each employee in the goal definition table.
    • Each employee can have a different target value, expressed in minutes.
  6. Select the Time Period: Week, Month, Quarter, or Year.
  7. Complete the remaining fields and save or publish the goal.

For details on assigning per-employee target values, see Goal Definitions (Employee-Level Metrics).

Worked example: A center manager creates a monthly employee-level goal for a team of five providers. The target value for each provider is set to 45 minutes. At the end of the month, a provider who completed 80 services with a total service time of 3,400 minutes has an Average Service Time of 43 minutes (3,400 Γ· 80 = 42.5, rounded up to 43). This falls below the 45-minute target, indicating faster-than-targeted service delivery.

Tips

  • Compare time periods to spot trends. Switch between WTD, MTD, and QTD on the metrics dashboard to see whether average service time is increasing or decreasing over time.
  • Set realistic targets based on service type. Centers offering longer treatments (such as full-body massages) will have a naturally higher average than centers focused on express services. Review historical values before setting a target value.
  • Use employee-level goals to identify coaching opportunities. Providers with significantly higher average service times than their peers may benefit from workflow support. Providers with very low averages may be rushing through services β€” use the metric alongside guest feedback data.
  • Account for the week start day when reviewing WTD values. If your organization's week start day is not Sunday, the WTD accumulation window may differ from what you expect. Confirm the setting with your administrator before drawing conclusions from WTD comparisons.
  • Publish goals only when the definition is final. Moving a goal from Published back to Draft is supported, but it removes the goal from the team's metrics dashboard view until it is republished. Plan goal definitions in advance to minimize disruption.

Troubleshooting

The Average Service Time metric does not appear on the metrics dashboard.

The metric may not be enabled in your organization's metric configuration. Ask your administrator to verify that Average Service Time is included in the active metric list. For setup steps, see Metric Configuration.

The displayed value seems unexpectedly high or low.

Check the selected time period. If you are viewing WTD and your organization's week start day is mid-week, the accumulation window may be shorter or longer than expected. Also confirm that the service client count for the period is not unusually small β€” a very low denominator can cause the average to appear inflated.

The metric value has not updated since yesterday.

Data refresh in ezPulse is backend-driven and runs on a scheduled basis. There is no user-triggered refresh. If the value appears stale beyond the expected refresh window, contact your administrator or Zenoti support.

I cannot select Average Service Time when creating a goal.

Confirm that the metric is enabled at the organization level in metric configuration. If the metric appears with an upgrade prompt, your organization's current ezPulse tier may not include this metric. Contact your administrator for details.

The WTD value resets at an unexpected time.

The WTD accumulation window starts on the organization's configured week start day. If the reset time does not match your expectation, the week start day setting may differ from your assumption. This setting is organization-level and cannot differ per center. See Organization Settings to verify the current value.

Was this article helpful?
Your feedback helps us improve our documentation.