The request sounds like the thing itself: "build a support app where an agent answers questions about my products". What comes back is not a chat window bolted onto a page - it is a screen with a conversation, a box to type in, the answers arriving as they are written, and a way to reach a person when the agent has had enough.

Where the answers come from is the first thing to settle, because an agent with no material invents. Give it the material in the request or in the app: your price list, your opening hours, the rules of your returns, the documents you already have. Then the agent answers from those and, when something is not in them, it says so instead of guessing. That one behaviour separates a useful assistant from a confident wrong one.

The key is the part people get wrong when they build this themselves. A model is called with a secret key, and a page is a public document - anything in it is readable by every visitor. So the app does not carry a key at all: it asks Kood for the answer and Kood pays with the account that is already signed in. Nothing secret is in the app, and nothing secret is in the export when you take the code with you.

Ask for the behaviour in the same breath as the screen, because that is what makes it an agent and not a text box. "If he doesn't know, offer to send the question to me on mail". "Show the sources". "Do not answer questions about prices without a price list". "Write a summary of the conversation when it is over." Each of those becomes a rule the app follows, and each is something you can then watch it do.

Four limits worth knowing before you put it in front of a customer. It can still be wrong, so keep a door to a person and do not let it promise refunds or dates on its own. It answers in the language it is written to, so ask for the language your customers use. Every answer costs a little of the account's credit allowance, which is the plan you already pay for - there is no separate bill and no key to buy. And it is not a search engine: what you did not give it, it does not know.

Test it the way a customer would: ask five real questions, including one you know the material cannot answer. If it says it does not know and offers the person, it is ready. If it invents a price, go back to the chat and name the document it should have used - that single sentence is usually the whole fix.