Customer Feedback
For businesses using voice feedback at the point of experience — at the table, after checkout, post-service. These templates cover the full response arc: warm acknowledgment, internal action, recovery, and the follow-up that most operators skip.
1
Positive Acknowledgment — Customer-Facing
Subject: We heard you — and it genuinely made our day
Hi [First Name],
Thank you for taking a moment to leave us a voice message after your visit on [Date]. We listen to every piece of feedback we receive, and yours stood out.
Hearing that [specific detail from the transcript, e.g. "your server Maria went out of her way to accommodate your dietary needs without making you feel like an inconvenience"] means a lot to our entire team. I've shared your words directly with [the team member / team mentioned] — they'll hear this today.
Guests like you are the reason we do this work. We hope to see you again soon.
Warmly,
[Your Name]
[Your Title], [Business Name]
[Direct contact if appropriate]
Pro tip: Pull one specific detail from the AI transcript and name it explicitly. Generic thank-yous get deleted. Specific ones get printed and stuck on the refrigerator. The difference is one sentence.
2
Constructive Feedback — Internal Team Action
[ACTION REQUIRED] Customer Feedback Logged — [Date]
A voice feedback came in today that we need to address as a team.
What the customer said (summary):
[1-2 sentence paraphrase. No identifying information.]
The issue:
[e.g. "Waiting over 18 minutes for a table despite holding a reservation is not acceptable and reflects a floor management breakdown during that shift."]
Who needs to act:
[Name or role] — please [specific action, e.g. "review the reservation log for that shift and identify what caused the delay"] by [specific deadline, e.g. "end of day Thursday"].
Tracking:
This feedback is logged in VoiceZero under reference [#ID]. Update the note when resolved so we can close the loop.
— [Manager Name]
Pro tip: Assign one owner and one deadline. "The team" is not an owner. "Soon" is not a deadline. If no one owns it by name, it won't get done. That's the entire reason most feedback dies after it's collected.
3
Negative Feedback — Service Recovery (Immediate, Customer-Facing)
Subject: We owe you a direct conversation — [Business Name]
Dear [First Name],
I'm [Name], the [General Manager / Owner] at [Business Name]. I personally listened to the feedback you left on [Date], and I want to be direct with you: what you described was not the experience we intend to deliver, and I'm sorry.
Specifically, I understand that [describe the issue precisely, e.g. "your order arrived 35 minutes late and was incorrect when it did arrive, and no one on staff offered an explanation or apology"]. That is a failure on our part, and I'm not going to make excuses for it.
Here is what I'd like to do: [specific, meaningful offer, e.g. "offer you a full refund plus a complimentary meal arranged personally by me, at a time that works for you"].
You can reach me directly at [phone / email]. I'd welcome the chance to speak with you — not to manage the situation, but because your experience matters and I want to make it right.
[Name]
[Title], [Business Name]
Pro tip: Never write "I apologize for any inconvenience." It's a signal you haven't actually read the feedback. Name what went wrong, specifically. Precision signals accountability. Vagueness signals the opposite.
4
Negative Feedback — Follow-Up 24 Hours Later
Subject: Following up — did we get this right for you?
Hi [First Name],
I wanted to follow up on the message I sent yesterday. [If action was already taken: "I'm glad we were able to [process your refund / arrange your next visit / resolve the issue]."]
I also wanted to let you know what changed internally as a result: [one sentence on the actual change made, e.g. "We've revised our delivery window confirmation process so customers are notified immediately if there's a delay rather than discovering it when they open the door."] Your feedback directly led to that change.
If there's anything else you'd like to share, my inbox is open: [email]. And if you're ever willing to give us another chance, I'll personally make sure your next experience is different.
Thank you for telling us. It's much easier to not say anything. We're glad you did.
[Name]
[Title], [Business Name]
Pro tip: The 24-hour follow-up is skipped by almost every business. Customers who had a bad experience followed by genuine, specific recovery are often more loyal than customers who never had a problem at all. This email is worth more than the initial response.
5
Compliment — Shared with Staff Member
[Staff Member Name] — wanted to share this with you directly.
A guest who visited on [Date] left a voice message specifically mentioning you. Here's what they said (nearly their exact words):
"[Quote or close paraphrase from the transcript, e.g. "The host remembered my daughter's name from our last visit six months ago. That kind of care isn't trained into someone. It's just who she is."]"
That's the kind of thing that reminds us why we do this.
I've also logged it in your record for your next review. Thank you for representing us that way.
— [Your Name]
Pro tip: Don't relay compliments in a team meeting where the recognized person gets embarrassed in front of everyone. Send it privately first. Then, with their permission, share it more broadly. People need to own their moment before it becomes public property.
6
Repeated Theme Alert — Same Issue 3+ Guests
PATTERN ALERT — Immediate Manager Review Required
Our voice feedback system has flagged a recurring theme across [X] separate messages in the past [timeframe, e.g. "7 days"].
Recurring issue:
[Theme stated precisely, e.g. "Long wait times at the host stand during dinner service, specifically between 7:00-8:30pm on weekdays."]
Messages flagged:
- [Date + brief one-line summary of message 1]
- [Date + brief one-line summary of message 2]
- [Date + brief one-line summary of message 3]
Why this matters now:
One complaint is a data point. Three is a pattern. This issue is affecting multiple guests independently, and if unaddressed, it will migrate from voice feedback to public reviews.
Required action by [Date]:
1. Identify the root cause (staffing gap, process failure, equipment, or scheduling?)
2. Implement an interim fix by [Date]
3. Report findings to [Name]
Do not wait for a fourth complaint.
— [Operations Manager / GM]
Pro tip: "Do not wait for a fourth complaint" is a directive, not a suggestion. You're quantifying a threshold and naming it. That specificity focuses attention in a way that "this is important" never will. Use it deliberately.
Employee & HR
The most legally and culturally sensitive category. These templates are written to protect anonymity, honor confidentiality obligations, and communicate with deliberate precision — because in HR, the wrong word in the wrong email becomes Exhibit A.
7
Anonymous Culture Feedback — All-Hands Communication
Team,
Over the past [timeframe], many of you took time to share anonymous voice feedback about your experience working here. I want to be direct about what we heard, and what we're going to do about it.
What we heard (themes, not individuals):
[Theme 1, e.g. "A significant number of responses raised concerns about workload distribution and feeling stretched thin, particularly in Q1."]
[Theme 2, e.g. "We also heard that communication from leadership about company direction could be clearer and more frequent — that people feel like they're finding out about changes too late."]
[Theme 3 if applicable]
What we're doing:
[Action 1 with owner and timeline, e.g. "Starting next month, I'm personally committing to a weekly 10-minute leadership update so you're never guessing about where we're headed. It'll be every Monday at 9am."]
[Action 2 with owner and timeline]
[Action 3 with owner and timeline]
What we are not doing:
We are not attempting to identify who said what. Anonymity is absolute. It was when you submitted and it remains so now.
Thank you for trusting this process. It only works because you used it honestly. Keep doing that.
[CEO / GM / HR Director Name]
Pro tip: The "what we are not doing" paragraph is the most important part of this message. Employees will test whether you mean it over the following weeks. The fact that you named it explicitly — in writing — builds more trust than every other sentence combined.
8
Management Concern — Confidential HR Note to Manager
CONFIDENTIAL — HR DOCUMENTATION
Date: [Date]
Subject: Pattern of Anonymous Feedback — [Manager Name / Role]
This memo documents a pattern of anonymous voice feedback received via VoiceZero between [Start Date] and [End Date] relating to [Manager Name]'s team.
Pattern observed:
[X] separate anonymous submissions raised concerns related to [theme stated precisely, e.g. "communication style in team meetings, specifically instances of language that team members describe as dismissive, condescending, or demoralizing"].
HR assessment:
This pattern meets our internal threshold for a proactive review. It does not constitute a formal investigation at this stage. The intent is development, not discipline.
Next steps:
1. Schedule a private meeting with [Manager Name] within [5 business days]
2. Frame the conversation around leadership development and team culture, not accusation
3. Agree on a coaching engagement for [duration]
4. Reassess via team sentiment check in [60-90 days]
Note on anonymity:
No identifying information from feedback submissions will be disclosed to [Manager Name] or to anyone outside HR leadership. The pattern is the evidence. The sources are protected.
Filed by: [HR Director Name]
Retention: Per HR policy, [X years]
Pro tip: Document the anonymity protection explicitly in the HR file before the manager conversation happens. If this ever escalates to a legal matter, written proof that you protected sources from day one is the difference between a defensible process and an exposed one.
9
Burnout Signal — HR Check-In (Sensitive Outreach)
Hi [Name],
I'd love to find 20 minutes to connect this week — nothing formal, no agenda to prepare for. I just want to check in on how things are going for you, especially given [neutral context if useful, e.g. "how much we've all had on across Q1"].
Would [Day] at [Time] work, or suggest whatever time is easier?
[Your Name]
---
[If the meeting happens, open with this — then stop talking:]
"I appreciate you making time. I genuinely just wanted to check in — not on project status, but on you. How are you actually doing? Because we've been running fast and I want to make sure you have what you need."
[Listen. Don't fill silence. Don't pivot to company EAP resources in the first five minutes. Let them talk first. What they say next is more important than anything you planned to say.]
Pro tip: Never open with "I noticed your feedback seemed..." You will destroy trust in the anonymous system immediately and permanently. The check-in must feel organic and genuinely human. If people believe the system surveils them, they stop using it. The safety valve has to work.
10
Positive Team Feedback — Shared in Slack
From our anonymous voice feedback channel — shared with permission:
Someone on the team shared this about [Person / Team / Initiative]:
"[Direct quote or close paraphrase, e.g. "The way the ops team handled the March system migration was genuinely impressive. They kept everyone informed, stayed calm when things broke, and made me feel supported even at 11pm on a Tuesday. I don't think they got enough credit for that."]"
We don't share every piece of feedback publicly — much of it stays confidential — but when something this generous comes through, it deserves to be heard by the people it's about.
[If tagging: "@[Name] — this one's for you."]
Keep going, everyone.
— [HR / Manager Name]
Pro tip: "Shared with permission" matters even though the submission is anonymous. It signals to your team that the system has governance — that not everything goes public and you're managing it responsibly. That signal makes people more willing to say hard things through the same channel.
11
Exit Interview Voice Summary — To Leadership
EXIT INTERVIEW SUMMARY — CONFIDENTIAL
Role / Department: [Role and department only — omit name if sensitivity warrants]
Departure date: [Date]
Interview method: VoiceZero Voice Feedback (unstructured)
Stated reason for leaving:
[e.g. "Career advancement. Accepted a senior role at a competitor offering a significant title and compensation step-up. This does not appear to be a dissatisfied departure by self-report."]
Constructive feedback shared:
[Theme 1 with brief context, e.g. "Described a lack of clarity around promotion criteria — felt they were held to an unwritten standard that was never explained."]
[Theme 2 with brief context]
Positive feedback shared:
[What they praised, stated specifically — e.g. "Spoke warmly about their immediate team and the quality of cross-functional collaboration in the product org."]
HR observation:
[Your professional pattern assessment, e.g. "The promotion clarity concern mirrors language from the previous two exit interviews from the same department. We recommend a structured review of how promotion criteria are communicated before the next performance cycle."]
Recommended action:
[Specific recommendation with owner and timeline]
Full recording retained in HR files per retention policy. Not for distribution.
HR Lead: [Name]
Date of brief: [Date]
Pro tip: The HR observation section is where the strategic value lives. Summarizing one exit is easy. Matching it to a pattern across three exits and making a recommendation is what separates an insight from a data point. That's the brief leadership actually needs.
12
Onboarding Feedback — 30-Day Check-In Debrief
30-Day Onboarding Voice Feedback: Cohort [Month/Year]
New hires surveyed: [X] | Response rate: [X%]
What's landing well:
[e.g. "The structured first-week schedule was consistently praised. New hires used words like 'oriented,' 'supported,' and 'clear.' The buddy program in particular was mentioned by 70% of respondents."]
What's not landing:
[e.g. "System access and tooling setup is creating friction. Three separate respondents mentioned spending their first two days waiting for credentials and software installs. This is a pure ops fix with zero cost."]
Sentiment snapshot:
Overall positive: [X%] | Mixed: [X%] | Negative: [X%]
One quote worth the room hearing (anonymized):
"[Verbatim or near-verbatim, e.g. "I felt like people were genuinely glad I joined. That's not something I expected to feel on day one."]"
Recommended changes to onboarding program:
1. [Specific change with owner and implementation date]
2. [Specific change with owner and implementation date]
Next cohort debrief: [Date]
Prepared by: [HR / People Ops Name]
Pro tip: Onboarding feedback is the easiest ROI story to tell. The cost of a poor onboarding experience is a re-hire within 90 days. Put the number in the room: "Fixing the credentials delay costs $0. Replacing a new hire costs $[X]." That number tends to accelerate IT tickets significantly.
13
Pattern Alert — Same Issue 3+ Employees in 30 Days
CONFIDENTIAL — PATTERN ESCALATION ALERT
To: [HR Director], [CEO / COO]
From: [HR Lead]
Date: [Date]
Our employee voice feedback system has surfaced a pattern that requires your attention before it escalates further.
What we're seeing:
[X] separate anonymous submissions in the past 30 days have raised concerns related to:
[Issue stated precisely, e.g. "Perceived favoritism in shift scheduling within the [Location/Department], specifically that the same small cluster of employees consistently receives premium weekend shifts regardless of seniority, tenure, or expressed preference."]
Why this is significant:
This volume of independent submissions raising the same specific concern is statistically meaningful. It reflects a widespread perception — and perceptions drive morale and attrition regardless of whether the underlying practice is intentional.
Recommended response:
1. [Immediate: e.g. "Audit 90 days of scheduling data for the flagged department against stated criteria."]
2. [Short-term: e.g. "Brief department manager with findings. Frame as a fairness audit, not an accusation. No anonymous details disclosed."]
3. [Follow-up: e.g. "Re-survey the same team in 45 days to assess whether the perception has shifted."]
Risk if unaddressed:
Morale erosion, voluntary turnover, and potential formal grievances. The cost of inaction is measurably higher than the cost of intervention.
This alert is logged. No further anonymous submissions on this topic will be shared outside this distribution.
[HR Director Name]
Pro tip: The phrase "statistically meaningful" is your defense against "it's just one disgruntled person." Three independent, unprompted voices saying the same specific thing is a signal, not noise. Name it clearly, back it with the count, and let the data do the arguing for you.
Restaurant & Hospitality
The highest-stakes real-time use case for voice feedback. A single difficult service can generate five one-star reviews before breakfast. These templates are built for speed, precision, and on-the-floor reality — because that's where the decisions get made.
14
Table-Side Feedback Received — Manager Action
LIVE FEEDBACK ALERT — Table [Number] — [Time]
AI urgency score: [Low / Medium / High]
Summary: [AI-generated one-line summary, e.g. "Guest reports the lamb was overcooked and their wine order has not arrived 25 minutes after ordering."]
Manager action:
If HIGH urgency: Approach the table within 90 seconds. Do not wait for a natural service window.
Script: "Good evening — I'm [Name], the manager on tonight. I understand we may have missed a couple of things and I wanted to come by personally. Can you tell me what's not working so I can fix it right now?"
Do not open with "I'm sorry to hear that." Open with an offer of action.
Address the wine: Check with floor staff immediately. If the order was missed, acknowledge it directly and deliver promptly.
Address the dish: Offer to re-fire the correct preparation or remove it from the bill without prompting.
If LOW urgency: Monitor. Check in at the next natural service touch point.
Log outcome in VoiceZero after the table departs. Close the loop.
Pro tip: The fastest recovery happens in the room, not via email 24 hours later. If the system alerts a manager's earpiece within 60 seconds, the guest has no idea their feedback triggered the visit — and the response reads as genuine attentiveness. That's the product.
15
Kitchen Issue Alert — Chef / Kitchen Lead
KITCHEN ALERT — [Time]
Manager to Chef / Kitchen Lead
Multiple guest complaints: [Dish name]
Issue: [Overcooked / Underseasoned / Wrong temperature / Incorrect preparation / Other]
Complaints this service: [X]
Action required:
- Inspect current batch and mise en place for [dish] immediately
- Hold further covers of this dish until cleared by [Chef Name]
- If issue confirmed: [pull dish / adjust recipe / restock ingredient / inform floor to offer alternative]
Tables affected: [Table numbers if known]
Manager on floor: [Name]
Debrief after service close.
Pro tip: A kitchen alert must read like a ticket, not a memo. Short sentences. Zero hedging. The chef is in the middle of service. Your communication style in this moment is itself part of operations. If you bury the action inside three paragraphs, the action won't happen.
16
Service Staff Recognition — Positive Voice Feedback
Pre-Shift Recognition — [Date]
Before we get into tonight's covers, I want to take 30 seconds.
We received a voice message from a guest who dined last [day/evening]. They specifically asked to make sure [Staff Member Name] knows how they felt.
Here's what they said:
"[Quote verbatim or near-verbatim from the transcript, e.g. "The server remembered that I'd mentioned a nut allergy at the start of the meal and flagged it again when I ordered dessert without me having to say anything. That kind of care is rare. Please tell her it made our anniversary dinner feel really special."]"
[Staff Member Name] — that's exactly what we're talking about when we talk about hospitality.
Now — tonight we have [X] covers...
Pro tip: Read the quote verbatim. Don't summarize it. The specific words from a real guest carry weight that a paraphrase never will. Watch the room when you read it — the whole team lifts a little. That lift is worth more than any bonus structure you could design.
17
Guest Recovery — Guest Still In-House
[Manager Approach Script]
"Excuse me, [Mr./Ms. Last Name if known, or "folks"] — I'm [Name], the [GM / Manager on Duty / Director of Guest Experience]. Do you have just a moment?
I wanted to come by personally because I understand your [evening / stay] hasn't been what it should have been, and I didn't want you to leave without us having a chance to address it properly.
Can you tell me, in your own words, what's been most frustrating? I'm not here to explain anything or defend anyone — I just want to understand and fix it."
[Listen fully. Do not interrupt. Do not offer explanations while they're still speaking. Take notes if appropriate. When they finish:]
"Here's what I can do right now: [Specific, meaningful offer: comp the dish / upgrade the room / waive parking / send complimentary dessert with a note / arrange a full replacement reservation].
[If appropriate:] And here is my direct card. If anything else isn't right before you leave tonight, please come to me first. Not the front desk — me."
[Do not ask them to leave a positive review in this moment. Do not. If the recovery is genuine, they will.]
Pro tip: "I'm not here to explain or defend anything" resets the adversarial dynamic in the room. Guests escalate because they're expecting to be dismissed. Remove that expectation before they say a word and the entire conversation changes register. This is the line that makes the script work.
18
Delivery / Takeout Complaint — Resolution Script
[Phone Script:]
"Hi, is this [Customer Name]? This is [Name] calling from [Restaurant Name]. You left us a message about your order tonight and I wanted to call you personally rather than send an automated response.
I'm really sorry. [Specific issue, e.g. "Your order arrived cold and was missing the side you ordered"] is not okay and that's entirely on us.
Here's what I'd like to do: [e.g. "issue a complete refund / send a full replacement right now / apply a credit to your account for your next order"]. No hoops, no hold music — it's already done on our end / I'll process it while we're on the phone.
Is there anything else about tonight's order I should know?
[Listen]
Thank you for telling us. We'd love the chance to get it right for you next time."
---
[SMS if no phone answer:]
Hi [Name] — [Manager] from [Restaurant]. Sorry about tonight's order. We've issued a [full refund / credit] to your account. Call me if you want to talk: [Number]. No pressure either way.
Pro tip: Calling instead of emailing a delivery complaint resolves it in under five minutes and prevents a negative review in the vast majority of cases. Most operators don't do it because a phone call takes more effort than a templated email. That gap is a competitive advantage you can take today.
19
Food Safety Concern — Immediate Escalation
FOOD SAFETY ESCALATION — DO NOT DELAY
Time received: [Time]
Date: [Date]
Reference: [VoiceZero ID]
Reported concern:
[Precise description, e.g. "Guest reports feeling ill following consumption of the pan-seared salmon. Nausea began approximately 2 hours after dining. Guest name if provided: [Name]. Contact: [Phone/Email]."]
Immediate actions (within 60 minutes):
1. Preserve all remaining product from the identified dish/batch — do NOT discard
2. Pull and retain temperature logs for [station / dish / date]
3. Photograph current kitchen conditions and any remaining prep
4. Contact [Food Safety Lead / Executive Chef] to inspect and sign off on findings
5. Do NOT contact the guest without guidance from legal — route all guest communication through [GM / Legal Counsel]
Do not admit liability in any written or verbal communication until reviewed by legal counsel.
Notifications required:
- GM: [Name] — notified at [Time]
- Legal / Insurance: [Name] — notified at [Time]
- Health authority: Required within [X hours] per local regulation — deadline [Time/Date]
This incident log is retained. All related records are placed on hold.
Pro tip: "Do not discard" is the most critical operational instruction in any food safety incident. Preserved evidence is what separates a defensible case from an indefensible one. Every kitchen lead should know this phrase by heart before they ever need it.
20
Review Interception — Guest Left Positively, Now Invite a Review
Hi [Name] — [Owner/Manager Name] from [Restaurant Name] here. We genuinely loved having you tonight, and so glad the experience landed the way we hoped.
If you have 60 seconds, a Google review would mean the world to our team — it directly helps the people who served you tonight: [Short Google Review link]
No pressure at all. Either way, thank you for coming in. Hope to see you again soon.
Pro tip: The 2-hour window is decisive. Reviews written while the memory is vivid are longer, more specific, and more credible. Inviting 48 hours later gets roughly a 20% response rate. Within 2 hours, you're closer to 55-60%. Set the automation and let the timing do the work.
Compliance & Legal
These templates exist in a different register from every other category. Every word is load-bearing. They are designed to create clean, defensible paper trails while ensuring the person who came forward feels heard, protected, and not abandoned.
21
Whistleblowing Report — Initial Acknowledgment
ACKNOWLEDGMENT OF REPORT — CONFIDENTIAL
Reference Number: [System-Generated ID]
Date and Time Received: [Date] [Time]
This message confirms that your report has been received by [Company Name]'s confidential reporting system.
Your report has been assigned reference number [ID]. Please retain this number. It is the only identifier for this matter. Your name has not been recorded.
What happens next:
Your report will be reviewed by [Compliance Officer / Independent Review Board / HR Leadership] within [X business days]. If additional information is needed, we will contact you via this secure channel using your reference number only — we will never ask you to identify yourself.
Your legal protections:
Under [applicable law, e.g. "the Whistleblower Protection Act / EU Whistleblowing Directive (2019/1937) / company policy section X.X"], you are protected from retaliation for making this report in good faith. Any attempt to retaliate against you should be reported immediately using this same channel and reference number.
Your anonymity:
Your identity has not been captured by this system. The report content alone has been received. We cannot and will not attempt to identify you through technical or other means.
You will receive an update on the status of your report within [X business days].
[Compliance Officer Name / Title]
[Company Name]
Pro tip: The reference number is the most important feature in this acknowledgment. It gives an anonymous reporter a mechanism to follow up, track progress, and provide additional information without ever revealing who they are. It also creates a defensible audit trail proving every report was acknowledged. Do not omit it.
22
Safety Incident Reported — Escalation to Legal / HR
SAFETY INCIDENT ESCALATION — CONFIDENTIAL
Escalated by: [Name / System]
Date/Time: [Date] [Time]
Incident reference: [ID]
Nature of report:
[Precise and objective description, e.g. "A voice feedback submission received at [Time] on [Date] describes a physical altercation between a supervisor and a team member in the warehouse area on [Date of alleged incident]. The person reporting states they witnessed the incident and did not believe it was safe to report through standard internal channels."]
Immediate actions required:
Within 1 hour:
- Notify [Legal Counsel]
- Secure any physical evidence related to the reported location and incident timeframe
- Do not question any named parties until advised by legal counsel
Within 24 hours:
- Assign an independent investigator (external to the involved department)
- Notify insurance carrier per policy requirements
- Review CCTV and access logs for the reported time and location
Within 48 hours:
- Provide initial written brief to [CEO / Board]
- Confirm regulatory notification requirements and deadlines for your jurisdiction
Communication restriction:
No information about this report is to be shared with anyone not on this distribution until advised by legal counsel. This is not optional.
[HR Director / Compliance Officer Name]
Pro tip: The communication restriction protects everyone in this situation — the reporter, the company, and even the person being reported, who has a right to a fair and untainted investigation. Information leaks poison investigations. Name the restriction explicitly and put it in writing.
23
Harassment Allegation — Confidential Investigation Intake
HARASSMENT ALLEGATION INTAKE — STRICTLY CONFIDENTIAL
Case Reference: [ID]
Date of Intake: [Date]
Source: VoiceZero Anonymous Voice Feedback System
Access restricted to: [Names / Roles]
Summary of allegation:
[Objective, non-editorial summary using the reporter's language where precise, e.g. "The submitter alleges that a [role, not name] within their immediate team made repeated comments about their physical appearance over a period of approximately [timeframe] and continued after the submitter explicitly asked them to stop. The submitter states this has materially affected their ability to work comfortably in the shared space."]
Classification:
[Verbal / Physical / Written / Digital / Quid Pro Quo / Hostile Work Environment / Under Assessment]
Severity assessment (preliminary, based on intake only):
[HR's initial assessment of seriousness and urgency]
Investigation protocol:
1. Assign investigator: [Name — must be independent of both parties and their direct management chain]
2. Preserve all relevant records (communications, scheduling, CCTV if applicable, prior HR files)
3. Separately interview: reporter (if willing), respondent, any witnesses identified
4. Complete investigation within [30 days] per company policy
5. Deliver written findings to [HR Director / Legal Counsel]
Interim protection measures:
[e.g. "Reporter and respondent placed on separate shifts effective immediately. Neither party will be informed of the reason beyond 'scheduling adjustment.'"]
Attorney-client privilege: [Note if applicable]
Document retention: Per litigation hold / HR policy — minimum [X years]
Access log: Maintained automatically.
Pro tip: The investigator independence clause is non-negotiable and must be named explicitly in the intake document. HR investigating a complaint that implicates someone in the CEO's inner circle is not independent. Name an external investigator in writing and your investigation starts defensible rather than compromised from day one.
24
Regulatory Concern — Documentation Template
REGULATORY CONCERN — FORMAL DOCUMENTATION RECORD
Document Reference: [ID]
Date Created: [Date]
Created by: [Name / Title]
Source of concern:
Voice feedback received via VoiceZero on [Date] at [Time].
Nature of concern:
[Objective, precise description, e.g. "The submission describes what may constitute a breach of [full regulation name and section, e.g. 'OSHA 29 CFR 1910.147 lockout/tagout requirements / GDPR Article 32 technical safeguards / local fire code Section 12.4 maximum occupancy'] at [specific location] on [date of alleged occurrence]. The submitter describes [specific factual detail]."]
Applicable regulation:
[Full statutory or regulatory citation]
Preliminary assessment:
[e.g. "Credible — requires immediate investigation" / "Requires verification before conclusion can be drawn" / "May reflect a misunderstanding of current requirements — to be confirmed"]
Internal actions taken:
[Date]: [Action taken, by whom]
[Date]: [Action taken, by whom]
Mandatory external notification assessment:
[e.g. "Mandatory regulatory notification required: Yes / No / Under review. If yes, deadline: [Date]. Reporting body: [Agency name and contact]."]
Legal hold:
All records relating to [the described process / location / timeframe] are placed on legal hold effective [Date]. Standard deletion schedules are suspended for these records until further written notice.
Reviewed and signed:
[Legal Counsel / Compliance Officer Name]
[Date]
Pro tip: The legal hold instruction is the detail most companies miss when they see a regulatory concern for the first time. Routine automated data deletion during a regulatory inquiry can convert an investigation into an obstruction issue. Place the hold in writing before you investigate. That order matters.
Closing the Loop
Most feedback programs collect. Very few complete the cycle by demonstrating that what was said actually changed something. These templates turn feedback into visible action — the step that makes customers and employees give feedback again next time.
25
We Changed Something Because of Your Feedback
Subject: You told us. We changed it.
Hi [First Name],
A few weeks ago, you left us feedback about [the specific issue, e.g. "our checkout process being confusing and making you enter your card details twice / the wait time at our service desk / the lack of vegetarian options in our dinner menu"].
You were right. And we did something about it.
Starting [Date / this week], we've [specific, concrete change, e.g. "redesigned the checkout flow so payment details are pre-filled once you're logged in / added a dedicated 5-minute express lane for quick service questions / introduced four permanent vegetarian dishes to the menu — all created because this kept coming up in guest feedback"].
This wouldn't have happened without you telling us. We read every voice message we receive, and yours was one of several that moved this from a conversation to an actual change.
Thank you for taking the time. We hope you notice the difference.
[Name]
[Title], [Business Name]
Pro tip: "You were right" is a two-word phrase that almost no business sends to a customer. Used sincerely and specifically, it creates more lasting loyalty than a discount code. Use it only when it's true. But when it's true, use it without hesitation.
26
Monthly Voice Feedback Summary — To All Staff
[Month] Feedback Roundup — What We Heard, What We're Doing
Each month we share a summary of what came through our voice feedback channels. Here's [Month]:
Volume:
[X] total voice messages • [X] customer • [X] employee
Sentiment:
[X%] positive • [X%] neutral • [X%] negative
[Context: e.g. "Positive sentiment up 8 points month-over-month, the highest since last October."]
Top themes from customers:
1. [Theme with one-line context]
2. [Theme with one-line context]
3. [Theme with one-line context]
Top themes from employees (anonymous):
1. [Theme with one-line context]
2. [Theme with one-line context]
Changes made this month based on feedback:
• [Change 1 — what changed, briefly why]
• [Change 2 — what changed, briefly why]
One message that stayed with us (anonymized):
"[A real quote from a customer or employee that captures something worth hearing]"
Questions or thoughts: [Name] at [email].
— [Operations / GM / People Team]
Pro tip: The "one message" section is the element managers cut when they're short on time. Do not cut it. A single human voice embedded in a data report is what people remember when they're deciding whether to give feedback next month. The data tells them it works. The quote reminds them that someone actually read it.
27
Quarterly Culture Report — Leadership Version
Q[X] [Year] Employee Voice Feedback: Culture Intelligence Brief
Prepared for: [CEO / Board / Leadership Team]
Prepared by: [HR Director / People Lead]
Classification: Confidential
Executive Summary:
Employee voice sentiment in Q[X] was [positive / mixed / showing early warning signs] overall, with notable improvement in [area] and an emerging concern in [area] that warrants leadership attention.
Key data:
• Submissions: [X] total (participation rate: [X%] of eligible employees)
• Sentiment index: [Score] vs. [prior quarter] ([direction and magnitude of change])
• Participation trend: [Increasing / Stable / Declining — note if declining, as this is itself a signal]
Strengths (what employees report is working):
[Theme with supporting data and sample language]
[Theme with supporting data and sample language]
Concerns requiring leadership attention:
[Theme with supporting data, honest assessment, and recommended action]
[Theme with supporting data, honest assessment, and recommended action]
Emerging signals (early; not yet a pattern, but worth watching):
[1-2 themes appearing for the first time this quarter, with context]
People risk assessment:
[Honest assessment: e.g. "Flight risk indicators are elevated in [department]. Three of the last four voluntary departures came from this group. The recurring theme of [issue] in this cohort's voice submissions suggests a systemic issue, not individual cases. If unaddressed, we project [X] additional departures in the next two quarters."]
Recommended leadership actions:
1. [High-priority action with owner and deadline]
2. [Medium-priority action with owner and deadline]
3. [Watch and monitor item]
Budget implications:
[Any resource requirements to address priority themes]
Appendix: Full theme breakdown available on request. All data anonymized per voice feedback policy.
Pro tip: The people risk assessment section is the one that makes this document strategic rather than descriptive. Naming a flight risk in a board brief before someone walks out the door is precisely why CEOs fund people programs. Be honest, be specific, and be early. That's the entire job.
28
Feedback That Led to a Policy Change — Company Announcement
Team,
I want to share a change we're making — and I want to be transparent about what caused it.
Over the past [timeframe], a number of people shared feedback through our anonymous voice channel about [the issue, e.g. "our policy requiring manager approval for any work-from-home day, even on an ad-hoc or personal emergency basis"]. The feedback was consistent, the reasoning was clear, and frankly it was correct.
After reviewing what was shared and discussing it with [the leadership team / HR / the affected teams], we've changed the policy.
Effective [Date]:
[New policy stated in plain language, e.g. "You no longer need advance approval for occasional work-from-home days. You do need to inform your direct manager before 9am on the day. The expectation of full availability and productivity remains unchanged. The trust goes both ways."]
This is a direct result of your feedback. The voice channel works because you use it and tell us the truth, and because we take what you say seriously enough to act on it.
[If appropriate:] For those who submitted feedback on this specific topic: thank you. You changed something.
[CEO / HR Director / GM Name]
Pro tip: Credit the feedback system by name every time a policy change comes from it. You're not just announcing a policy update — you're proving to your entire organization that speaking up works. Every announcement like this increases participation in the next feedback round by a measurable margin.
WhatsApp & Digital
For businesses running WhatsApp feedback and ordering channels with AI handling first-touch responses. These templates define what the AI sends and precisely when the human takes over — because the handoff moment is where digital experience either breaks or distinguishes itself.
29
WhatsApp Order Confirmation (AI-Generated, Customer Receives)
[Confirmation message — sent immediately on order placement:]
Hi [First Name]! Your order is confirmed. Here's what we have:
*Order #[Order Number]*
[Item 1] — Qty [X] — [Price]
[Item 2] — Qty [X] — [Price]
[Special instructions if captured, e.g. "*Note: No onions on the burger — confirmed.*"]
*Total: [Amount]*
*Estimated ready: [Time]*
[If delivery: "*Estimated delivery window: [Time].*"]
We'll message you the moment it leaves us. If anything looks wrong above, just reply here — we'll fix it straight away.
Once your order arrives, we'll send a one-question check-in. Your honest answer genuinely helps the team. Ten seconds, no pressure.
Thanks for ordering with [Business Name].
---
[Post-delivery follow-up — sent 30 minutes after estimated delivery time:]
Hi [First Name] — did everything arrive okay?
How was your experience today?
Reply with:
*Great* — everything was perfect
*Okay* — it was fine, nothing special
*Had an issue* — something went wrong
If you had an issue, just tell us what happened and a real person will be in touch within the hour.
Pro tip: The three-option reply format (Great / Okay / Had an issue) gets 3-4x more responses than an open-ended question. People ignore "how was your experience?" They'll tap one word in under a second. Start binary, then pull detail from the negatives with a human follow-up call.
30
WhatsApp Escalation Handoff — AI to Manager
[AI sends to customer:]
Hi [First Name], I can see this is important and I want to make sure you get the right help quickly. I'm connecting you now with [Name], our [manager / customer experience lead], who can resolve this properly. They'll be with you in just a moment.
Thank you for your patience.
---
[Simultaneous alert to Manager via Slack / SMS:]
WHATSAPP HANDOFF — RESPONSE REQUIRED
Customer: [Name]
Number: [WhatsApp number]
Order / Reference: [ID if applicable]
Handoff time: [Time]
SLA: Respond within [10] minutes. Breach at: [Time]
Reason for escalation:
[AI-generated summary, e.g. "Customer reporting delivery arrived with incorrect items. Requests full refund. Tone: frustrated but civil. Urgency score: Medium. No safety concerns."]
Full conversation: [Link to chat log]
Suggested approach:
[e.g. "Acknowledge the error without asking them to re-explain. Offer refund or replacement immediately. Do not suggest they re-order through the app — this was flagged as a friction point in their message."]
---
[Manager responds in the same WhatsApp thread:]
Hi [First Name], I'm [Name], [the manager on duty / the customer experience lead]. I've read through what happened and I'm sorry.
[Address the specific issue directly. Offer the resolution. Do not ask any question the customer already answered in the chat above.]
Pro tip: The handoff fails almost every time when the manager asks the customer to repeat information they already gave the AI. Before typing anything, read the full conversation thread. "I've read through what happened" is the three most important words in the manager's opening line — because they prove you did the work before you picked up the thread.
Templates are only as good as the feedback behind them
Every template here starts with a voice message someone actually recorded. VoiceZero gives you the system to collect that voice — and the AI tools to know which template to reach for.
Start collecting voice feedback free →