[Workflows] Triage chat transcripts based on context to the right team via email
SubmittedCustomers want to send each chat transcript to a different team, based on what the chat is about. Today this only works with an AI step, which costs credits for every chat that ends, including the ones it skips.
There are three gaps:
#1 Route on chat context. Let workflow conditions use the context a chat already has:
- Pre-chat form answers (including department and custom fields), and offline form answers for offline messages
- Widget the chat came from (picked by name)
- Visitor attributes and events set with the JavaScript API
- Linked contact
- Visitor country
Today a condition can only check tags, rating, the last message, the visitor's name and email, and whether it was an answered chat or an offline message.
#2 Include the transcript "as is". Let Send email and Create ticket include the chat transcript and the visitor's name and email, for example as an "Attach transcript" option. Today the Fetch conversation output and the visitor's details can't go into these actions, so an AI step has to copy them word for word (which also unnecessarily consumes credits).
#3 Assign tickets. Let Create ticket set a department or agent, with the visitor contact as the requester. Today it has neither field, and the visitor's saved name and email can't go into the requester fields. So a workflow can't open a proper ticket for the right team.
This only covers visitors whose name and email are saved to their contact: by a required pre-chat form, the offline form, a ticket or lead form, or a (human) agent filling them in manually.
Details the visitor only typed in the chat aren't saved. An AI step can pick them out for that run, but a workflow can't save them to the contact: Update contact fields has no email field, its name field doesn't accept runtime data, and a chat trigger gives it no contact to update.
With 1 and 2, this use case needs no AI and no credits. With 3, tickets become a real option for visitors whose details are saved.
Comments (0)
Sign in to post a comment.
No comments yet.