Your site is a brochure. Visitors still need a first conversation.

Service businesses already get traffic.

The site explains the practice. It does not start the conversation. A visitor lands after hours, or while the owner is mid-client, reads a few paragraphs, maybe opens a form — and leaves. Interest cools. The owner finds out later, if at all, with almost no context.

If you build for yourself or for small clients, you’ve seen this pattern a hundred times. The owner is the product. Their calendar is full of real work. The website is still a brochure with a contact form taped on the end.

We built Lobby for that gap.

Lobby is an AI site concierge — not another chatbot.

A chatbot usually answers FAQs or deflects support tickets. A site concierge greets the visitor, guides them toward what actually fits (inside boundaries the owner sets), and emails the owner a lead with context: who they are, what they wanted, and a suggested reply.

Same chat bubble on the surface. Different job.

What it does

Three beats:

1. Greets — every visitor is welcomed and asked what they came for.
2. Guides — answers and services that fit that person, inside sanctioned claims. If it doesn’t know, it says so and hands over contact details instead of inventing.
3. Hands you the lead — details, intent, suggested reply — by email.

You can run it two ways (or both):

• Embed on the site you already have — one script; DNS and rankings stay put.
• Hosted page at lobby.host/c/… if you don’t want to touch the site yet.

WhatsApp is in the mix for how owners already talk to clients; the core path is still greet → guide → lead on the web, with the handoff by email.

Boundaries matter

Owners list what the concierge must never claim. Replies are checked against that list. Fit guidance happens inside those boundaries — not open-ended improvisation about the business.

That’s the difference we care about when someone says “isn’t this just ChatGPT in a widget?”

Second story: agents

Lead capture is the job. Agent readability is the second beat — and it’s early.

The same concierge can publish a plain-text summary (llms.txt) and expose structured tools via WebMCP so an assistant visiting the page can ask without guessing from a brochure. WebMCP is evolving; we don’t overclaim here. If you care about agent discovery, we wrote it up: agent discovery guide.

See it, don’t take our word

Talk to live concierges from the homepage — real businesses, not a canned demo of ours. Open one and decide for yourself.

If you’re sorting “concierge vs chatbot,” this compare page is the short version: AI site concierge vs chatbot.

Building for consultants or local services? ICP pages: for consultants · for local services.

Ask

I’m posting this for feedback from builders who ship for service clients — or who are the service client.

Try the free tier, kick the tires on real traffic, and tell me what’s missing. If you get stuck after you’ve tried it, ask in the comments and I’ll help personally.

---

Links

• Homepage / try free: https://lobby.host/
• Concierge vs chatbot: https://lobby.host/compare/ai-site-concierge-vs-chatbot
• llms.txt guide: https://lobby.host/guides/llms-txt
• Agent discovery: https://lobby.host/guides/agent-discovery
• For consultants: https://lobby.host/for/consultants
• For local services: https://lobby.host/for/local-services

CTA

Try free on https://lobby.host/ — 20 conversations a month, no card. Comment with your niche if you’d install this for clients (or for yourself).