|
1 | 1 | ---
|
2 |
| -title: 'Workflow Rules' |
| 2 | +title: "Workflow Rules" |
3 | 3 | ---
|
4 | 4 |
|
5 |
| -<Frame></Frame> |
| 5 | +<Frame> |
| 6 | +  |
| 7 | +</Frame> |
6 | 8 |
|
7 |
| -<br/> |
8 |
| -<Info> |
9 |
| -Workflow Rules are available on the [Grow pricing plan](https://www.plain.com/pricing) and above. |
| 9 | +<br /> |
10 | 10 |
|
11 |
| -If you are interested in trying this feature, please reach out to us at [email protected] or via our shared Slack channel. |
| 11 | +<Info> |
| 12 | + Workflow Rules are available on the [Grow pricing plan](https://www.plain.com/pricing) and above. |
12 | 13 |
|
| 14 | + If you are interested in trying this feature, please reach out to us at [[email protected]](mailto:[email protected]) or via our shared Slack channel. |
13 | 15 | </Info>
|
14 | 16 |
|
15 |
| -You can use workflow rules to help you automate your team's processes. |
| 17 | +You can use workflow rules to help you automate your team's processes. You can either choose from pre-defined conditions, or use our "Matches AI prompt" field to trigger actions. |
16 | 18 |
|
17 | 19 | Some common use-cases include:
|
18 | 20 |
|
19 | 21 | - Assign someone to handle all support requests from a given company or tier (e.g. Enterprise)
|
| 22 | +- Automatically ignore spam messages |
20 | 23 | - Set a threads' priority if it includes certain key phrases
|
| 24 | +- Route demo requests or trial extension threads to your sales team |
21 | 25 | - Assign threads based on the used support email (e.g. Give all security@ emails to Jane)
|
22 | 26 |
|
23 | 27 | To manage your workflow rules go to **Settings** → **Workflow Rules**.
|
24 | 28 |
|
25 |
| -When building a new rule, you can choose among a set of **conditions** which result in one or more **actions**. |
| 29 | +When building a new rule, you can choose among a set of **conditions** which result in one or more **actions**. You can also use the "AI match prompt" to write exactly what your trigger should be. |
| 30 | + |
| 31 | +There are a few conditions you can choose from, based on the thread's attributes: |
26 | 32 |
|
27 |
| -There are a couple of conditions you can choose from, based on the thread's attributes: |
28 | 33 | - a given label is applied
|
29 | 34 | - is from a given company
|
| 35 | +- belongs to tenant |
30 | 36 | - is from a given slack channel
|
31 | 37 | - is from a specific support channel (Slack, MS Teams, chat, API)
|
32 | 38 | - has a specific tier (ie Enterprise)
|
33 |
| -- is for a specific support address (ie [email protected]) |
| 39 | +- is for a specific support address (ie [[email protected]](mailto:[email protected])) |
34 | 40 | - contains a certain keyword (ie vulnerability)
|
35 | 41 |
|
36 | 42 | When the chosen condition matches a thread, you can perform any of the following actions:
|
| 43 | + |
37 | 44 | - assign someone to the thread
|
| 45 | +- set thread status |
| 46 | +- set tier |
38 | 47 | - set the thread priority
|
39 | 48 | - apply a given label
|
40 |
| -- add a customer to a customer group |
41 |
| -- add a note to a thread |
| 49 | +- add a customer to a customer group |
| 50 | +- add a note to a thread |
0 commit comments