How quickly your bot answers
Member·3 minutes to read
What this does for you
Short messages get quick answers without you choosing anything. A greeting, a thanks, a sum or a one-line question — "hi", "thanks!", "17×23", "what's the capital of Norway?" — is answered in a couple of seconds, with no tool step and no working box in between. There is no fast mode to switch on, and nothing in the chat, the status line or the run details shows which way a message went.
How it works
- You send a message. Before your bot does anything, the product looks at the message itself: is it short, on one line, with no file, no link, no mention, no list, and no request to make, find, send or book something?
- If it is, your bot answers straight away, in a sentence or two, without thinking out loud and without opening any tool.
- If your bot finds that the message needs more after all — a search, your inbox, today's weather, a file — it moves to its full set of tools by itself. You still get one answer, not two.
- Every other message — a task, a longer question, anything with a file or a link — is answered the normal way, with your bot's tools and the time the work needs.
A worked example
You type "hi". Your bot replies "Hi! What can I do for you?" a moment later, with no status line and no report under it.
You type "who won the match last night?". Your bot sees that it needs something live, moves to its tools, and answers once — the same as if it had taken that path from the start.
What stays the same
- Your data stays where your organisation's policy says. A quick answer uses only a route your organisation allows; if there is none, your bot answers the normal way, and nothing tells you it did.
- A bot an administrator has set to one specific model keeps that model for every message.
- Routines, group chats, Slack and other channels, and tasks your bot works on in their own thread are not changed.
See also
- Read a transcript — when a reply carries a report, and when it is a plain answer.
- See what your bot is doing — the status line while a longer answer is being worked on.
Last verified against build 74d5149.