An AI Receptionist for Your Website’s Front Desk

What a receptionist does that a contact page can’t

A good receptionist rarely solves the problem a visitor walks in with. What they do is quicker and just as valuable: they find out who you are, work out who can help, and make sure that person hears about you with enough detail to act. A website AI receptionist does that same job inside the chat window of your site.

Consider a property management company with three very different audiences landing on the same homepage. Current tenants want to report a broken dishwasher or ask about a late fee. Property owners want to know when their monthly statement posts or who is handling a vacancy. Prospective renters want to know whether a unit is still available and how to apply. A single contact form funnels all three into one inbox, and somebody spends the first hour of every Monday sorting it. A receptionist sorts at the moment the visitor arrives, so the maintenance request reaches the maintenance coordinator and the owner question reaches the owner-relations manager without anyone forwarding anything.

Four jobs make up the role, and we design each one separately: greet the visitor in a way that fits the page they are on, identify what kind of visitor they are and what they need, route them to the right person, queue or calendar, and record a message complete enough that nobody has to call back just to ask what the problem was.

One clarification up front. This page covers the receptionist that lives on your website and works in text. An AI phone answering line is a separate build with its own constraints, such as speech recognition and call transfer. The routing map, message format and boundaries described below can be shared by both if you add a phone line later, which is one reason we write them as plain documents instead of burying them in a chatbot settings screen.

Draw the routing map before anyone writes a prompt

The first working session on a receptionist project has nothing to do with AI. We sit down with you, usually on a video call, and fill in a routing map: every kind of visitor who shows up, what they typically want, where that request should land, and what the person on the receiving end needs to know. For the property management example, part of that map looks like this.

The last row matters as much as the first. Some visitors should simply be pointed to a page, and a receptionist that takes a message from everyone floods your staff with requests they never needed to see.

A frequent mistake is routing by internal department names. Visitors do not know you have an “owner services” team; they know their rent statement looks wrong. So the map is written in the visitor’s language on the left and your org chart on the right, and the receptionist’s real work is translating one into the other. When a request fits none of the rows, it goes to a single catch-all destination you choose, never into silence.

The first exchange: a greeting that fits the page, then one good question

Receptionists that open with a paragraph of menu options get ignored. Ours open with a short greeting and a single question, and both change depending on where the visitor is. On a property listing page the greeting might offer to check whether that unit is still available. On the tenant portal login page it asks whether the visitor needs to report a repair. On the careers page it points to open roles. The receptionist knows which page it was opened on and picks from greetings you have approved.

Identification comes next, and it is lighter than it sounds. The receptionist asks whether the visitor is an existing customer, and if so, it collects the reference your team actually uses to look people up: an invoice number, a property address, a client name as it appears on the account. It does not verify identity and it does not reveal anything about the account. That line is deliberate. Reading account records safely requires login integration and identity checks, which belongs to a website virtual assistant built to complete tasks. A receptionist earns its keep by getting the request to the right desk with the right reference attached.

Visitors are told plainly that they are chatting with an AI assistant, and the receptionist offers a person whenever one is available. Giving it a fake human name erodes trust the moment a visitor figures it out, and in some settings it creates legal exposure you do not need.

A message your staff can act on without calling back first

The classic pink phone slip said “Call Mrs. Ortiz back.” It told you who and nothing else, so every callback began with “What was this about?” The most practical improvement a website receptionist makes is replacing that slip with a structured message. Each one we set up contains:

• The visitor’s name and preferred contact method, with the time of day they said works.
• Whether they are new or existing, plus whatever reference they gave.
• The request in their own words, unedited.
• A one-line summary written by the receptionist and labeled as a summary.
• The urgency level the conversation matched, and the reason.
• Exactly what the visitor was told would happen next.

That final field prevents a surprisingly common failure: the receptionist tells a visitor “someone will call you this afternoon” while the staff member receiving the message has no idea that promise was made. When the expectation is written into the message, your team can keep it or correct it.

Here is how that plays out for an accounting practice in tax season. A returning client writes that they received a letter from the state and want to know whether their extension went through. The receptionist does not answer, since it cannot see filing records and a wrong answer could cost the client money. It records the client name, notes that a state notice is involved, suggests uploading the letter through the practice’s secure portal, and routes the message to the preparer assigned to that client. The visitor hears that a preparer will review it and reply by their preferred method, and the message records that exact wording.

Messages are delivered wherever your team already works: a shared inbox, a help desk ticket, a CRM activity, or a text alert for urgent items. We avoid creating yet another dashboard your staff has to remember to open.

Live transfer, callbacks and the hours in between

A receptionist is only as good as its knowledge of who is actually available. We give it your business hours per location, your holiday schedule and, if you staff live chat, a signal showing whether anyone is signed in to take conversations.

During staffed hours it can offer to connect the visitor with a person. The transfer passes the whole conversation along, so your staff member starts informed instead of asking the visitor to repeat everything. If nobody accepts within a window you set, the receptionist says so honestly and switches to taking a message. It never leaves a visitor staring at “connecting you…” indefinitely.

Outside staffed hours, it takes the message and states when your office reopens. If you want callbacks, it can offer open slots from a calendar you designate, so the visitor chooses a time rather than being told someone will reach out eventually. For overnight coverage with more depth, such as answering common questions while the office is dark, see our page on an after-hours support chatbot.

Multi-location businesses add one routing question. For an auto repair business with two shops, the receptionist asks which shop the visitor uses or which is closer, then routes to that shop’s service writer and quotes that shop’s hours. Location is asked early and confirmed in the message rather than guessed from an IP address, because sending a customer to the wrong shop is worse than asking one extra question.

Urgent situations travel on their own track

Every business has a short list of situations that cannot wait for Monday’s inbox. For property management it is water actively leaking, no heat in freezing weather, a lockout, or a smell of gas. We write that list with you, then test the receptionist against the many ways people actually describe those situations: “water coming through the ceiling,” “my bathroom is flooding,” “the unit above is leaking into mine.”

When a conversation matches, three things happen. The visitor gets immediate safety instructions you have approved; for a gas smell that means getting out first and phoning 911 or the gas company from outside, not troubleshooting in a chat window. Your on-call person is alerted by text or phone through the channel you pick. And the message is marked urgent with the matching reason, so whoever handles it can see why it jumped the queue.

Tuning this involves a genuine trade-off. Set it loose and a real emergency sits unread until morning. Set it tight and your on-call manager gets woken for a dripping faucet. For anything touching safety we deliberately lean toward over-alerting, log every false alarm, and refine the wording of the urgent list after reviewing those alarms with you. A miss nobody sees is worse than a false alarm everybody sees.

What a website receptionist is not allowed to do

Receptionists get into trouble when they try to help beyond their role. We write explicit boundaries into every build, and each one comes with a scripted alternative so the visitor still ends up somewhere useful:

• No prices it wasn’t given. If you publish a rate, it can repeat it; otherwise it explains who can quote and routes the request.
• No promised appointment times unless it booked the slot through a real calendar and got confirmation back.
• No professional opinions. Tax, legal, medical and safety judgments go to qualified people, even when the visitor insists.
• No account confirmations. It won’t say whether a payment posted or a filing went through.
• No sensitive numbers in chat. Card numbers, Social Security numbers and passwords are declined, with a pointer to your secure channel. If a visitor types one anyway, it is masked in the stored transcript.
• No arguing. An angry visitor gets acknowledgement and a fast route to a person, not a debate.

We also test against visitors trying to push the receptionist off its script, whether by telling it to ignore its instructions, asking it to write something unrelated, or coaxing it into commitments on your behalf. Its scope is limited to your business topics, and anything outside that scope gets a polite redirect.

Reading the front-desk log

A receptionist improves through review, not by quietly learning on its own. In the early weeks we go through conversations with you on a weekly rhythm, later monthly, looking at a handful of specific things:

• Routing accuracy. Staff can flag a message as misrouted with one click, and we sample conversations to catch the ones nobody flagged.
• Message completeness. How often did the recipient still have to contact the visitor just to get basic information? Each case points to a question the receptionist should have asked.
• Response time by route. The receptionist may be instant while the human follow-up takes two days; this shows where the real delay sits.
• Urgent alerts and false alarms, reviewed together so the list gets sharper.
• Questions with no good answer. These often reveal a missing page on your website, such as a pet policy that lives only inside a PDF lease.

Logs keep the text of each exchange and every routing decision, with sensitive fields masked, and you decide how long they are retained.

How EVOTECH puts a receptionist on your website

We are EVOTECH IT LLC, a web, software and AI shop based near Houston, and receptionist projects are delivered remotely to businesses anywhere in the United States. A build usually moves through these steps:

1. Free consultation by phone or video, where we look at your site, your current contact paths and where requests get lost today.
2. Routing map and boundaries drafted with you in plain language your staff can review.
3. Greetings, questions and the urgent list written and approved page by page.
4. Connections to the places messages should land: your inbox, help desk, CRM, calendar or on-call alerts.
5. Staging tests with realistic visitor messages, including messy, misspelled and deliberately tricky ones.
6. Launch on selected pages, then expansion once routing proves reliable.
7. Scheduled reviews of logs and flags, with adjustments to the map.

Generic chat plugins can greet visitors, but they tend to route on keywords and send every message to one email address. A custom receptionist carries your routing map, your urgent list and your boundaries, and delivers into the systems your team already uses. You receive a fixed-scope written quote before any work begins. The company has more than 20 years in business behind it and a 5.0 rating on Google; to talk it through, call (832) 359-2425 or read about our broader AI agent development work.

Related services

Frequently asked questions