Setup

What the page is for

Setup is the guide that teaches your AI assistant the business: where it is, what its website is, where the enquiries come from, whether replies should also go out from an email address, what the business does and sells, and what an enquiry should end in. The customer goes through it once, and the assistant starts automatically once every required step is filled in.

The guide is one question per screen with a chapter band at the top. The customer can always pause and continue later: the answers are saved step by step. The page can also be opened again afterwards to correct a single step. The guide only saves what the customer has changed in the guide, so a field changed somewhere else in the meantime (for instance with Auto-fill under Your business in Settings) is not written back to the old value by a guide left open in another tab.

The website is asked for before the integrations: for a customer who pays themselves, right after the payment, and otherwise as the first step (in the mobile app right after Country, if the customer has not paid yet). While the customer does the rest of the guide, your AI assistant reads the website in the background, and at the end one combined screen shows what it found: "Here's what we learned about <company>". The customer corrects anything that is off and presses "Looks right". Whatever it did not find is asked afterwards, one question at a time.

A team member, that is a user who has been invited onto the account without owning it, is sent on to Conversations: the setup belongs to the owner.

What it looks like

The guide opens straight on the first step: Country for a new customer who has not paid, otherwise the subscription step or the website. There is no welcome screen to click through first. At the top of that step there is a welcome instead, "Welcome to Konverto" and "Let's get you set up in a few minutes", and from the second step the logo plus the brand name is shown instead. For a partner's customer it is always the partner's name, also when the customer is logged in on the platform's own domain: there the partner's name is shown without a logo, and if the partner has no name set up, it just says "Welcome".

When the guide opens by itself (when a partner's customer logs in before the setup is finished, and in the mobile app), it continues on the first step that is missing. A customer who has not got past Connect yet does start in Connect, also when you have filled in the website, the goal and the booking for him: the steps there are optional, but only the customer can set up the calendar and the chatbot. When a customer has got past Connect is described under "What is your website?" below.

Below that, a chapter band: one point per chapter on a line. Each point is a small pie that fills one slice for every step in the chapter the customer has completed (four steps give a quarter each), and a full pie turns into a tick. The chapter the customer is in has a soft ring around its pie. On a computer the chapter names sit under the points. On a phone or tablet the chapter name and "Step X of Y" sit above the band. Every step is still one question; the chapters only group the steps under one name.

The number of steps in a chapter can only go down along the way, never up. Before the goal is chosen, and as long as the customer is on the goal step, "Goal and booking" counts the largest number of steps any goal can give (inspection, six steps), and so does "Your business", so the number does not move while the customer tries out the goals. When the customer moves on with a goal with fewer steps, the number drops (for example to five for a phone meeting). If the customer later goes back to the goal step, the largest number counts again while they are there. "Your business" also counts one step for every field the website can fill in, until the website has been read, and the number drops for every field it found. The chapters come in this order:

1. Country (only before the payment, for a customer who is not set up yet)
2. Subscription (only when the customer pays themselves)
3. Website
4. Connect: Facebook, email, calendar, website, the chatbot on your website and other systems, one step each. The chapter is completed (full pie) as soon as at least one source of enquiries is connected: Facebook, Instagram, email, website or other systems. The calendar is not a source and does not count. The chatbot only counts as a source when the customer's package has Chatbot; otherwise it is an optional step like the calendar. If the customer has no agents in their package yet, every step is shown, so the customer can set it all up; it is used once the package is bought.
5. Goal and booking (the same name as the tab in Settings): first the goal, then the booking steps that fit it (duration, service area, price, working hours and period, or the goal's own follow-up step)
6. Your business: "Here's what we learned about <company>" (what the website showed), one question for every field it did not find (company name, industry, description, services, your name and the phone number), and the final details (address, locations, services and useful links). The pie counts the fields the website can fill in: the six questions and the address, when the goal uses an address (before the goal is chosen, the address counts). If the website had everything, the chapter is completed straight away, also before the goal is chosen; if one field out of seven is missing, the pie is almost full, and if it found nothing, the pie is empty. The final details are steps, but not part of the pie, because the website cannot complete them. While the website is being read, the circle is a loader: an arc runs around it and the pie fills up by itself. When the reading is done, the pie jumps to what it found.
7. Done

Once the website is approved, a small pill sits on the right above the band: "Reading <domain>" with a pulsing dot and the number of pages read. Once the website has been read, the pill disappears again. The pill is not shown on the website step itself, nor when nothing is being read, or if the reading fails.

While the guide loads the customer's data, a grey outline of the step is shown instead of an empty screen. The steps slide in briefly, and the movement is switched off if the customer has chosen reduced motion on their device.

The order is deliberate: the website comes right after the payment, and everything the website can fill in comes late, so your AI assistant has time to read the site while the customer does the rest.

In the middle is the step: a heading, a short subtitle, and the fields or the options.

The connection steps (Facebook, Instagram, email, calendar, website and other systems) all look the same. At the top is a row of small icons, one per connection the customer meets in the guide, in the same order as the steps. The icon for the step the customer is on has a ring in the brand colour, and a connection that is in place has a small tick. The other line icons are dimmed, but Facebook, Instagram and email always show in colour (email in black), so for them it is the tick that shows the connection. A step the customer has not reached yet is always dimmed. When a step is waiting for something, the icon has a small yellow clock instead of the tick: the website awaiting verification, other systems waiting for the first enquiry, and a calendar that is connected without a chosen calendar. So the icon always shows the same as the card below it. Facebook and Instagram show their real logos in colour, and email shows a black mail icon until the email is connected: then the icon in the row changes to the Gmail or Outlook logo, while another email provider keeps the black icon. The website shows a globe until it is connected: then the icon changes to the website's own icon (the small image the browser shows next to the site's name), and the pill says "<domain> is connected" (for example "yoursite.com is connected"); if the site has no sharp icon, the globe stays. Tapping an icon goes to that step, but only if the customer has got that far (the same rule as the chapter band). Below the row is "Connect <name>" (the row is the card's only icon, so "Skip" is visible without scrolling), one line about what the connection gives, a large "Connect <name>" button and below it "Skip". Once the connection is in place, it says for example "<page name> is connected" or "<email address> is connected" instead of the button, and below that what belongs to the connection (for example "Wrong page? Choose another" and the Disconnect link). Every connection step has the same underlined link below the pill: Disconnect for Facebook, Instagram, mail, calendar and website, and "Don't use it after all" for other systems. The icons only show the steps the customer actually has: the calendar, the chatbot and "Other systems" only when those steps are shown. The step "Chatbot" also has its icon in the row, a speech bubble between the website and other systems, and the row is also shown above the chat step itself. The speech bubble gets a tick when the chatbot is on, and a small yellow clock when the customer has opened the guide but the chatbot is not on yet (we turn it on ourselves once we find the line). Below the row the chat step looks like the other connection steps (see "Chatbot" below). With Instagram (admin only) there are seven icons, and on a narrow phone they get a little smaller so they still fit on one line.

At the bottom, a bar that is always visible, with Back on the left and Next on the right (plus Skip when the step is not filled in). On the connection steps Next is grey until the connection is in place; there the customer moves on with "Skip" in the middle of the screen. While the step is fetching the status of the connection (a moment, with a small spinning ring in the card), Next is enabled, so the customer is never left without a way forward. Below the bar is the link "Finish setup later". While a step is being saved, Next shows a small spinning ring; there is no message saying it was saved.

Which steps are shown depends on the answers. If the customer picks "Book phone meeting", the address and service area fall away. If the customer picks "Buy on website", every booking step and the calendar step fall away and are replaced by the website steps. The guide is the same for a partner's customers and for customers who signed up themselves. The only differences are Country and the subscription step. Country is only shown before the payment, to a customer who signed up themselves and is not set up yet (see "Where is your business located?" below). The subscription step is only shown to a customer who pays themselves and has no active subscription. If the customer has an active subscription, or is a partner's customer, the website is the first step. In the mobile app there is no subscription step, and the website comes right after Country if the customer has not paid yet. If a payment on the subscription has failed, the subscription step is shown again as the first step, but Country is not. The website always comes before the integrations. The step "Other systems" is only shown when the customer has not connected any of the other integrations, or asks for it.

The guide does not ask for numbers about the business (enquiries per month, how many become customers, customer value and hours). Those are asked for on Overview, in the task "Tell us where you stand today".

Buttons and fields

Back

Goes one step back and saves what has been written along the way. It is disabled on the first step. On the website step, though, an address is only saved with Approve.

Next

Saves the step and moves on. It is disabled until the step is filled in. If the customer presses it anyway, it says "Please fill in all required fields". On the connection steps (Facebook, email, calendar, website, other systems) it is grey until the connection is in place; they are all optional, and the customer can always move on with "Skip" in the middle. On the calendar step the connection only counts once a calendar has been chosen. While a connection step is fetching its status, Next is enabled. On the website step it is only enabled when the field shows the approved address (the grey field), and then it just moves on. Customers who chose "I don't have a website" before 7 October 2026 can always press Next. On the screen "Here's what we learned about <company>" the button is called "Looks right" when the fields were filled in from the website. If the save fails, it says "Could not save".

Skip

Only shown when the step is not filled in, and never on the subscription step, the website step or the last step. It saves what has been filled in, and moves on without requiring the field to be complete. The step comes back on the list of what is missing at the end.

On the connection steps "Skip" sits below the large Connect button instead of in the bar. It moves on without connecting anything, exactly as No did before. If the customer comes back to a step he skipped, he can simply press Connect. The card shows no extra text about the skipped step (Frederik 26/10); that text only appears in the agency's version.

On the step "Chatbot", "Skip" sits in the middle of the screen, as on the other connection steps, until the chatbot is on, or the customer has opened the guide; until then Next is grey. The step is never a requirement.

Finish setup later

Leaves the guide. If the account has no active subscription, the customer lands on the subscription step instead of getting out; otherwise it goes to Overview. A partner's customer and the mobile app do not have the subscription step, so they always go to Overview. What has been filled in is saved, and the guide carries on where the customer was.

On the subscription step the link is only shown to a customer who has finished the setup before or has paid before, for example after a cancelled subscription. There it leads to Overview, so the customer can get out without choosing a plan.

The chapter band

The pie in each point shows how much of the chapter is completed, and screen readers read it out in words, for example "Goal and booking, you are here, 2 of 5 completed". While the website is being read, "Your business" says "reading your website, 40%" instead. If the customer types a new address in the middle of the reading, the reading starts over, and so does the loader, visibly from 0. The chapters can be clicked, but only the ones the customer has already reached: a click goes to the chapter's first step. So there is no skipping past a step that is missing. That includes the website step: without an approved address, the band stops there, except for customers who chose "I don't have a website" before 7 October 2026.

Where is your business located?

The first step, the Country part. The step is only shown before the payment, to a customer who signed up themselves and is not set up yet. If the customer has or has had a subscription, has a failed payment, has or has had a phone number from us, or has a finished setup, or is a partner's customer, the step does not exist at all: it cannot be reached with Back, the chapter band or a link, and a link to it lands on the step after Country. The country decides the phone number, so it is chosen once, before the payment.

The customer picks a country, and the choice governs currency, phone format, time zone and language for the rest of the setup. The country is guessed in advance ("We think your business is in <country>. Change it if that is wrong."), so the step never blocks. The country is the only question: it also decides which country's phone number the customer gets, and which language your AI assistant writes in. Below the buttons it says "You get a phone number from that country, and your AI assistant writes in its language." The choice is between Denmark, Sweden and Finland; Norway is not included yet. A Finnish customer gets a Finnish number and the AI assistant writes Finnish, while the app itself is in English (there is no Finnish version of the app). If the save fails, it says "Could not save your country. Please try again."

If the customer opens the guide again before paying and has picked a country before, the step is skipped, and the customer lands on the step after Country: the subscription step, in the mobile app the website. On a new computer or phone Country can be shown once more, unless the customer has already approved a website, chosen a goal or answered how many inquiries they get a month. An old link to one of the questions the guide asked before 8 October 2026 lands on the step after Country: the subscription step for a customer who pays themselves and has not paid, otherwise the website.

Try Konverto free for a month

The subscription step. The customer picks Monthly or Yearly (with the label "Save 15%") and presses the button to get to the payment. Below it says "Cancel during your free month and you pay nothing." The step is a hard gate: there is no Skip, and the customer cannot get on to the website step and the integrations without an active subscription. If the payment cannot be opened, it says it has to be tried again.

The step is not shown for a partner's customers (they see "We take care of your subscription") and not in the mobile app.

What is your website?

The Your website part, right after the subscription step. If the customer has paid, or is a partner's customer, it is the first step. In the mobile app it comes right after Country, if the customer has not paid yet. Right after paying, the customer lands here, unless the website is already known. The step always looks the same: the field "Website", where the customer types their address, for example yourcompany.com, with the button "Approve" next to it. Approve (or Enter in the field) saves the address, and your AI assistant starts reading the website in the background while the customer carries on with the rest of the guide. The customer does not wait on this step.

Once the address is approved, the field stays with the address in it, but it turns grey, and the button changes to "Approved" and cannot be pressed. The grey means the address is approved. Next is enabled, and Next does not save anything by itself. While the address is being saved, a spinner turns on the button, and the field cannot be edited in the meantime.

For a new customer, Next from the website always goes to the next step, Connect (Facebook), also when the guide opened directly on the website (a partner's customer and the agency's version). Only a returning customer who has already got past Connect jumps ahead to the first step that is missing, so he does not have to click through what he has done. The customer has got past Connect when he has completed the setup before, chose the goal himself or created his addresses for Book a time, or has moved on from every Connect step: the guide remembers every Connect step the customer moves on from (with Next or "Skip"), and if he has only been on some of them, it continues on the first one he is missing. The other steps after Connect do not count, because they can be filled in without the customer having seen them: with a default value (for example "Free" or "All of Denmark"), with what the website showed, or because you left the step to the customer.

Approve always reads the website again from scratch (13 October 2026), also when the address is the same as before, and also for a customer who has already completed the setup. What your AI assistant finds replaces what it read last time. The field is therefore only grey while another press would not do anything: while the website is being read, while the reading waits for the payment, and for the rest of the visit after the customer pressed Approve. If the customer comes back to the step later, the saved address is in an ordinary field with the button "Approve" and the line "Press Approve to read the site again. What we find replaces what we read last time." Next is enabled, so the customer can move on without a new reading. Only a press on Approve starts a reading for a customer who has completed the setup: opening the guide, a link to a step, changing steps or reloading the page never does. If the website is already being read when Approve is pressed, the guide follows that reading instead of starting another one, and a double press gives one reading. If the weekly update of the website is running, the guide waits for it and reads afterwards, instead of showing an error.

The field can always be edited, also when it is grey. As soon as the customer changes the text, the grey disappears, the button says "Approve" again, and Next is disabled until the new address is approved. If the customer changes it back to the approved address, the field turns grey again without anything being saved. If the customer leaves the step with a change that has not been approved (for example with Back or the chapter band), it is not saved, and next time the approved address is in the field, grey.

An #anchor after the address (for example yourcompany.com#contact) never counts as a new address. While the website is being read, or once it has been read, "www." in front or http instead of https does not either: the field stays grey, so the same site is not read again from scratch, for example when the customer pastes the address from the browser. If the site could not be read, they do count as a new address, so the customer can approve for example the www version and have it read.

The reading starts straight away. If the payment has not been registered yet when the customer saves the address (it can take a moment), the reading waits and starts on its own the moment the subscription is active. The customer does not have to do anything.

Below the field with the approved address there is a small line about how far the reading has got:

• "We're reading your website", with the number of pages read when it is known
• "Website read"
• "We will read it as soon as your account is active", when the reading is waiting for the payment
• "We couldn't read the site. You can enter the details yourself later.", with "Try again" when a new reading can be started

If there is nothing to show yet, there is no line. While the field has been changed and not approved, there is no line either. A customer who has completed the setup only sees "We couldn't read the site" and "Try again" for the reading they asked for themselves with Approve, never for an old one.

If the customer signed in with a business email, there is a suggestion below an empty field, for example "Is it yourcompany.com?". The suggestion is only filled in when the customer presses it. There is never a suggestion from gmail, hotmail and other free email addresses.

There is no button to skip the step: everyone has to enter a website and press Approve to move on. The chapter band cannot take the customer past the step either, and the setup cannot be finished without an approved address (see "Go to dashboard"). The "I don't have a website" button was removed (7 October 2026). Customers who chose it before just see an empty field with Approve and can press Next whatever is in the field. What they type is only saved with Approve, and the guide does not send them back to the step. In the agency's version of the guide, the agency can still press "Let the user fill it in" on the step, so the customer enters the address themselves.

A Facebook page does not count as a website. If the customer types one, it says "That looks like a Facebook page. Enter the address of your own website instead." and Approve is disabled. If the address cannot be read (for example "yourcompany" without .com), Approve looks disabled too, and when the customer presses it or leaves the field it says "Enter a valid address, e.g. yourcompany.com".

A new address is always read from scratch, and what was found on the old one is not used. If the payment is not in place, the reading waits as described above, also for a customer who has completed the setup.

Connect Facebook

The first step in the Integrations part: "Connect Facebook" and the line "Leads from your Facebook ads come straight in, and your AI assistant answers them right away." The "Connect Facebook" button starts the Facebook login, and afterwards the customer picks which page to listen on ("Choose a page"). If it is connected, it says "<page name> is connected" (or "Facebook is connected" if the page is not known), "Wrong page? Choose another" and the Disconnect link, and Next is enabled. "Skip" moves on without Facebook. The step does not block. If the connection works, the message "Facebook is now connected!" appears. If the customer presses Cancel at Facebook, a calm message appears: "You cancelled. Nothing has changed." If the customer disconnects here, the task "Get more out of your Facebook inquiries" disappears from Overview right away. Right after paying, the customer lands here if the website is already known; otherwise the website step comes first.

Connect Instagram

Only for the platform's own admin accounts for now, so an ordinary customer does not see the step. "Connect Instagram" starts the Instagram login. Under the button it says "You need a Meta business account, and you log in through your browser." If it is connected, it says "@<name> is connected". Optional: "Skip" moves on.

Connect email

The Integrations part, after Facebook. The step is optional: below the button it says "Optional. Without email, your AI assistant answers your leads by SMS. You can connect email later under Settings." The customer can move on with "Skip" without connecting anything. If he connects an email, your AI assistant can also reply from the customer's own address. If the customer's package does not have the Booking agent (for example only Chatbot), no AI assistant answers on email or SMS: the line under the heading then says "Customers who book in the chat get a confirmation and a reminder from your email address.", with nothing below the button. The agency's version says "Optional. Your email is only used for messages about a booked appointment, such as the confirmation and reminder. You can connect email later under Settings." The "Connect email" button shows the field for the email address (filled in with the login email); the customer presses Connect next to the field, after which the guide finds the provider itself. If the provider is picked by hand, there are three options: Gmail ("Gmail or Google Workspace"), Outlook ("Outlook or Microsoft 365") and "Other provider" (one.com, Simply and the like), which asks for the password to the mailbox. Once the connection is in place, it says "<email address> is connected" with the Disconnect link below it. In the mobile app the consent opens in the browser and comes back automatically. The calendar is not connected here, but on the next step.

If the customer comes back without every checkbox ticked on Google's page, it says: Google was not given permission to send email, try again and leave every checkbox ticked.

Connect calendar

The Integrations part, right after email. "New appointments land in your calendar, and your busy times never get booked." The "Connect calendar" button shows the three choices in the card: Google Calendar, Outlook and Apple. Afterwards the customer picks which calendar to use. If it is connected, it says "<name of the chosen calendar> is connected". Optional: "Skip" moves on, and the calendar can be connected later under Integrations. The card here looks as before; only the line under Integrations shows the account, the chosen calendars and when they were last read when it is unfolded (and the email account's profile picture, when the calendar is connected with the same account as the email). Folded, that line just says "Connected".

If the customer closes the calendar choice without choosing, the calendar is connected, but no busy times are read. Then it says "Connected, no calendar chosen" with a yellow clock, and the large button says "Choose calendar". Next is grey until a calendar has been chosen (or the customer presses "Skip"), and the icon at the top has the clock instead of the tick. It is the same warning as on Integrations.

The step is shown before the customer has picked a goal, and for the goals that book (inspection, phone meeting, video meeting, Book appointment). If the customer picks "Buy on website", it disappears. When a partner fills in the guide on the customer's behalf, the step is not shown: the customer has to connect their calendar themselves.

If the customer uses Gmail, Google's consent comes twice in a row: once for the email and once for the calendar. They are two different connections.

Connect website

The same part, after the calendar: "Inquiries from the form on your website come straight in." The "Connect website" button opens the setup of the form on the customer's own website (the code and the instructions). Once the setup has been opened, it says "Awaiting verification" and the button "Continue setup", and Next is enabled: the customer has done their part, and the verification only happens when the first enquiry from the website lands. Then it says "Your website is connected". "Skip" moves on. It does not block.

The step is not shown when the customer's package does not have the Booking agent, neither in the customer's own guide nor in the agency's version: the form's enquiries are only used by the Booking agent (the same rule as Integrations).

Chatbot

In Connect, right after "Connect website", and with the same look: a large speech bubble at the top, the heading "Chatbot", below it "Your AI assistant answers your visitors based on what we have read on your website.", one large button "Set up the chatbot" and "Skip" below it.

The button opens the same window as "Open the guide" in Settings: a ready message for the web developer, or step by step for the customer's own website platform, with the code line itself and the button "Copy". The code line is no longer shown directly on the card. It is exactly the same line as in Settings, the Chatbot tab. For a partner's customer it points at the partner's own domain.

Once the guide has been opened, it says with a yellow clock "Turns on by itself once the line is on your website" and the button "Continue setup", which opens the guide again. At night the customer's front page is checked for the line, and once it is there, the chatbot is switched on without the customer having to press anything. There is no check button in the setup; if the customer does not want to wait, they can press "Go live" in Settings, the Chatbot tab. If the chatbot is already on, it says instead, with a tick, "The chatbot is on. It shows on your website when your AI assistant is running." and below it the link "See the code line", which opens the same window.

The step is optional, just like the calendar: it counts in "Step X of Y" in Connect, but the chapter's pie only follows the sources of enquiries (and the chatbot, when the customer's package has Chatbot). It is completed when the chatbot is on for at least one website, or when the customer has opened the guide. Until then Next is grey, and the customer moves on with "Skip". If the customer's package has Chatbot, the chatbot is a requirement on the Ready screen until it is set up (see "Go to dashboard").

The step is only shown in the customer's own guide, when the customer's package includes the chatbot (the same rule as the Chatbot tab in Settings), when the customer has a website saved, and when the account is set up to reply (without that the chat can only answer with a fixed text). For a new customer the account is set up a few seconds after the payment, and the step appears as soon as that has happened, while the customer is on the website step or in Connect (the guide keeps checking for up to about two minutes). If the customer reloads the page on the step, the customer stays on it. For a partner's customer it is only shown once the partner's own domain is ready, so the line never points at a foreign domain.

The guide does not ask about the look of the chatbot or its suggested questions. We find the colour ourselves on the customer's website when it is read (see Settings, the Chatbot tab); the theme follows the visitor's system, and there are no suggested questions until the customer writes some in Settings.

Connect other systems

The same part: "Inquiries from forms, portals or Zapier come straight in." The "Connect other systems" button shows the customer's own webhook address with a copy button; nothing has to be switched on, the address already works. Until it is used it says "Waiting for the first enquiry", and Next is enabled. Below the address is the link "Don't use it after all": it undoes the choice (the answer is cleared, and the card shows the "Connect other systems" button again), so the step is not shown as in use. "Skip" moves on. It does not block.

The step always sits in Connect like the other sources, also when the customer has connected something else. Without the Booking agent in the package it is not shown, as on Integrations.

Your phone number

"The number you answer customer calls on". The customer only gets this step when the website had no number, and it is the last of the questions in Your business (the Phone number part). If your AI assistant found a Danish number on the website, it is shown on the screen "Here's what we learned about <company>" instead, where the customer can correct it. For Swedish, Norwegian and Finnish customers nothing is ever filled in beforehand, so they always get the step, unless the number is already saved.

Required, and it has to be a valid number in the format of the customer's country, otherwise it says for example "Enter a valid phone number, for example 12 34 56 78" (in Sweden "070 123 45 67"). Below the field, in a blue box: "Customer calls are forwarded to this number. Change it if they should reach a different one."

The number belongs to the Booking agent (email and SMS). If the customer's package does not have the Booking agent, for example only Chatbot, the step does not exist, also not in the agency's version of the guide, and the number is not shown on "Here's what we learned about <company>".

What is your primary goal?

The first step in the Goal and booking chapter (the Communication part), right after the integrations, and the choice that governs the rest of the guide. Five options:

• "Book inspection" the lead is guided to book an inspection, put in the calendar based on address and availability.
• "Book phone meeting" the lead books a phone meeting based on the customer's availability.
• "Book video meeting" as for a phone meeting, and the meeting link is created and sent automatically.
• "Book appointment" the lead books an appointment at one of the customer's addresses, and the address is included in the confirmation.
• "Buy on website" the lead gets answers about products and prices and is sent to the right place on the customer's own website.
• "Qualification" the AI assistant asks the customer's own questions and only passes on the inquiries that fit. The goal does not book and has no booking steps.

Required. Some goals can require a particular plan, and then it says "Requires the Pro plan".

"Book inspection" only exists for Danish customers, because it is built on Danish postcodes and Danish addresses. A Norwegian, Swedish or Finnish customer does not see the goal. If a Norwegian, Swedish or Finnish account already has the goal from before, it stays in the list with the text "Inspections only work for Danish businesses. Choose another goal so your inquiries can be followed up.", and the account takes no new inquiries until another goal is picked.

Important for the partner: "Book appointment", "Buy on website" and "Qualification" are still in testing and are shown ONLY for the individual test customers they have been opened for, plus the platform's own admin accounts. An ordinary customer sees only three goals in the list, so the steps belonging to the first two beta goals ("Where can appointments be booked?", "Which services can be booked?", "Useful links" and "Record purchases automatically?") are out of reach for them. Do not promise them to a customer without getting it confirmed first.

Record purchases automatically?

Only shown for the goal "Buy on website". "Can your webshop or booking system notify us when someone has bought?" Yes shows the address the customer's own system has to call, with a copy button. When a purchase is reported in, the lead is marked as converted, the follow up stops, and the sale counts in the results on Overview. No moves on: the customer can mark sales by hand and switch this on later in Settings. It does not block.

Duration

The first booking step. "How long does an inspection take?" or "How long does <the meeting type> take?" The customer picks a number of minutes from 5 to 120 in steps of five. Required. The step is not shown for the goal "Book appointment", where every service has its own length.

Service area

"Which areas do you cover for inspections?" Three options: "All of Denmark", "Only my local area" with a "Max driving distance" in kilometres, or "Specific regions" where at least one area has to be picked. Not shown for phone and video meetings.

Does it cost anything?

"Does an inspection visit cost the customer anything?" or to book the meeting. Three options: "Free" (no obligation, the default), "Fixed" with a fixed amount, or a rate, "Per km" or "Per minute", with a rate value. There is no note field on the step. Not shown for the goal "Book appointment", where the price belongs to the individual service.

Working hours

"When can customers book inspections?", or the meeting type instead of inspections. The customer sets times per weekday. At least one day has to have a valid time range. If the customer runs alternating weeks, both the even and the odd week have to have a valid day.

Booking period

"How far ahead can bookings be made?" A choice between 1 week, 2, 4, 8, 12, 16 and 24 weeks. Required.

Here's what we learned about <company>

The first step in the Your business chapter, after Goal and booking. The screen SHOWS what your AI assistant found on the website, and only that: "Company name", "Industry", "Short description", "Services / Products", "Your name" and the phone number (with the box saying customer calls are forwarded there). If it found "Additional Information", that is shown too; otherwise there is a small "Add other information (Optional)". Every field it did not find becomes its own question afterwards, and at the bottom it says "We'll ask about the rest next, one question at a time."

The heading is "Here's what we learned about <company>" with the text "We read your website. Correct anything that isn't right." The customer corrects freely and presses "Looks right". Empty fields are filled with what the website had, and that is saved when the customer moves on. A field that is already filled in is never overwritten without the customer seeing it. If the customer chose the "Book a time" goal and it found services on the site, they are listed below with checkboxes (other goals use no services with a duration, so the list is hidden there), and the ticked ones are created as the customer's services. The owner can also switch on keeping the fields updated from the website every week.

If the customer pressed Approve on the website step, and the website had been read before (or the customer had completed the setup when they pressed), the chapter behaves as for a new customer: first the waiting screen, then the screen with what the new reading found, and afterwards one question for each field it did not find. The screen shows the new findings in the fields on top of what is saved, and above the fields it says "The fields show what we just found on your website. What you saved before is only replaced when you press "Looks right"." Only that button saves the new findings: if the customer leaves the screen with Back, the chapter band or "Finish setup later", what is saved stays unchanged, and the new findings are shown again next time. If the customer corrects one of the new fields on the screen, the correction is what gets saved. In the questions for the fields the reading did not find, the saved value is already in the field, so the customer can just press Next. A field that is not on the screen (for example the phone number for a customer without the Booking agent, or a field the agency filled in) is never changed from here. Once the customer has pressed "Looks right" or completed the setup, the reading is used up: a later visit to the guide shows what is saved as before, and a new reading takes a new press on Approve. If the customer has switched on the weekly update, and it is running when Approve is pressed, it can write the description and the services from the new reading before the customer has pressed "Looks right". If the customer then leaves the screen with Back or "Finish setup later", the two texts the screen showed before can be saved again.

If the reading is not finished yet, a calm waiting screen is shown: a ring that fills up by itself with the percentage in the middle, "We are still reading your website", the domain, roughly how long is left ("About 1:20 left", at the end "Almost done") and how far it has got ("11 of 20 pages read", afterwards "Putting together what we learned"). The time is worked out from how fast this particular reading is going, and the percentage follows the time, so the two always match. Before the reading has counted the pages, it assumes a large site (just over two minutes). The clock never goes up: if the reading turns out to take longer, it counts down more slowly, and if it goes faster, it glides down over a few seconds. If the reading stands still, the percentage stands still too, and the clock only counts down slowly. The percentage never goes backwards and does not reach 100 before the reading is done. The screen moves on by itself to what it found as soon as it is done. The customer cannot skip the wait: there is no button past the screen, and Next cannot be pressed while waiting. In return, the screen never hangs. If the reading stands still for 2.5 minutes, or takes too long in total, the screen gives up and shows the error message below. "Too long" is twice the expected time for the size of the site, but at least 3 and at most 7 minutes (the readings measured so far all took under 2.5 minutes). If the reading finds more pages along the way than it first counted, the largest number is used. Once the screen has given up, it does not come back for the same reading, not even if the reading shows signs of life again.

The waiting screen covers the whole chapter. If the customer lands on one of the one-at-a-time questions while the reading is running (for example via "Get started" on the dashboard after "Finish setup later", or with Back from a later step), the waiting screen is shown instead. In the agency's version, "Let the user fill it in" is not shown on the waiting screen.

If the website could not be read, took too long, or nothing useful was found, the screen says "We couldn't read your website, so you'll fill it in yourself." (or that not enough was found), and the customer gets the questions one at a time. "Try again" reads the site again. A customer who has completed the setup only sees the message and "Try again" for the reading they asked for with Approve. If the screen gave up while the reading is still running, "Try again" only appears once the reading itself has stopped or has stood still for 4 minutes: a new reading on top of the old one would read the site twice. If a reading that took too long finishes after all while the customer is in the chapter, what it found is shown. If there is no website (a customer who chose "I don't have a website" before 7 October 2026), the screen is called "Tell us about your business", and everything is asked one at a time.

The requirements are the same as always: name and industry have to be filled in, description and services at least 50 characters each, and the phone number in the country's format. "Additional Information" is optional. The description can be up to 2,500 characters, services and additional information up to 6,000, and what the website gave is cut at a whole line, never in the middle of a word. The fields can be corrected afterwards in Settings.

What is your business called?, Which industry are you in?, Tell us briefly about your business, What do you sell? and What is your name?

One question per screen in the Your business chapter, right after "Here's what we learned about <company>", but only for the fields the website did not have. Same fields and requirements as on the combined screen: the name and industry have to be filled in, the description and services must be at least 50 characters. "What is your name?" is the owner's own name ("So we know who we are talking to."); it is shown on the account and in the calls, but it does not block going live and is not on the list of missing things. An industry the website reading could only call "other" does not count as found, so the customer chooses it.

Which questions the customer gets is settled once the website has been read, and it does not change while the customer goes through them. If the website's suggestions arrive while the customer is on one of the questions, the empty fields are filled in, and the customer just presses Next. After a new reading the customer asked for with Approve, there is a question for each field the reading did not find, also when something is saved in it; the saved value is in the field.

Your address

The Final details part. "Enter your address so the system can calculate the distance to the customer." Both the street name and a postcode in the country's format have to be filled in. If your AI assistant found a complete Danish address on the website, it is filled in beforehand. Not shown for phone and video meetings, which have no physical place.

Where can appointments be booked?

Only for the goal "Book appointment". The customer writes the addresses the lead can come to. There has to be at least one active address, otherwise your AI assistant cannot offer an appointment at all, and the step blocks. If the customer has only one address, the assistant never asks the lead about a place, it simply states it.

Which services can be booked?

Only for the goal "Book appointment". The customer adjusts the list of services and gives each one a length. At least one service has to have a length, otherwise there is nothing to book. The services from the website are normally created on the screen "Here's what we learned about <company>". If they only arrived afterwards, there is a button, for example "Add 4 services from your website". If some services are missing a length, the box "Services without a length" appears with the choice "Continue anyway" or "Fill in the length". A service without a length is not offered to leads.

Useful links

Only shown for the goal "Buy on website", which is a beta goal. "The pages your AI assistant should send customers to. One per line, e.g. "Prices: https://yourcompany.com/prices"." It does not block: the knowledge itself comes from the business fields.

Go to dashboard

The last step, the Activate part. The button sits in the bar at the bottom right, where Next sits on the other steps, with Back on the left, and is the guide's "done". This step has neither "Skip" nor "Finish setup later". The screen sits directly on the guide without a box around it, like the other steps. The heading is "You are almost ready!" as long as something is missing, and "That's it!" when everything is in place. The step line at the top is the same as on the other steps.

If something is missing, only what is missing is shown, never what has already been done. It sits in one list with a frame around it. Each line has an empty red circle, a title, one short line about what the item is and why it needs doing, and a button on the right (below the text on a narrow screen) that jumps straight to that exact step. The first button in the list is filled, the rest have an outline. The order is fixed:

1. First the things about the account and the payment: Account locked and Payment issue (the button "Fix payment") and Subscription with the text "Choose your plan so your AI assistant can get started." (the button "Choose plan"). For a partner's customer, Subscription means the account is not active with the agency: then it says "Contact your agency and they will activate the account.", and the line has no button. Email is not on the list: it is optional. The buttons only lead to the subscription step when the guide has it. If the customer already has an active subscription (for example a used-up plan or a locked account), the button opens "Manage payment" instead, as in Settings. In the mobile app the lines have no button, and the text is "Your subscription is managed on the website." For a partner's customer the lines have no button either.
2. Then the fields that are missing, in the guide's order, with the button "Fill in": Purpose of inquiries, Meeting duration, Service area, Booking price, Working hours, Booking period, Company name, Industry, Company description, Your services / products, Phone number, Booking address, Meeting locations, Services, Website & products. Under "Your services / products" it says, for example, "What you offer, so your AI assistant can answer correctly." The owner's name is not on the list: it is not a requirement.
3. Then "Inquiries in your plan" (there are no enquiries left, the button "Choose plan", which opens "Manage payment") and "SMS number" with the text "Your SMS number isn't set up yet. Contact support and we will set it up." Both are only shown when the customer has a subscription: without one, only Subscription is shown, since there are no inquiries without a plan, and the number is bought together with the subscription.
4. Finally Inquiries, if no source is connected, "The chatbot is not set up", if the customer's package has Chatbot and it is not set up, and at the very bottom Calendar, if it is missing (see below). A connected TikTok account (under Integrations, shown when the connection has been opened for customers) also counts as a source, even though it has no step in the guide.

A business field or the phone number jumps to its own question, or to the screen "Here's what we learned about <company>" if that is where the field is shown. The SMS number line has no button: there is nothing the customer can fill in themselves, and the number has to be set up by support. If the number is ordered and on its way, and nothing else is missing (not a source of inquiries either), "That's it!" is shown instead with a screen saying the number is coming. If something else is missing, the list is shown as usual under "You are almost ready!", without SMS number. "That's it!" is never shown above a red line.

If the screen says "You are almost ready!" but cannot point to a specific step, "Something in the setup is missing" is shown with the text "Contact support and we will find the cause." (in the agency's version "Something is missing for the customer"), so the list is never empty. A goal that books (inspection, phone meeting, video meeting or Book a time) always counts as automatic booking, also when the goal was set by the agency: the booking's own steps (for example duration and working hours) decide whether something is missing.

If the customer has a goal that books (inspection, phone meeting, video meeting or Book appointment) but no connected calendar, "Calendar" is shown at the bottom of the list with the badge "Recommended", a dashed amber circle and a faint amber background, and the text "Not a requirement. With your calendar your AI assistant can see when you are busy, so you avoid double bookings." It is advice, not a requirement, and it is never red. Bookings still land in the internal calendar. The button "Connect" jumps to the calendar step. A calendar that is connected but has no selected calendar counts as not connected: the line is shown then too. This applies to every package, also a package with only Chatbot, because the chatbot books by itself. The line is on every version of the screen, also on its own under "That's it!", but it does not change the message that the AI assistant is running. In the bureau's version of the guide, the same line is shown when the customer's own calendar is missing, but without a button: it says "Not a requirement. With the customer's calendar your AI assistant can see when the customer is busy. The customer connects their calendar themselves under Integrations."

If the customer's package has Chatbot (only Chatbot, or Booking and Chatbot) and the chatbot is not set up yet (it is not switched on on a website, and the customer has not opened the instructions during this visit), "The chatbot is not set up" is shown on the list as a requirement: a red circle and no badge, above the calendar. The text is "The chat must be on your website before your AI assistant can answer your visitors." and the button "Connect" jumps to the step "Chatbot". If the step does not exist for the customer (for example without a saved website), there is no button, and the text points to Settings, the Chatbot tab. In the bureau's version the line has no button and the text "You find the code line for the customer's website under Chatbot in the customer list." As long as the line is shown, the screen says "Almost ready" and says neither that your AI assistant is running nor that the setup is done. If the chatbot's status cannot be seen (it is loading, or the lookup failed), the line is not shown.

Right after payment, everything can be in place while the AI assistant is still being set up in the background (this usually takes less than a minute). The screen then says "We're getting your AI assistant ready" instead of "That's it!", with the text "This usually takes less than a minute. You can finish the setup in the meantime, and your AI assistant starts on its own." The screen switches by itself once it is ready, and the customer can press the button in the meantime.

If no source of inquiries is connected (Facebook, Instagram, email, the website or other systems, the same rule as the Connect chapter), "Inquiries" is on the list with the text "Connect your website, Facebook or email so your leads land here." and the button "Connect", which leads to the first step in Connect. As long as the line is shown, the screen does not say that your AI assistant is running. The calendar is not a source. If the customer's package has Chatbot, the chatbot counts as a source once it is set up (on for a website, or the customer has opened the guide), exactly as in Connect. For a customer whose package has no booking agent, the line is not shown, also not in the bureau's version while the screen waits for the customer to accept the invitation.

If the package has no booking agent, the screen does not say that your AI assistant is running, but that the setup is done. With Chatbot in the package, once the chatbot is set up, it says "The setup is done. The chatbot answers visitors on the website, and enquiries from other channels land in the inbox." Without Chatbot, or while the chatbot's status cannot be seen, it says that new enquiries land in the inbox, and that the customer follows up on them. In the bureau's version it says "The setup is done. The customer's package has no booking agent, so new enquiries land in the customer's inbox, and the customer follows up on them." The goal and the booking steps have to be filled in for every package before the screen says that the setup is done.

"That's it!" and the message that your AI assistant is running are only shown when the system itself reports that your AI assistant answers new inquiries. If the setup is filled in but something else holds it back (for example an SMS number that is not set up yet, a pause, no source of inquiries or a chatbot that is not set up), the screen says "Almost ready" with the text "Your AI assistant starts as soon as this is in place:" and one line per reason in the same list, each with its own explanation, for example "No calendar receives bookings" with "Choose the calendar the bookings should land in." If the subscription is missing or cancelled, "No inquiries left" is not also shown. "No booking agent" is never shown: it is the customer's package, not something missing, and the chatbot books by itself. Reasons the customer cannot jump to have no button. In the bureau's version of the guide the reason cannot always be seen: the line then says "Something is missing for the customer" with the text "Something in the customer's setup is not in place yet, for example the SMS number. Contact support and we will find the cause." When the calendar is also on the list, it says "More may be missing" with the text "Something other than the calendar may also be missing, for example the SMS number. If the screen still says Almost ready after the customer has connected their calendar, contact support and we will find the cause." instead.

When everything is in place, a check mark is drawn in the brand colour with a short burst of confetti (only the first time, and not if the customer has chosen reduced motion on their device). The screen does not show what the customer has already connected, not even when everything is in place.

Below the list or the text there is "Optional" with the number of links in brackets, for example "Optional (2)". It is closed until the customer presses it. It then opens the "Next steps" card with the link "Team members". The chatbot and the Knowledge bank are not listed here: the chatbot has its own step in the guide, and the Knowledge bank is not something the customer sets up. A link finishes the setup the same way as the button, but opens the page in Settings instead of Overview.

For a direct customer on the web (not a partner's customer, and not in the mobile app) there is also "Download the phone app" in the opened part, below the card, with two buttons: App Store and Google Play, the same as in the task on Overview. They open the store in a new tab. It does not finish the setup and is not a requirement: the customer can carry on without the app. A partner's customer never sees it, and the number in brackets is then one lower.

In the bureau's version of the guide, the screen says "Waiting for the customer to accept the invitation" instead of "That's it!" when the setup is in place but the customer has not accepted the invitation yet. Until then, the AI assistant does not answer the customer's enquiries. If the customer's package does not have the Booking agent, it says "The customer can only receive enquiries once the invitation has been accepted." instead. The invitation can be sent again with "Resend invite" in the customer list. The button is shown for every customer who still has to accept, also those who have been logged in.

The customer's own version shows the same state: if the customer has not accepted the terms, and nothing else on the list is missing, it says "The terms have not been accepted yet". If you have added a privacy policy, the customer can accept right on the screen with the button "Read and accept". It opens a window that says "Terms from" and your name, with links to your privacy policy and (if you have one) your data processing agreement, which open in a new tab, the checkbox "I have read and accept the terms above" and the button "Accept". The text above says "Your AI assistant gets started as soon as you have accepted the terms below." (without the Booking agent "You can only receive enquiries once you have accepted the terms below."). Once the customer has pressed it, the screen moves on by itself. If the row "The terms have not been accepted yet" is on the list together with other things that are missing, the button "Read and accept" sits on that row, and once the customer has accepted in the window, the row slides softly out of the list. The same goes for every row on the list that gets resolved. The link in the invitation still works as before.

Only the customer can accept. If you view the account as the customer (Manage), the checkbox and the button are there but turned off, with the text "Only the customer can accept the terms. You are viewing the account as someone else, so the button is turned off." The same applies when we view the account. The button only works when the customer is logged in with a password they chose themselves through the link in their email. If the password was set some other way, or the customer is logged in with a one-time link from an email, the button is turned off with the text "For security reasons, you can only accept here once you have chosen your password through the link in your email. Use "Forgot password?" on the login page to get a new link, and you can accept the terms there." If you have not added a privacy policy, the customer does not wait for the terms at all, and neither the row nor the button is shown. If the terms cannot be fetched, the old text is shown: "Your AI assistant gets started as soon as the terms are accepted through the link in the invitation. Contact us if you cannot find it." The screen never says "That's it!" in the meantime, and the button at the bottom gives the message "Your setup has been saved". If something else is missing, the list is shown as usual.

The agency's version opens on the first step that is missing when it is opened from the customer list. If you have not clicked through Connect yet (Next or "Let the user fill it in" on each step), it opens on the first Connect step neither you nor the customer has been on. A link to a specific step (for example after reloading the page) opens on exactly that step, as in the customer's own guide.

In the bureau's version of the guide the button is called "Back to customer list", and it leads there. When the bureau presses it, the customer still gets their own ready screen when they open the setup themselves. If the bureau presses Next on Facebook, Instagram, email, the website or other systems without anything being connected, the step stays with the customer, exactly like "Let the user fill it in". Only a connected step counts as done by the bureau. For other systems, connected means that the customer has said yes themselves, or that the first inquiry has arrived: the bureau's own Yes on the screen is not saved.

When the bureau presses the button, the message is "The customer's setup is ready. The customer logs in with the invitation, and you can send it again from the customer list." when the screen says the customer is running, and otherwise "The customer's setup is saved." with the same continuation. The guide does not send an invitation itself: it is sent when the customer is created, and can be sent again with "Resend invite".

The button can be pressed even when other things are on the list: it marks the setup as completed and sends the customer to Overview. If the screen says your AI assistant is running, the message is "All set up! You are ready to receive leads.", otherwise "Your setup has been saved". If the setup cannot be saved, it says "Could not save. Please try again.", and the customer stays on the screen and can press again.

The exception is the website. If the customer has got here without an approved website (for example through a link from Overview), the button sends the customer to the website step with the message "Enter your website and press Approve to finish the setup." Once the address is approved, Next leads to the first step that is still missing, or back here. Customers who chose "I don't have a website" before 7 October 2026 are not affected.

What the customer sees afterwards

If "Go to dashboard" is pressed on the last step, the setup is marked as completed, and the customer is no longer sent into the guide automatically. If every requirement is met, your AI assistant starts on its own and replies to new enquiries. If something is missing, it only starts once the last thing is filled in: "Your AI assistant starts automatically when all steps are filled in."

If the customer's phone number only becomes ready afterwards, a message about it appears, and the number is shown in Settings.

The guide itself sends no emails or text messages to leads. What it does is open connections in the customer's name: the Facebook login, the email account and the calendar. From the moment the email account is connected, your AI assistant can send from the customer's own address, so leads see the customer as the sender. Without an email account your AI assistant replies by SMS. The website, which was read along the way, becomes your AI assistant's knowledge about the business.

Everything the guide saves can be corrected afterwards in Settings. The customer can also open the guide again and go straight to a single step.

The guide does not ask about reminders for the customer themselves: they come as a notification in the app. When a new customer picks inspections, the message the evening before about the next day's inspections is switched on, and the notice for an inspection is always 24 hours, as in Settings.

Typical questions from the customer

"Do I have to fill in everything in one go?"

No. Press "Finish setup later", and what has been filled in is saved, and the guide carries on where you were. If you do not have a subscription yet, you land on the subscription step.

"Why can't I move on?"

Next is disabled until the step is filled in. On the connection steps (Facebook, email, calendar, website, other systems) Next is grey until the connection is in place: press "Skip" below the Connect button to take it later. If the calendar is connected but Next is still grey, a calendar has not been chosen yet: press "Choose calendar". The fields that most often stand in the way are the descriptions, which need at least 50 characters, and the phone number. If there is a "Skip", the step can be taken later; if it is not there, the step is required.

"Why can't I finish the setup?"

The only thing that blocks "Go to dashboard" is the website: without an approved address, the button sends the customer to the website step. Everything else on the list of what is missing can be filled in later.

"Why am I not asked for my numbers in the setup?"

The setup no longer asks for numbers about the business, neither for customers who signed up themselves nor for a partner's customers. Enquiries per month, how many you reach, how many book, how many meetings become a sale, what a customer is worth, and how many hours a week you spend following up are asked for on Overview, in the task "Tell us where you stand today". The task stays until all six are answered, and it does not block anything.

"What do you use the numbers for?"

They show what you got out of your enquiries yourselves, before your AI assistant took over. The results are held up against that, so it can be seen whether it goes better than before. The numbers are not shown to your leads.

"Can I skip the email?"

Yes. Email is optional, and your AI assistant replies by SMS without it. The customer just presses "Skip" on the email step. The email can be connected later under Settings, on the Integrations tab, and then replies can also go out from the customer's own address. Enquiries that only left an email address get no reply until an email is connected.

"Why do you ask for my website before the integrations?"

So your AI assistant can read it while you do the rest. By the time you get to "Here's what we learned about <company>", the fields are usually already filled in, and you only have to correct what is off.

"I don't have a website"

The guide requires a website. There is no longer a button to skip the website step, and a Facebook page does not count. The customer can leave the guide with "Finish setup later" and enter the address when it is ready. As long as there is no address, the guide sends the customer back to the website step when the setup is resumed, and the setup cannot be finished. Customers who chose "I don't have a website" before 7 October 2026 keep their choice and can move on as before.

"My address is grey. Can I still change it?"

Yes. The grey just means the address is approved and being read (or was just approved). Type the new address in the field and press Approve. As long as the new address is not approved, Next is disabled, and if you change it back to the old one, the field is grey again.

"Can I have my website read again?"

Yes. Go to the website step in the setup and press Approve, even if the address is the same. Your AI assistant reads the site again from scratch, and what it finds replaces what it read last time. Under Your business you see the new findings, and your saved details are only replaced when you press "Looks right".

"What your AI assistant found on my website is wrong"

Correct it directly on the screen "Here's what we learned about <company>" before you press "Looks right", or afterwards in Settings. Fields you have typed in yourself are never overwritten by the website without you seeing it: after a new reading the new findings are in the fields, and they are only saved when you press "Looks right".

"It is still reading my website"

It usually takes one to two minutes, longer for large sites; the waiting screen shows roughly how long is left and how many pages have been read. The wait cannot be skipped, but it never hangs: if the reading stands still for 2.5 minutes, or takes too long (at most 7 minutes), the guide stops waiting, so you can write it yourself. "Try again" appears once the reading has stopped.

"Why do you ask about some things and not others?"

What your AI assistant found on the website is on the screen "Here's what we learned about <company>", where you can correct it. The guide only asks about what it did not find, one question at a time. That is why two customers do not always get the same questions, and why "Step X of Y" in Your business drops once the website has been read.

"Do you read my calendar?"

Only if the customer connects it on the calendar step (or later under Integrations). Then new appointments land in the calendar, and the busy times are not booked. Without a connected calendar the times that can be booked come only from the working hours the customer has set up.

"Why is Connect completed when I have only connected one thing?"

One source of enquiries is enough for your AI assistant to get going, so the chapter counts as completed with the first one (Facebook, Instagram, email, website or other systems). The rest can be connected at any time under Integrations. The calendar on its own does not count, because it does not bring in enquiries. If the package has Chatbot, the chatbot also counts as a source.

"What happens if I pick the wrong goal?"

The goal can be changed, and then the following steps change with it. If you have got far, the booking steps for the new goal have to be filled in. Three of the goals, "Book appointment", "Buy on website" and "Qualification", are still in testing and most customers cannot pick them at all.

"When does the AI assistant start replying?"

When every required step is filled in, the subscription is active, and at least one source of inquiries is connected. The last step shows exactly what is missing, and it only says that your AI assistant is running once the system itself reports it.

"I cannot see the subscription step"

It is not shown when the subscription is already active, when it is managed by a partner, or in the mobile app.

"Why can't I see the step about the chatbot?"

It is only shown when the package includes the chatbot, when the website is saved, and when the account is set up to reply. The chatbot can always be set up afterwards in Settings, the Chatbot tab, and on Overview there is the task "Put the chatbot on your website".

"Where do I choose my country?"

The country is chosen once, in the first step of the setup, before the payment: it decides which country's phone number the customer gets, and which language the AI assistant writes in. Once the customer has paid or is set up, the step is no longer shown, and a partner's customers never see it. If the country or the number has to be changed afterwards, it has to go in as a support case.

Limitations and errors

The guide cannot be taken by a team member: a plain team member who opens /onboarding is sent to Conversations. The agency's own version of the guide, where a card can be passed on to the customer, sits on the partner's own page and not here. There the connection steps look as before (the question with Yes and No), and the icon row does not exist.

The chapter band can only be used for the chapters you have reached. There is no skipping past a step that is missing, and the subscription step cannot be got around at all.

For a customer who pays directly, reading the website only starts once the payment has been registered. Right after paying this can take a few seconds (at most about two minutes), and meanwhile the line under the field says "We will read it as soon as your account is active". A partner's customers and the agency's version of the guide never wait.

The setup is being rebuilt as a chat: a sphere that asks one question at a time, types it out, shows the latest answers above the question and has a text field at the bottom. The chat view is hidden until the pilot: it is not switched on by default, and a customer sees the guide as described here unless the chat view has been switched on for the account. It uses the same steps, the same requirements and the same bottom bar with Back, Next, Skip and Finish setup later. A partner's customers and the agency's version of the guide never get it: they see the guide as described here. The text field cannot be used yet; answers are given with the step's own buttons and fields.

In the chat view the connection steps are also asked as a question. Below the question the connection's state is shown as a short answer with the same logo as in the row of icons: "Not connected yet", or for instance the Gmail logo and "Your email is connected". The button to connect, Skip, Disconnect and the dialog that confirms a disconnection are the same as in the guide. The payment is asked as the question "Choose how you want to pay." with the same plan, the same price and the same button to the payment page as in the guide. "Here's what we learned about <company>", the services and the form for another email provider sit on a panel below the question, with the same fields and requirements. The ready screen shows the same messages, and Go to dashboard still sits in the bottom bar and finishes the setup as before.

In the chat view the country and the goal move on by themselves when the customer taps an answer. The answer is saved first (for the goal also once the booking settings for the new goal are loaded), Next shows a small spinner meanwhile, and two quick taps only move one question. A new goal tapped while the setup is moving on with the first one is ignored. If saving fails, the customer stays on the question with the same error message as with Next. The industry, the length of the meeting and how far ahead bookings can be made are dropdown lists, and there the customer taps Next, as on questions with several fields (opening hours, services, addresses, the description, "Here's what we learned about <company>", area and fee). Back works as before, and if the customer picks a new country or goal, the setup moves on again. When there are more answers than there is room for, the list fades out at the bottom, and a small arrow scrolls down to the rest.

Above the text field in the chat view sits "Ask something". It opens the help: two suggested questions about the step the customer is on (for instance "Why should I connect my email?" or "Can I change it later?") and a field for a question of their own of up to 1000 characters. A suggestion answers at once with a fixed explanation. A question of their own is answered by an AI based on the step, and the answer appears as a message from the sphere. The help can only explain: it changes no answers, saves nothing and never moves the customer on, and what the customer writes in the help never becomes an answer to the step. A customer can ask 30 questions of their own a day, after which it says "You have asked a lot of questions today. Please try again tomorrow." If the help cannot answer, it says "Could not answer right now. Please try again shortly." The help closes when the customer moves on.

Once the customer has answered at least one question, "See the conversation" sits next to it. It shows every question the customer has answered in the setup, with the answers, including those there is no room for above the question. The conversation is remembered in the browser tab, also when the customer comes back from Google, Microsoft, Facebook or the payment page. It is deleted when the customer logs out or the tab is closed, and another user in the same tab never sees the previous user's conversation. Codes (passwords, the email code and the Apple code) never appear in the conversation: a step without a short answer shows as "Answered".

When the customer comes back from Google, Microsoft, Facebook, Instagram, the calendar or the payment page, the chat view lands on the same step as the guide, and the orb briefly says what happened: for example "Your email is connected.", "Thank you, your payment went through. Let's carry on with the setup." or, when the guide is opened to continue, "Welcome back. Let's pick up where you left off." If a connection did not work, the orb says for example "Facebook was not connected." with a short explanation (cancelled along the way, expired, a missing permission or an account already connected somewhere else) and a "Try again" button, which is the same button as in the card. The message disappears when the customer moves on. While the website is being read, the orb pulses faster with a short line below it, for example "Reading murermesterjeff.dk", and on "This is what we learned about <company>" the waiting time is shown there instead of the ring. If the reading fails, the orb says "We could not read your website.", and the rest is as in the guide: "Try again" and the fields the customer fills in.

In the chat view the optional connections are first asked as one question: "Where do your inquiries come from?". The customer picks among the sources the guide has for the customer (Facebook, Instagram, email, the website, Other systems and the chatbot on the website when the package includes Chatbot), and what the customer has already connected is picked in advance. The ones picked are then shown as their own steps, and the others are skipped, exactly as with Skip. The calendar is not a source of inquiries and still has its own step, and no required step can be left out. The answer is remembered in the browser tab for this setup and deleted on logout. The customer can always go Back or tap an icon in the row to connect a channel that was left out after all.

Next on the website step requires an approved address. There is no longer an opt-out, so a new customer without a website cannot complete the step, and so cannot finish the setup either. This also applies to customers who were in the middle of the setup on 7 October 2026 without having chosen "I don't have a website".

Three of the six goals, "Book appointment", "Buy on website" and "Qualification", are in testing and are only shown for the individual test customers they have been opened for, plus the platform's own admin accounts. So if a customer says they can only pick three goals, that is not a fault.

Steps that fall away for a goal do not exist: there is, for instance, no meeting duration for "Book appointment" (every service has its own), no address for phone and video meetings, and no booking steps for "Buy on website" and "Qualification".

A service without a length is not offered to leads, even though it is on the list.

The booking link ("Book meeting") and the number the lead should call ("Call you") are not asked for in the guide: those two goals are retired, and the fields are in Settings under "Goal and booking".

Error messages the partner may be asked about:

• "Please fill in all required fields": Next was pressed on a step that is not complete.
• "Enter your website and press Approve to finish the setup." "Go to dashboard" was pressed without an approved website. The customer is now on the website step.
• "Could not save", "Could not save your country. Please try again." and "Could not save. Please try again." (on the last step) The save failed. The step has to be tried again.
• "Google was not given permission to send email." A checkbox was removed on Google's consent page. Run the email step again and leave every checkbox ticked.
• "Could not connect Google", "Could not start Facebook login", "Could not start Google login", "Could not start Microsoft login" The consent did not get going. Try again, and watch out for whether the browser is blocking the window.
• "The webhook address cannot be fetched right now." or "The address cannot be fetched right now." The address can always be found again under Integrations or Settings.
• "We couldn't open the payment." The payment page did not start. Try again, and if it keeps happening, report it on.

The website is only read automatically for new customers. If the customer has already completed the setup, or the website has been read before, the guide never starts a new reading by itself, because it would replace your AI assistant's current knowledge. Only a press on Approve on the website step starts a new reading, and it always does, also with the same address, also for a customer who has completed the setup, and also in the agency's version of the guide. The new reading replaces the pages your AI assistant answers from, just like the weekly update does. If it finds no pages at all, the old ones stay. The customer's own details (name, industry, description, services, the owner's name, phone) are only replaced when the customer presses "Looks right", and only the fields the screen shows. The exception is customers with the weekly update: if it is running when Approve is pressed, it can write the description and the services from the new reading before that. If the start fails and the customer comes back another day, the guide does not start the reading by itself: the customer presses Approve again. The website can also be read again with Auto-fill under Settings, on the Your business page, where the suggestions are shown before they are used.

For a new customer who signed up themselves, the website is only read once the subscription is active. If the customer says no to all the integrations, they can therefore reach the screen "Here's what we learned about <company>" before the reading is done and see the waiting message for up to a couple of minutes.

Websites behind a login or a cookie wall cannot be read. The screen then shows the message that the fields have to be filled in by hand.

The suggestions from the website are always written in Danish, also for Swedish and Finnish customers. Phone and address are only filled in beforehand for Danish customers.

The Instagram step is only shown for the platform's own admin accounts until Instagram is opened for everyone.

The step "Chatbot" does not exist in the agency's version of the guide: it reads the chatbot's status with the customer's own login.

Connect Facebook, switching the Facebook page and Connect Instagram work on every package (26/10-2026), both in the customer's own guide and in the agency's version. The package only decides what the connection is used for, and the step's text says so:

• Without the Booking agent (for example with only Chatbot) the Facebook step asks "Do you advertise on Facebook?", and the connection gives the AI assistant insight into the active ads. With the Booking agent, enquiries from the ads come in, and the AI assistant answers them. The Disconnect box follows suit: without the Booking agent it says that the AI assistant no longer gets insight into the active ads.
• Without the Social media agent the Instagram step says that AI replies to messages need the Social media agent. The account is connected, but the AI does not reply.
• AI replies on Messenger are only switched on by themselves with the Social media agent.

If the message is We could not check your package right now. Try again in a moment. after the Instagram login, the package could not be looked up, and nothing has been connected. Try again in a moment.

The guide only shows the steps that are relevant for the package. The package only hides what belongs to the Booking agent (email and SMS). Without it, for example with only Chatbot, the phone number, the website form and "Other systems" are not shown, both in the customer's own guide and in the agency's version. The goal, the calendar and the booking steps are shown for every package, because the chatbot books by itself. While the package is being looked up, the skeleton is shown, so the steps do not flicker in and out. If the package could not be looked up, all steps are shown as before. Under Settings, Integrations the customer can still connect the website form and "Other systems" on every package.