Use Manager Office Hours to Restore Practice
Turn a lightly attended manager office hour into a focused support routine.
A quiet office hour is useful evidence. Attendance alone does not explain why managers stayed away. A vague invitation, a forecast meeting, or an urgent customer issue might have taken priority. Start with details already available. Read the invitation. Check when managers received the notice. Look at replies, calendar conflicts, and earlier questions from manager meetings. Then ask an enablement leader for one coaching situation managers face often. A customer success manager gains a better starting point from this small review than from a broad request for more attendance.
Give each session one clear job. A manager who needs help opening feedback after a weak discovery call has a different need from a manager who wants help reading a report. Combining both needs in one meeting leaves people unsure about attendance or preparation. Name the problem in plain language, state who belongs in the room, and describe one result participants will leave with. A narrow promise helps managers decide whether their calendar time is worthwhile. The focused promise also gives the customer success manager a way to judge topic fit after the meeting.
Consider this fictional account situation. Kay leads enablement for a sales group. She tells customer success manager Andre, “Two managers joined our last office hour.” Andre asks, “What did your note ask managers to work on?” Kay shows a subject line reading, “Optional manager help.” Andre asks which coaching conversation managers have raised during recent meetings. Kay says managers delay feedback after discovery calls because opening a direct conversation feels awkward. Andre writes down her words. He avoids offering a format before learning what managers need.
Andre responds, “Would a thirty minute session on opening discovery call feedback serve those managers? Everyone brings one reviewed moment and leaves with a first question.” Kay says managers resist long workshops, yet Thursday at 3:00 already belongs to manager development. Andre asks whether a respected manager would introduce a focused session. Kay names Priya, who has spoken about shallow call feedback during leadership meetings. Kay agrees to ask Priya to invite six managers whose teams recently reviewed discovery calls. The choice connects an office hour with a familiar work problem.
The invitation should answer practical questions without extra promotion. Kay writes, “Managers preparing feedback after discovery call reviews are invited Thursday at 3:00. Bring one call moment and write an opening question for your next conversation.” She asks for replies by Wednesday noon. Each reply includes a short description of the call moment, without customer details. Andre suggests a response list rather than an attendance promise. Four replies indicate managers see relevance. No replies suggest a problem with timing, sponsor support, or wording. Either result guides the next decision.
Preparation protects the session from turning into an open ended help desk. Kay asks each attendee to select one moment where a seller moved into a product detail before learning a buyer goal. Priya reviews the selected moments and removes account names from shared notes. Andre prepares a private worksheet with room for a first question, a likely seller response, and a follow up question. The worksheet is not a script. Managers use their own words and adapt them to their team. Preparation gives everyone a real situation instead of a vague complaint.
Priya opens the fictional session by saying, “Feedback feels harder when you wait until a full call review is complete. Today we will work from one moment.” Andre asks managers to write an opening question silently. One manager writes, “What were you hoping would happen after your first question?” Another writes, “What led you toward product detail before you knew the buyer goal?” Priya asks each manager to read their question aloud and explain why they chose this wording. The group tests whether each question invites reflection instead of a defensive answer.
A short agenda keeps attention on practice. Priya uses five minutes to restate the problem and collect each manager’s call moment. Managers use fifteen minutes to write, read, and revise an opening question. The remaining time goes to obstacles raised from their own reviews. Andre asks a manager what they expect a seller to say, then asks how they will respond if silence follows. He does not take over coaching judgment. When someone asks whether a score should require a certain action, Priya records the issue for the internal quality lead.
After the meeting, Kay collects signals suited to this routine. Attendance shows who protected time. Reply notes show whether the invitation prompted preparation. Submitted examples show whether managers understood what to bring. Kay also asks one short question: “Which part of your next feedback conversation feels easier to begin?” A fictional manager writes, “Choosing one moment helped me prepare.” Another asks for a future session on setting next steps after feedback. Kay places both notes beside the date and topic for Priya to review before scheduling another session.
Do not treat a room full of attendees as proof of better coaching. Kay and Priya choose an observation inside their normal work rhythm. At a later manager meeting, Priya asks participants to share an opening question they used and what happened next. Kay tracks recurring requests from office hours beside questions raised during manager meetings. If managers bring prepared examples yet attendance drops after two sessions, the topic sequence needs attention. If people do not reply before a session, Kay asks Priya about competing meetings before moving the time.
Ownership needs names. Kay owns the invitation, reply list, and follow up question. Priya owns manager context and the opening message. Andre owns preparation support and notes on recurring obstacles. Their shared note places each task beside a date. On Wednesday morning, Kay sees whether Priya confirmed the invitees. If confirmation is missing, Kay decides whether a short postponement will protect the session. If replies show two managers have closely related call moments, Priya plans a paired discussion rather than two unrelated examples.
Use a fictional practice situation before changing a live routine. Give a colleague an invitation reading, “Office hours for managers.” Ask what coaching problem started the request, when managers face a similar problem, and what one item belongs in preparation. Rewrite the invitation aloud with those answers. Then ask your colleague to say Thursday conflicts with forecast review. Offer a choice between moving one week later or asking Priya which development slot managers already protect. Listen for wording which makes a decision easier for Kay.
In the fictional account, Kay sends the revised invitation on Tuesday morning. Four managers reply before Wednesday noon, each with one discovery call moment. Priya adds a note from a manager who wants help opening feedback without sounding accusatory. Kay places the four moments in a private agenda, reserves one space for a new issue, and schedules Priya’s opening message for 2:55 on Thursday. Andre begins by asking the first manager to read the opening question they plan to use after their review.
Practice these next
Address uneven use of summary tools through workflow evidence, quality review, and explicit local ownership.
Coordinate adoption work when a contact center opens a new site with unfamiliar processes.
Use an operational review to revise goals, evidence, and ownership after a contact center changes direction.
Keep contact center coaching data in context when an HR team asks about workforce decisions.
Protect daily platform routines when experienced supervisors move teams or leave the contact center.
How a customer success manager can address outdated answers that affect agent confidence and customer effort.