Complaint escalation at Penvale Dental, a fictional dental practice

Decision flowchart slide for escalating a patient complaint

A decision flowchart slide shows a process that forks, with diamond shaped questions sending the work down different paths depending on the answer. This one tells the front desk at Penvale Dental, a fictional practice, exactly when a patient complaint goes to the practice manager and when the desk resolves it.

Create a presentation with OneCraftOne 1920 × 1080 slide on the Process: Decision Flowchart layout

When to Escalate a Complaint

Penvale Dental front desk, every patient complaint, in person, by phone or by email.

YesNoYesNoYesNoComplaint inLog same dayClinical?Tell manager nowDesk fix?Fix and confirmOver $200?Manager, 2 daysDesk lead, 5 daysDentist callsReply and logClosed

04

The finished slide as it renders, built on the Process: Decision Flowchart layout.

What is on the slide

Title and scope
When to Escalate a Complaint. Penvale Dental front desk, every patient complaint, in person, by phone or by email.
Decisions
Three diamonds: Clinical?, Desk fix?, Over $200?, each with Yes and No branches.
Paths
Clinical yes: Tell manager now, Dentist calls. Desk fix yes: Fix and confirm, Closed. Over $200 yes: Manager, 2 days. Over $200 no: Desk lead, 5 days.
Ends
Starts at Complaint in and Log same day. Every branch ends at Closed, all but the desk fix through Reply and log.

When this is the right slide

Pick this slide when staff must follow a process that forks on yes or no questions, and the thresholds and owners need to be visible at the exact point each decision is made.

What to swap it for

Tree: Yes/No Binary Flow. Use the yes and no tree when there is one root question and each answer needs a verdict card and two details rather than a branching chain.

What this slide shows

The title reads When to Escalate a Complaint, and the framing line covers every patient complaint at the Penvale Dental front desk, in person, by phone or by email. The flowchart runs left to right across twelve nodes. It starts at a pill, Complaint in, then Log same day, then the first diamond, Clinical? A yes goes to Tell manager now and Dentist calls. A no goes to the second diamond, Desk fix? A yes goes to Fix and confirm, then Closed. A no reaches the third diamond, Over $200? A yes goes to Manager, 2 days and a no to Desk lead, 5 days. Dentist calls, Manager and Desk lead all flow into Reply and log, then Closed. Only three shapes appear: pills for the start and finish, rectangles for actions and diamonds for questions. The diamonds carry Yes and No on their outgoing lines, so nobody has to guess which way a branch runs. The framing line above the chart lists the three ways a complaint can arrive, which makes it clear the chart applies to all of them.

When this is the right slide

Use a decision flowchart slide when a process forks on a question and staff need to know which way to go: complaint handling, refund approval, triage, access requests. It replaces a paragraph of if and then rules with a picture people can follow in the moment. It is the wrong slide for a straight sequence with no decisions, which a stepped process slide shows with more room for detail, and for a single yes or no choice with a long explanation on each side, which a binary tree layout gives more space to. The slide also suits induction for new reception staff, a refresher after a complaint went wrong, or a quality audit where the practice has to show it has a clear escalation path. Printed on A4, the same chart can sit beside the front desk phone, so the training slide and the working reference are one and the same picture.

How to adapt it

First, add the response time to each end step, for example Reply in 10 days, when the audience is a manager checking compliance rather than staff learning the steps. Second, replace a rectangle with a circle for a waiting state, such as Awaiting patient reply, so pauses look different from actions. Third, split the chart in two when it needs more than twelve nodes, ending the first at a pill named after the second chart's start. Keep diamond labels to a short question with a question mark, and print the full policy wording in the speaker notes. When the chart is used in a team meeting, add the name of the practice manager and the desk lead in the speaker notes rather than on the slide, so the chart stays valid when people change roles. Review the thresholds once a year, and update the date in the framing line when the rules change, so staff know they are reading the current version.

What makes this slide work

Safety is the first question

The first diamond asks Clinical? before anything else, so any complaint about care or safety goes straight to Tell manager now and then Dentist calls. Putting the highest risk question first means a busy receptionist cannot accidentally resolve a clinical complaint at the desk.

Numbers sit in the labels

Over $200?, Manager, 2 days and Desk lead, 5 days put the thresholds and deadlines into the chart itself. Staff do not need to remember a separate policy page to know who acts and how fast, because the numbers are where the decision is made.

Every path closes

Fix and confirm leads to Closed, and every other branch passes through Reply and log before reaching the same Closed pill. The single end point makes the rule visible: no complaint is finished until a reply is sent and logged, or a desk fix is confirmed in writing.

Questions people ask

How many nodes can this decision flowchart layout hold?

The layout caps the flowchart at 12 nodes, and this slide uses all twelve: two pill shaped ends, seven steps and three diamond decisions. Twelve is about the limit for labels that stay readable on a projected slide. A process with more branches should be split into two flowcharts, each starting where the other leaves off.

How short should the labels in a flowchart be?

Two or three words for decisions and three or four for steps. Diamonds have less room than rectangles, so a question like Over $200? fits where a full sentence would be cut off. Put the full rule, such as a refund over $200 needs the manager, in the speaker notes or the written policy.

Which shapes should a decision flowchart use?

Rectangles for actions, diamonds for yes or no questions, and pills for the start and end. The flowchart here uses exactly those three, and the product's flowchart offers four shapes in total: rect, diamond, pill and circle. Keep one meaning per shape across the whole deck so nobody has to relearn the code.

Should every branch of a flowchart end at the same place?

Where the real process does, yes. Here every path finishes at Closed, which tells staff that no complaint is left open, whichever way it went. If some paths end somewhere else, such as a referral to the dental board, give that end its own pill so it stands out.

Can I move the boxes after the flowchart is laid out?

Yes. Flowchart nodes are laid out automatically and can then be dragged to tidy a crossing line or group related steps. If the layout gets messy, the auto layout button restores a clean arrangement. Check the edge labels after moving nodes, because a Yes or No label can end up far from its diamond.

How do I present a decision flowchart to front desk staff?

Walk one real complaint through it from start to finish, for example a patient unhappy with a bill of $340. Then walk a second one down a different branch. Two stories teach the rules faster than reading every box, and staff remember the examples when the next complaint arrives.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other slide examples

Want the steps in the builder? Read Add charts, maps and diagrams to slides, then Add, reorder and restructure slides. For everything this generator can do, see the slide maker.

Sources

Written and checked by the OneCraft team. Last checked .