PPaT Wiki
DocumentationPathwayForumBlogContact
Week streakFOUNDATION0 badges
Language: English
  • English
  • Nederlands
  • Français
  • Deutsch
  • Lea faka-Tonga
  • Te reo Māori
  • မြန်မာ (Burmese)
Ask the community

Your PaT Pathway

0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
  • Company Structure: adding a new user
  • Company Structure: customer companies
  • Company Structure: departments, job titles and roles
  • Company Structure: modules for a site or a country
  • Company Structure: process categories
  • Connections: linking PaT to Microsoft 365
  • Forms - API Integration
  • How to create a campaign for the PaT Lite training portal
  • How to edit an existing Bulletin Board Post
  • How to set up your SD Map
  • LMS Feedback: learner ratings and comments
  • LMS Metrics - If you can't measure it, you can't manage it
  • Manage users
  • Pacing recertifications and escalations
  • PaT Business Unit Template Overview
  • SD Workflows - Multi Submit
  • SD Workflows - Workflow Settings
  • System Activity: escalations, logins, emails and more
  • System Config: company settings
  • The org chart
  • Add any Image as a Section Header Icon
  • Assigning an SD to a new parent
  • C2E Attachments
  • Chat reminder
  • Chat to email to chat
  • Chat to SD
  • Chat to task to project
  • Comprehension Audits
  • Customer-specific training: how it works
  • Different Form Uses
  • Docked Chats
  • Docking SDs and Updating Images
  • Email to BFF
  • Email to chat to email – non PaT users
  • Embedding live data in an SD (graphs and spreadsheets)
  • Embedding SDs in SDs
  • Evidential audits: completing one
  • Filing and retrieving SDs
  • Form Wall
  • Health and safety templates
  • How PaT Manages Inactive Users
  • How SD chats work with SD Members and External Users
  • How to unlock a module for a staff member
  • Info Icons
  • Inline chats
  • Invite Attendees
  • LMS Architecture
  • Moving Section Headers
  • Multi-Tasks
  • PaT AI
  • Pop-Out Chat Feature
  • Recurring tasks: create and edit
  • Running Meetings with SDs
  • Safe Walks
  • SD Element Categorisation
  • SD Form Responses: finding and exporting form responses
  • SD Owner Functions
  • SD Task wall view
  • Share and record your screen
  • Task Integrity: what it is and why it drops
  • Track Engagement
  • Using SDs as a report or meeting minutes app
  • Video rooms: guests joining and asking to record
  • Activity Notifications
  • Add members and set permissions
  • AI Summary: a quick summary of an SD
  • Capture and Manage Accidents
  • Capture and Manage Hazards
  • Chat to task
  • Chat Wall
  • Company wiki: searching your company's own modules
  • Contextual Communication
  • Convert a Note to a Task
  • Create a new SD
  • Create a Task
  • Critical Chrome Extensions
  • Document Store: shared links, your folders and favourites
  • Fast Notes
  • Getting help: the PaT Helpdesk
  • Global Search
  • Group Chats
  • How to embed Outlook onto your PaT
  • How to resize your browser to best view PaT
  • How to use the PaT Lite training portal
  • Insert links
  • Module Learning - Desktop
  • Module Learning - Mobile
  • My Profile
  • Newbie PaT Intro – Chats and SDs
  • Notes
  • Out Of Office: turning it on, and the calendar on your Task Wall
  • Outlook 2FA Issue
  • PaT Chat Overview
  • PaT Mobile App – Overview
  • PaT service status: the status page, status alerts and status notices
  • PaT Wiki: finding your way around
  • PaT Wiki: searching, the AI answer and rating it
  • Preview, download and share files
  • Publish a Bulletin Board Post
  • Reading an SD in another language
  • Release-note alerts: a Sys Bot chat when PaT's release notes change
  • SD Elements
  • SD Main page useful features
  • SD Overview
  • Section Headers
  • Security measures for multiple users on a device
  • Share Feedback
  • Signing in to PaT and resetting your password
  • Signing in with MFA: the second step
  • Task Management
  • Task Management System
  • Task Wall
  • The connection icon on your PaT desktop
  • Traffic light progress
  • Upload file attachments
  • Video calls on the mobile app
  • AI Playbook: checking for other tickets with the same number
  • Auto Escalation
  • Build a reporting system
  • Calculated fields and calculated columns
  • Charts: options for lines, bars, axes and single values
  • Chat Management - Pro Tips
  • Conditional Formatting
  • Configuring a UDF: columns and calculated columns
  • Configuring a UDF: filters, grouping and endpoint details
  • Customer-specific training: setting it up
  • Data sources: stage filters, dynamic dates and page values
  • Endpoint Manager: finding endpoints and building your own UDF
  • Form builder: field types
  • Form Builder: layout at each screen size
  • Form Builder: tools and shortcuts
  • Form buttons, PDFs and what happens after submit
  • Form fields: defaults, read-only and other settings
  • Form Test Mode
  • Forms - Extract Data (the AI form builder)
  • Grids linked to a reporting SD: history charts and review comments
  • Grids: columns, formats and filters
  • Grids: conditional formatting
  • Grids: flatten and transpose data
  • Grids: rows, default values and editing rules
  • How managers can turn on OOF for their staff
  • How to build modules in the Module publisher
  • How to create module comprehension audits
  • How to create module evidential audits
  • How to create module quizzes
  • How to embed an SD into the LMS
  • How to make form templates live for everyone to use
  • How to upload form elements to an SD
  • How to use the PAR SD
  • Live H&S Reporting
  • Mastering the Business Strategy Template
  • Module Admin: finding and managing modules
  • Module Completion Notification Setup
  • Module Publisher Content Options
  • PaT SD Map Overview
  • PaT SD Map Presentation
  • PaT SD Templates Overview
  • Playbook Admin: the tickets behind each Quality and Cost category
  • Playbook Admin: when your shadow run is ready to review
  • Playbook editor: adding a portal lookup step
  • Playbook editor: adding a step that cancels an order
  • Pure Forms
  • Required fields, validation and containers
  • Rich text, file uploads and speech to text
  • SD Dashboard: building a dashboard
  • SD Forms
  • SD Security Settings
  • SD Template Helper Functions
  • Stacked views, flip cards, tabs and stages
  • Strategy System
  • Throttling
  • Using Chat to SD to go from being a good manager to a great one
  • Using SDs as the LMS Document
  • PaT Lite: Key aspects of PaT you need to understand
  • What is PaT and why it matters
  • PaT Lite: Chat to Task
  • PaT Lite: Introducing Strategy Documents
  • PaT Lite: Core Philosophy - Standards and Tactical Execution
  • PaT Lite: Intelligent tools that think with you
  • PaT Lite: The Future of business is Culture
  • Security
  • Integrations
0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
  1. Documentation
  2. Advanced
  3. AI Playbook: checking for other tickets with the same number

AI Playbook: checking for other tickets with the same number

Summary When the AI Playbook works on a ticket, it first reads and understands it. Straight after that, it checks for other tickets from the same customer that carry the same order, inwards or…

Check yourself

Checking your PaT sign-in…

How To

On this page
  • How the check works
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • What staff see
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Where the numbers come from
  • Step 1
  • Step 2
  • Step 3
  • Purpose / Intent of the Module
  • Header One

Summary When the AI Playbook works on a ticket, it first reads and understands it. Straight after that, it checks for other tickets from the same customer that carry the same order, inwards or consignment number, open or closed. It shows staff up to five of them, newest first, so nobody starts a second investigation into something that is already being handled.

How the check works

Step 1

The check runs by itself on every Playbook run: you don't need to start it. It runs right after the Playbook's first AI step, once the ticket has been understood. In the Playbook's list of tools it is called Check other tickets.

Step 2

It looks for the ticket's numbers: the Order Number, Inwards Number and Ticket/Consignment Number answered on the ticket form, and order or reference numbers written in the ticket itself.

Step 3

It searches the same customer's other tickets, open and closed. Only tickets from the same customer company are matched.

Step 4

Numbers match even when they are typed a little differently: a # sign, spaces, and capital or small letters are ignored. Other differences, such as a missing digit, are not matched.

Step 5

It keeps up to five matches, newest first.

What staff see

Step 1

For each match, the Playbook shows the other ticket's number with a link to open it, who raised it and when, and whether it is open or closed.

Step 2

It also shows how the other ticket was resolved: its Resolution Summary, or the staff's last note on it when it has no summary.

Step 3

Pat Bot's note to staff names each match with its link, and the run's links include each one, so the earlier ticket opens in one click.

Step 4

Read the earlier ticket before you reply. If it is still open, carry on that investigation instead of starting a second one. If it is closed, check how it was resolved before you decide what to do.

Where the numbers come from

Step 1

A new ticket's numbers are filed within about 15 minutes of it arriving, from the three number fields on the ticket form.

Step 2

When a ticket is finished, the numbers mentioned in its chat and in its Resolution Summary are filed too.

Step 3

Tickets from before November 2026 were filed once, when the check was switched on, so older tickets can be found as well.

Purpose / Intent of the Module

A brief description of what this module is about

Header One

Ready? Back to the quiz

Rate this page

Checking your PaT sign-in…

PreviousVideo calls on the mobile appNext Auto Escalation

On this page

  • How the check works
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • What staff see
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Where the numbers come from
  • Step 1
  • Step 2
  • Step 3
  • Purpose / Intent of the Module
  • Header One
PPaT Wiki

Documentation, knowledge base and community support for People and Tasks.

Documentation

  • Getting started
  • Core concepts
  • Integrations
  • API reference Coming soon

Support

  • Knowledge base
  • Release notes
  • Community forum
  • Contact us
  • Service status

Company

  • PaT
  • Blog
  • Terms
  • Privacy

© People and Tasks. All rights reserved.