The moments that lead here
If one of these is your afternoon, you are in the right place.
Set up an automated reply that acknowledges support requests about site accessibility and routes them to the right person.
2 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+Configure the support reply template to acknowledge accessibility requests, add routing rules so…
Execute — do the immediate task
+Configure the support reply template to acknowledge accessibility requests, add routing rules so requests tagged 'accessibility' go to [assignee=Maya] in ops, and enable reminders on the template so the assignee follows up within two business days.
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 enabling the automated reply, reduce bounce and misrouting: include a short triage checklist…
Improve — make it easier to accept
+Before enabling the automated reply, reduce bounce and misrouting: include a short triage checklist in the acknowledgement that prompts reporters to supply browser and assistive tech, route high-severity tags to Maya and copy the accessibility lead, and set reminders for 48-hour and one-week follow-ups.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Who does this, and with what
The same task is different work inside a different job.
Next to this one
Other send work people do in Adobe Acrobat.
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.