Generate a weekly business report from sales and feedback data

작성자: AILesson9 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Reconcile weekly sales and customer feedback into a decision-ready report without overstating causes. 제공할 내용: Sales and operations data, Customer feedback evidence, Report contract. 예상 결과: A traceable weekly report with metric table, comparisons, feedback themes, exceptions, actions, and data-quality notes.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Sales and operations dataCustomer feedback evidenceReport contract

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Generate a weekly business report from the supplied sales, operations, and feedback evidence.

Sales and operations data:
[sales]

Customer feedback:
[feedback]

Report contract:
[report]

First audit scope, field definitions, date coverage, currency, duplicates, missingness, refunds, cancellations, tax, denominators, and reconciliation. Do not silently repair data. Build a table showing current value, comparison value, absolute change, percentage change when valid, target, status, source, and caveat. Use not computable when a denominator is zero or required data is absent. Separate observed facts, calculated results, customer-reported themes, hypotheses, and confirmed causes. For feedback themes show count and denominator, source coverage, representative privacy-safe paraphrase, counterexamples, and confidence; do not generalize from a small or self-selected sample. Connect actions only to supplied evidence, showing owner, due date, expected signal, and decision or escalation trigger; leave missing fields explicit. End with reconciliation, data-quality issues, and questions that must be answered next week.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Sales and operations data: Report week 11–17 August, comparison 4–10 August, CNY, Asia/Shanghai. Paid order export after duplicate removal: current 118 orders, gross merchandise sales 29,800, refunds issued 1,640 across 7 orders, net merchandise sales 28,160; previous 104 orders, gross 27,040, refunds 520 across 3 orders, net 26,520. Net excludes delivery fees and tax. Payment settlement current 30,020 consists of merchandise 29,800 plus delivery 1,120 minus payment discounts 900; it is before later refunds and therefore does not equal net merchandise sales. Current product units: starter kit 72, refill 41, accessories 19; prior 61, 45, 15. Current fulfilled by cutoff 109 of 118; prior 101 of 104. Current first-time buyers 44, but prior first-time-buyer field is missing. Website sessions current 2,360 and prior 2,120; checkout source lost 85 sessions during a six-hour outage. No confirmed cause for changes.
Customer feedback evidence: Current week: 31 post-purchase survey responses from 118 orders, self-selected; average 4.2/5. Six mention refill packaging leaked, all for batch R0812; two refill buyers explicitly say no leak. Five praise beginner instructions. Three say delivery updates were late; two of those orders were fulfilled after the carrier cutoff. Support log contains 14 contacts: four about leakage, four delivery status, three address changes, three other. Public reviews: three new reviews, all positive. Privacy-safe paraphrases only. Prior week had 18 survey responses averaging 4.4; theme coding was not performed, so theme comparison is unavailable.
Report contract: Audience: owner and operations lead. Decisions: whether to quarantine refill batch R0812 and whether to adjust carrier handoff. KPI formulas: net merchandise sales = gross minus issued refunds; average order value = net merchandise sales divided by paid orders; fulfillment-by-cutoff rate = fulfilled divided by paid orders; refund rate = refunded orders divided by paid orders; website order rate = paid orders divided by sessions but flag tracking outage. Targets: net sales 27,000; fulfillment 95%; refund rate at most 4%. Show current versus prior and one decimal for rates. Material issue means at least five feedback mentions or any suspected product defect. Owner assigns actions in Monday review; do not invent names or dates.

예시 출력

Weekly business report — 11–17 August

Executive readout: net merchandise sales exceeded target and rose 6.2% on a comparable definition. Fulfillment remained above target but weakened. Refund rate rose above its threshold. Six of 31 survey respondents reported leakage, all tied to batch R0812; this is a defect signal requiring a quarantine decision, not an estimate of all-customer incidence. No cause of the sales or fulfillment changes is confirmed.

Metric	Current	Prior	Change	Target/status	Source and caveat
Paid orders	118	104	+14, +13.5%	no target	deduplicated order export
Net merchandise sales	CNY 28,160	CNY 26,520	+1,640, +6.2%	above 27,000	excludes delivery and tax
Average order value	CNY 238.64	CNY 255.00	-16.36, -6.4%	no target	net sales / paid orders
Fulfilled by cutoff	92.4%	97.1%	-4.7 pp	below 95%	109/118 versus 101/104
Refund rate	5.9%	2.9%	+3.0 pp	above 4% ceiling	refunded orders / paid orders
Website order rate	5.0%	4.9%	+0.1 pp	directional only	85 checkout-source records lost; do not infer conversion improvement
First-time buyers	44	not available	not computable	no target	prior field missing

Mix: starter kits +11 units, refills -4, accessories +4. These are counts, not explanations of revenue movement. Payment settlement reconciles as 29,800 + 1,120 - 900 = 30,020; it is before later refunds and is not expected to equal net merchandise sales of 28,160.

Feedback evidence: leakage appears in 6/31 survey responses and 4/14 support contacts; all six survey reports identify R0812, while two refill respondents report no leak. Confidence is moderate that R0812 needs investigation, but population incidence is unknown because the survey is self-selected. Beginner instructions are praised by 5/31 respondents. Late delivery updates appear in 3/31 surveys and 4/14 support contacts; two survey cases followed late fulfillment. This association does not confirm a carrier-handoff cause. Rating moved from 4.4 with 18 responses to 4.2 with 31; samples differ and no significance test is supplied. Theme trend versus prior is unavailable.

Decision actions: review whether to quarantine R0812 immediately; owner and deadline are unassigned until Monday. Expected signal: inspected units, affected-order count, and leak reports by batch. Escalate if any additional suspected defect appears. Review cutoff misses against carrier handoff timestamps; owner and deadline unassigned. Change handoff only after the sequence is verified.

Data-quality follow-up: restore checkout-source logging; add prior first-time-buyer field; define prior theme coding; reconcile refund timing to settlement. Next-week questions: Is leakage confined to R0812? How many R0812 units shipped and remain? Which step caused nine cutoff misses? Did late updates occur without late fulfillment?

효과가 있는 이유

1
A shared metric table prevents narrative emphasis from hiding denominator or reconciliation problems
2
Evidence-counted feedback themes keep vivid comments from masquerading as customer-wide truth

결과 확인

Do totals reconcile and do all changes use comparable definitions and periods?
Are facts, calculations, feedback themes, hypotheses, and confirmed causes clearly separated?
Does every proposed action have evidence, an owner or explicit gap, and a measurable trigger?

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Generate a weekly business report from sales and feedback data”?

For “Generate a weekly business report from sales and feedback data,” prepare Sales and operations data, Customer feedback evidence, and Report contract. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Generate a weekly business report from sales and feedback data” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A traceable weekly report with metric table, comparisons, feedback themes, exceptions, actions, and data-quality notes—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Generate a weekly business report from sales and feedback data”?

The published test record for “Generate a weekly business report from sales and feedback data” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

더 많은 탐색 방법