There may be a practical reason to say “please” and “thank you” to your chatbot or coding agent.
Not because AI has feelings. And not because we want to be remembered kindly when the robot apocalypse arrives. The real reason is simpler: the way you communicate with AI shapes the kind of response you get back.
AI is not a search box
A lot of people still use AI like a search engine. They type “Write a product launch post,” “Review this code,” or “Give me marketing ideas,” and then wonder why the answer feels generic.
It feels generic because the request was generic. A search box returns the most relevant page it already has. A language model does something quite different.
How the answer actually gets made
Current models don’t look up one fixed answer and hand it back. They generate a response from patterns learned across enormous amounts of text, shaped by the context, instructions and framing you give them in the moment.
That means your prompt matters a lot. Not because it unlocks some hidden genius mode, but because it tells the model which kind of response to produce. A vague prompt invites the most average answer. A clear one narrows the space toward the answer you actually need.
Give it a frame, not just a task
So instead of only giving the model a task, give it a frame:
- Context: what’s going on, and what it needs to know.
- A goal: what a good result looks like.
- Constraints: budget, time, scope, what to leave out.
- A perspective: whose point of view to take, and what that person cares about.
Roles work when they say what to care about
Assigning a role is the most common prompting trick, and it’s only half useful. Saying this is better than nothing:
You are a senior engineer. Review this code.
But this is much more useful:
Review this code from the perspective of a senior engineer responsible for production reliability. Focus on security risks, edge cases, performance issues, maintainability, and whether this is safe to merge. Give me the top issues first.
The improvement doesn’t come from the fancy title. It comes from the clearer lens.
The same goes for marketing. Instead of “Give me marketing ideas,” try:
We have a new mobile app, a limited budget, and 30 days to test acquisition channels. Suggest practical experiments, estimate how hard each one is, and tell me which three you would try first.
A role helps only when it defines what the model should care about. A senior engineer cares about reliability, security, scale and maintainability. A growth strategist cares about experiments, channels, budget and priorities. An editor cares about clarity, tone, structure and cutting fluff. Name the role, and then name what it pays attention to.
AI doesn't get smarter because we give it a title. It gets more useful when we give it a better frame.
So, should you say please?
Yes, and here’s the honest reason. The AI doesn’t need kindness. But a thoughtful tone usually comes with better instructions, more context and a more collaborative way of working. People who write politely tend to write clearly.
The point isn’t to memorise magic prompts. It’s to communicate better. “Please” and “thank you” were never the secret. Clear thinking is.