Appearance
Waiting and choosing
Four steps change how a rule goes on: Wait holds it for a while, If… else… chooses between two sets of steps, Run another rule runs a shared rule, and Stop ends it.
Wait: chase a ticket that waits for the customer
Step: Wait. When a ticket is put on Waiting, the customer gets a reminder three days later. If there is still no answer four days after that, the ticket is solved, with a comment saying why. If the ticket changes in the meantime, the rule stops by itself.
Administration › Automation, Entity: Tickets, Add a rule.
Name:
Chase waiting tickets.When: A record is changed, only when Status changes.
Only if: Status is any of Waiting.
Add a step: Wait. Leave For a while, and set
3days. Leave Then go on only if the record still meets the rule’s conditions ticked.Add a step: Send an email. To: The address in Customer › Email. Text: Written here. Subject and Email:
twigDo you still need help with "{{ subject }}"? Hello {{ customer.name }}, we are waiting for your answer. Reply to this email and we will go on.Add a step: Wait, For a while,
4days, the same setting ticked.Add a step: Set fields, Status, To a value, Solved.
Add a step: Add a comment:
Solved by the rule: no answer for a week.Save the rule.
While it waits, the run's state in the Runs tab is Waiting, until the time shown. When the wait is over, the setting you left ticked checks the conditions again: if the customer answered and the ticket is Open again, the run is Stopped, and nothing more is sent.
Wait can also be Until a date of the record: for example 2 daysbefore Expected close at 09:00, for a deal. A wait lasts a year at most. Waits need cron.
Stop: nothing to send without a customer
Step: Stop. The rule above writes to the ticket's customer. A ticket without one should not go on. Put this before the first step:
- Open the rule Chase waiting tickets again (click its name in the list). Add a step: If… else…. In its settings, click Up until it is step 1.
- Under If the record, as it is now, matches, add the condition Customer is empty.
- Under Then, click Add a step to “then”, Add a comment:
No customer to write to: the ticket is not chased. - Add a step to “then” again, Stop.
- Leave Else empty, and Save the rule.
Stop ends the run: no step after it runs, in the branch or after it. The run shows as Stopped.
If… else…: urgent or not
Step: If… else…. Every new ticket gets an assignee: an urgent one goes to Sue, the others to the Support people in turn.
- Entity: Tickets, Add a rule, Name:
Assign new tickets. - When: A record is created. Leave Only if as Always: the rule is for every new ticket.
- Add a step: If… else…. Its settings have three parts.
- If the record, as it is now, matches: add the condition Priorityis any of Urgent.
- Under Then, Add a step to “then”, Assign someone: In the field Assignee, Who A given person, The person Sue Helper.
- Under Else, Add a step to “else”, Assign someone: In the field Assignee, Who The next of a role’s or a team’s people, in turn, Whose people take turns Support.
- Save the rule.
The steps of a branch are numbered under their If (1.then.1, 1.else.1). The run shows which branch was taken. A branch can hold another If… else…, three levels deep. The condition looks at the record as it is when the step runs, so it sees what earlier steps changed.
Run another rule: share steps between rules
Step: Run another rule. Several rules should tell the support team the same way. Write the steps once, in a rule that only other rules run.
The shared rule:
Entity: Tickets, Add a rule, Name:
Tell the support team.When: Another rule runs it. Nothing sets it off by itself.
Add a step: Send a notification, To: Support (a role), Message:
twig{{ subject }} needs a look.Save the rule.
Using it: in the rule Assign new tickets above, open the If… else… step and, under Then, click Add a step to “then”, Run another rule, and choose The rule: Tell the support team. Do the same in A comment reopens a waiting ticket. Change the shared rule once, and every rule that runs it follows.
The shared rule runs for the same record. If it has conditions, they are checked first; if the record does not meet them, it does not run. Only rules of the same entity can be run this way.