The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Add the chat widget to our marketing site so incoming visitors see the brand greeting and can…
Execute — do the immediate task
+Add the chat widget to our marketing site so incoming visitors see the brand greeting and can choose Sales or Support, capture their email before handing to a live agent, and route chats to the Sales team on weekdays and Support overnight. Test on desktop and mobile, confirm the greeting reads “Hi — how can we help you today?”, and report any broken links before it goes live Friday.
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 we push the site chat live, make it frictionless for visitors to convert: put the expected…
Improve — make it easier to accept
+Before we push the site chat live, make it frictionless for visitors to convert: put the expected wait time and team choice up front, show the savings of chatting (fast answer vs email), surface the email field only if agent is unavailable, and flag any flows that would send a visitor to an agent who isn’t logged in.
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 installed the site chat widget and mapped Sales to the Sales queue, but incoming chats from…
Decide — diagnose the stuck moment
+I just added the widget but some chats aren't reaching Sales.
I just installed the site chat widget and mapped Sales to the Sales queue, but incoming chats from desktop go straight to the general inbox while mobile routes correctly. The teams are Tom in Sales, Maya in Support; the launch is Friday and I can’t tell if this is a routing rule, a browser issue, or a mis-tagged contact source. What’s the most likely cause and the fastest fix to ensure Sales gets desktop chats?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time we add a chat widget I spend hours troubleshooting routing, agent availability, and…
Become — change the pattern
+We keep deploying widgets that fail to route correctly.
Every time we add a chat widget I spend hours troubleshooting routing, agent availability, and mobile behavior. It costs me credibility with Sales and delays launches. How should I standardize the widget setup and a short validation checklist so new installs route correctly first time and I can hand off installs without firefighting?
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 CRM and marketing work people do in HubSpot.
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.