Build your agent
Advisor Mode
Advisor Mode turns an agent from a chatbot that answers whatever it's asked into an assistant that behaves like an experienced employee: before it advises, it makes sure it understands the visitor. When one short question would lead to a genuinely better answer, it asks that question first β otherwise it answers immediately. It works for every kind of business, because only the knowledge and the goal change, never the behaviour.
Turn it on per agent under Agents β your agent β Settings β Advisor Mode. Off (the default) is the standard chat, completely unchanged.
The decision the assistant makes before every reply
There are no decision trees to build or maintain. Before each reply the assistant decides, silently, in the same step it uses to write the answer:
- Can I already answer this well from the site's content and what the visitor has told me so far? If yes, it answers immediately. Simple factual questions β opening hours, address, price, returns, contact details β are always answered on the spot, with no follow-up.
- Would exactly one short question make my advice materially better, and would the answer actually change what I recommend? If yes, it asks that one question and nothing else.
If the missing information isn't in the site's own content, the assistant never interrogates the visitor to cover for it β it answers honestly with what it has, or offers the next step. (That gap is also surfaced to you through Content gaps so you can add the missing content.)
Guardrails, so it never feels like an interrogation
- At most one question per reply β never two at once. This is enforced on the server, not merely requested in the prompt: if the model ever adds a second question β whether as a separate sentence or a second ask joined into the same sentence (“… and what are your goals?”) β it is trimmed before the visitor sees it, so a smaller model can't turn the conversation into a checklist.
- At most three questions in a whole conversation, then it gives its best recommendation with what it knows.
- It never re-asks something the visitor already answered.
- Factual questions bypass the funnel entirely.
The Primary Goal
A business has several objectives overall, but the assistant should have one priority per conversation. The Primary Goal is that priority β what the assistant steers toward when a conversation could go several ways. Your visitor's explicit request always comes first; the goal only decides the direction when the visitor hasn't shown one.
Each goal steers toward an outcome the widget already delivers, so Advisor Mode adds no new visitor-facing UI:
- Inform visitors β a clear, complete answer with links to the most relevant pages.
- Generate qualified leads β an invitation to leave contact details, enriched by what the visitor shared.
- Recommend products β specific product cards that fit the visitor's needs.
- Book appointments β help booking a call or appointment.
- Support customers β resolving the issue, or handing off to a human when it can't be resolved.
An optional Extra guidance field lets you describe the goal in your own words (for example, "Our priority is helping visitors choose the right storage unit; if they're interested, guide them toward a reservation."). It's fed to the assistant, never shown to visitors.
Contextual quick replies
The tappable chips under a reply follow the conversation. While the assistant is qualifying, the chips are likely answers to the question it just asked β after "What kind of business do you run?" the visitor sees "A webshop", "A service business", "Something else" and can tap instead of typing. Once the assistant recommends, the chips become the natural next actions toward the agent's goal β "Book a call", "Talk to a human", or a relevant next step.
This needs no setup: the assistant chooses the chips per reply based on what it just did. They're delivered through the same mechanism as the standard follow-up suggestions, so tapping one simply sends it as the visitor's next message.
Qualification capture
While the assistant qualifies a visitor, it is learning things worth keeping: what kind of business they run, what they're trying to achieve, which objection is holding them back. Advisor Mode records those question-and-answer pairs so they can inform reporting and follow-up. This is the one part of the conversation that cannot be reconstructed after the fact, so it is captured from the first day the mode is on.
- Each Advisor conversation gets one session β a record of the goal it pursued and, when the conversation converts, the outcome it led to. A submitted lead, a booked call, or a clicked call-to-action is stamped back onto the session automatically, so you can see which qualified conversations actually drove results β the attribution link between "what the assistant asked" and "what the visitor did". The strongest outcome wins: a booking is never overwritten by a later, lighter click.
- Each qualifying question the assistant asks, and the answer the visitor gives on the next turn, is stored as one turn.
Capture happens after the reply is sent to the visitor, so it adds nothing to how fast the chat feels. Every workspace's data is its own β isolated by the same tenant boundary as the rest of your content β and used for that workspace's own reporting and attribution.
Review it under Analytics β Advisor
(/app/analytics/advisor): every qualified session, the
questions the assistant asked and the visitor's answers, the outcome each
session drove, and summary stats β qualified sessions, conversion rate,
and leads / bookings / CTA clicks β filterable by agent, outcome and time
window.