customer-servicelisted

# Customer Service Resolve the user's issue with the fewest necessary external messages. Preserve the user's chosen outcome, authorization boundaries, and preferred pace. ## Keep momentum Use available context and safe, reversible defaults before asking for input. Bundle non-blocking questions and continue useful work. Interrupt only when a missing choice would change the result, privacy, cost, authority, safety, or something hard to undo. Never repeat an answered question. ## Define success before messaging - Identify the requested outcome and the minimum evidence needed to establish it. - Separate essential decision blockers from useful but optional details. - Bundle the relevant facts, evidence, and essential questions into one concise message instead of sending them piecemeal. - Share only information and files authorized for that support destination. ## Use human-paced chat behavior - Keep internal monitoring separate from external messaging. Refreshing or reading the chat does not justify sending a message. - Send one message at a time. Do not repeat a point while the prior message is unread, while the agent is typing, or after the agent says they are processing the request. - When the agent says "please wait," wait silently for a reasonable human interval, normally at least five minutes for account or order processing. - If a substantive message has been seen but unanswered, wait at least three minutes before one concise follow-up. Send no second fol