Automating your work using customer intents

Updated 1 month ago by Victor Suo

If you're not familiar with the basics on Rules in Gorgias check out the articles below before you get started: - Rules - getting started

Customer intents

If you want to automate repetitive tasks, such as tagging tickets or responding to common questions, but do not want to spend a lot of time writing rules triggers, Gorgias offers a much more convenient way to simplify rules by using detected customer intents.

Each time a new customer message arrives, we take a guess at figuring out the customer's intent. Intents include:

  • shipping/status
  • refund/request
  • exchange/request
  • order/damaged
  • order/cancel
  • and many others

Intent detection supports 104 languages, so even if the customer is writing over to you in another language, we can detect the keywords and trigger the rule!

Intents can be used to automate your ticket processing workflow. Here is how.

Common use cases

1. Intents are used as triggers within rules

Even if customer intents are automatically detected on all customer messages, they do not trigger automated actions by themselves. In fact, intents are just additional information embedded within rules and the best way to think about intents is to consider them as automated, optimized triggers in rules.

The two following screen captures show the kind of rules logic that can be simplified by intents:

Without using customer message intents (long, tedious, non comprehensive)

Using customer message intents (easy and comprehensive)

2. Tagging tickets using customer intents
  1. In Settings, go to Rules and click Create new rule
  2. Select WHEN new message in ticket and/or ticket created as a trigger
  3. Click on THEN, and select an IF statement
  4. Select message -> intents -> contains one of -> "shipping/status"
  5. Click on following THEN, select Add tag as an action, and type "ORDER-STATUS"
  6. Click Save
  7. Don't forget to activate the rule!

This example shows a simple rule tagging tickets for "shipping/status", ''order/cancel' and "refund/request" intents.

Now, each time you receive a customer message asking about an update on a delivery or an unusual delay, that ticket will be automatically tagged!

You can then filter tickets based on customer intents by creating views.

2. Setting auto-replies based on customer intent

Some customer intents are suitable for automatic replies such as "shipping/status". For that, you can set up a rule that would apply a specify macro when an intent is found on a new customer message.

Since we generally don't want to auto-reply multiple times in a given ticket, we recommend to add a "auto-reply" tag when auto-replying to tickets using intents and use an additional filter to avoid avoid auto-replying twice.

List of customer intents

Name

Description

account/cancel

Deprecated

discount/policy

Deprecated

discount/request

Asks for a discount or needs help applying one

exchange/policy

Deprecated. Merged in exchange/request

exchange/request

Requests to exchange a received product or get a replacement

exchange/status

Requests a status update on an ongoing exchange

feedback/positive

Positive feedback from a customer

feedback/negative

Negative feedback from customer

email/unsubscribe

Deprecated

job/application

Deprecated

order/cancel

Requests to cancel an order before it ships

order/change

Requests to edit an order before it ships

order/damaged

Received order contains damaged item or customer needs troubleshooting

order/wrong

Received order contains wrong/missing item

other/no_reply

A message that does not need a reply. The ticket can probably be closed*

other/question

General question on product, brand, policies ...

other/thanks

The customer expresses gratitude. The ticket can probably be closed**

product/question

Question about a specific product (usage, properties...)

product/recommendation

Requests help chosing a product (size, color, model...)

password/reset

Deprecated

refund/policy

Deprecated. Merged in refund/request

refund/request

Requests to proceed a refund

refund/status

Requests a status update on an ongoing refund. Can overlap with return/status

return/policy

Deprecated. Merged in return/request

return/request

Requests to return a received product

return/status

Requests a status update on a received product

shipping/change

Requests to change shipping information (address, name)

shipping/delivery-issue

Notifies of an error with a package (lost, not in the mailbox...)

shipping/policy

Asks information on shipping (countries, usual delays)

shipping/status

Asks a status update on an expected order

stock/request

Asks about the availability of a product

subscription/cancel

Requests to cancel a subscription (auto-shipment, monthly order)

subscription/change

Requests to edit a subscription (frequency, content...)

*other/thanks intent: This intent is often found on messages where the customer is concluding a ticket with a kind word or a thank you message to the agent. Examples of messages that correspond to this intent are "Great - thanks so much! Appreciate the quick response and follow up!", "Thanks so much! Will do!", "Oh ok cool. I think we'll all end up ordering one! Have a great night!" , "". Finding an 'other/thanks' intent on a message often means the ticket can be closed.

**other/no_reply: This intent is often found on messages that do not need to be replied to. Messages that correspond to this intent are for example "Your Amazon order has just been delivered" or "Call ended. Duration: 57s" or "A customer just ordered a ...". Finding an 'other/no_reply' intent on a message often means the ticket can be closed. Social media tags also fall into this category.

Supported languages

Intent detection works in most commonly spoken languages, so it's a huge advantage over writing custom rules with keywords! The main languages supported are, but 104 languages are supported in total:

  1. Arabic (ar)
  2. Chinese (PRC) (zh)
  3. Chinese (Taiwan) (zh-tw)
  4. Dutch (nl)
  5. English (en)
  6. German (de)
  7. French (fr)
  8. Italian (it)
  9. Portuguese (pt)
  10. Spanish (es)
  11. Japanese (ja)
  12. Korean (ko)
  13. Russian (ru)
  14. Polish (pl)
  15. Thai (th)
  16. Turkish (tr)

FAQ: Common questions

  • How does intent classification work?
    • Gorgias intent classification system is based on state-of-the-art artificial intelligence algorithms. You have nothing to do. It's fully automated!
  • The intent found is wrong, what should I do?
    • Unfortunately, that can happen as language comprehension is hard. There are usually a lot of ways to say the same thing. You can combine message intents with simple logic for a better result.
  • Can I use message intents along with usual rules logic (IF ... THEN)?
    • Of course. Please do so.
  • Can a single message have multiple intents?
    • Yes, each message can have multiple intents. Besides, if you use intents to auto tag tickets, tickets will be tagged with the intents of all messages it includes.
  • Do all messages have an intent?
    • No, there is a predefined list of possible intents. Moreover, when the system is not confident about a prediction, it will not detect the intent.
  • Can I add an intent to the list of intents that can be detected?
    • No, but you can definitely contact us any particular request of feedback you may have!


How did we do?


Powered by HelpDocs (opens in a new tab)