Skip to content

Chatbots answer. Aivah works.

Share your AI employee.

Hire and train an AI employee in your workspace, then put it in front of customers wherever they are: a link, a chat bubble, a voice widget or a page of your own. One snippet, no dependencies.

An example conversation: Nova, an AI employee, moves an order's delivery to the visitor's office and confirms the change.
  • Ready when they are.

    Visitors can type the moment it opens. Sound turns on with their first tap, with no dialog to click through.

  • The microphone only for calls.

    The browser asks for it when a visitor starts a call, never on page load or hover.

  • Always an AI employee.

    Every conversation shows the AI employee's name and says it is an AI, from the first message.

Channels

Four ways to share.

Publish once. Visitors reach the same AI employee, with the same business knowledge, wherever they find it. Replace EMBED_ID with the id on your workspace's Share screen.

  • A full-page conversation to share by email, in a chat or as a QR code.

    Link
    https://chat.aivah.ai/chat/EMBED_ID
  • Chat bubble

    A launcher in the corner of every page. It opens a panel on desktop and a full-screen sheet on phones.

    Script
    <script
      src="https://chat.aivah.ai/embed.js"
      data-aivah-id="EMBED_ID"
      async
    ></script>
  • Voice widget

    One tap starts a live voice call. The browser asks for the microphone only then.

    Script
    <script
      src="https://chat.aivah.ai/embed.js"
      data-aivah-id="EMBED_ID"
      data-aivah-mode="voice"
      async
    ></script>
  • Inline embed

    The AI employee inside your own page layout, sized to its container.

    HTML
    <div id="ai-employee"></div>
    <script
      src="https://chat.aivah.ai/embed.js"
      data-aivah-id="EMBED_ID"
      data-aivah-mode="inline"
      data-aivah-route="chat"
      data-aivah-target="#ai-employee"
      async
    ></script>

Sites that only accept iframes

Keep the full allow list. Without it the browser silently blocks the microphone, camera, screen sharing, sound, fullscreen slides and the copy buttons. The visitor is still asked before the microphone, camera or screen is used.

Iframe
<iframe
  src="https://chat.aivah.ai/chat/EMBED_ID"
  title="Chat with our AI employee"
  style="display: block; width: 100%; height: min(720px, 85svh); border: 0"
  allow="microphone; camera; display-capture; autoplay; fullscreen; picture-in-picture; clipboard-write; screen-wake-lock"
  referrerpolicy="strict-origin-when-cross-origin"
></iframe>

Go-live checks

Before you go live.

Most sites need nothing more. These two checks are for sites with strict security headers or corporate networks.

For sites that send Permissions-PolicyLet calls use the microphone, camera and screen.

A header that lists these features without the Aivah origin turns them off inside every iframe on the page. Add the origin to your existing header and keep the features you already list.

Header
Permissions-Policy: microphone=(self "https://chat.aivah.ai"), camera=(self "https://chat.aivah.ai"), display-capture=(self "https://chat.aivah.ai")

Firewall allowlist

For corporate networks that filter outbound traffic. Calls fall back to TCP and then TLS on port 443.

HostPortUsed for
chat.aivah.aiTCP 443The widget itself
api.aivah.aiTCP 443Conversations
storage.googleapis.comTCP 443Slides, video and images
*.livekit.cloudTCP 443Call signalling
*.turn.livekit.cloudTCP 443Calls when UDP is blocked (TURN/TLS)
*.host.livekit.cloudUDP 3478TURN/UDP
Any LiveKit serverUDP 50000–60000Call audio and video (optional, best quality)
Any LiveKit serverTCP 7881Call media over TCP (optional)