Skip to main content

Customer complaints

The Customer complaints log is the structured log SafetyBrik uses to record any complaint that gets reported to your business about food, service, or staff conduct. It is the digital replacement for the back-of-the-diary scribbles that most operators rely on, and it is the record an Environmental Health Officer expects to see when they ask "what complaints have you had recently and what did you do about them?".

You will find it as a tab on the Records page at /safety/records?tab=complaints. Individual complaints have their own deep-linkable detail pages at /safety/complaints/{id}.

Why this is in your EHO pack​

The Safer Food Better Business pack (Management method "Customers", page 66) explicitly asks you to keep a record of any complaint that suggests a food safety issue. The pack singles out three categories that need investigation: suspected food poisoning, allergic reactions, and foreign objects in food. EHOs reading your pack will look for evidence that you took complaints seriously, investigated the source, and notified the local authority where appropriate.

A logged complaint with a clear summary, a documented action, an EHO-notification tick where relevant, and an outcome note is the kind of evidence that turns a difficult inspection conversation into a tick in a box.

What you can record​

Each complaint captures:

  • Complaint date - when the incident actually happened, which is often a different day from the day it was logged. It can't be after today (the site's today, or your business's for an All sites complaint): "A complaint can't be dated after today."
  • Location - which site (only shown if you run more than one).
  • Category - one of the six standard categories (see below). The serious ones (food poisoning, allergic reaction) trigger an EHO escalation prompt. Other needs its own label in Custom type label.
  • Summary - what the customer told you, in your own words.
  • Customer details - name, phone, email if the customer left them. All optional. Anonymous complaints are recorded as Anonymous. An owner can erase them later: see Removing a customer's personal details.
  • Suspected source - free text, e.g. "the chicken sandwich at lunch".
  • Supplier - if the complaint points at a specific supplier, link them here. The dropdown reads from your Suppliers list (the same list CostingBrik uses if you have it). If the supplier has been removed since the page loaded, the save is refused with "That supplier wasn't found. Choose another one, or leave it blank." Editing a complaint whose supplier has since been removed still works. If your suppliers can't be loaded just now, the form says so where the dropdown goes, with Try again, and you can still save: a new complaint without a supplier, or an edit keeping the supplier it already has.
  • Batch info - best-before date, batch code, lot number if available.
  • Action taken - what you did about it. Refund, replacement, apology, supplier contacted, kitchen briefing, anything.
  • EHO has been notified - tick it, with the date you told them, if you reported the complaint to your local Environmental Health Officer. The log form asks for it on the two serious categories; for any category, tick EHO has been notified on the complaint's page. The date can't be after today: "The date the EHO was told can't be in the future."
  • Photos - up to ten photos. Foreign-object complaints in particular benefit from a photo of the object and of the original packaging.
  • Follow-up - who will see the complaint through, and by when. Every new complaint is on the Follow-ups list until someone says how it was resolved (see Resolving a complaint). A complaint can't be logged as already resolved.

When you press Log complaint (or Save changes) with something missing, nothing is saved. Each problem shows in red under its field, and you are taken to the first one:

  • "Enter the date of the complaint."
  • "Choose the location." (if you run more than one site)
  • "Say what kind of complaint this is." (an Other complaint with no label)
  • "Enter the date the EHO was notified." (when EHO has been notified is ticked)
  • "Enter a summary of the complaint."
  • "Say what action you took."

Each message goes as soon as the field is filled in. The button is only greyed out while photos are uploading or the complaint is saving.

Clearing a box when you edit a complaint removes that detail, so a customer's name, phone number or email can be taken off later. When a customer asks for their details to be erased, an owner can use Remove personal details instead, which also records that it was done and stops them being added back (see Removing a customer's personal details). The same goes for the suspected source and batch info. Changing an Other complaint to a named category drops its own label.

The six categories​

CategoryWhen to useNotification?
Suspected food poisoning / illnessCustomer reports being unwell after eatingYes - notification fires to owners and admins
Allergic reactionCustomer reports an allergic reactionYes - notification fires to owners and admins
Foreign object in foodHair, plastic, glass, packaging, anything that should not be in the foodNo automatic notification
Food quality (taste, freshness, presentation)Stale, off, undercooked, overcooked, wrongNo automatic notification
Service / staff conductRudeness, slow service, billing disputeNo automatic notification
OtherAnything that does not fit (with a custom label)No automatic notification

The two serious categories send every owner and admin their own in-app alert the moment they are logged, for example New complaint: Allergic reaction with "Complaint dated 3 May 2026 at Station Road: ..." and the start of the summary (the site is named when you run more than one). This is deliberate: an alert about a food poisoning report sitting in someone's inbox for 24 hours is the kind of thing that turns a complaint into a Food Hygiene Rating ding. Other categories stay quiet to avoid alert fatigue.

  • Each copy is your own. Reading it marks it read only for you, not for the other owners and admins. Members and viewers don't get one.
  • A complaint changed into a serious category while it is still open alerts them, for example Complaint changed to: Allergic reaction. A resolved one doesn't. Each complaint alerts once at most, so changing its category back and forth sends nothing more.
  • If no owner or admin is on file, one shared alert goes to everyone who signs in to Brikly instead.
  • Voiding a complaint removes its alerts from everyone's notifications, and a voided complaint never alerts.
  • Nothing is sent while SafetyBrik notifications are switched off in Notification preferences.

EHO escalation​

When you select food poisoning or allergic reaction, the form modal shows a yellow banner reminding you that the FSA expects suspected food poisoning and allergic reactions to be reported to your local Environmental Health Officer. The banner includes:

  • A link to the FSA's local-authority finder.
  • An EHO has been notified checkbox.
  • A Date notified input that becomes required once you tick the box. It can't be after today.

Once EHO has been notified is ticked, the banner stays on show even if you change to a category that isn't serious, so its date is never asked for out of sight.

The notification record renders in your EHO PDF report next to the complaint, so an inspector can see at a glance which complaints you escalated and when.

When to notify

Notifying your local authority is a judgement call. The FSA's general guidance is that any suspected food-related illness involving more than one customer, or a single severe case, should be reported. If you are unsure, call your EHO and ask. Recording the call in this log is the audit trail.

Photos​

You can attach up to ten photos per complaint. They show as small pictures under the complaint in the EHO Report Pack. Useful for:

  • The actual foreign object (a hair, a piece of plastic, a fragment of packaging).
  • The original food packaging if the complaint relates to a manufactured product.
  • The customer's receipt or order ticket.
  • Any visible damage or quality issue.

Photos can be JPEG, PNG or WebP, up to 5 MB each. A photo in the iPhone's HEIC format is refused with "This photo is in HEIC format. Save it as a JPEG and try again."

While photos are still uploading, the save button reads Uploading photos... and waits; Cancel still works. If a photo fails, the others are kept and the form says "That photo couldn't be uploaded. Try again." (or, for several, "2 photos couldn't be uploaded. Try them again."), with the reason instead when Brikly has one, such as the HEIC sentence above.

Photos are private to your business. Brikly opens each one through a link that works for an hour, and reloading the page gets fresh links, so a page left open for longer shows broken pictures until you reload it. While a link works, anyone who has it can open the photo, so don't copy photo links into emails or messages. The EHO Report Pack shows the photos as pictures, never as links.

When an owner or admin removes a photo while editing a complaint, the file is deleted too, unless another record uses the same photo; when a team member removes one, Brikly keeps the file privately until the account is deleted. A voided complaint keeps its photos, unless an owner removes them with the customer's personal details.

Live-edit on the detail page​

The complaint detail page lets owners, admins, and members edit two fields in place without opening the form modal:

  • The EHO has been notified checkbox.
  • The Date notified.

Ticking EHO has been notified works for every category. It records today's date (at the complaint's site), and Date notified then appears so you can change it if you told them on another day. Unticking it clears the date. Emptying the date while it is ticked isn't saved, and the page says "Add the date the EHO was told, or untick EHO has been notified."

Each field saves as soon as you change it. A small spinner shows while the save is in flight. If a save fails, an inline message says so and the field shows what is stored. Everything else - summary, action taken, customer details, supplier - is edited via the Edit button which opens the same form modal you used to log the complaint. Whether it is resolved isn't on the form: see Resolving a complaint.

If a save from the form fails, the form stays open with the reason at the top, or "We couldn't save the complaint. Check the details and try again." It can't be closed while it is saving. If someone else voids the complaint while you have it open, a change you then make is refused, and the page turns read only and shows their void. If the page can't be refreshed after a change, it keeps what it shows, with "We couldn't refresh this complaint, so it may be out of date." and Try again.

Complaints at a closed site​

A complaint at a site that has been switched off or removed names its site as "Station Road (closed)" and is read only. Its page shows "Station Road is closed. Its records can be read and printed but not changed.", with no Edit, Void, Resolve or Reopen, and the two fields above can't be changed. An owner can still remove the customer's personal details from it. Its row in the list has no Resolve or Void either. It still prints in that site's EHO Report Pack. The site filter lists your open sites, so choose All sites to find a closed site's records in the list.

A new complaint can only be logged at an open site, and a complaint can't be moved to a closed one. A change sent from a page left open is refused with "This site is closed, so its records can be read and printed but not changed." Before you switch a site off, the site closure dialog in Settings > Locations counts its open complaints, so you can resolve them first.

Resolving a complaint​

Every complaint has a follow-up on the shared Follow-ups list, "Resolve this complaint", with who it is for and the day it is due. It opens as the complaint is logged and stays open until someone says how the complaint was resolved, so an open complaint always has a name and a day against it. It shows on the Follow-ups list, on Today and on the complaint's page. Complaint follow-ups show on the web only for now, not on the Team App.

When you log it​

The form's Follow-up box says "Resolve this complaint. It stays on the follow-up list until someone says how it was resolved.", with:

  • Who - who will see it through. Leave it blank and it is yours: "Optional. Leave it blank and it is yours."
  • By when - a day at the complaint's site, a week on to start. Until you pick a date, it follows the site you choose. It must be today or later at the site.

If your device is offline, the complaint isn't sent, and the form keeps what you typed.

How was it resolved?​

You can resolve an open complaint from three places, and each opens the same Resolve complaint dialog:

  • Resolve in the Outcome section of the complaint's page.
  • Resolve in the complaint's row menu in the list.
  • Close follow-up on its follow-up, on the Follow-ups page, on Today or in the Follow-up section of the complaint's page.

The dialog asks How was it resolved?, which is required, for example "Refunded the meal and briefed the kitchen on the allergen board". What you write becomes the complaint's outcome, its follow-up is closed with it, and SafetyBrik records who resolved it and when. If someone else resolved it first, the dialog says so, for example "Already resolved by Sam Taylor at 10:05 on 12 Nov." If the resolve can't be saved, the dialog stays open with what you typed.

Once it is resolved, the Outcome section shows How it was resolved, read only, with who resolved it and when, for example "Resolved 12 Nov, 10:05 by Sam Taylor". A complaint resolved without an outcome reads "No outcome recorded". An open complaint reads "Not resolved yet."

The outcome can't be edited. If it needs changing, or the complaint needs more work, reopen it.

Reopening a complaint​

Reopen is on a resolved complaint's page, for owners, admins and members. It asks "Reopen this complaint?": "Any earlier outcome stays in its history. A new follow-up opens, due in a week, and resolving it again needs a fresh note." The new follow-up is for whoever logged the complaint, or for you if they have left. The complaint is open again, and its earlier outcome is kept under its follow-ups. Use Change on the new follow-up to give it to someone else or move its day.

The complaint's follow-up​

The Follow-up section of the complaint's page shows its open follow-up, with Close follow-up and Change, and its earlier follow-ups under it, newest first, each with its outcome, for example "Resolved 10 Nov, 16:20 by Sam Taylor" followed by what they wrote. An outcome recorded before complaints joined the Follow-ups list reads "Resolved earlier".

  • Change can reword it, give it to someone else (Who) or move it to another day (By when, today or later at the site). See Changing a follow-up.
  • It can't be voided on its own. A complaint's follow-up goes with the complaint, so there is no Void on it. If the complaint was logged by mistake, void the complaint, which voids its open follow-up too.
  • There is no Add follow-up. A complaint's follow-up opens when it is logged and again when it is reopened, one at a time.
  • Moving the complaint to another site moves its open follow-up with it. It stays due on the same day, now at the new site, and the move is in the audit log as Follow-up changed.

Resolving and reopening are in the audit log as Customer complaint resolved and Customer complaint reopened.

Complaints logged before this change​

The old Mark as resolved switch and the Outcome notes box have gone: a complaint is resolved only through How was it resolved?. Every complaint that was still open now has a follow-up for whoever logged it. A complaint already resolved keeps its outcome, and if it is reopened that outcome stays in its history as "Resolved earlier". A change to whether a complaint is resolved, or to its outcome, sent from a page opened before this change is refused with "This page is out of date. Refresh it and try again."

Voiding a complaint​

A complaint is never deleted. One logged by mistake (a test, a duplicate, or a complaint about a different business, say) is voided instead: it stays on file, with why, who and when, and still prints in the EHO pack.

Owners and admins can void a complaint, with Void on its page or in its row's menu in the list. Void asks "Void this complaint?": "Void a complaint only when it was logged by mistake. It is never deleted: it stays on file and in the EHO pack as voided, with your reason." Why are you voiding it? is required. If the void can't be saved, the dialog stays open with what you typed. If someone else voided it first, yours is treated as done and the page shows their void.

A voided complaint:

  • Shows when, who and why. Its page has a Voided badge in place of Open or Resolved, and a notice with when and who, for example "Voided Mon 9 Nov, 14:32 by Sam Taylor", then the reason and "This complaint was logged by mistake. It stays on file and in the EHO pack as voided, and can't be changed."
  • Is read only. It has no Edit, Void, Resolve or Reopen, and the two live-edit fields can't be changed. Its photos are kept. An owner can still remove the customer's personal details, and its photos with them.
  • Is hidden from the list. Turn on Show voided to see voided complaints, greyed out and marked Voided.
  • Takes its open follow-up with it. Any open follow-up on the complaint is voided too, with the same reason, who and when.
  • Is left out of every count. It isn't in the list's open count, the Daily diary, the 4-weekly review's prompts or the site closure dialog's open complaints, and it never sends an alert. A voided serious complaint's alerts are taken out of everyone's notifications.
  • Prints in the EHO pack as voided, with who voided it, when and why (see How it shows up in the EHO report).

A void can't be undone. If a complaint was voided by mistake, log it again. If a customer asks for their name, phone number or email to be taken off a voided complaint, see Removing a customer's personal details. A complaint at a closed site can't be voided.

Removing a customer's personal details​

When a customer asks you to erase their personal details, an owner can take them off the complaint with Remove personal details on its page. It works on any complaint, open, resolved or voided, and at a closed site too. Only owners have it: admins, members and viewers don't.

It asks "Remove the customer's personal details?" and says exactly what it will do:

  • What is cleared. The customer's name, phone and email: "This clears the customer's name, phone and email from this complaint. Its photos stay unless you tick below."
  • The photos, if you tick them. When the complaint has photos, there is an Also remove photos (3) tick. Ticked, the photos are taken off the complaint and their files deleted, unless another record uses the same photo.
  • What stays. The complaint itself, with its date, category, follow-ups and any void. Nothing typed into it changes: the summary, what you did, the outcome, follow-up notes or a void reason. If any of those name the customer, edit them first (a voided complaint can't be edited). Alerts already sent, and EHO packs already downloaded or sent, aren't changed either.
  • It can't be undone. "After this, no personal details or photos can be added to this complaint. You can't undo this."

If it can't be saved, the dialog stays open with "We couldn't remove the personal details. Please try again."

Afterwards:

  • The page says who and when, for example "Personal details removed 10 Nov 2026 by Olive Owner", where the customer's details were.
  • The list and the diary say so. The complaints list shows Removed where it would say Anonymous, and the Daily diary shows "Customer details removed".
  • Nothing can be added back. Edit shows "The customer's personal details have been removed. They can't be added again, and no photos can be added." in place of the customer details. Photos still on the complaint can be taken off, but no new ones added. A save from a form opened before the removal is refused: "This complaint changed while you had it open. We've updated the form: check it and save again."
  • Photos left on it can be removed later. If you didn't tick the photos, Remove personal details stays on the page. Its dialog's button is greyed out until you tick Also remove photos, as there is nothing else left to remove.
  • It is in the audit log as Customer's personal details removed, with which details went but never the details themselves.

An anonymous complaint​

A complaint with no name, phone or email can still be marked, so you have a record that the request was handled. The dialog says "No name, phone or email is recorded on this complaint. This records that a request to remove them was handled." Once it is marked, the page shows who and when, and the button goes (unless the complaint has photos left to remove).

Permissions​

The Customer complaints log uses standard SafetyBrik role permissions:

RoleViewAddEditLive-edit, resolve and reopenVoid
OwnerYesYesYesYesYes
AdminYesYesYesYesYes
MemberYesYesYesYesNo
ViewerYesNoNoNoNo

Members can log, edit, resolve and reopen complaints, but only owners and admins can void them. Only owners can remove a customer's personal details.

How it shows up in the EHO report​

The EHO Report Pack has a dedicated Customer Complaints section that lists the complaints dated in the pack's period, and any complaint voided within the pack's dates, whatever its date. With none, it says "No customer complaints were logged in this period." Complaints are grouped by category in the same canonical order as the dropdown, so the EHO sees food poisoning first and Other entries last (an Other complaint under its own label, for example "Other: Cleanliness"). Each complaint shows:

  • The complaint date.
  • The summary, with its photos as small pictures under the complaint and a line saying so ("Photo below" or "3 photos below"). Up to 10 photos a complaint, and 60 in the whole pack, are shown. Any more, and any the pack can't show (a HEIC photo or a damaged file, say), are counted instead, for example "2 more photos on file in Brikly", or "Photo on file in Brikly" when none of the complaint's photos can be shown. The pack never contains a link.
  • The action taken.
  • EHO notified - "Yes, 3 May 2026" (with the notification date), "Yes" or "No".
  • Resolved - who resolved it and when, for example "Resolved 12 Nov by Sam Taylor", or "No" in red while it is open, as on the day you make the pack (a line under the section heading says so, for example "Resolved is as on 7 Oct 2026, the day this pack was made."). A complaint that was reopened lists its earlier outcomes under that, newest first, for example "Resolved 10 Nov by Sam Taylor: Refunded", and an outcome recorded before complaints joined the Follow-ups list as "Resolved earlier: Refunded". A complaint resolved before then with no follow-up reads "Resolved". A voided complaint reads "Voided" here, with a line under its summary saying when, by whom and why, for example "Voided 8 Oct 2026 by Sam Taylor: Logged twice".
  • Outcome notes - how it was resolved, "No outcome recorded" for one resolved without one, or "-" while it is open.
  • Logged by - who logged it, or "Former team member" if they are no longer on file.

A site's pack lists that site's complaints plus those logged without a site. An all-sites pack lists every complaint in the period with a Site column ("All sites" for a complaint logged without a site).

Each complaint's follow-up is also in the pack's Follow-ups section. A complaint logged before the pack's dates that is still unresolved, and not voided, isn't left out: its open follow-up is listed in the pack's Still open from before this period section, with the other follow-ups (complaints have no list of their own there). If it was reopened or logged during the period, its follow-up is in the Follow-ups section instead.

How it feeds the 4-weekly review​

The 4-weekly review has a built-in question: "Has every food complaint been investigated and the safe methods reviewed?", with N/A for No complaints. Before complaints had a structured home, this question was answered by counting corrective actions in the period - a rough proxy. Now the review reads directly from the complaints log and surfaces three different prompts depending on what it finds:

  • Zero complaints: "No complaints logged in this period. If none were received, choose No complaints." (A review started before the questions were reworded says "... answer Yes." instead.)
  • Some complaints, all resolved: "N complaints in this period, all resolved. Review whether safe methods need updating." (or "1 complaint in this period, ...")
  • Some complaints, some still open: "N complaints in this period (M still open). Resolve open complaints and review whether safe methods need updating."

The counts cover the review site's complaints plus those logged without a site, and leave voided complaints out. When complaints from an earlier period are still open, a sentence is added, for example "1 complaint from an earlier period is still open - resolve it and review your safe methods." or "2 complaints from an earlier period are still open - resolve them and review your safe methods."

This means an open complaint sat in the system at quarter-end is impossible to miss when the duty manager works through the review.

What it does not do​

This feature is intentionally a complaint log, not a customer service platform:

  • There is no customer-facing portal - complaints arrive via your existing channels (in person, phone, email, social).
  • There is no automated EHO reporting - the EHO has been notified tick is a record of an action you took outside the app, not an API call.
  • There is no link from a complaint to a corrective action yet. A picker that lets you attach a recent corrective action to a complaint is on the roadmap. In the meantime, mention any corrective-action reference in the Action taken field so it lives alongside the rest of the complaint record.
  • There is no Team App capture yet - logging a complaint is a manager flow on the web for now.
  • There is no customer notification log (refunds, apologies, hospital references) as a structured sub-entity. Use the Action taken field, and what you write when you resolve it, for that.

If your business handles enough complaints that any of these limits start to bite, talk to us - we are sizing the next phase of the feature based on real usage.