โ† Back to system overview
Live ยท public

callconnor.com

The public front door: an "Ask Connor" chatbot that talks to visitors, researches their company in real time, scores the conversation, and turns it into a qualified lead.

0
Claude models orchestrated
0
Lead signals scored
0
Downstream destinations
0
API keys in the browser
What happens in a conversation
Visitor in, qualified lead out

Every chat runs through a single Netlify serverless function that quietly does four jobs while it talks.

๐Ÿ’ฌ Visitor chatscallconnor.com
asks name + company up front natural conversation (Sonnet)
โ†“
๐Ÿ”Ž Live company researchon name capture
Sonnet + web_search injected into the system prompt every later reply is company-aware
โ†“
๐Ÿ“Š Sentiment scoringevery few exchanges
Haiku JSON classifier sentiment ยท interest ยท topics ยท fit ยท priority
โ†“
๐Ÿ—ƒ Logged to Airtableone row per lead
name ยท company ยท first question full conversation + scores
Where leads go
From a chat to your morning

A captured lead doesn't sit in a table; it surfaces where you'll actually see it.

๐Ÿ—ƒ Airtable

The system of record: structured fields, full transcripts, sentiment scores.

store

๐ŸŒ… Morning briefing

New leads show up in your daily briefing automatically.

daily

๐Ÿ” Weekly review

The week's pipeline rolls into the weekly review.

weekly

๐ŸŽ› Command Center

A dashboard panel shows leads and lets you edit the bot's prompt and redeploy.

live

๐Ÿง  Right model per job

Sonnet for conversation + research, Haiku for the cheap sentiment classifier.

3 models

โœ‚๏ธ Cost control

History capped at 10 turns per request, plus a hard spend cap in the console.

capped
Built right
A real deployment, not a toy

Key stays server-side

The Anthropic key lives only in the Netlify function, never shipped to the browser. All calls route through the serverless backend.

Auto-deploy from git

Source is a private GitHub repo; Netlify rebuilds on every push to main.

Edit the bot from the dashboard

The Command Center can rewrite the chatbot's system prompt and push a redeploy. No code editor needed.

Spend is bounded

Turn-history truncation plus a console spend cap keep a public, always-on bot from running away on cost.