Front Desk Summary
Conversations, bookings, conversion and revenue, per channel. The same numbers the shop reads on its own screen.
GET /v1/front-desk/summary
Authenticationโ
Requires a valid API key with frontdesk:read scope.
Query Parametersโ
| Parameter | Type | Description |
|---|---|---|
since | string | Only count conversations from this date onward (ISO 8601) |
Request Exampleโ
curl "https://app.equipdash.com/api/v1/front-desk/summary?since=2026-09-01" \
-H "Authorization: Bearer eqd_live_your_api_key"
Response Exampleโ
{
"data": {
"chat": {
"conversations": 96,
"bookings": 14,
"conversion": 14.6,
"revenue": 3180.00
},
"phone": {
"conversations": 32,
"bookings": 11,
"conversion": 34.4,
"revenue": 2415.00
},
"waiting_on_you": 2,
"counts": {
"all": 128,
"chat": 96,
"phone": 32,
"needs_owner": 2,
"archived": 4
}
},
"meta": {}
}
conversion is the percentage of conversations on that channel that led to a booking. revenue is the total of those bookings, in the shop's own currency.
counts is what each filter on the list would return, so a dashboard can label its filters without asking for every list in turn. It reads the same query the rows do, so a number can always be evidenced in the rows it opens. Two things to know about it: counts leaves archived conversations out, while the per-channel scoreboard above counts everything the channel ever did; and since narrows the scoreboard only, never counts.