The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need read receipts turned off for our support account so customers who prefer privacy aren’t…
Execute — do the immediate task
+I need read receipts turned off for our support account so customers who prefer privacy aren’t worried. Disable read receipts for the Support Lead’s device and confirm messages to customers now show only delivered/seen as appropriate; list any contacts who will still show receipts. Complete this by Wednesday afternoon and report what changed.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I disable read receipts on the Support Lead’s phone, make it easy for management to approve:…
Improve — make it easier to accept
+Before I disable read receipts on the Support Lead’s phone, make it easy for management to approve: explain the impact on SLA tracking, surface which active customer threads will lose read status, and flag any internal threads where managers still need receipts to coordinate handoffs.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I just disabled read receipts for the Support Lead and managers say they can’t tell whether urgent…
Decide — diagnose the stuck moment
+I turned receipts off and managers now complain SLA tracking is blind
I just disabled read receipts for the Support Lead and managers say they can’t tell whether urgent customer messages were actually read. I’m unsure if we should disable for only external contacts or adjust reporting instead. What’s the likely trade-off and the best immediate fix to preserve SLA visibility without exposing customer read status?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep toggling read receipts whenever a customer raises privacy concerns, and each time our SLA…
Become — change the pattern
+We flip privacy settings when a VIP complains, then forget the business impact
We keep toggling read receipts whenever a customer raises privacy concerns, and each time our SLA reporting breaks. Where are we losing credibility or accuracy, and what policy will prevent ad hoc toggles while protecting customer privacy?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other messaging work people do in WhatsApp.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.