AgeBridge
AgeBridge Guided Project · IntermediateAbout 8 hoursPro

Website lead assistant (chat widget)

A chat widget takes a name and an email, asks three qualifying questions, scores the visitor, replies in their own words and puts the lead in the CRM with the reasoning attached.

What you'll have at the end

A published chat widget you can drop into any page with one iframe line, a Make scenario that scores every conversation with Claude and answers the visitor within seconds, and a HubSpot contact with a note per conversation and a task when someone asks for a person.

What it proves

embeddable UIqualificationCRM write

Accounts to create

LovableWeb apps from a description, with Supabase built inDocsFree offerMakeVisual scenarios, free plan with 1,000 operations a monthDocsFree offerClaude APIThe model behind the steps; pay per useDocsFree offerHubSpot CRMFree CRM with a generous APIDocsFree offer

What it costs: Free: Lovable's free messages, the Make free plan, a free HubSpot CRM, plus a few cents of model usage.

Have this ready

  • A made-up company the widget answers for, in one line
  • A free HubSpot CRM with no real customers in it
  • A booking link of your own that the widget can offer

How it fits together

Widget on the pagename, email, three qualifying questionsMake custom webhookone run per conversationClaudescore, reason and the replyWebhook responsethe reply and the booking linkHubSpot contactcreated or updated on the emailNote on the contactthe answers, the score, the reasonTaskonly when someone asks for a person
  1. Widget on the page: name, email, three qualifying questions
  2. Make custom webhook: one run per conversation
  3. Claude: score, reason and the reply
  4. Webhook response: the reply and the booking link
  5. HubSpot contact: created or updated on the email
  6. Note on the contact: the answers, the score, the reason
  7. Task: only when someone asks for a person

The steps

  1. 1. The endpoint the widget will talk to

    A Make webhook that already knows the six fields a conversation sends, and already answers with JSON a browser is allowed to read. Building this first means the widget works the moment it exists.

  2. 2. Lovable builds the widget

    A published chat that takes a name and an email, asks the three qualifying questions, sends them to your webhook and shows whatever comes back. It is a visitor's whole view of this build.

  3. 3. Claude scores the visitor and writes the reply

    The fixed sentence becomes a real answer: a score, a reason a person can argue with, and two or three sentences back to the visitor that never invent a price.

  4. 4. The lead lands in HubSpot

    Every conversation becomes a contact with the reasoning attached, and only a visitor who asked for a person creates a task. The CRM is where a business will look, not Make.

  5. 5. The widget on a real page

    One line of HTML that puts the widget in the corner of any site, and proof that it behaves on a phone. This is what you hand a client, and it is the part they will judge.

  6. 6. Five visitors, five outcomes

    The scenario runs without you pressing anything, and you have five conversations in the CRM that show the score doing real work rather than being decoration.