Help visitors work out whether your product fits.
A visitor can ask how a feature works or which published plan includes it. Write the information you want the agent to use as sales knowledge, then review and approve it. The conversation gives buyers another way to explore details while they are on your site.
Keep your sales answers separate from support.
The sales channel has its own approved sources. It does not automatically see support FAQs or imported GitHub documents. You can set a different voice, greeting, instructions and human contact number for each channel.
Choose where the sales widget appears.
Configure the marketing website origins allowed to use the agent, then install the generated sales embed. You can customise its button label and test the conversation before enabling customer access.
Review product and pricing changes before they go live.
Manual sales notes keep the starting scope clear. Update and approve the material when your offer changes. Website URL imports are disabled in the current pilot, so publishing a page does not automatically change the agent’s answers.
Common questions
Does the sales agent make outbound prospecting calls?
No. The sales widget starts a browser conversation when a website visitor chooses to use it. The separate founder phone test is for testing a configured agent with a fixed recipient.
Does the agent book meetings or update my CRM?
The pilot supports product conversations and approved knowledge. Calendar booking and CRM connections are not part of the current integration set.