Confidence Week.
Five days. Five videos.
One calmer team.
Customer Service Week usually means donuts and a banner. This year, give your team the thing that actually helps on Tuesday at 2:40 PM when a customer says this is ridiculous: the exact words to say, and the confidence to say them. One short video a day, a two-minute team conversation, and a way to rehearse the hard call before it happens.
Free. No sign-up. Built for frontline teams, and for the managers who lead them. This is the same material I teach inside Amazon, Walmart, McDonald's, and three NFL franchises, opened up for one week.
How to run the week
Ten minutes a day. That is the whole commitment.
Confidence is not a mood. It is a skill, and skills are built by repetition, not by inspiration. So the program is deliberately small. Do these three things each day, Monday through Friday, and by Friday your team will sound different on the phone. Nothing here asks anyone to bend a policy. Every phrase works inside the rules you already have. It changes how the rules sound, not what they are.
Watch
Play the day's video at the start of the shift, in the huddle, or send the link the night before. Each one runs under fifteen minutes and most are shorter. Cannot pull everyone off the phones at once? Run it by shift, or let people watch on their own and bring the Try It Today phrase to the next huddle.
Talk
Ask the two huddle questions under each video. Two minutes, no slides. The talking is where the confidence gets built, because people hear themselves say the new words out loud.
Rehearse
Use the day's Try It Today phrase on a real call, and if you want to go further, run one of the AI rehearsal prompts below. Practice on a fake customer so the real one gets your best.
The five days
One video a day. One skill a day.
Each day builds on the last: saying no, cooling the temperature, handling the supervisor request, dropping the reflex apology, and holding the floor when you are interrupted. By Friday, that is a complete confident call.
How to Say No to a Customer Without a Fight
Most escalations do not start with anger. They start with a no that landed like a wall. Today is about saying no and staying calm while you do it, by giving the customer two doors that are actually open instead of one that is shut.
What is the no you dread saying most this week?
What are the two things you CAN offer in that moment?
Here is what I can do.
Ten Anti-Inflammatory Phrases That Calm an Angry Customer Fast
Some words pour gasoline. Some words pour water. Today you get ten sentences that do the second thing, so you stop bracing for what the customer will say and start steering what happens next.
Which of the ten phrases do you already use? Which one have you never tried?
What is the phrase you catch yourself saying that makes things worse?
I hear you, and I have a plan.
Why Customers Ask for a Supervisor
"Let me speak to your supervisor" feels like a verdict on you. It is not. Once you understand what the customer is really asking for, you can handle the request without flinching, and often without the transfer.
What do you think the customer actually wants when they ask for a supervisor?
What would you need to feel confident handling it yourself?
I can help you with that, and here is how.
Why You Should Never Apologize to a Customer
Some of us over-apologize, and it is usually nerves talking, not manners. Every extra sorry hands the customer a little more power and makes you sound a little smaller. Today you learn what to say instead, so you sound accountable without sounding afraid.
Count your sorrys on your next three calls. What is the number?
What would you say in place of the second and third one?
You are right. That should not have happened. Here is what I am doing about it.
What To Do When a Customer Interrupts You
You cannot win a fight for airtime, and trying makes you sound like a rep who would rather talk than listen. Today is about getting the floor back without raising your voice or losing your place. The calm version of holding your ground.
What is your instinct when a customer talks over you? Louder, faster, or quieter?
What is one sentence you could hold ready for the moment they pause?
Marcus, I want to get this right for you, so here is what I can do.
A note from Myra
Five videos will change how your team sounds this week. They will not change how your team sounds in March. That takes rehearsal on your real calls, with your real policies, in a room where it is safe to get it wrong first. That room is what I build for seventeen teams a year, and I explain how it works further down this page. Finish the week first. Then decide.
Rehearsal prompts
Practice the hard call before it happens.
Pilots do not wait to feel calm before an emergency. They run the checklist, and the calm follows. These three prompts turn any AI assistant into a difficult customer you can practice on. Copy one, paste it into Claude, ChatGPT, or Copilot, and play it out. Ten minutes of rehearsal changes how the real call sounds.
One rule: never paste a real customer's name, account number, or personal details into any AI tool. Describe the situation, not the person.
The Two Doors Rehearsal
Use before a shift where you know a no is coming.
You are an angry customer and I am the customer service representative. Play a customer who is demanding something I cannot give: a full refund on a non-refundable purchase. Start at an intensity of 4 out of 5. Stay in character and respond only as the customer. Do not coach me until I type DEBRIEF. When I type DEBRIEF, step out of character and grade my last three responses on these criteria: 1. Did I acknowledge before I redirected? 2. Did I offer two doors that were actually open instead of restating the one that was closed? 3. Did I use any hedge words (um, I think, maybe, let me see if) or apology stacking? 4. Did I end with a clear next step? Give me one thing I did well, one thing to change, and the exact sentence you would have said instead. No em dashes in your writing. Begin now as the customer.
The Apology Audit
Use after a call or email you keep replaying.
I am a customer service professional working on sounding confident instead of anxious. I over-apologize. Below is what I said (or wrote) to a customer. Do three things: 1. Count every apology, softener, and hedge (sorry, unfortunately, I think, just, maybe, if that is okay, I apologize). 2. Rewrite my response with at most one acknowledgment and zero apologies, keeping it warm and accountable. Use the structure: name the truth plainly, then say what I am doing about it, then say what happens next. 3. Tell me in two sentences what my original version was signaling to the customer. Keep your rewrite under 120 words and do not use em dashes. Here is what I said: [PASTE WHAT YOU SAID HERE]
The Supervisor Request
Use with someone who freezes when the customer asks for a manager.
Role play with me. You are a frustrated customer who has just said "I want to speak to your supervisor." You have already explained your problem once and you do not want to repeat it. I am the representative. Your goal is to test whether I can keep you with me without a transfer. Stay in character. Escalate if I get defensive, apologize repeatedly, or recite policy. De-escalate if I acknowledge you, take ownership, and give you a concrete plan with a time attached. After four exchanges, or when I type DEBRIEF, step out of character and tell me: 1. The exact moment you decided whether to trust me. 2. Any sentence that made you angrier. 3. A better version of my weakest line. Do not use em dashes. Start now with your first line as the customer.
Want the full guided version, with a scoring rubric and my feedback built in? The free rehearsal is at myragolden.com/rehearsal.
The warm-up bank
Sixty seconds before the shift.
Confidence is built in the minute before the call as much as on it. Six Shorts, each under a minute, each one a single idea to carry into the next conversation. Play one at the top of the huddle, or send one to the teammate who is having a day.
The manager's playbook
How to lead the week without adding to your week.
Everything below fits inside the huddles you already run. Print this section, tape it by your desk, and follow the schedule. Recognition matters, but recognition attached to a skill matters more, so every idea here points back to the day's lesson.
The schedule
Ten minutes a day. Watch, talk, try.
| Day | Watch | Talk about | Recognize |
|---|---|---|---|
| Monday | How to Say No to a Customer Without a Fight | The two doors you can always open | Whoever names the no they dread out loud first. Courage starts the week. |
| Tuesday | Ten Anti-Inflammatory Phrases That Calm an Angry Customer Fast | Water words versus gasoline words | Catch someone using one of the ten phrases on a real call and say so in front of the team. |
| Wednesday | Why Customers Ask for a Supervisor | What the customer really wants from a supervisor | The person who kept a supervisor request without a transfer. Tell the story at Thursday's huddle. |
| Thursday | Why You Should Never Apologize to a Customer | What to say instead of the second sorry | Lowest sorry count wins. Make it a friendly competition, not a scolding. |
| Friday | What To Do When a Customer Interrupts You | Getting the floor back calmly | Everyone who made it through the week. Hand out the certificate below and mean it. |
The phrases card
Five sentences that sound sure, even when you are not. Print it, post it, say it out loud.
- Here is what I can do.Skips the apology spiral and walks the customer to the open door.
- I am going to take care of this. Give me two minutes.An action and a time. People relax around plans.
- I hear you, and I have a plan.Lowers the temperature, then announces the adult in the room has arrived.
- That is a fair question. The answer is...Then answer it. No preamble, no hedge.
- Let me tell you what happens next.The ending is the part they remember. Nobody escalates a call that ends with a plan.
The Friday challenge: The Second Take
Ask everyone to bring one call from the week they wish they could redo. Not the worst one, the one they keep replaying. In pairs, they run it again using the week's tools: two doors, an anti-inflammatory phrase, one acknowledgment instead of three apologies, and an ending that names what happens next. Two minutes per person. Then ask the room what changed. That conversation is the whole point of the week.
Three recognition ideas that stick
- The Confidence Wall. A shared doc or whiteboard where teammates post one sentence a colleague said this week that they want to steal. Specific beats generic every time.
- The handwritten note. One line from you to each person naming one specific thing you heard them do well. People keep these for years.
- The certificate. Print the one below for everyone who finished the week. It is small, and it is not nothing.
Your certificate
Finished the week? Print your certificate.
Type your name exactly as you want it to appear. A one-page certificate signed by Myra opens ready to print or save as a PDF.
Managers: print one for each person, or send them this link and let them print their own.
Where I come in
If this is what I give away, imagine what your team gets in the room.
I am Myra Golden. For twenty-five years I have done one thing: teach the people who take the hard calls exactly what to say, and rehearse it with them until it is theirs. 3.2 million people trained. Amazon, Walmart, Coca-Cola, McDonald's, Frito-Lay, Lowe's, Lands' End, Victoria's Secret, Bath & Body Works, Fabletics, and three NFL franchises. My LinkedIn Learning courses are among the most watched on the platform, and the frameworks on this page, The 3R Conversation Control Method™, The Baby Chimp Effect™, and the Two Doors close, are taught on call center floors and retail floors across the country.
Before any of that, I was the supervisor they asked for. I ran a call center floor, took the escalations nobody else could close, and watched good people freeze on calls they knew how to handle. That is where this work started, and it is why I do not teach theory. I teach the sentence.
Here is what I have learned in those twenty-five years. Nobody has a knowledge problem. Every rep on your team knows they should stay calm. What they do not have is the sentence, rehearsed until it comes out before the nerves do. That is the only thing I build, and I build it from your calls, not mine.
The Monday after
Picture your floor three weeks from now.
A customer says this is ridiculous and your newest rep does not flinch. She says the customer's name, opens two doors, and the call ends with a plan instead of a supervisor request. The rep next to her has stopped apologizing four times per call, because she does not need to anymore. Your supervisors are coaching to a shared language instead of putting out fires. Escalations drop, not because you told anyone to escalate less, but because fewer calls ever get that hot. And the person who used to dread Tuesday afternoons is the one other reps come to for the words.
For you, it shows up in the numbers you already watch: escalations, repeat calls, QA scores on the empathy and ownership lines, and how often your name gets pulled onto a call. It also shows up somewhere you do not measure. You stop being the fire department.
That is not a mood. It is a set of sentences, rehearsed on your real scenarios, in a room I run. It holds, because we built it in their mouths, not on a slide.
How it works
Application first. Then we build it from your calls.
Apply
Four questions, about four minutes. The application is not a test. It is how I keep a seventeen-date calendar honest. I read every one myself within two business days and tell you plainly whether I am the right fit. Sometimes I am not, and I will say so.
Discovery
A short call, then a questionnaire and a story-mapping session with my creative director. I want your real escalations, your real policies, and the three calls your team dreads most. The workshop is built from those, not from a deck I already own.
The room
In person or live virtual. Your team practices on customers built from your scenarios inside the 3R Live Lab, gets the words, says them out loud, and leaves with a shared language your supervisors can coach to on Monday. Nothing is theory. Everything is said aloud.
For distributed and enterprise teams: live virtual reaches every site and every shift, the scenarios are built to your policies and your QA scorecard so nothing I teach conflicts with what you already coach to, and every engagement includes a supervisor coaching guide so the language survives turnover and new-hire classes.
This is for you if
- Your team takes the calls nobody wants: refunds you cannot give, policies customers hate, the moment after the bot failed them.
- You have tried scripts and scorecards, and your best people still sound unsure when the customer gets loud.
- You want a shared language your supervisors can coach to, not a motivational hour that fades by Friday.
- You run a team of any size. I have built this for a twelve-seat retail support desk and for enterprise contact centers with thousands of agents across airports and continents. The method scales. The scenarios are always yours.
This is not for you if
- You want a keynote that makes people feel good and changes nothing on Monday. I can be inspiring, but that is not what you are paying for.
- You are not willing to hand me your real calls. Generic scenarios produce generic reps.
- You need it next week. The build takes time because it is built for you, which is exactly why it holds.
Seventeen dates a year. That is all I take.
Two dates left in 2026. Two open in the first quarter of 2027.
I cap the calendar at seventeen engagements so every team gets the build, the rehearsal, and me, not a franchise version of me. As this page goes live for Customer Service Week, two dates remain in 2026 and two in January through March of 2027. When those are gone, the waitlist gets first pick when new dates open, roughly three times a year, before anyone else hears about them.
Updated October 5, 2026. The application takes about four minutes and commits you to nothing but a conversation.
Every application is read by me, personally, within two business days.
