report_sla_compliance
Updated May 19, 20261 min read
SLA completion breakdowns and time-bucketed trends across processing, collection, delivery, and customer-promise stages.
The right tool when the question is "are we hitting our SLAs?" — either at the aggregate level or sliced by carrier, lane, merchant, etc.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
tenantId | string | Yes | The tenant to report on. |
from | string | Yes | Range start. |
to | string | Yes | Range end. |
shipment_type | string | No | forward or reverse. |
select | string | No | json-mask syntax. |
merchant / location_access / country_access | string | string[] | No | Standard scope filters. |
tzoffset | string | No | Timezone offset. |
Returns
A composite — overall SLA completion percentages plus stage-by-stage (processing, collection, delivery, customer promise) and trend buckets.
Example agent prompts
"What's our overall SLA compliance over the last month?"
report_sla_compliance(
tenantId="…",
from="2026-04-07",
to="2026-05-07"
)
"Did SLA slip this week vs last week?"
Run twice with different ranges; the agent compares.
Related tools
report_carrier_performance— drill into the carriers behind an SLA dip.report_failed_delivery_analysis— drill into the failures causing SLA misses.report_transit_time_analysis— same data through the transit-time lens.
Common chain
Why did SLA slip last week? —
report_sla_compliance → report_carrier_performance →
report_failed_delivery_analysis.
Equivalent in the dashboard
Reports → service level Performance.