Playbook editor: adding a step that cancels an order
Summary In the Playbook editor, the step Cancel the order in the portal comes after a conclusion. Once a person approves the run's card, it cancels the customer's order in the portal, but only while…
Check yourself
Checking your PaT sign-in…
How To
On this page
Summary In the Playbook editor, the step Cancel the order in the portal comes after a conclusion. Once a person approves the run's card, it cancels the customer's order in the portal, but only while the order is Entered. First it adds the ticket number to the order's instructions and saves the order, then it cancels the order with a reason and says when it is done. A shadow run never cancels anything.
Adding the cancel step
Step 1
On a Sandbox draft of the playbook, click the conclusion step in the diagram: the step where a person approves the run.
Step 2
Under Add a step after this one, choose Writes: cancel the order in the portal. It is offered only after a conclusion, or after another step that writes.
Step 3
In the list beside it, choose the way out that starts On "Approved", so the order is only cancelled after a person approves.
Step 4
Type a name for the step, or keep the one shown: Cancel the order in the portal. Then click Add step.
Step 5
The page says Step added. Name it and fill in its details, then Save changes. Click Save changes to keep the new step.
Step 6
The cancel step is offered only when the portal's cancel tool is shared with the form.
What the step does
Step 1
The step's details say what it does: once a person approves the run's card, it cancels the order in the portal, only while it is Entered.
Step 2
Before it cancels, it adds the ticket number to the order's instructions, as PaT ticket: and the number, and saves the order.
Step 3
It cancels with a reason from the account's own list. Under Reason, the details say AI chooses (most often Customer Request).
Step 4
An order past Entered is never cancelled: it goes to a CSR.
Step 5
Under In shadow, the details say Never: a shadow run only says what it would do.
When it cancels, and when it does not
Step 1
The step needs an earlier portal lookup in the same run that found exactly one order. Without one, it cancels nothing and a person needs to look.
Step 2
At the conclusion, the AI decides whether the ticket asks for the order to be cancelled, and chooses the reason. If the ticket does not ask, nothing is cancelled.
Step 3
The run's card offers the cancel only when the ticket's title starts with its PaT ticket number and the ticket has a staff assignee.
Step 4
In a shadow run, the step's line says what it would do, or why it would not cancel.
Approving a cancel
Step 1
When the run would cancel, its card in the ticket's chat says Approve also cancels the order, and names the order.
Step 2
The card says what Pat Bot will do: add the ticket number to the order's instructions and save the order, then cancel it with the chosen reason, and say in the chat when it is done.
Step 3
If anything else on the order changes, or it is no longer Entered, nothing is cancelled and you are told.
Step 4
Disapprove cancels nothing.
Step 5
Approve does not send the reply to the customer: send it yourself once the cancel is confirmed.
Step 6
A cancel is never tried twice.
Step 7
Until PaT turns cancelling on, no card offers a cancel, and no order is changed or cancelled.
Purpose / Intent of the Module
A brief description of what this module is about
Header One
Rate this page
Checking your PaT sign-in…