1import{j as e}from"./index-lo9aeXuc.js";import{C as t}from"./CEMMethodChapter-BmoUcRbA.js";import"./vendor-react-Ct1rbV2t.js";import"./vendor-supabase-BxfRiNd4.js";import"./vendor-ui-CEoLnMhL.js";const o={number:5,title:"Customer Listening Architecture",promise:"Build listening systems that capture signal over noise and inform decisions through structured feedback loops.",watchTime:"4 min",toolTime:"15 min",quizTime:"3 min",videoUrl:"https://www.youtube.com/embed/YpJvZZyu0So",takeaways:["Most organisations collect more customer feedback than they act on - the problem is not a lack of listening but a lack of architecture that routes signal to the people with authority to fix the underlying causes.","Effective listening systems combine multiple sources - transactional surveys, unstructured feedback, operational data, and frontline observation - because no single channel captures the full picture of customer reality.","A feedback loop is only complete when the customer sees evidence that something changed; closing the loop visibly is as important for retention as resolving the original issue."],worksheetContent:"<h3>[Worksheet content for Chapter 5]</h3><p>[Instructions and exercises]</p>",quizContent:"<h3>Knowledge Check</h3><p>[Quiz questions for Chapter 5]</p>",answerKey:"<div><p>[Answer key for Chapter 5]</p></div>",mentorScenario:"<h3>Scenario: [Title]</h3><p>[Scenario content]</p>",worksheetDownloadUrl:"/cemmethod__ch05.pdf",assets:{oneSlide:"#",excoScript:"#",proofStory:"#",checklist:"#"}};function c(){return e.jsx(t,{data:o,prevChapter:4,nextChapter:6,seoTitle:"Chapter 5: Customer Listening Architecture - CEMMethod",seoDescription:"Build a listening system that captures signal, not noise. Design feedback loops that inform decisions and drive continuous customer experience improvement.",seoKeywords:"customer feedback systems, voice of customer, CX listening architecture, customer feedback loops, CEMMethod chapter 5, VoC programs, customer insights, feedback design"})}export{c as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.