-
Notifications
You must be signed in to change notification settings - Fork 9
Description
Is there an existing feature request for this?
- I have searched the existing issues
Describe the Feature
SLA metrics are becoming a more crucial reporting mechanism for Intercom customers, particularly with how customer success teams evaluate the effectiveness of their teammates.
This feature would add the following data:
- Add
median_next_response_timemetric tointercom_conversationsmodel, would need to be calculated upstream inintercom_conversation_partsmodel. (This could be the heaviest lift, so open to discussing). - Configurable variables for
target_first_response_time_minutesandtarget_next_response_time_minutesfor the customer and set, to allow us to define whether SLAs get hit or not in our models. - Add
is_sla_hitoris_sla_missboolean fields based ontarget_first_response_time_minutesandtarget_next_response_time_minutesconfigurable variables in `conversation_metrics. - Add
sla_hitsandsla_missesto eventually calculate SLA hits and misses by admin and company, toadmin_metricsandcompany_metrics.
Describe alternatives you've considered
The SLA metrics we get directly from Intercom do have 'hit', 'miss', 'cancelled' values according to documentation. So we could technically get aggregate SLA hit and miss rate over a particular time period if we want to scope down.
However, we do not know what the actual SLA targets are, customer-by-customer, as they are configurable goals that could very much differ. It'd be better if we set SLA goal metrics on our end based on targets.
If median_next_response_time is too complicated to calculate, it might be worth discussing whether we parse down this to request to only the first_response SLA targets.
Are you interested in contributing this feature?
- Yes.
- Yes, but I will need assistance and will schedule time during your office hours for guidance.
- No.