On a Pepper site, a visitor's own AI assistant can do what the visitor could do by hand, under the same rules. It can find a free table, ask for a quote or book an appointment. Nobody at your business needs to answer it, and the visitor does not need to fill in the form themselves.
This page is for business owners who use Pepper widgets or a Pepper website. It explains what a visitor's AI client can do, where it stops and what Pepper keeps. Pepper calls the entry point the visitor door.
An example
A visitor tells their assistant: "Book a table for four at Harbour Salt on Friday at 19:30." The assistant reads the restaurant's booking widget and checks the free times. It sends the booking with the visitor's name, email and acceptance of the booking policy. The restaurant sees an ordinary booking with the channel Visitor agent.
The booking passes the same capacity, service-hour and policy checks as the booking form. If Friday at 19:30 is full, the assistant gets the same refusal a person gets.
What the visitor's AI can do
- Read your published menus, price lists, listings, opening hours and website pages.
- Calculate an estimate, check whether you serve a postal code and read free booking times.
- Ask for a quote, send a form or a listing enquiry, and answer a survey.
- Book a time with the same details and policy acceptance as the form.
- Claim an offer or join a stamp card, after the visitor passes on the email code Pepper sends.
- Prepare a shop cart and give the visitor a link to it.
- Find out where one of your printed QR codes leads.
What stays with the visitor
- Ordering and paying. The assistant cannot place an order or pay. The visitor opens the cart link, signs in, places the order and enters card details at your payment provider.
- Sending files. A form with a file upload gives the assistant its page address. The visitor sends the file in a browser.
- The email code. Where a form asks for an email code, the code goes to the visitor's own inbox. The assistant cannot sign in without it.
- Redeeming an offer. Your staff redeem it at the counter, as before.
The assistant never reaches your staff screens, private records, unpublished widgets or another business's widgets. It has no staff account. Your team's own AI connections are a separate door with their own permissions and approvals.
The privacy boundary
- No visitor identifier. Pepper keeps no IP address, device, token or other identifier for an agent call. Analytics shows calls per day, tool, widget and widget family, and the records agents made. It withholds the details when agents made fewer than 5 calls.
- Nothing sent anywhere. Pepper sends nothing to search engines, AI providers, registries or any other third party.
- First-party discovery only. Your published widget pages and your website's
llms.txtname the door on your own installation. That is the only discovery Pepper adds. - Text is data. What the assistant reads is your business content, and what it sends is visitor input. Neither becomes an instruction to your staff agents, automations or the Assistant.
Agent calls never count as human views. A record an agent creates goes through the same validation and consent as the form.
You stay in control
The visitor door is on by default. Open Settings > Widgets and use Visitor agents to turn it off, or close single widget families such as Bookings or Offers. With the door off, every agent request gets the same short refusal and nothing else.
To see what a visitor's AI sees, add the door address from Settings > Widgets to your own AI client without signing in.
What Pepper does not promise
Pepper does not promise that any AI assistant finds your business, chooses it or books with it. It promises no visitors, bookings, sales, visibility or ranking. The door makes your published widgets readable and usable for an assistant that comes looking.
Read Visitor agents for the owner's settings and results. Developers can read the visitor door reference.