AI

Sites on the Business plan can call AI from their own server-side code. There's no API key to set up and no provider account to manage: the site asks for a completion and gets one back, and what it does with the answer is up to your logic.

What you can build

• A chatbot that answers visitors' questions about the business, in the site's own design and voice
• An assistant that takes action — submitting a contact form, looking up an order, checking availability or booking a slot on the visitor's behalf
• Summaries of submissions, reviews or long records
• Classification — tagging, routing or prioritizing incoming inquiries
• Written content — drafting replies, emails and descriptions in real time

Building a chatbot

A chatbot is something the site builds from parts it already has, rather than a fixed widget. The conversation runs over a realtime channel, so the answer reaches the visitor the moment it's ready, and its history lives in the site's own database, where you decide what's kept and for how long. What the bot knows is whatever your code gives it — your pages, your records, the business details you choose. The simplest way to give it the site's own knowledge is site search: search the site for the visitor's question and hand the matching passages to the model, so it answers from what the site actually says, in the visitor's language. To answer from a table such as an FAQ, search it with the database search.

You can also give the model tools: actions your code defines, such as "submit a contact request" or "find available times". The model decides when a tool is needed and with what details; your code checks those details like any other visitor input and carries the action out. That's how a chatbot moves from answering questions to getting something done.

A page request has a short time budget, which suits a single quick answer. A conversation that takes several steps belongs in a realtime channel or a background job, which have room for it.

Handling the answer

Calling AI hands back a result rather than raising an error, so your logic decides what happens next — the result tells a temporary problem (the model is busy) apart from a permanent one and from the site having used its allowance. A site should always have a sensible fallback, such as offering the contact form, for when there's no answer.

Usage allowance

AI usage comes from a monthly allowance included in the Business plan, shared by every call the site makes. The app shows how much of it has been used as a percentage, and it resets with the billing period. When the allowance is used up, calls are refused until it resets, so a site's AI features stay within a known cost.

Local preview makes real AI calls, and they count against the same allowance as the live site.

Telling visitors

A site that lets visitors talk to AI must tell them they're talking to AI — for example, a short note in the chat window.

Availability

AI is part of the Business plan; agency-owned sites include it. See Capabilities overview.