Who this is—and is not—for
Designed for: Support agents, quality teams and support managers.
Not designed for: Teams expecting unsupervised replies or unsupported policy interpretation.
Starting requirement: Approved assistant and a fictional source pack with escalation rules.
What participants leave with
Reviewed cited support workflow with escalation cases. The work remains accompanied by the method, evidence and limitations needed for someone else to review it.
Representative curriculum
- Grounded answers
- Classification and quality review
- Escalation
Standard 1.5 days agenda
| When | What happens |
|---|---|
| Before event | Device, account, network, permissions and safe-data preflight |
| Day 1 · 09:30–12:30 | Orientation, working examples, workflow choices, safety and capstone selection; includes a short break |
| 12:30–13:30 | Lunch |
| 13:30–14:45 | Guided build |
| 14:45–15:00 | Break |
| 15:00–16:45 | Individual or team application with a fallback starter |
| 16:45–17:30 | Verify, document limits and prepare the presentation |
| Day 2 · 09:00–12:30 | Showcase, feedback, recognition and next commitments |
Tools and preparation
The final toolchain is approved before delivery. Participants need a laptop, working accounts, permitted browser and network access, and either safe data or the supplied synthetic fallback. Product names are not guessed before the buyer and faculty approve them.
Showcase and assessment
For the standard 1.5-day format, each presenting unit receives ten minutes plus two minutes for feedback and changeover. Assessment covers usefulness, correctness and evidence, repeatability, safe handling and explanation. A critical factual or data error requires rework.
Price and dates
No exact rate or delivery window has been approved. This outline therefore shows Register interest and Dates not released. A preference is reviewed by staff against the complete external calendar; it never reserves a slot.
Possible alternative: Native may fit when the audience or intended output differs.