After-hours site visitors ask the same five questions and then leave. Owners buy a chatbot. The bot talks. Nothing lands in the CRM. That is not a concierge. It is another inbox you do not watch.
MajotoAI already runs Nora on this site as our own concierge. The point of this note is when that pattern is the right first project for a small business, and when it is not. See also the pillar on leads vs chatbots.
What a concierge actually does
It answers FAQs you already know (hours, service area, what to bring, how booking works). It captures name, intent, and a callback window. It creates or updates one CRM record. It offers a calendar slot or a human route. It stops when someone on your team replies.
Done state in one sentence: after-hours site questions get a useful answer, one record, and a next step, without a bot that keeps pitching.
What not to buy first
- A widget whose only job is to chat. If it cannot write to your system of record, it is decoration.
- A bot that quotes prices. That creates disputes and compliance risk.
- A concierge before missed calls are covered. If the phone is the leak, start with text-back.
Rules that keep it honest
- Publish the questions it is allowed to answer. Everything else goes to a human.
- No licensed advice, diagnoses, or guaranteed outcomes.
- Honor STOP and do not add people to a blast list from a chat.
- One record. No "new lead" for every page refresh.
How to know this is the first project
Look at after-hours form fills and chat attempts for two weeks. If volume is tiny and the phone is on fire, do not start here. If people already use the site at 9pm and you answer next day, this can pay.
Widget vs owned concierge
| Question | Chatbot widget | Owned concierge |
|---|---|---|
| Writes to your CRM once? | Often no | Required |
| Can book or route a human? | Rarely | Required |
| Stops when you reply? | Often no | Required |
| You can change allowed topics next week? | Vendor UI | Your runbook |
For a longer menu see 10 automations. Pricing is on offers.
What MajotoAI will and will not do
Will: map whether the site is the leak, bound the topics, ship a concierge into tools you own, leave a runbook.
Will not: bolt a toy widget on a brochure page and call it done, or invent client results.
FAQ
Is a website concierge the same as a chatbot widget?
No. A widget that chats and forgets is a toy. A concierge writes to your CRM, can book or route, and stops when a human replies.
Should this be the first project?
Only if missed calls and form follow-up are already handled, or if most demand already arrives on the site after hours. Otherwise start with text-back or CRM hygiene.
Can it quote prices or give licensed advice?
No. Keep the first replies to hours, service area, what happens next, and a human handoff. Do not automate promises you cannot keep.
Ready to map the real bottleneck?
Book a free Architecture Review. Bring one messy workflow. We will tell you if it is the first project or not.
Book a Free Architecture Review