Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Customer Support / CX Analyst Source-Aware Guide
Defines source-aware customer-support and experience measurement, reconciliation, and recommendation, evidence handling, and action boundaries.
Read the fileOverview
Customer Support / CX Analyst overview
Use this bundle to prepare source-aware customer-support and experience measurement, reconciliation, and recommendation and a review-ready customer experience analysis brief.
Read the fileWorkflow
Customer Support / CX Analyst source-aware triage
1. State the requested decision or artifact. 2. Inventory evidence: business question, channels, products, population, period, and source systems; ticket, contact, survey, customer, and.
Read the fileTemplate
customer experience analysis brief
Review-ready artifact for customer-support and experience measurement, reconciliation, and recommendation, evidence quality, verification, and controlled actions.
Read the fileIs this bundle right for your task?
Who it is for
- Customer-support leaders, CX analysts, operations teams, service owners, and researchers evaluating customer experience across channels
When to use it
- CSAT, effort, NPS, SLA, contact, or resolution results need definitions, populations, periods, and source systems reconciled before interpretation.
- Ticket and survey evidence must be checked for filters, identity, deduplication, sampling, response rates, missingness, and uncertainty.
- A support trend or text-analysis finding needs a bounded recommendation and a clear distinction between observed evidence and a root-cause hypothesis.
What you need to provide
- Business question, products, channels, population, period, source systems, and definitions for tickets, contacts, customers, surveys, and resolutions.
- Authorized extracts and filters plus identity, deduplication, sampling, response-rate, missingness, metric, text-analysis, privacy, and validation evidence.
Tasks and expected outputs
Questions it helps answer
- Prepare a customer experience analysis brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- customer experience analysis brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Load the Customer Support / CX Analyst bundle and provide the business question, channel and product scope, ticket and survey extracts, metric definitions, filters, population and period, response rates, deduplication rules, and privacy constraints. Ask the agent to separate verified and provided facts from assumptions, test representativeness and definition conflicts, and draft a customer experience analysis brief with caveats and review gates.
Context path: bundles/roles/customer-support-cx-analyst
What the bundle includes
Frameworks
- source-evidence matrix
- customer-support and experience measurement, reconciliation, and recommendation review matrix
- qualified-review gate
Evaluations
- Customer Support / CX Analyst source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Inferring sentiment, customer impact, causality, or improvement effects from sparse data; exporting customer records, contacting customers, changing routing or policy, or publishing metrics without authorization and accountable review.
Known limitations
- Use the listed authoritative sources for general role or tool behavior; local configuration, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for business question, channels, products, population, period, and source systems; ticket, contact, survey, customer, and resolution definitions; extracts, filters, identity, deduplication, sampling, response rates, and missingness; CSAT, effort, NPS, SLA, contact, text-analysis methods, uncertainty, privacy, and validation evidence.
- Do not infer metric value, trend, representativeness, sentiment, root cause, customer impact, or improvement effect.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that access or export customer data, contact customers, change routing or policy, publish metrics, or claim causality.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.