Playbook editor: adding a portal lookup step
Summary In the Playbook editor, a portal lookup step reads what a ticket is about from the portal, without changing anything: an order, its products and their stock, an inwards shipment, or the…
Check yourself
Checking your PaT sign-in…
How To
On this page
Summary In the Playbook editor, a portal lookup step reads what a ticket is about from the portal, without changing anything: an order, its products and their stock, an inwards shipment, or the customer's notification settings. A returns lookup step reads the customer's graded returns in Twoboxes, the returns portal, also without changing anything. On a Sandbox draft, add the step after the one it should follow, choose whether a failed lookup hands the ticket to a person, then save your changes.
Adding a portal lookup step
Step 1
On a Sandbox draft of the playbook, click the step in the diagram that the lookup should come after.
Step 2
Under Add a step after this one, choose the lookup you need: Tool: portal lookup for an order, Tool: order drop time & status to check when an order dropped in and whether it left in time, Tool: portal lookup, order lines and stock to check an order's products and their stock, Tool: portal lookup, inwards shipments for an inwards shipment, Tool: portal lookup, notification settings to see who is emailed when the customer's dockets are confirmed, or Tool: returns lookup (Twoboxes) for a customer's returns.
Step 3
If the step has more than one way out, choose which way out the new step goes on. Type a name for the step, or keep the one shown: Portal lookup, Check order drop time & status, Portal lookup: order lines and stock, Portal lookup: inwards shipments, Portal lookup: notification settings, or Returns lookup (Twoboxes).
Step 4
Leave If it fails, hand the ticket to a person (Lookup failed) ticked, so a failed lookup goes to staff. 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.
What each lookup reads
Step 1
Portal lookup reads the order by its number or reference, and its carrier and tracking.
Note. Check order drop time & status reads the order by its number or reference, and its status; when it dropped into the system, and the day it was due to leave: the same working day if it dropped before the cut-off (1 pm unless the company's settings say otherwise), else the next working day; and whether it left in time, or is overdue. Every order lookup makes this check: this step is named for it.
Note. Portal lookup: order lines and stock reads the order by its number or reference, and its lines: each product and the units ordered. For the first 10 lines it reads each product's stock on hand, the total units in the warehouse, and its stock available: on hand less the units for orders entered or picking, less stock on hold. Given a product code on its own, it reads that product's stock.
Step 2
Portal lookup: inwards shipments reads the inwards shipment by its number, PO or reference, open shipments first and then processed ones. It reads its lines: each product, the quantity expected, its batches, and what was received once it was processed.
Step 3
If the ticket gives no shipment number, the inwards lookup reads the customer's open shipments with the nearest ETAs, and any product the ticket asks about.
Note. Portal lookup: notification settings reads the customer's notification settings: who is emailed, and in which format, when a despatch, inwards or stock adjustment docket is confirmed. It also reads any recipient set for one docket only, account by account. It changes nothing: adding or changing a recipient stays with a CSR, who is told exactly what to add.
Note. Returns lookup (Twoboxes) reads the customer's graded returns in Twoboxes, found by the order, tracking or RMA number in the ticket. For each return line it reads whether it arrived, its grading, its disposition and the conditions graded, with its product and site. It never reads the end customer's name, email or address.
Step 4
All six lookups are read-only: under Changes anything? they say No: read-only. The notification settings lookup adds that a CSR makes any change to a recipient, and the returns lookup adds Never the end customer's name, email or address. The notification settings lookup makes up to 6 requests, the returns lookup up to 4, and the other portal lookups up to 20 each.
Step 5
The portal lookups are offered only when the portal tool is shared with the form, and the returns lookup only when the Twoboxes returns lookup tool is shared with it.
Purpose / Intent of the Module
A brief description of what this module is about
Header One
Rate this page
Checking your PaT sign-in…