Kustomer Conversations notifying a channel in Slack

Hi there!

As a food manufacturer, I want Kustomer conversations around food safety and quality (FSQA) escalated to our FSQA team in a Slack channel, so that they can have immediate visibility into these situations to provide guidance to our service agents.

I currently have a workflow set up that, if an attribute is set to a relevant FSQA issue, or it is changed to one of those issue types, it will trigger a Rest API step to Zapier. From Zapier, depending on the issue type, I will populate different information into a a channel message in Slack, tagging the relevant folks from our production facility. For updates on the same conversation, I thread those messages within the original one (I needed to institute a delay step to ensure that the threading worked)

What I'm noticing, however, is that Kustomer is treating each individual attribute update on the conversation as a separate request, so my Zapier queue gets backlogged, and we receive multiple spam messages for irrelevant or out of date updates.

Any one else encounter this or have a suggestion for me?

4 replies