How it worksFeaturesSolutionsGuides PricingFAQ Ask on WhatsApp
Help Getting started

Setting up your assistant by chat

Set up by chat interviews you about your business and drafts a whole assistant from the conversation — what it says, what it sells, what it knows — and nothing it writes is live until you publish it.

Updated 22 August 2026 11 min read

Most people know their business perfectly well and have no idea what a “business rule” or a “prompt” is. Set up by chat is the door for that: you answer five short questions, then have a conversation about what you do, and at the end Kooday drafts the whole assistant from what you said — its description, the things it must never do, your products and prices, and answers to the questions customers actually ask.

It is a conversation with a review at the end, not an assistant that builds itself. Everything it produces is written as a draft, the assistant it creates is switched off, and it answers nobody until you read what was written and publish it. That last step is deliberately yours.

⚠️ It will keep asking. “We sell furniture” is not enough to build an assistant that can answer a real customer, so the interview probes — prices, opening hours, what you refuse to quote over chat. That is the point of it, and the Progress checklist tells you when there is finally enough.

Where to find it: Bots, under Assistants in the left-hand menu — the Set up by chat button beside Create assistant. On an account with no assistants yet it is the main button on the page, and it is also offered inside the Create assistant dialog as “Set up by chat (recommended)”.

The five-minute version

  1. Click Set up by chat. If you have a website, type its address in the box before you start — that is the only moment it can be attached.
  2. Answer the five questions at the top. They save as you type.
  3. Talk to the interview in the chat pane. Answer in your own words.
  4. When Review & create turns on, click it.
  5. Read the report, click Review & publish instructions, and publish.

Steps 1–4 can be spread over days. Nothing is lost between visits.

Step 1 — The basics

Five boxes, all of them short. They exist to give the interview a running start rather than a blank page.

QuestionWhat it wants
What is the business called?The name customers know you by.
What kind of business is it?A few words — “Dental clinic” is plenty.
Where are you?The area a customer would recognise.
WebsiteOptional, and see below.
When are you open?Include the days you are closed — customers ask.

The five basics boxes filled in for a coaching academy, with a green 'We read your website' chip.

They save about a second after you stop typing, and again when you click out of a box or leave the page. There is no save button and you do not need one: if an answer fails to reach us you get “That answer wasn’t saved” with a Try again button, and what you typed stays in the box.

Your website

If you give an address when you start, Kooday reads that one page and uses it to ask better questions — you type less because it already saw your services.

What to know about it:

  • It can only be attached when the session starts. Typing an address into the Website box later records your answer, but there is nothing to read: the field then says so plainly. If you want the site read, start a fresh setup.
  • Failing is normal and harmless. Sites block robots, sites are slow, sites are built entirely out of images. When that happens the chip reads “We couldn’t read your site — let’s do it by chat” with a Try again beside it, and the interview asks you instead. Nothing is blocked — the chat is already open behind it.
  • Type the whole address, including https://. “example.com” on its own is refused — “website_url must be an absolute http:// or https:// URL” — and so is an address with a username and password in it.
  • Give the address the site actually lives at. The read does not follow redirects, so if example.com bounces visitors to www.example.com, type the www. one. This is the most common reason a perfectly good website cannot be read.
  • What it reads is treated as a lead, not as fact. The page is handed to the interview as untrusted material it may ask you about — the intent being that a three-year-old price still on your homepage gets questioned rather than copied into your assistant. Read what the interview tells you it learned and correct it there; your answer is what the assistant is built from.

Step 2 — The interview

This is the part that does the work. Answer in ordinary sentences; it asks one thing at a time and follows up when an answer is too thin to build on.

  • Nothing here is live. The pane says so: “Nothing here is live — everything you say becomes a draft you review before anything is built.” No assistant is created, nothing is published, and no customer sees any of it while you talk.
  • Every message is saved the moment you send it. Close the tab, lose your connection, come back tomorrow — your side of the conversation is already stored. If a reply is interrupted you may lose that one reply; you never lose what you typed.
  • One setup at a time. Starting a second while one is in progress is refused with “A wizard session is already in progress. Resume it or abandon it before starting a new one.” Returning to Set up by chat shows “You have a setup already in progress” with Resume and Start fresh. Starting fresh puts the old one aside — it is kept, never deleted.
  • It has a name for the assistant. The interview will offer suggestions and ask you to settle on one. Whatever you agree on in the chat is the name the assistant is created with.

The Progress checklist

Beside the chat — below it on a phone — the Progress panel is not decoration. It is the same gate the server applies, and Review & create stays off until all five required items are done:

RequiredDone when
About the businessThe description reaches 80 characters.
Opening hoursThe hours are recorded, including the closed days.
Products & servicesAt least one named product or service exists.
Assistant nameA name has been settled on.
Things it must never doAt least one rule — a price it must not quote, a promise it must not make.

The Progress checklist part-way through, with two required items still open and the Review & create button greyed out.

Below those, Common questions, Current offers, Policies, Questions it should ask and Opening line are marked (optional). They are optional for building, not for quality: a Worth adding list appears when, say, three of your five services have no price — “The assistant will have to say it does not know.” Fix those in the chat before you build, not after.

While the button is off it explains itself: “This turns on once the interview has enough to build an assistant that can actually answer.”

Step 3 — Review & create

One click builds everything, in a single step that either completes or leaves nothing behind. Then you get a report headed ”… is built — and nothing is live yet”, listing what was written where:

Where it wentWhat lands there
Business detailsThe description (with your opening hours folded into it), the rules, the offers, the questions it asks customers
CatalogueYour products and services, with prices where you gave them
Knowledge baseThe FAQs and policies from the interview
The assistant itselfIts name and opening line

Everything in that list is a draft, and the new assistant is switched off. To bring it live, click Review & publish instructions, read what was written, and publish — the assistant comes live by itself once it passes its readiness checks. If it does not, see Why isn’t my assistant live yet?.

What it will and will not overwrite

If this is the first assistant you have ever set up, the first build writes into an empty business and none of this bites until you build a second time from the same conversation.

If you already have an assistant, one thing does bite immediately. Your business description, rules, offers and the questions your assistants ask belong to the BUSINESS, not to one assistant — so a setup conversation that produces new ones replaces what is there. When that would happen, the first build is refused and you are sent to the comparison screen first, exactly as a second build is. You will see the old wording beside the new before anything is written.

Whichever build it is, from then on:

  • Nothing changes without being shown to you first. Building again goes through the comparison screen, which lists every difference — including your own hand-edits, which appear as changes you are being asked to confirm. If anything about the assistant moves between you reading that list and pressing the button, applying is refused rather than merged. See Changing things afterwards below.
  • Your description, rules, offers, the questions it asks, its name and its opening line are rewritten wholesale from the interview when you apply again. That is what applying means — but you will have seen each one on the comparison screen first, so nothing goes past you unannounced.
  • It never deletes a catalogue entry. Your products are mirrored into your knowledge base and onto your shopfront, so removing one is a decision with consequences elsewhere — it is always yours to make, on the Catalogue screen.
  • It does tidy up its own knowledge base entries. A FAQ or policy that this same setup conversation wrote earlier, and that the interview no longer holds, is removed when you apply again. Entries from anywhere else are not touched.
  • It leaves alone anything it did not write. A catalogue entry or knowledge base entry created by you — or by a different setup conversation — is skipped, and the report says so under “Some of it was already yours”. That version stays in force; if you prefer the interview’s wording, edit it yourself.

Changing things afterwards

Once a setup has built an assistant, that conversation stops accepting messages and is kept as the record of where the assistant came from. The screen says so — “This session already built an assistant” — and offers three ways on:

  • Reopen to make changes. This opens the interview back up so you can keep talking. As it does, it re-reads your assistant as it stands today — including anything you changed on its own screens — and carries on from that, so an edit you made elsewhere is never quietly undone. The banner that replaces it is headed “Picking up where your assistant stands today” and reassures you that “Nothing has changed yet, so you can stop here and leave the assistant exactly as it is.” Changed your mind? Stop making changes closes it again, having written nothing.
  • Review the changes. This compares what the interview holds against your assistant as it stands now and shows you two lists before anything is written. Will be applied is what the button does. You’ll need to do these yourself is what it will not — a catalogue entry it would have removed, or something you created that it will not overwrite. Applying again writes drafts, exactly as the first build did.
  • Edit the assistant directly. Business details, Catalogue, Knowledge base and the Studio are all normal screens, and after a build they are the fastest route to a small change.

The Review the changes dialog, split into what will be applied and what you must do yourself.

If someone edits the assistant in another tab while you have the comparison open, applying is refused with “This assistant changed while you looked” and the list is reloaded. Look again before you apply — that refusal is the reason nothing gets quietly overwritten.

What your trial includes

On a trial, setting up by chat is capped:

Included in a trial
Setup conversations3
Messages per conversation60

Those are the current allowances rather than a permanent entitlement — we can raise them, and this page is where the number lives. Paid plans are not capped this way; if you ever see a limit message on a plan you are paying for, tell us — that is not what is meant to happen.

Two details that matter more than the numbers:

  • A conversation you never typed in does not count. Start one, change your mind, click Start fresh, and the slot comes back. Once you have sent a single message, it has been used.
  • Hitting 60 messages never traps your work. The cap stops the conversation, not the build: “You can still create the assistant from what you have described so far.” Review & create keeps working.

Both refusals name a way forward rather than a dead end, under the heading “Your plan’s limit is reached”, with a link to your plan and add-ons.

Troubleshooting

”A wizard session is already in progress”

You have an unfinished setup. Go to Set up by chat and choose Resume to carry on, or Start fresh to put it aside and begin again. Setting one aside never deletes it.

”You have used all 3 setup conversations included in your trial”

The trial allowance above. If one of the three is still unfinished, resume that one — it costs nothing extra. Otherwise the link in the message goes to your plan.

The button says “Review & create” but it is greyed out

Something required is missing, and the Still needed list under the checklist says exactly what — “At least one product or service the business sells”, “At least one thing the assistant must never do — a price it must not quote, a promise it must not make”, and so on. Answer it in the chat and the button turns on by itself.

The checklist has disappeared

You see “We can’t show a checklist right now” instead. Carry on — the button still works, and anything missing is listed when you press it.

It says it couldn’t read my site, and the site is fine

Three things account for most of it, in order:

  1. The address redirects. Type the one the site settles on — usually the www. version, always https://.
  2. The page is built entirely in the browser. A site whose text only appears after its scripts run has nothing to read in the page itself.
  3. The site blocks robots, or it is behind a protection service.

None of it matters much: click Try again if you have a better address, or carry on in the chat, which asks for the same things.

It has been “Reading your website…” for ages

A read that is working finishes inside about a minute. A read that has died — a dropped connection at our end, say — leaves the chip saying “Reading your website…” with nothing behind it, and Try again starts working about three minutes after it began. So: give it a minute, then try again a couple of minutes later, or ignore it and carry on in the chat, which covers the same ground.

I can’t find the report from my build any more

It is kept for the browser tab you built in — reloading that tab keeps it, a new tab or another device does not. Nothing is lost — everything it listed is on the Business details, Catalogue, Knowledge base and Studio screens, which are the real record. Use Review the changes to see the current state of your assistant against the interview.

By chat, or doing it yourself?

Both doors build the same thing and neither is better; they suit different starting points.

Set up by chatCreating it yourself
Best whenYou are starting from nothing and would rather talk than fill in formsYou know what you want to change, or you are adding a second assistant like the first
You getA whole draft assistant — description, rules, catalogue, knowledge baseAn empty assistant to fill in
TimeAs long as it takes to describe the business, spread over as many sittings as you likeMinutes to create, then as long as writing the instructions takes
Goes liveOnly when you publishOnly when you publish

Whichever you use, the assistant is a draft until you publish it, and the publishing step is the same one.

Still stuck? We answer support mail the same working day.

Email support