From your website to your first conversation.

You have already done much of the writing an assistant needs. Your website explains the product, describes who it is for, and shows how you want the business to look. Start onboarding with that URL.

Darwin finds relevant pages and uses them to prepare the knowledge base and business details. It also looks for the colors, fonts, and assets that can shape the chat widget. You get a draft to review instead of a collection of empty fields.

Think of this as a head start. You still know things about the business that a website cannot tell an assistant, especially when a page is missing or out of date.

Open Settings → Knowledge. Are the pages you would send a prospect actually there? Check pricing, your main products, and any integration or service details that come up in sales conversations.

The initial setup selects key pages so you can get started quickly. It does not import an entire large website in that first pass. You can bring in more pages afterward.

A failed import needs attention. Retry the source or add the missing information another way, then ask a question that depends on it. A page appearing in a list is not enough; you want to know the assistant has the answer.

A color that works for a large website heading may be hard to read inside a small chat bubble. Look at the imported design in context: the text, the input field, the avatar, and the widget itself.

Brand detection gives you a starting point. Fonts and assets are not equally accessible on every site, so a few adjustments in appearance settings may be needed. Try a narrow phone screen as well as your desktop.

You do not need to redesign the whole thing. If the chat looks like part of your site and the messages are easy to read, you are close.

Open Test chat and ask a buying question in your own words. Follow up. See whether the answer holds up when you add a detail or ask something outside the knowledge base.

Then ask to speak with sales. Check that the booking path uses the right provider and takes the visitor toward the calendar you intended. Preparing an assistant and connecting a working scheduler are separate parts of setup.

Test-chat activity stays out of Darwin’s live analytics and billing. Use it to work through the rough edges. After you install the embed, visit the actual website as well: that is where you can check the site key, placement, and behavior visitors will see.

In the first few days, read some conversations instead of only checking the totals. A question the assistant could not answer gives you a specific piece of knowledge to add. A confusing reply may lead you back to a page that needs a clearer explanation.

Pay attention to scheduling, too. If people open the form but never finish, try that path yourself before assuming they lost interest.

Once the setup works, you can enable opening experiments on eligible pages. Darwin handles the repeated work of trying new invitations to chat. Your team keeps the underlying business information accurate and takes the meetings that come through.