How to route Support Requests by AI Intent detection?

Use ZENIE intent when customers describe the same problem in different ways.


Recommended Settings

Setting

Recommended Value

Conversation status

Open

Channels

Any, or selected support channel accounts

Message matching

ZENIE intent

Example intent

Support queries - “Product Enquiry”, “Doubts”, “Help” 
Finance queries -  "Billing", "Payments", "Invoice"

Re-enrollment

Enabled for repeat assistance

Follow-up actions

Route the conversation to the appropriate support team or finance team and apply an issue tag


Example

“I cannot sign in” and “I am having trouble accessing my account” may express the same intent without sharing an exact configured phrase.


For one status event, ZEPIC selects at most one matching intent flow. Independently matching keyword or state-only flows may also enroll. Avoid conflicting intent configurations across active flows with overlapping statuses and channels.


Configure and Activate the Flow

  1. Use the organization’s standard Contact object.

  2. Add the Conversation Status Change trigger.

  3. Apply the recommended settings above.

  4. Connect the trigger to the required workflow actions.

  5. Validate the flow, resolve configuration errors, and launch it.


Only the Active flow’s launched definition is used for enrollment. Publish draft changes before expecting them to affect the running flow.


For eg., you can create 2 flows to route support queries to one team, billing related queries to another team as shown


Flow 1


Support queries flow being routed to Support team members



Flow 2


Billing queries flow being routed to finance team members



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article