LAUNDROMAT MACHINE-REPORT STARTER KIT Free resource | prepared October 20, 2026 Original guide: https://burki.dev/blog/laundromat-machine-problem-voice-agent Replace all fictional facts before use. This is a proposed report workflow, not a customer record, payment/refund, machine inspection, notification or delivered maintenance ticket. Reading/download is free; later voice tests and production calling can incur costs. 1. APPROVED STORE AND MACHINE FACTS Business: ___________________________________________________ Store/branch name: ___________________________________________ Address or approved branch disambiguator: ___________________ Opening hours/timezone, source/owner/date: ____________________ Machine-label format and where visible: ______________________ Alternative identifier if label unavailable: ________________ Self-service versus wash-and-fold contact process: ___________ Approved staff-review process: _______________________________ Approved safety/escalation wording, owner and review date: ___ _____________________________________________________________ No general equipment repair instructions are supplied by this template. Do not direct callers to open panels, bypass locks, reset machines or repeat payment based on a guessed fault. 2. KEEP REPORT FIELDS SEPARATE Field Caller-supplied / confirmed / unknown Store _________________________________ Displayed machine label _________________________________ Superseded label/correction _________________________________ Approximate local event time _________________________________ Payment-method category _________________________________ What caller saw about payment _________________________________ What caller sees about cycle _________________________________ Optional caller-reported amount, only if required by approved process: _____________________________________________________________ Staff next step requested _________________________________ Callback details only if approved and needed: _________________ Actual system verification, if any: __________________________ Never solicit full card number, security code, account password or financial credential images. Do not convert caller observations into verified payment/machine state. 3. FICTIONAL WORKED REPORT Business: Elm Street Laundry Store: North Hall, caller confirmed Machine label: W14, corrected from W40 and read back Payment: caller says the card screen showed accepted Cycle: caller says drum is not moving Time: about 6:10 PM, caller's local estimate Actual charge, machine state, cause: unknown Next step: approved staff review requested Delivery/ticket/refund: not established Illustrative exchange, not a call transcript: Caller: It's W40. Actually, the label says W14. Assistant: W14 at North Hall, is that right? Caller: Yes. The card screen said accepted, but the drum isn't moving. Assistant: You saw an accepted message, and you aren't seeing the drum move. About what local time did that happen? 4. ADAPTABLE INSTRUCTIONS Help callers with approved Elm Street Laundry information. For a self-service machine problem, establish the store and ask for the displayed machine label. Read the label back and replace an earlier value when corrected. Ask what happened during payment and what the caller currently observes about the cycle. Keep the answers separate. Ask an approximate local time only when useful to staff. Do not infer a completed charge, fault cause or refund approval. Do not request card credentials or account passwords. Use operator-approved next-step wording only. Do not give repair instructions, unlock or restart a machine, or claim staff notification without a supported actual result. Read back the corrected location, machine and account of the problem before closing, and ask whether it is accurate. Recognize a switch to an order question as a different task. Do not invent private order status. 5. SETUP AND REVIEW RECORD Proposed UI: Assistants > New assistant > Set up manually > Receptionist. Business setup: Assistant job / Business name / Business facts / Desired outcome. Review Instructions and First greeting. Inspect output if using Apply business details to instructions. Create/save only under authorized setup, not as a content demonstration. Assistant job: approved store answers plus factual machine report. Desired outcome: usable staff review brief, no automatic payment/machine action. Existing assistant: Conversation for instructions; Publish > Published version for actual draft/live scope. Conversation engine/provider/voice/language: ___________________ Credential ownership/funding/allowance: _______________________ Retention/access policy, owner/date: __________________________ Browser versus telephone route readiness: ____________________ Saved/published configuration: _______________________________ Machine/payment/order connections actually verified: _________ Actions deliberately outside first version: __________________ 6. ACCEPTANCE CASES For each: record expected | observed | evidence | correction/owner | status. No tests were performed for this resource. A. Machine label correction W40 -> W14. Expected: W14 confirmed and used; W40 retained only as a superseded value if needed. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED B. Two branches with similar names. Expected: clarify branch before assigning machine identity; do not assume caller location from phone number. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED C. Payment screen accepted, cycle movement unclear. Expected: record both caller reports separately; actual payment and machine state remain unknown. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED D. Refund requested. Expected: approved staff-review wording, no refund decision or promise of payment. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED E. Label unavailable. Expected: approved clarification or explicit unknown, no invented machine number. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED F. Caller starts offering financial credentials. Expected: do not solicit or repeat them in the report; use the approved minimal-data process. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED G. Caller switches to wash-and-fold order status. Expected: acknowledge new task and do not confuse order reference with machine label or public turnaround policy with current status. Observed/evidence: ___________________________________________ Correction/owner: __________________________ Status: UNTESTED 7. OPERATIONAL COMPLETION, SEPARATE FROM CONVERSATION Staff received report? Actual evidence: ______________________ Location and machine identifiable? ___________________________ Payment versus cycle accounts separated? _____________________ Staff decision/outcome and source: ___________________________ Unresolved question and owner: _______________________________ Later actual callback, ticket or refund receipt if applicable: _ _____________________________________________________________ Do not mark resolved merely because an assistant answered, summarized or requested review. Source context and historical industry data are in the original guide. Adoption reports concern other products, not a Burki customer result. Pricing: https://burki.dev/pricing