Lesson plan
Supporting Moraph products: triage, severity and troubleshooting
Triage problems with Moraph products before you raise a ticket, choose a severity from product-specific examples, fix the common issues yourself, and know when Moraph or a vendor takes over.
- Product
- Moraph Support
- Level
- Practitioner
- For
- Support teams, Administrators
- Total time
- 2 hr 14 min
- Lessons
- 13 in 3 modules
- Assessments
- 4
Course objectives
- Run a consistent triage routine on a reported problem before deciding whether to raise a ticket
- Use Moraph Status and Moraph Docs to rule out known incidents and find documented fixes
- Decide whether a problem belongs to Moraph, your own teams, an outside source or a platform vendor
- Choose a severity for a product problem using the documented examples for that product
- Write a ticket that includes the references and evidence Moraph needs, and leaves out what it must not contain
- Fix the most common issues in Moraph products that are caused by data, roles, settings and Work API keys
- Escalate problems with a managed platform such as Identity Access Management through Moraph, and act on your side during a vendor outage
Before the course
- You have completed Working with Moraph Support, or already know the S1 to S4 severities and how to raise a ticket
- Your account belongs to your organization in Moraph Support, so you can raise tickets at every severity
- You are the help desk, super-user or administrator people go to first when a Moraph product misbehaves
Module 1: Triage before you raise a ticket (35 min)
| Lesson | Type and time | Learners will be able to | Activity and assessment |
|---|---|---|---|
| Your role as first-line support | Reading 9 min |
| Reading |
| A triage routine that works for every product | Reading 11 min |
| Reading |
| Using Moraph Status and Moraph Docs | Reading 9 min |
| Reading |
| Module 1 knowledge check | Assessment 6 min |
| 5 questions · pass mark 70% · unlimited attempts |
Module 2: Severity and tickets (43 min)
| Lesson | Type and time | Learners will be able to | Activity and assessment |
|---|---|---|---|
| Choosing a severity, product by product | Reading 12 min |
| Reading |
| What to put in a product ticket | Reading 10 min |
| Reading |
| Practical: triage a morning of reports | Practical exercise 15 min |
| Practical exercise with a checklist |
| Module 2 knowledge check | Assessment 6 min |
| 5 questions · pass mark 70% · unlimited attempts |
Module 3: Troubleshooting and escalation (56 min)
| Lesson | Type and time | Learners will be able to | Activity and assessment |
|---|---|---|---|
| Common issues and their fixes | Reading 12 min |
| Reading |
| Roles, settings and Work API keys | Reading 11 min |
| Reading |
| Managed platforms and vendor escalation | Reading 12 min |
| Reading |
| Module 3 knowledge check | Assessment 6 min |
| 5 questions · pass mark 70% · unlimited attempts |
| Final assessment | Assessment 15 min |
| 12 of 18 questions · pass mark 80% · 3 attempts |
Completing the course
Every lesson must be completed: reading lessons are marked complete by the learner, exercises when every checklist item is confirmed, and assessments only when passed. Completing the course issues a certificate of completion with a verification code.