On this page
Each row is a metric's name, its number and one short line. The ⓘ beside the name says how the number is counted and which days it covers. Until you import from Freshdesk (or Help Scout) the page describes Colliedesk alone: there is no "before" column and nothing to compare.
The numbers are worked out in the background, never while you wait: the page says when they were last updated (usually within the hour). Nothing on the page changes your conversations.
Where the "before" numbers come from
When a Freshdesk import finishes, Colliedesk works out the same numbers from the history it imported. That import is the baseline:
- The first import whose full run finishes becomes the baseline, and the moment it finished is the moment the baseline describes. Running the import again later never moves it: it only fills in what was missing, so the before numbers stay the same while you keep Freshdesk running.
- The baseline windows end at the newest ticket a customer opened before that moment. An account whose history ends long before the import (a quiet Freshdesk) is measured over its last 30 or 7 days of tickets.
- Undoing that import removes the baseline. The next import to finish becomes the new one.
- An import that ended FAILED shows no before numbers: some tickets did not arrive, so the numbers would be wrong. An UNVERIFIED import shows its numbers with a label saying so; when the only reason is an archive that the Freshdesk plan does not let Colliedesk read, the page shows a plain note instead of a warning. Fix what its report names and run the import again.
- Help Scout imports give a baseline too, without resolve times (Help Scout does not share them).
- Freshdesk shares no reopen history, so there is no "before" reopen rate.
A workspace that imported before this page existed gets its earliest import as the baseline. That import did not read Freshdesk's resolve times: run it again to fill them in (it changes nothing else).
How each number is counted
The same rules apply to both sides, so the two columns can be compared.
Which conversations. Only conversations a customer started: the first message that is not a note came from the customer. Conversations your team started, problem reports and, on the Colliedesk side, conversations brought in by an import are left out. A conversation counts in a window by the day it was created. A conversation marked as spam is left out, and so is the time it spent in Spam: one taken out again counts as if it had stayed where it was.
Measured at a moment. Each side counts only what had happened by its moment: the Colliedesk side now, the baseline when its import finished. A reply that came later does not count.
First response time. Time from the customer's first message to the first reply your team sent after it. Notes, automatic replies (a channel's own received notice among them) and forwards are not replies. The page shows the median (half got a reply faster) and the 90th percentile (90% got one within that time), with how many were answered and how many still wait for a first reply. Time is calendar time, nights and weekends included.
Time to resolve. Time from when the conversation came in to when it was resolved, counting only a resolution that stayed resolved (or closed) for 7 days. If it was reopened and resolved again, the later resolution counts; each conversation counts at most once. Waiting on the customer (pending) and a customer who went quiet are never resolved. Because a resolution needs those 7 days, this number uses conversations created a week earlier: for "Last 30 days", conversations created 37 to 7 days ago. The page shows how many were resolved and how many are not resolved or still settling. On the Freshdesk side the resolve time is the one Freshdesk reports for tickets that were still resolved or closed when they were read; a ticket without one is counted separately.
Reopened within 7 days. Of those resolutions, the share that came back within 7 days: the customer wrote again (even just "thanks!") or a teammate reopened it.
Conversations per week. Conversations in the window divided by its weeks, or by the weeks since your first conversation if that came later. Until a customer has started a conversation in Colliedesk (right after you move), there is no weekly number and nothing to compare: the page says so instead of showing "100% fewer". While less than a week of conversations exists, the row shows the count ("3 conversations") and how many days it has so far, not a weekly rate that would only extrapolate them.
Handle time. The time your team logged on a conversation in Freshdesk, added up, for the resolved conversations; the median. Colliedesk does not record time yet (issue #119).
Small samples. A median, a 90th percentile or a reopen rate needs at least 5 conversations; with fewer the row says what it needs and how many there are so far, for example "Needs 5 answered conversations · 0 so far · 0 waiting": the counts stay links to the conversations they name.
Status history. Colliedesk records every status change since your server was updated to a version with this page (or since the workspace was created). A window that needs resolutions from before that says "From" the day it will be available, and the day its status history must start.
AI drafts
For the same window, by the day a person decided: AI drafts sent nearly unchanged (at least 90% the same as the draft), sent after edits, and discarded. A draft replaced by a newer one, or left until it expired, is not counted.
Hours saved appears only when the baseline has a handle time from at least 5 conversations in that window. It is an upper bound and the page prints the formula:
conversations with at least one draft sent nearly unchanged × the median handle time in Freshdesk
It assumes each of those conversations would have taken as long as it did in Freshdesk.
Open the conversations behind a number
Click a number (or a count under it, such as "8 waiting for a first reply"). The inbox opens with the filter Counted in: … and every status; Back to Reports returns to the page. The numbers are worked out again every hour or so and the list belongs to the count you clicked; a count replaced more than a day ago says "These numbers were refreshed. Open Reports again."
Share the numbers
People with results:share (the admins) see Share and email at the bottom of the page.
Share link. Create link makes an address anyone can open without signing in: the page's totals, medians and sample sizes, and nothing else (no customer or team names, no subjects, no message text, and no way into the conversations). Copy it when it appears: it is shown only once. Create a new link turns the old one off; Turn off stops it. A link that was turned off says "This link was turned off. Ask the team for a new one." The page shows who made the link, when, and when it was last opened (updated at most once an hour). On Colliedesk Cloud a workspace whose plan ended shares nothing.
Weekly email. Every Monday at 8:00 in the workspace's timezone, everyone with results:share gets the last 30 days
next to the baseline, last week's volume and the AI drafts, with a link to the page. Totals only,
never customer names or messages. Each of them turns it off (or on again) for themselves with Email
me on Mondays; the email has the same link at the bottom. A workspace with no numbers yet gets no
email. It needs the server's outgoing mail settings (self-host email); without
them the page says so and shows no switch, and your choice shows again once the server can send.
For developers and AI agents
GET /api/v1/results returns the numbers (results:read), and GET /api/v1/conversations?result=…
the conversations behind one. The MCP tool colliedesk_results_get and the result argument of
colliedesk_inbox_search do the same (MCP). The share link needs results:share, since
the numbers leave sign-in: with it, a token reads, creates and turns off the link
(colliedesk_results_share_link_get, colliedesk_results_share_link_create,
colliedesk_results_share_link_revoke), and creating one returns the link to the agent at once. A
token created before roles cannot. colliedesk_results_email_set turns the token owner's weekly email
on or off.
Was this page helpful?
Updated
This page is rendered from the repository. Spot a mistake? Open an issue or a pull request.