Internal work can determine whether a customer receives the promised result. When a client and an outsourcing provider report on back-office tickets, they need a shared understanding of what completion means before interpreting the time taken to reach it.
In a November 19 update, Intercom announced SLA reporting for back-office and tracker tickets, including Time to resolve and Time to close measures in reports used for conversations. An SLA is a service-level agreement; here the practical subject is an agreed service-level target. The announcement describes reporting capabilities, not the terms of a particular client contract or proof that a customer’s underlying request was completed. We have not tested an account’s timestamp calculations.
Describe the result the internal team owes
The following is our original client–provider operating analysis, using an invented case. It is not legal advice, a platform configuration guide or a report of measured service performance.
Imagine a provider handling a customer’s request to correct information in a booking. A customer-facing colleague creates an internal ticket for the team responsible for the change. The client and provider need to decide what result that internal team is expected to deliver.
It could be a completed correction, an assessment of whether a correction is allowed or a request for missing information. Those are different results. Calling each one “done” without explanation would make the service report difficult to interpret.
Write the expected outcome in ordinary language. The colleague receiving the ticket should understand what evidence would show that their part of the work is complete and what must be passed back to the customer-facing team.
Separate the internal result from the customer update
In the hypothetical case, suppose the back-office team completes the correction. Someone may still need to tell the customer what changed. A completed internal task and a completed customer interaction are related, but they are not automatically the same event.
The handover should identify who communicates the result and where that responsibility is recorded. If the service report discusses internal completion, preserve that scope rather than describing it as the whole customer journey.
This gives both sides a clearer way to investigate a complaint. They can examine whether the internal work finished, whether its result reached the right colleague and whether the customer received the expected response.
Agree how unresolved dependencies are described
An internal team may need information from the client before it can proceed. In our invented example, a request could lack a detail needed to identify the correct booking. The provider should make the missing information and the person responsible for supplying it visible.
Agree how that dependency will be described in the actual working process and report. Ask the reporting owner how the relevant system treats the states being used. Do not assume that a particular status automatically stops, resets or excludes time from a measure.
The operational account should remain useful even before a metric is calculated. What is missing, who has been asked and what happens next are questions a supervisor can act on during the work.
Review the target alongside examples of the work
When client and provider discuss the results, compare the reported measure with examples of what the ticket required. A simple correction and a case needing a client decision may involve different work. The review should explain which cases were included and which comparison is intended.
A few selected examples can expose a misunderstanding about completion, but they cannot establish the frequency of every issue. Keep the distinction between the reported population, the examples examined and the explanation the team proposes.
Include the owner of any outstanding customer update in that account, so an internal status does not obscure the remaining communication.
Internal reporting becomes more useful when the target has a shared meaning. Define the required result, preserve the boundary between internal completion and customer follow-up, and make dependencies clear enough for the right person to act. Then the client and provider can discuss time alongside the work that time represents.
AI-generated conceptual photograph of a fictional internal-work review; the blank documents and clock do not show measured service performance.