4 ways to automate customer complaint logs

#1 - The basic check-in

Who it's for: Single-site businesses that field the occasional complaint and want it written down instead of left in someone's head.

Available on: Basic.

What it is: A customer complaint log is a structured record of what a customer was unhappy about, what was done about it, and how it ended. This version is four typed fields on a phone: the customer's name, what they said, how it was handled, and the outcome. Each completion is one stamped record with a server timestamp and the staff member who filed it. The person who took the complaint logs it on the spot, and the audit trail is the running list of complaints over time.

In practice: Take a single-site bakery with a counter team of five. A customer says their birthday cake had the wrong message piped on it. The assistant who served them opens the canvas, types the customer's name, writes "ordered 'Happy 40th Dave', got 'Happy 40th David'" in their own words, records that they remade the message plaque on the spot and knocked 10% off, and marks the outcome as "left happy, took the corrected cake". One stamped record, filed in 30 seconds, before the next customer is served and the detail is forgotten.

Why it works: A complaint that lives in someone's memory is a complaint nobody can act on later. The work of handling the customer does not change. What changes is that there is now a typed, time-stamped record of every complaint, attached to the person who took it. One complaint on its own is an incident. Twenty of them in a log is a pattern, and a pattern is something the manager can fix at the source.

Steps included:

• 1 text input (customer's name)
• 1 text input (what they said, in their own words)
• 1 text input (how it was handled)
• 1 text input (the outcome, how they left)

When to upgrade:

1. Add written guidance (#2) once more than one person fields complaints, so de-escalation and escalation stay consistent across the team.
2. Add photo evidence (#3) once complaints are about a physical product or paperwork and a description alone does not capture the issue.
3. Add a signature (#4) once the log is reviewed by an auditor or a franchise head office and the record needs to be signed by the staff member.

#2 - With written guidance

Who it's for: Sites with rotating or part-time front-line staff who all field complaints and need to handle them the same way.

Available on: Standard.

What it is: The basic log plus two guidance panels woven through the canvas. One panel coaches the staff member on how to de-escalate before they start typing. The second, placed after the outcome, tells them when to pull in the duty manager. A weekend hire on their second shift handles a complaint the same way a long-serving supervisor would, without anyone standing over them.

In practice: Take a 30-room hotel with a reception desk staffed across three shifts. A guest comes down at 7am furious that the wifi dropped during a work call. The night porter just finishing up reads the de-escalation panel first: stay calm, apologise that they are unhappy, ask what would make it right. They log the complaint in the guest's own words, record that they offered a late checkout and logged a fault with maintenance, and mark the outcome as "calmer, accepted the late checkout". The escalation panel reminds them this one does not need the duty manager, but a refund request over the threshold would. The next porter on the next shift handles the next complaint to the same standard.

What it adds to the previous template:

1. A "how to de-escalate" panel before the fields that coaches the staff member to stay calm, apologise that the customer is unhappy, and ask what would make it right.
2. A "when to involve a manager" panel after the outcome that names the triggers: a refund over a set amount, a threat to post publicly, or aggression.
3. A standing reminder in that panel to log every complaint, even the verbal ones that calmed down quickly, because patterns matter.

Why it works: Written guidance sits inline at the moment the staff member is about to act. The de-escalation panel is on the screen before they have typed a word, which is exactly when a flustered new starter needs it. The escalation panel is right there after the outcome, when they are deciding whether this one goes up the chain. It is not a training session they sat through in their first week and forgot. It is on the phone at the moment of the complaint.

Steps included:

• 1 guidance panel (how to de-escalate)
• 1 text input (customer's name)
• 1 text input (what they said)
• 1 text input (how it was handled)
• 1 text input (the outcome)
• 1 guidance panel (when to involve a manager)

When to upgrade: Move to Customer Complaint Log #3 once a typed description is not enough. Once complaints start being about a damaged product, a wrong order, or a piece of paperwork, the staff member's words about it are weaker than a photo of it.

#3 - With photo evidence

Who it's for: Businesses that want photo evidence of the product or paperwork a complaint was about, especially across more than one site.

Available on: Standard.

What it is: The guided log plus a photo step taken at the moment of the complaint. If the complaint is about something physical (a faulty product, a wrong delivery, a marked-up invoice, a damaged item), the staff member photographs it straight into the record. The photo lands in the same stamped completion as the typed account, so the description and the evidence are filed together rather than the photo sitting lost in someone's camera roll.

In practice: Take a three-site garden centre. A customer returns to the largest branch with a rose bush they bought a week ago that has arrived diseased. The assistant reads the de-escalation panel, logs the customer's name and exactly what they said, photographs the affected plant and the original receipt side by side, records that they replaced it and refunded the difference, and marks the outcome. Head office, looking across all three sites at the end of the month, can see not just that plant complaints are up at this branch but what the affected stock actually looked like. The photo turns a vague run of "plant quality" complaints into something the buyer can take back to the grower.

What it adds to the previous template:

1. A photo step after the outcome for the product, paperwork, or anything physical the complaint was about.
2. Visual evidence filed in the same record as the typed account, instead of the description carrying the whole weight on its own.
3. A multi-site view where head office can see what the complained-about item actually looked like, not just a line of text.

Why it works: A description is one person's account. A photo is the thing itself. The two together survive a challenge in a way that either alone does not. The typed record says what happened and how it was handled; the photo shows the customer was right about the state of the product. Captured in the same completion, on the same device, the photo cannot be reconstructed or argued away after the fact.

Steps included:

• 1 guidance panel (how to de-escalate)
• 1 text input (customer's name)
• 1 text input (what they said)
• 1 text input (how it was handled)
• 1 text input (the outcome)
• 1 guidance panel (when to involve a manager)
• 1 photo step (product or paperwork)

When to upgrade: Move to Customer Complaint Log #4 once the log is reviewed by an auditor or a franchise head office and the record needs to be signed by the staff member who handled it.

#4 - With photo and signature

Who it's for: Audited or franchise businesses that need a signed complaint trail, where head office or an auditor pulls records and expects each one attributed.

Available on: Standard.

What it is: The photo-evidenced log plus a staff signature at the end of every record. The person who handled the complaint signs on the touchscreen to confirm the log is honest. That gives four things on a single complaint: a server timestamp, the typed account, a photo of the item, and a signed confirmation from a named staff member. An auditor or a franchise field manager would accept this as a contemporaneous record at the level expected from a signed paper complaint book, captured in under a minute on a phone.

In practice: Take a franchise coffee chain with eight outlets under one owner. A customer at one outlet complains that a gift card they were sold a month ago will not scan. The barista who deals with it logs the customer's name and what they said, photographs the faulty card and the original till receipt, records that they issued a replacement and escalated the batch to head office, marks the outcome, and signs the record on the screen. When the franchisor's quarterly audit lands, the field manager pulls a sample of complaints from across all eight outlets and finds a named, signed staff member on every one. The audit closes in an afternoon instead of a week of chasing "who dealt with this?".

What it adds to the previous template:

1. A signature step at the end of every complaint record.
2. A named, attributable confirmation on the same record as the timestamp, the typed account, and the photo.
3. A signed trail at the level a franchise head office or an external auditor expects to see when they sample records.

Why it works: The signature is what closes the loop. The other three say a complaint happened, here is the account, and here is the item. The signature adds: and this staff member confirms the record is honest. Captured on the same device, in the same completion, the four together are what an auditor or a franchisor expects when they ask "who handled this, and can they stand behind it?".

Steps included:

• 1 guidance panel (how to de-escalate)
• 1 text input (customer's name)
• 1 text input (what they said)
• 1 text input (how it was handled)
• 1 text input (the outcome)
• 1 guidance panel (when to involve a manager)
• 1 photo step (product or paperwork)
• 1 signature step (staff confirmation)

When to upgrade: The next variations layer Poppi on top. A Poppi briefing that surfaces last week's open complaints before the shift starts. A Poppi gate that decides whether a complaint needs escalating the moment it is logged. A Poppi action that posts a serious complaint straight to the duty manager's channel. Coming in the next post update.

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. You only need to answer three questions about how your team runs.

Is it just you running this, or do other people run it too?

If it is just you, the basic log (#1) is enough. You know how to handle a complaint and when to step in, so you do not need the canvas to coach you.

If anyone else fields complaints (a counter team, a reception rota, a part-time weekend crew), go to #2 onwards. The guidance panels are what stops one person handling a complaint brilliantly and the next person making it worse. You write the de-escalation and escalation guidance once; everyone reads it inline at the moment they need it.

Do you need a photo as proof, or is the typed record enough?

If your complaints are about service or experience (a rude interaction, a long wait, a booking mix-up), the typed record captures it. Go to #1 or #2.

If your complaints are about something physical (a faulty product, a wrong delivery, a marked-up invoice), the description alone is weaker than the thing itself. Go to #3. A photo of the product or paperwork, filed in the same record, turns one person's account into evidence anyone can check.

Do you need someone to sign off at the end?

If the log is internal and no auditor or head office will ever pull it, a record is enough. Stick at #3.

If the log is reviewed by an auditor or a franchise head office, the signature is the lock. Go to #4. A signed record names the staff member who handled the complaint and confirms the account is honest, on the same record as the timestamp and the photo.

Related workflows

• Lone worker check-ins
• Damage reports
• Lost and found logs
• Job completion sign-offs
• Anonymous feedback
• Maintenance fault reports

Conclusion

A customer complaint log is a structured record of what a customer was unhappy about, what was done about it, and how it ended. The version an audited or franchise business runs attaches a photo and a signed staff confirmation to every record, so a head office audit that used to take a week closes in an afternoon.

Pick the version that matches how your team runs today, not the most sophisticated one you can imagine running someday. Open each template in the playground above and log your next complaint through it this week.