Questions people ask about an AI receptionist for their website

Agent Front Desk is new, and we are setting it up for a limited number of businesses, by hand. You get hands-on help and a say in what we improve. You should expect some rough edges.

Each implementation is quoted per business after a short call, and you get the quote in writing before anything is built. There is no price list during the beta. AI, voice and email usage is paid to those vendors at cost, on your own accounts. Updates and support are by arrangement.

We read your request and reply by email. If it looks like a fit, we book a short call about your site, your CRM and your questions, then send a scope and a quote. If you go ahead, we set it up together.

About a day of hands-on setup, usually one to two weeks from kickoff because accounts and content take time. We confirm a timeline in your quote.

No. It is a set of WordPress plugins that runs inside your own WordPress, with your database and your API keys. There is no hosted service and nothing is routed through us.

The main product is a suite of WordPress plugins. For sites that are not on WordPress, we offer a custom option: the same assistant as a separate app that we deploy in your own cloud account.

Yes. Install and activate the plugins, add your keys, and the chat launcher appears on the site. It reads your published pages and posts, so it can answer from what is already there.

You do, directly to the vendors, at their list prices, on your own accounts. We add no markup per seat or per conversation. See the pricing page for the real figures.

HubSpot is built in. Other CRMs are connected during the implementation, as a small plugin built on our documented connector interface. We tell you what that takes before you commit.

Yes. The HubSpot add-on creates or updates contacts by email, adds notes and meetings to the timeline, and, when the scopes allow, finds or creates the company, opens a deal in the pipeline you choose and assigns an owner. A step that lacks a scope is skipped and logged with the exact scope to add.

It is built to answer from your knowledge base and to say so when it cannot. The test playground and the gaps list show where it is weak, so you can fix content before and after launch. No AI is perfect, so review early conversations.

This one proposes times from your booking rules, and nothing is booked until the visitor presses Confirm in chat or says yes on a voice call. Connecting a real calendar needs a calendar connector, which we build for you.

In Agent Front Desk a visitor can ask for a person. Staff get a notification and a waiting chat in Live chats, take over, and the visitor sees that a person has joined. Handover uses short polling, about every 2.5 seconds, and covers chat.

Not yet in the WordPress suite. Today it handles chat, browser voice and a callback request form that creates a lead and notifies staff. Live phone calls are planned, and the custom engine already has a phone path that needs your own Twilio number.

Yes. The MCP add-on is a remote MCP server with OAuth 2.1, so it works as a custom connector in ChatGPT and claude.ai, and with a token in Claude Code. We test the connector with you at install, since those apps’ screens change.

MCP is a standard way for AI apps to use tools. The MCP add-on lets you add your front desk as a connector in ChatGPT or claude.ai, or use it from Claude Code, and ask about your leads and conversations. You choose read-only or read and write.

Yes. The code is GPL and runs in your WordPress, with your database and your own accounts at the AI and voice vendors. You pay those vendors at cost and nothing per minute or per conversation to us.

Conversations, leads, bookings and knowledge live in your WordPress database. The assistant calls the AI vendor you choose, and optional voice, embeddings and HubSpot services, using your own keys. Nothing is stored by us.

This one. It collects what you need to qualify the lead, proposes a time, and shows a confirmation card. The booking is only created when the visitor confirms.

Yes. Custom connectors, such as a CRM, a calendar or an internal system, are built as a small site plugin on our documented extension API. Because they live in your plugin and not ours, updates never break them.

The plugins are GPL and every feature works without a license, forever. An optional license key adds automatic updates and support, delivered to your site like any plugin update. Without one, you update by uploading a new zip. Terms are by arrangement during the beta.

Deactivate the plugins and your site is untouched. Uninstalling removes the plugins’ tables, options and staff role. You keep your pages, your keys and your accounts.

A virtual receptionist is a person, usually at an outside company, who answers for you. An AI receptionist is software. Agent Front Desk is software on your own site that can hand a visitor to your own staff when a person is needed.

The terms overlap and are not standardised. We use “AI receptionist” for the assistant that greets and answers visitors, and “front desk” for the wider job: capturing leads, booking, handing over and syncing to your CRM. Agent Front Desk does both, on your own WordPress site.

Yes. The chat opens with a plain notice, and you set the wording. Voice adds a recording notice that visitors accept before the microphone starts.

We build to WCAG 2.2 AA. Automated axe checks pass on the admin screens in light and dark and on the widget. Automated tests alone are not proof, so a keyboard and screen reader pass is part of acceptance.