How to Use Chipp to Build a Lead-Capture Website Agent

The short answer: if someone on your team spends the week answering the same pre-sales questions, a Chipp agent on your website can take that queue on the one plan Chipp sells, $299 a month with $100 of AI usage included (pricing page, checked on 24 October 2026): load your FAQ, pricing and service pages as knowledge, write short instructions, turn on sign-up with two or three extra fields, connect HubSpot, paste the widget script into your site, and read the first week of chats before you change anything.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job is narrow on purpose: one agent, one website, and one question at the end of the month, whether a visitor who asks about price now leaves a name and a company behind. For what the platform is and costs, see the Chipp glossary entry.

Before you build, three numbers:

1. What it costs to find out. At $299 a month the test costs $3,588 over a year, before any setup help (pricing page, checked on 24 October 2026). Chipp's usage guide estimates a support bot on Gemini 2.5 Flash at about $2.50 for 10,000 messages (Pricing & Usage), so for a question-answering agent the plan fee is the number to justify, not the model bill.
2. What you already have. The answers exist somewhere: the FAQ, the pricing page, a sales deck, the email a rep sends after a first call. Those become the knowledge sources, and an answer that is not written down cannot be retrieved, as Chipp's knowledge guide says.
3. What counts as working. Write down how many contact-form leads arrive in a normal week now. After launch, count widget sign-ups that carry a company name, and set one against the other.

What you need first

• The plan, or a free first look: Chipp's homepage offers a 20-minute build session in which its team builds a first tool with you on your data.
• Admin access to HubSpot if contacts should land in the CRM; the HubSpot integration page requires it.
• Access to your site's template, to paste one script tag before the closing body tag.
• A privacy notice that covers chat sign-ups. The European Commission's summary of the GDPR principles allows collection only for a purpose stated when the data is obtained, and only what that purpose needs.

Step 1: Start from a template or a blank app

A template is a full agent blueprint with a system prompt, a model and suggested messages, per Chipp's skills and templates page; skills are smaller prompt pieces stacked on an existing app. Add the Anti-Hallucination skill that page lists, so the agent admits a gap instead of inventing a price.

Step 2: Pick a model that fits short questions

Pre-sales questions are short and factual. The usage guide points quick Q&A and FAQ work at Gemini 2.5 Flash or GPT-5 Nano and keeps heavier reasoning models for complex analysis. You can switch models later in the Build settings.

Step 3: Load the knowledge sources

Upload the pages and files from your list. The knowledge guide accepts PDFs, Word files, spreadsheets, URLs, YouTube links and audio, and gives the agent a search tool it calls when a question needs your content. Each search blends meaning with keywords, weighted 70% to 30% by default, so plan names still match exactly. Add the pricing page as a URL and refresh it whenever prices move.

Step 4: Write instructions the agent can follow

Three short paragraphs do it: who the agent speaks for, what it answers from the knowledge sources, and what it does when the answer is missing (say so, and offer the sign-up). Then test it in the chat preview with the ten questions your team hears most, plus two it ought to decline.

Step 5: Turn on sign-up and add Signup Fields

Open Launch > Access and choose Required Sign-up or Encouraged Sign-up; Chipp's lead form guide hides Signup Fields under Open Access, because there is no form to attach them to. Switch on the Signup Fields card and add Company and Role from the presets. The form already asks for an email address. A form can hold up to 20 fields, and the guide advises keeping it short; data minimisation under the GDPR says the same: ask for what sales will use.

Step 6: Connect HubSpot, with a person checking its writes

In the builder, go to Brain > Integrations, choose HubSpot and click Connect HubSpot, as the HubSpot integration page describes. The agent gets nineteen tools, among them one that finds a contact by email or creates it when missing, so repeat visitors do not become duplicates.

Here the agent acts on your systems, and the same page warns that it will be able to create and modify CRM records. So put a person beside it. For the first two weeks, instruct the agent to create contacts and add notes, never deals, and have one person compare each new contact with its transcript every morning before sales picks it up. When a fortnight matches, widen the instructions.

Step 7: Embed the widget and say what it is

Open Launch > Share, copy the snippet from the Chat Widget card and paste it before the closing body tag of your site, per the embed guide. Use the greeting attribute to say what the visitor is talking to. Article 50 of the EU AI Act asks that people are told they are interacting with an AI system, at the latest at the first interaction, unless that is obvious (AI Act Service Desk). A greeting such as "AI assistant: ask about plans, pricing or setup" covers it in seven words.

Step 8: Read the chats before the copilot edits anything

After a week, open Insights. The Overview tab counts sessions, unique users and messages, and the Conversations tab filters chats by source, Widget among them, per the analytics guide. Read twenty transcripts yourself. Then ask the Alchemist copilot to analyze your conversations; the copilot guide says it reports knowledge gaps and frustration patterns and can apply its own fixes. Let it propose, and approve one change at a time, so you know which edit moved the number. Then export the sign-ups from Insights > Consumers as a CSV and set them against your baseline.

A word on the free session

The build session is a fair offer and also the first step of a sale, designed to end with a plan chosen while your data is already on the platform. Bring a test document and your ten questions, and decide after you have read real transcripts.

What Chipp's docs warn about

• Signup Fields that never appear. The lead form guide lists the causes: Open Access mode, the switch left off, no field added, or SSO-only login, which rules Signup Fields out.
• Appearance changes that never reach the site. Theme, colour, icon, z-index and language are written into the embed code, so after changing them you copy the snippet again; position, greeting and auto-open update live.
• An agent that goes quiet. The usage guide says that when credits run out the app's AI pauses until more are bought, with warnings sent as the balance falls.
• Answers that sound sure and are wrong. The knowledge guide's tip: unclear documents produce unclear answers.

FAQ

Can the same agent answer on WhatsApp too?

Yes. The AI App Builder docs list WhatsApp, Slack, email and phone integrations next to the widget. Add one channel at a time, and read its first conversations before trusting it.

Does the HubSpot connection cost extra?

There is no separate fee. The HubSpot page says its tool calls are billed as standard model token usage, which draws on the $100 of AI usage each plan includes (pricing page, checked on 24 October 2026).

Should sign-up be required or encouraged?

Both modes support Signup Fields, per the lead form guide. Required Sign-up puts the form in front of every chat; Encouraged Sign-up shows it without forcing it. Run each for a week and keep the one that brings more contacts sales accepts.