Description
Returns average response time and responded-review count for each location. Use it to find the fastest or slowest branches.Parameters
Example Usage
Example Response
Response Fields
The response contains account-wide summaries plus adataPoints entry for each location. Each entry includes the location label, businessNumber, avgResponseTime, and respondedCount for the actual and comparison periods.
Notes
- For the slowest location, use
sortBy: "avg-resp-time"andorder: 1; for the fastest, useorder: 0. - Response time does not indicate response rate or unanswered count. Use
get_review_response_rate_by_locationfor those metrics. avgResponseTime.days,hours, andminutesrepresent one duration.- When
startDate/endDateare both omitted, the live API does not default to 3 months back — it returns full account history (observeddateDiffspanning 13,000+ days) grouped by year. Pass explicit dates for a bounded window. compareis only present in the response when bothcompareStartDateandcompareEndDateare supplied; otherwise eachdataPointsentry (andsummary) contains onlyactual.- Locations with very few responses (1-2) can show multi-year average response times that skew the default
avg-resp-timesort — consider filtering by a minimumrespondedCountbefore surfacing “slowest location” results operationally.