autoch.at Documentation

Appearance

Widget Configuration ​

The Live Chat widget is intentionally lightweight: it’s easy to embed, branded enough to feel “yours”, and connected to the same assistants, routing rules, and conversation history as the rest of autoch.at.

This page covers what you can configure today, and how to do it without guesswork.

Embed-time options ​

When you embed the widget, you can set:

  • primaryColor — the accent color used for the widget button and header
  • companyName — the label shown in the widget header
  • position — bottom-right (default) or bottom-left
  • avatarUrl — optional assistant avatar image
  • headerLogoUrl — optional header icon (replaces the default chat icon)
  • headerWordmarkUrl — optional header wordmark image (replaces the company name text)

Example:

html
<script src="https://app.autoch.at/web-widget.js"></script>
<script>
  ChatWidget.renderWebWidget({
    tenantId: "your-tenant-id",
    apiUrl: "https://app.autoch.at",
    token: "your-widget-token",
    primaryColor: "#3B82F6",
    companyName: "Your Company",
    position: "bottom-right",
    avatarUrl: "https://example.com/avatar.png",
    headerLogoUrl: "https://example.com/icon.png",
    headerWordmarkUrl: "https://example.com/wordmark.png"
  });
</script>

Tip: The Widget Playground in the app can generate this snippet for you.

Proactive messaging (optional) ​

The widget supports proactive messages (a friendly “Need help?” that can appear based on triggers like time on page, scroll depth, idle time, exit intent, etc.).

In the current widget implementation:

  • Proactive messaging is typically configured per-tenant and fetched via GET /api/widgets/:tenantId/config.
  • If proactive messaging is enabled for your tenant, the widget will automatically use it (you don’t need to hardcode it into the embed).

Widget tokens are meant to be embedded on your site, which means they live in the browser. The best way to keep that safe is to restrict where the widget is allowed to run.

When the widget calls the API, autoch.at can enforce an allowlist of approved domains for your tenant. If a request comes from an unapproved domain, the API will return 403 and the widget won’t load/send messages.

If you don’t configure any domains, the platform defaults to allowing all domains (for backwards compatibility and easier testing).

What the widget does automatically ​

  • Collects name + email before the first message (so your team can follow up)
  • Creates/links a client record and connects it to the conversation timeline
  • Sends messages via HTTP to POST /api/widgets/:tenantId/chat and returns a response immediately
  • Shows a “Powered by AI and autoch.at” link in the widget footer

Next steps ​

autoch.at Documentation

Copyright © 2024 autoch.at