# Confluence Extract — Product Operations

**Exported:** 2026-03-28 08:00 UTC
**Space:** PO1
**Pages included:** 3

## Tier 2 Ticket Guidelines

**Space:** PO1 | **Last updated:** 2026-01-07 by H. Evans

### Overview
This page covers the standard process for handling tier 2 ticket guidelines within the Product Operations team.

### Steps
1. Escalate payment flow status in Jira
2. Escalate onboarding compliance in Jira
3. Document payment flow configuration in CSP
4. Document api compliance in CSP
5. Escalate dashboard records in Confluence
6. Review payment flow records in CSP

### Key Thresholds
- Risk score > 80: Escalate immediately
- Stable + Major = Status conflict, investigate before proceeding

### Contacts
- Team Lead: P. Young
- Escalation: H. Evans

---

## Complaint Audit Checklist

**Space:** PO1 | **Last updated:** 2026-01-12 by N. Clark

### Overview
This page covers the standard process for handling complaint audit checklist within the Product Operations team.

### Steps
1. Review payment flow data in Jira
2. Check terminal configuration in Jira
3. Review dashboard records in CSP
4. Check api status in CSP
5. Escalate payment flow documentation in CSP
6. Update api data in Confluence

### Key Thresholds
- Risk score > 80: Escalate immediately
- Declining + Critical = Status conflict, investigate before proceeding

### Contacts
- Team Lead: O. Lewis
- Escalation: P. Young

---

## Help Centre Content Review

**Space:** PO1 | **Last updated:** 2026-01-19 by Q. Harris

### Overview
This page covers the standard process for handling help centre content review within the Product Operations team.

### Steps
1. Confirm payment flow compliance in Jira
2. Confirm onboarding status in CSP
3. Check terminal compliance in Confluence
4. Escalate onboarding data in Jira
5. Document payment flow data in CSP

### Key Thresholds
- Risk score > 80: Escalate immediately
- Active + Major = Status conflict, investigate before proceeding

### Contacts
- Team Lead: A. Smith
- Escalation: Q. Harris

---