When a bot says it cannot do something
What a bot is told to say when something is not available, how it checks the documentation with murage_help, and what to do before you take no for an answer.
What a bot is told to say
Every bot carries the same instruction about this. If something is not in the documentation, or the documentation says Murage cannot do it, the bot says so plainly, then points to the nearest real setting or page that helps. It is told never to invent a setting, a switch, a menu or a command, and never to send you looking for one by a name it is not sure of.
When it is unsure, it calls murage_help, which answers from the documentation that ships with the app, and quotes what came back. Bots on an engine with no tools cannot look anything up, so they are told to say "I am not sure" instead of guessing.
Two examples of the nearest real setting, straight from the bot's own instructions:
- Asked to turn on a switch that lets bots talk to each other: there is no such switch. Bots on the same team can already contact each other, and Bot settingsPermissionsCan talk to widens that.
- Asked to change something only you can change in the desktop app, such as Full access: the bot tells you where it is and does not try to change it itself.
When a bot needs something from you, it tells you what it tried and what stopped it, in plain words, and names who can change it: your Chief of Staff, the bot's team lead, or your own Settings.
Three things to try before you accept a no
- Ask it to check. "Check murage_help and tell me what the docs say." A bot that answered from memory will often come back with the real answer.
- Search Settings. Open Settings and type the thing you want in the search box. Search finds every setting by name, including the ones under Advanced. Pages were renamed in a recent release, so a bot or an older help page may use a name that no longer exists. See where things moved.
- Ask for the job another way. Murage has no fixed list of features. If a service is not among the connected apps, a bot can use its public API with a key you give it. If there is no tool for a task, a bot can do it in the built-in browser, on a computer it controls, or through an MCP server you add. Describe the outcome and let it find the route.
When the no is real
Some things are not available, and the bot should say so. Murage Cloud (coming soon) and the official WhatsApp business route are two examples today. A bot that says "not available yet" and points you to the nearest thing that works is doing its job.
If you find a bot that invents a setting, tell us. That is exactly the behaviour the instruction above exists to stop.