A website agent should do more than answer
Most website assistants wait for a question and return a block of text. The Aivah Website AI Guide is designed to stay inside the journey: it understands the page a visitor is viewing, explains what is in front of them, and can move the interface to the next useful place.
A visitor can ask to see pricing, open a product page, find a specific section, move up or down the page, or begin a sales enquiry. The conversation continues while the website changes, so the visitor does not need to restart or repeat the context.
How the guided journey works
The experience connects conversation, page context, approved website actions, and visible feedback. Each action is narrow enough to verify and useful enough to move the journey forward.
- The visitor asks naturally by voice or text, in the language they prefer.
- Aivah reads the current URL and the page's approved section map.
- The guide selects an allowlisted action such as navigate, scroll, focus a section, or prepare a form.
- The website performs the action and returns a success or failure receipt.
- The same conversation continues with the new page and section context.
Control must be useful and safe
Website control should never mean unrestricted browser control. Aivah works from a declared map of public routes, named sections, and permitted actions. Private systems, hidden data, and unsupported actions remain outside the guide's boundary.
For sensitive steps, the visitor stays in control. Aivah can collect contact details one field at a time and prepare an enquiry, but it should recap the information and request explicit permission before submitting it. Failed actions should be explained clearly and handed back to the visitor instead of being repeated.
Prepare for the Aivah API
The public Aivah developer platform is coming soon. It will let teams bring the same guided behavior to their own approved website journeys without exposing model credentials or internal business systems in the browser.
A strong integration starts with a small contract: publish the routes and sections the guide may use, send the current page context with the conversation, subscribe to structured action events, execute those actions in the website, and return a receipt. Keep the conversation identifier stable across navigation so voice, memory, and visitor intent stay connected.
- Route manifest: public destinations, aliases, and the purpose of each page.
- Section manifest: stable section identifiers and plain-language labels.
- Action policy: what the guide may do automatically and what needs confirmation.
- Session context: current URL, current section, language, and completed actions.
- Outcome events: navigation success, form progress, signup intent, sales handoff, and errors.
Use it across the customer journey
A sales visitor can compare capabilities and reach the right contact path. A new customer can be guided through onboarding. A support visitor can open an exact Help Center answer. A multilingual visitor can explore the same journey without translating the site manually.
The useful pattern is consistent: understand the intent, show the relevant information, perform one approved action, and keep the person oriented. The guide should recommend signup or sales only when it fits the conversation, not repeat a call to action after every answer.
Start with one measurable outcome
Begin with the journey visitors struggle to complete today. Map the pages, sections, and decisions involved; define the action the guide may take; and measure whether more visitors reach a useful outcome with less friction.
Aivah's own Website AI Guide is the working example: one realtime employee that can explain the product, navigate the public site, guide a visitor to the right resource, and help them take the next step.
