Intents
Retrieval answers questions. An intent is where you take control.
Control means one of two things. Say exactly this and ignore my website. Or: do this thing, and collect these details first.
Everything else, the "do you do wedding cakes" and "where are you", is answered by searching what Jabee read off your own site. Intents are not how it answers. They are how you override it, and how anything gets done.
Saying exactly this
For the answers where wording matters and a paraphrase is wrong. A refund policy. A price that must not be approximated. Something legal.
Add the intent under Management → Intents, describe when it applies in your own words, and write the answer. From then on, a customer asking that gets those words rather than a sentence assembled from your site.
Doing something, and collecting details first
For when a customer wants an outcome rather than an answer. Book a table. Get a quote. Arrange a viewing.
You say what you need before it can happen, and Jabee collects it in the conversation rather than sending a form. It reads several at once: "Tuesday at 7, four of us" fills three fields in one message.
Then it does the thing. That might be a booking in the diary, an enquiry written down, or your own system being called.
When it is not sure
It asks, in plain words, which of two things they meant. This only happens when the model is genuinely uncertain, never as a routine step, because a product that asks you to confirm every message is worse than one that occasionally guesses.
When an intent matches and you have not set it up
The thread goes to a person and you get told. Somebody wanted something done and there is nothing here that can do it, so guessing would be worse than handing over. The alert says which intent it was, which is usually the prompt to go and build it.
Trying one before a customer does
The test chat in the dashboard runs the same intent engine as the worker, through shared wiring so the two cannot drift. It names the rule that matched underneath the reply, and it really does the action: a real booking in the diary, a real enquiry, your real system called.
Two things it will not do, both because they would reach somebody else: it does not send an owner alert, and it does not notify you about a newly discovered intent.
One limit worth knowing
The intent engine is English only today. Retrieval, alerts and the rest of the product are bilingual, and an Arabic message is still answered from your Arabic content. An Arabic intent was built, did not work well enough, and was taken out rather than left half working.
Questions
How many intents should I have?
Most businesses need five or ten. They are for the questions where you want control, not for every question.
Do I have to write keyword lists?
No. You describe when it applies in your own words and the model reads that against what the customer wrote.
What happens if two intents could match?
Jabee asks which one they meant, in plain words, and only when it is genuinely unsure.
Can an intent collect details and then call my API?
Yes. That is the main reason to use one. Collect what you need in the conversation, then the action runs.
Do intents work in Arabic?
Not yet. The intent engine is English only. Arabic messages are still answered from your Arabic content by retrieval.