AgeBridge Guided Project Reference build by AgeBridge
Website Assistant That Captures Leads
An assistant on the site that answers from the company's own pages with links to them, says plainly when something is not covered, and asks for an email once a visitor shows real intent.
AgeBridge built this as a worked example of the solution. No client results are claimed. Build your own version and it becomes proof on your profile.
Build this yourselfBusiness problem
A company website answers most questions somewhere, but visitors do not find them. The few visitors with real intent read a page, leave, and the company never learns who they were.
Solution
An assistant on the site that answers from the company's own pages with links to them, says plainly when something is not covered, and asks for an email once a visitor shows real intent.
What was built
- •Weekly crawl of the site into chunks that carry their page title and URL
- •Retrieval with a similarity threshold, below which the model is never called
- •Answers limited to the retrieved excerpts, with the source pages listed
- •Lead capture triggered by a buying signal, not by a timer
- •Server-side endpoint with rate limits and a monthly spend cap
Architecture / workflow
- 1Crawler turns the site into clean markdown and splits it on headings
- 2Chunks are embedded and stored with their page title and URL
- 3A question is embedded and matched against the store
- 4Below the threshold the assistant refuses and offers a human
- 5A buying signal triggers one email request, and the lead is stored with the conversation
Integrations
SlackSupabase
Tools / stack
OpenAIpgvectorn8n
Screenshots
Screenshot slot
Screenshot slot
Demo
No demo added yet. Builders can attach a short video.
Results
No verified results shared. AgeBridge only displays real, builder-reported outcomes.
Evidence
- Architecture notes · Retrieval design and the refusal ruleHow data flows and why you designed it that way.
Proof
Proof score
10/100Add demo video — 60 seconds showing the thing actually running. The single strongest proof.
Not reviewed yet. Evidence is shown exactly as the builder attached it.
Decisions and tradeoffs
- •A refusal is cheaper than a wrong answer, so the threshold is deliberately strict.
- •Prices and timelines are only ever repeated from the site, never generated.
- •The email is asked for after the visitor gets value, never before.
What went wrong
Nothing notable was reported.
What I'd do next
Answering in the visitor's language from a Hebrew version of the site.
Need something like this?
Talk to the builder behind the project, or build your own version.