Inside Kreygo
Ask before you assume
When a request is unclear, our agents ask before they assume. They do not guess and then present the guess as fact.
Not every request is clear. "Send it to the usual people." "Make it match last time." Someone who knows the work can usually fill the gap. An agent that fills it wrongly will do the wrong thing quickly and quietly.
So our agents have a habit: when a request is unclear, ask before you assume.
One question, written plainly. The agent says what it understood, what it could not tell, and what it needs to know.
It does not guess to look helpful. A confident wrong answer is worse than a short wait. If the missing piece matters, the agent does not pick the likeliest reading and carry on as if it were sure.
Some questions are not for the agent to settle. Anything that needs the owner's say-so is the owner's to decide. The agent asks. It does not decide for them.
The same thinking sits in how we start a project. In discovery, the first step, we talk through the workflow and the goal and write down what the agent will not do. Nothing starts until the scope is agreed in writing. If a task does not fit an agent, we say so.
What this is not. It is not a promise that an agent never gets a request wrong, and it is not a reason to ask about everything. Clear requests should just get done. The habit is for the gap that actually matters.
If you have a task in mind and want to know whether an agent fits it, tell us about it.
