A high-value customer is experiencing a critical outage due to an integration issue with a third-party API, and their internal technical team is blaming your product's recent update. How would you, as a Customer Experience Manager, navigate this blame game, de-escalate the tension, and lead a collaborative effort with both your engineering team and the third-party vendor to identify the root cause and restore service, while maintaining the customer relationship?

CIRCLES Method for Crisis Management:

1. Comprehend the Situation: Immediately acknowledge the customer's critical outage and their team's perception. Gather initial facts without assigning blame.
2. Identify Stakeholders: Pinpoint key contacts: customer's technical lead, your engineering lead, third-party vendor's technical lead, and your account manager.
3. Report & Reassure: Communicate empathy and commitment to resolution. Reassure the customer that all resources are being mobilized.
4. Collaborate & Coordinate: Establish a joint war room/communication channel. Facilitate a technical bridge call with all parties. Focus on data-driven diagnostics.
5. Lead Investigation: Guide the teams to systematically isolate the issue (e.g., API logs, recent changes, network traces). Use a 'no-blame' post-mortem approach.
6. Execute Resolution: Prioritize and implement fixes. Communicate progress transparently and frequently to the customer.
7. Sustain Relationship: Post-resolution, conduct a follow-up, review preventative measures, and rebuild trust.

My immediate priority would be to de-escalate tension and establish a collaborative problem-solving environment. I'd initiate a 'no-blame' incident management protocol, focusing purely on data and resolution. First, I'd acknowledge the customer's frustration and the severity of the outage, reassuring them of our full commitment. I'd then convene a joint technical bridge call, including the customer's technical lead, our engineering lead, and the third-party vendor's technical representative. During this call, I would act as a neutral facilitator, ensuring all parties present their findings objectively, focusing on log analysis, API call traces, and recent change logs from all systems involved. My goal would be to guide the conversation towards identifying the precise point of failure, rather than assigning blame. Post-resolution, I'd conduct a thorough post-mortem analysis with all stakeholders to document the root cause, implement preventative measures, and rebuild trust through transparent communication and a clear action plan for future stability.