Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Metrics for "Zendesk Messaging" tickets are incorrect #125

Closed
2 of 4 tasks
elishasand opened this issue Nov 9, 2023 · 3 comments
Closed
2 of 4 tasks

[Bug] Metrics for "Zendesk Messaging" tickets are incorrect #125

elishasand opened this issue Nov 9, 2023 · 3 comments
Labels
type:wontfix This will not be worked on

Comments

@elishasand
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the issue

Zendesk Messaging is an alternative to Zendesk Live Chat.

The Messaging conversation with the user is saved as a ticket and this is the only entity we have to work with when analyzing our Messaging performance (There is no designated API like with ZD Live Chat).

The problem is that the metrics calculated here by Fivetran for ZD Messaging tickets are off.

This mostly has to do with how the Messaging data is saved in the Comments table.
For example he logic used:

case when coalesce(ticket_comments.count_public_agent_comments, 0) = 0
    then null
    else ticket_reply_times_calendar.first_reply_time_calendar_minutes
end as first_reply_time_calendar_minutes,

This created many nulls for Messaging tickets since the actual replies are not logged as individual comments and so many times the count_public_agent_comments = 0 although the agent has responded many times.

Is there a way to fix this and address the ZD Messaging tickets metrics?

Relevant error log or model output

No response

Expected behavior

Calculate ZD Messaging ticket metrics correctly

dbt Project configurations

ZD Messaging metrics are calculated correctly.

Package versions

dbt_zendesk

What database are you using dbt with?

snowflake

dbt Version

1.6.6

Additional Context

No response

Are you willing to open a PR to help address this issue?

  • Yes.
  • Yes, but I will need assistance and will schedule time during our office hours for guidance
  • No.
@elishasand elishasand added the bug Something isn't working label Nov 9, 2023
@fivetran-joemarkiewicz
Copy link
Contributor

Hi @elishasand thanks for opening this issue! This is actually something that has come up in the past and I believe is being actively being investigated at the connector level. Since the messaging and chat data comes in as a single comment, it is quite difficult for us to parse through this and calculate proper metrics from the data as it currently is synced.

As such, we are planning to hold off on making any updates to the dbt package until there is an update from the connector side to properly handle chat and messaging tickets. I would recommend opening a support ticket to let our connector team know that this is something you would like to see. Once this update is applied at the connector we will then make the appropriate updates to the data model.

Thanks!

@fivetran-joemarkiewicz fivetran-joemarkiewicz added type:wontfix This will not be worked on and removed bug Something isn't working labels Nov 14, 2023
@fivetran-joemarkiewicz
Copy link
Contributor

Marking this as wont fix until appropriate updates are applied at the connector level.

@fivetran-joemarkiewicz
Copy link
Contributor

I will close out this issue as the connector will soon support the Zendesk Messaging tickets. While this has not yet been rolled out to the connector, it should be live in the near future. Please be sure to follow Issue #137 for progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants