WEBVTT

1.1
00:00:00.000 --> 00:00:08.800
<v Speaker 1>Let's map out how a tricky issue moves through support teams. The goal is to fix things fast without clogging the pipeline.

1.2
00:00:08.800 --> 00:00:15.200
<v Speaker 2>Each tier focuses on what it does best. Knowing where your ticket belongs saves everyone time.

2.1
00:00:15.200 --> 00:00:22.000
<v Speaker 2>Tier 1 is the front desk. They reset passwords, guide users through quick checks and follow scripts.

2.2
00:00:22.000 --> 00:00:27.200
<v Speaker 1>If the script doesn't solve it, they escalate so the queue keeps moving.

3.1
00:00:27.200 --> 00:00:34.400
<v Speaker 1>Tier 2 technicians dig deeper. They have access to system logs and configuration tools to unravel stubborn faults.

3.2
00:00:34.400 --> 00:00:41.200
<v Speaker 2>When they spot a code bug or design flaw, it's time to bring in Tier 3 specialists.

4.1
00:00:41.200 --> 00:00:48.400
<v Speaker 2>Tier 3 is often the product developers or vendor engineers. They tackle root causes and push permanent fixes.

4.2
00:00:48.400 --> 00:00:54.800
<v Speaker 1>Once resolved, details flow back down so Tier 1 can handle similar issues faster next time.