總覽 / 示範對話

示範對話|Set 5:客訴處理與致歉

卡 01 交貨延遲的緊急來電

角色:Client = 客戶採購總監(強硬施壓)/You = Nexchip 客戶成功經理

  1. Client: "This is the third time Nexchip has pushed back the delivery date. My production line stops on Friday. What exactly are you going to do about it?"
  2. You: "Mr. Chen, I hear you, and I want to resolve this today. I completely understand your frustration, and I take full responsibility for keeping you informed from now on." → 我聽到了,也想在今天解決。我完全理解您的不滿,從現在起由我負全責向您回報。(先承接情緒,不辯解)
  3. Client: "Words are cheap. I've heard promises from your sales team twice already. What's different this time?"
  4. You: "A fair question. Let me walk you through exactly what happened and what we're doing to fix it. Our wafer supplier had an equipment failure that cost us ten days — that's context, not an excuse — and we've since qualified a second source." → 讓我完整說明發生了什麼與補救措施。"That's context, not an excuse."=這是背景說明,不是藉口。
  5. Client: "I don't care whose equipment failed. My line stops Friday. What arrives before Friday?"
  6. You: "As an immediate step, we can arrange a partial shipment by air freight at our cost — forty percent of the order, landing at your dock Thursday morning." → 立即措施:部分貨品空運、費用我方承擔,週四早上到貨。
  7. Client: "Forty percent buys me maybe a week. What about the rest?"
  8. You: "The remaining sixty percent ships in two batches, next Wednesday and the Friday after. I'll send you the lot-level schedule within the hour so your planners can work with real dates."
  9. Client: "And if that slips again? Frankly, we're considering switching suppliers."
  10. You: "I'd ask you to judge us on the next two weeks, not the last two. Starting today you'll get a daily status update at 9 a.m. your time — and if any date moves, you hear it from me first, not from a late shipment." → 挽留句:請用接下來兩週評斷我們。任何日期變動,您會第一個從我這裡得知。
  11. Client: "I also want to talk about the penalty clause. This delay has a cost."
  12. You: "You're entitled to raise that, and we won't walk away from it. May I suggest we secure your production first, and put the commercial discussion on Monday's agenda once your line is safe?" → 先解決、再談賠償:您有權提出、我們不迴避,但先保住產線,商務問題週一談。
  13. Client: "Fine. But if Thursday's air shipment slips, we're done."
  14. You: "Understood. Let me recap our commitments: forty percent arrives by air Thursday morning at our cost; the balance ships on the 20th and the 29th; you get a daily 9 a.m. update from me; and we meet Monday on commercial terms. You'll have all of this in writing within thirty minutes." → 結尾 recap & commitment:總結行動項目+回報時間,30 分鐘內書面確認。
  15. Client: "Make sure it happens."
  16. You: "You have my word. Thank you for the straight talk today — it helps us fix this faster."

Useful takeaways

  1. 開場先承接情緒(I hear you / I completely understand your frustration),再進入事實,順序不能反。
  2. 說明原因時加一句 "That's context, not an excuse.",既交代背景又不顯得推責。
  3. 補救方案要給「可驗證的具體數字」:幾 %、哪一天、到哪裡、誰付錢。
  4. 面對「考慮換供應商」,用未來式挽留:"Judge us on the next two weeks, not the last two."
  5. 賠償話題不迴避但排序後移:"We won't walk away from it — let's secure your production first.",結尾必做 recap+書面確認時點。

卡 02 瑕疵批次的致歉會議

角色:Client = 客戶品質工程主管(冷靜、要數據)/You = Nexchip 品保主管

  1. Client: "We've completed incoming inspection on lot #A-2273. The defect rate is 3.1%, which is four times your contractual limit. We need a formal explanation."
  2. You: "You'll get one today, with data. But first — on behalf of Nexchip, I sincerely apologize for the quality escape in this lot. This should not have reached your dock." → 正式致歉句型:sincerely apologize for+具體事項(quality escape),不是輕飄飄的 sorry for the inconvenience。
  3. Client: "Apology noted. What's the root cause?"
  4. You: "Our root cause analysis points to a calibration error at the final test stage. A tester was recalibrated on June 3rd against an out-of-spec reference unit, so marginal parts passed that should have been rejected." → 根因指向最終測試站的校準誤差——給日期、給機制,展現調查已做。
  5. Client: "How many lots went through that tester in that window?"
  6. You: "Three. Lot #A-2273, which you have, plus two lots still in our warehouse — both quarantined as of yesterday. Yours is the only affected lot that shipped."
  7. Client: "What's your containment plan for the parts already on our line?"
  8. You: "As containment, we ask you to stop using the lot immediately; our team can be on site tomorrow to 100%-rescreen your floor stock. Separately, we will replace the entire lot free of charge and submit a corrective action report within five business days." → 圍堵與矯正分開講:先止血,再附免費換貨與 5 個工作天內交 CAR 的承諾。
  9. Client: "A CAR in five days is fine. What corrective actions are you actually considering?"
  10. You: "Two directions: locking the calibration recipe so an out-of-spec reference physically can't be loaded, and adding a golden-unit verification at every shift start. We are committed to preventing recurrence through both — but I'd rather confirm effectiveness with data in the CAR than over-promise today." → 不說 guarantee this will never happen again,改說 committed to preventing recurrence through…,保住可信度。
  11. Client: "Good. I've heard 'never again' too many times in this industry. We may also want to audit your line."
  12. You: "You'd be more than welcome. An on-site audit would let you verify the fixes first-hand — shall we target the week after the CAR is issued, so you're auditing actions rather than intentions?" → 歡迎稽核並主動給時程:讓客戶「驗證行動」而非「聽取意圖」。
  13. Client: "Reasonable. Timeline on the replacement lot?"
  14. You: "Replacement parts ship in ten days by air, at no charge. To recap: line-stop and on-site rescreen tomorrow, CAR within five business days, replacement in ten days, audit the following week."
  15. Client: "Send me the containment confirmation and quarantine records in writing today."
  16. You: "You'll have both by end of day. And once more — I apologize for the escape, and thank you for handling this with us so professionally."

Useful takeaways

  1. 重大品質事故的致歉公式:on behalf of + 公司, I sincerely apologize for + 具體事項,替公司具名扛責。
  2. 根因說明帶「日期+機制+波及範圍」三件套——冷靜型客戶要的是數據不是情緒。
  3. 明確區分 containment(今天止血)與 corrective action(防止再發),分開報告。
  4. 永遠不說 "guarantee it will never happen again",改用 "committed to preventing recurrence through + 具體措施"。
  5. 客戶要稽核時反守為攻:"You'd be welcome — so you're auditing actions rather than intentions." 並主動提時程。

卡 03 帳單錯誤的客服對話

角色:Client = 客戶行政經理(疲憊、不信任)/You = Orion Telecom 企業客服專員

  1. Client: "I've called twice about this billing error already. Each time someone promises a callback, and nothing happens. I want this fixed on this call — not next week."
  2. You: "You're right, and I'm sorry you've had to chase us on this — that's not the experience we want you to have. I'm not transferring you anywhere; we resolve it on this call." → 您說得對,很抱歉讓您一再追問。加一句「不轉接、這通就解決」,直接回應對方核心要求。
  3. Client: "That's exactly what the last agent said."
  4. You: "Understood — then let me show you rather than tell you. Give me sixty seconds. … I've pulled up your account, and I can confirm the roaming charges were applied in error." → 已調出帳戶,確認漫遊費確實誤收。"Show you rather than tell you"=用行動而非承諾重建信任。
  5. Client: "Finally, someone says it plainly. How did this even happen?"
  6. You: "Your corporate plan includes an APAC roaming bundle, but a plan migration in April dropped that bundle from your account, so calls were billed at standard rates — and here's what I'm doing right now: re-attaching the bundle and reversing the charges." → 說明原因後立刻接行動:and here's what I'm doing right now——只解釋不行動等於沒道歉。
  7. Client: "How much comes back to us?"
  8. You: "NT$38,400 — the full overcharge across the May and June bills. I'm issuing the credit right now, and I'll stay on the line until you see the confirmation email." → 立即開立折讓,並在線上等您收到確認信——把「解決」變成對方看得到的事實。
  9. Client: "And next month? Am I going to be making a fourth call?"
  10. You: "Honest answer: I can't promise a system will never fail. What I can promise is that I've flagged your account for manual review on the next two billing cycles, and you're getting my direct line — if anything looks off, you call me, not the queue." → 無法保證系統不出錯的誠實安撫法:「我不能保證 X,但我能保證 Y」,Y 是自己可控的行動。
  11. Client: "Hmm. And what about all the time my team has wasted on this?"
  12. You: "That's fair to raise. We'd like to apply one month's credit on the roaming bundle as an apology — not to close the subject, but because your team spent real time fixing our mistake." → 主動補償而不像打發人:說明補償的「理由」(你們花了真實時間),而非只丟數字。
  13. Client: "…Alright. The email just came in. The credit is showing."
  14. You: "Great. To recap: charges fully reversed, bundle restored, your next two bills manually reviewed, one month's credit applied, and I'm your single point of contact going forward — my direct number is in that email. Anything else on the account while I have it open?"
  15. Client: "No, that covers it. Thank you — this is what should have happened on the first call."
  16. You: "Agreed, and I'm sorry it took three. You'll also hear from me after the July bill posts, just to confirm everything is clean."

Useful takeaways

  1. 對「追了很多次」的客戶,第一句先認錯+共情:"You're right, and I'm sorry you've had to chase us on this."
  2. 信任破產時少承諾多示範:"Let me show you rather than tell you.",當場做給對方看。
  3. 解釋原因後必須立刻接行動句 "…and here's what I'm doing right now.",禁止在解釋處收尾。
  4. 不能保證的事用「I can't promise X, but I can promise Y」句式,Y 必須是自己可控的具體行動。
  5. 結束前三件事:recap 已完成項目、指定唯一窗口(single point of contact)、約定主動回報時點。

卡 04 大規模斷網的高層致歉與賠償談判

角色:Client = 客戶營運長(層級高、引用合約)/You = Orion Telecom 大客戶事業部副總

  1. Client: "Six hours of downtime, in trading hours. Your SLA promises 99.95% availability. Before we discuss anything else, I want to hear how Orion Telecom intends to make this right."
  2. You: "There's no excuse for an outage of this scale, and you have my personal apology. Before we get to terms, let me be clear about one thing: accountability starts with us." → 高層致歉三件套:沒有任何藉口+我個人的歉意+「責任由我們先扛」,絕不提不可抗力。
  3. Client: "I appreciate that. But apologies don't recover trading losses. What actually happened?"
  4. You: "We're still finalizing the incident report, but here's what's confirmed: a fiber cut on the primary route, and our automatic failover did not switch over as designed. You'll have the full root cause analysis by Wednesday noon." → 報告未完成時只講已確認事實,並給 RCA 明確交付時點;不猜測、不定性。
  5. Client: "Your failover failing is precisely what 99.95% is supposed to prevent. Clause 12 entitles us to service credits — and frankly, credits don't come close to what six hours cost us."
  6. You: "Under the SLA, you're entitled to service credits, and we're prepared to go beyond that given the impact." → 依 SLA 您有權獲得折抵,且考量影響我們準備超出條款補償——先肯認權利,再表態加碼。
  7. Client: "Define 'beyond.' I want a number today."
  8. You: "I understand why, and I won't hide behind process — but any figure I gave you this afternoon would be one I couldn't yet stand behind. I'd rather bring you a board-approved offer on Friday than an empty number today." → 得體地不當場承諾數字:不說「我沒權限」,而是「今天的數字我無法負責,週五給您一個核准過、算數的方案」。
  9. Client: "Friday. And in the meantime my trading systems sit on the same fragile network."
  10. You: "That's the more urgent conversation, and I'm glad you raised it. May I propose we agree on the remediation plan first, and schedule the follow-up on commercial terms by Friday?" → 先補救、後商務:是否容我建議先就補救計畫達成共識,商務條件週五前續談?
  11. Client: "Go on."
  12. You: "Three commitments, all in writing as an SLA addendum: dual-path routing over physically diverse fiber within thirty days, at no cost to you; failover drills run jointly with your team every quarter; and a direct escalation line to my organization with a fifteen-minute response commitment." → 加值補償具體化:免費雙路由、季度聯合演練、15 分鐘升級響應,全部寫進 SLA 附約。
  13. Client: "The diverse routing should have existed already. I'll accept it — as remediation, not as compensation."
  14. You: "That distinction is fair, and I accept it. Compensation remains fully on the table for Friday." → 接受「補救≠賠償」的定性,不硬拗,讓賠償談判保持乾淨。
  15. Client: "Have the incident report to me by Wednesday noon. If the RCA is thin, Friday will be a very different meeting."
  16. You: "You'll have it Wednesday noon. To recap: full RCA Wednesday, remediation starting immediately with the addendum drafted this week, and a board-approved commercial offer on Friday. And once more — you have my personal apology for what those six hours meant to your business."

Useful takeaways

  1. 高層事故對話開場:no excuse + my personal apology + "accountability starts with us."
  2. RCA 未完成時只講「已確認的事實」並給報告交付時點;絕不主張 force majeure。
  3. 被逼當場報數字的話術:"Any figure I gave you today would be one I couldn't stand behind — I'd rather bring you an approved offer on Friday."
  4. 用 "May I propose we agree on the remediation plan first…" 主導議程排序:先技術補救、後商務條件,避免過早報數被錨定。
  5. 對方定性「這是 remediation 不是 compensation」時大方接受("That distinction is fair."),賠償另桌談。

卡 05 客服態度客訴的升級處理

角色:Client = 客戶方資深工程師(感覺被冒犯)/You = Nexchip 技術支援團隊主管

  1. Client: "I don't complain lightly, but your engineer talked over me repeatedly and implied I hadn't read the manual. I've worked with Nexchip for five years and I've never been treated like that."
  2. You: "Thank you for bringing this to me directly — I take feedback about how we treat customers very seriously. And five years of partnership makes this matter more, not less." → 感謝直接反映+鄭重看待,並把「五年老客戶」轉為加重處理的理由。
  3. Client: "He kept cutting me off. When I described the log error, he said, 'That's covered in the manual, page one.' I've been in this field for thirty years."
  4. You: "That is not the standard we hold our team to, and I apologize for how the conversation made you feel. Being talked down to is unacceptable, regardless of the technical question." → 那不符合我們對團隊的標準,我為對話帶給您的感受致歉——先 validate 感受,不替部屬辯解。
  5. Client: "So what happens now? Or is this apology the whole process?"
  6. You: "No, there's a process. I will review the call recording, address it with the engineer, and get back to you personally by Wednesday." → 處理承諾三要素:有動作(調錄音)、有期限(週三前)、有本人(親自回覆)。
  7. Client: "I want him to apologize to me himself."
  8. You: "I understand why you'd want that. Let me review the recording first so I handle this fairly for everyone involved. If it happened as you describe — and I have no reason to doubt you — a direct apology is a reasonable outcome, and I will raise it with him." → 評估而不拒絕:先查證以示公正,同時用 "I have no reason to doubt you" 維持信任。
  9. Client: "Fine. And I meant what I said about the vendor scorecard."
  10. You: "That's your call to make, and I won't argue with it. I'd only ask that you score us on the complete response — including how we close this out. May I check one thing while we're talking: the boot-loop issue in your ticket — is the technical problem itself resolved?" → 不對抗負評,只請求「用完整處理過程評分」;並不著痕跡把對話導回正事。
  11. Client: "No. That's the worst part — I got lectured, and my issue is still open."
  12. You: "Then as of right now it's my issue. I'm assigning our senior engineer to your ticket today, with a workaround targeted by tomorrow noon. She'll contact you within the hour."
  13. Client: "That's more like it."
  14. You: "On the conduct matter — you'll have my personal update by Wednesday. I'll be transparent about the outcome, though I'll keep some internal details confidential. What I can tell you is this: I will handle it internally and make sure it doesn't happen again." → 對外不承諾懲處細節:內部處理、確保不再發生;透明但保留人事機密。
  15. Client: "Alright. I appreciate you taking this seriously."
  16. You: "Thank you for giving us the chance to make it right. To recap: our senior engineer calls you within the hour, workaround by tomorrow noon, and my personal follow-up Wednesday. Feedback like yours is what keeps our standards honest — I mean that."

Useful takeaways

  1. 對人不對事的客訴,第一步 validate 感受:"I apologize for how the conversation made you feel."——調查歸調查,感受先認可。
  2. 絕不替部屬辯解("He didn't mean it that way." 是大忌),也絕不對外承諾懲處,改說 "I will handle it internally."
  3. 處理承諾要三有:有動作、有期限、有本人(review the recording / by Wednesday / personally)。
  4. 客戶要求當事人道歉時:先查證以示對雙方公正,同時說 "I have no reason to doubt you" 保住信任。
  5. 道歉之外記得導回正事:"Is the technical problem itself resolved?",並當場升級資源解決它。

5 篇完成,每篇 16 輪,各卡的 3 句必用句型都已嵌入對話並附中文旁註,錯誤陷阱則反向轉化為 takeaways。剛才嘗試存檔到 materials/dialogues/set5-客訴處理示範對話.md 未獲寫入授權——如果想留檔,跟我說一聲即可再存。 nd I apologize for how the conversation made you feel.** Being interrupted and second-guessed is not support — it's the opposite." → 那不符合我們對團隊的要求標準,我為那通對話帶給您的感受致歉。(先 validate 感受,不辯解、不打折) 5. Eng: "Your apology is appreciated, but I've heard managers smooth things over before. What actually happens next?" 6. Lead: "Three concrete things. I will review the call recording, address it with the engineer, and get back to you personally by Wednesday. Not a form email — me, on the phone, with what I found and what I did." → 我會調閱通話錄音、與該工程師檢討,並在週三前親自回覆您。(把「處理」拆成可查核的三步) 7. Eng: "Review the recording, fine. But I'll say it now: I expect a personal apology from him, not just from his manager." 8. Lead: "That's a fair thing to ask, and I understand why it matters. Let me review the recording first — if it confirms what you've described, I believe he'll want to make that apology himself, and I'll make the space for it. What I won't do is stage a forced apology that neither of you would find sincere." → 請容我先調閱錄音——若內容證實您的描述,我相信他會願意親自道歉,我也會安排這個場合。但我不會安排一場雙方都覺得虛假的強制道歉。(評估而不拒絕,守住程序) 9. Eng: "Hm. That's more honest than I expected. But understand — if this isn't handled properly, it goes into the vendor scorecard." 10. Lead: "You're entitled to score us on how we behave, and I won't argue with that. I'd only ask that the scorecard reflect both the incident and our response to it — and my job this week is to make the response worth recording." → 您完全有權依我們的行為打分。我只請求評鑑同時反映事件本身與我們的處理——而我這週的工作就是讓這個處理值得被記上一筆。 11. Eng: "We'll see by Wednesday. And no, I don't want the man fired — I want him to understand what he did." 12. Lead: "Understood, and thank you for saying that. I will handle it internally and make sure it doesn't happen again — how we coach our people stays inside our walls, but the outcome will be visible to you in every future call." → 我會在內部處理並確保不再發生——如何輔導同仁屬於內部事務,但結果會在未來每一通電話中讓您看得見。(不對外承諾懲處細節) 13. Eng: "Alright. Wednesday, then." 14. Lead: "Before I let you go — I want to make sure this doesn't leave you with an unsolved problem twice over. Setting the behavior issue aside for a moment: is the original technical problem on the FPGA timing actually resolved, or is it still open?" → 暫且放下態度問題——原本 FPGA 時序的技術問題本身解決了嗎?還是仍未結案?(把對話導回正事,確認技術問題沒被客訴掩蓋) 15. Eng: "Partially. His workaround runs, but I never got the root-cause explanation because the call went sideways." 16. Lead: "Then you'll get two things by Wednesday: my follow-up on the conduct issue, and a written root-cause note from a senior engineer — reviewed by me before it reaches you. You came to us with one problem and ended up with two; by Wednesday you'll have zero." → 週三前您會收到兩樣東西:態度事件的處理回覆,以及由資深工程師撰寫、經我審閱的根因說明。您帶著一個問題來、變成兩個問題;週三前會歸零。

Useful takeaways

  1. 對人不對事的客訴,先 validate 感受:"I apologize for how the conversation made you feel" 為感受道歉不需等調查結果;替部屬辯解("He didn't mean it")是大忌。
  2. 把處理過程拆成可查核的步驟:調錄音 → 內部檢討 → 週三前親自回覆——給時限和形式(電話而非罐頭信),承諾才有重量。
  3. 對「要求當事人道歉」的回應公式:先查證 → 若屬實則促成自願道歉 → 明言拒絕「表演式道歉」,既尊重客戶也守住程序正當性。
  4. 人事處理只承諾結果不承諾細節:"I will handle it internally and make sure it doesn't happen again"——對外承諾懲處既不專業也可能違規。
  5. 別讓客訴掩蓋原始問題:用 "Setting the behavior issue aside for a moment—" 把對話導回技術正題,離開時客戶手上的問題數要歸零。

補充說明:5 張情境卡都在同一個檔案 set5-客訴處理與致歉.md 內(不是 5 個獨立檔案)。每篇對話都自然嵌入了該卡的 3 句必用句型、避開了卡上列的錯誤陷阱,並把部分「延伸追問」(如轉單挽留、不當場承諾數字、導回正事)直接演示在對話中。我原本要把全文存成 set5-示範對話.md 但未獲寫入權限——若你希望存檔,授權後我可以直接寫入。