LiveChatAI

OpenAPI imports turn a customer's API operations into callable AI Actions. Builders supply the schema, choose Basic, bearer or custom authentication and add the resulting endpoints to the bot. The agent gathers required parameters from the visitor before executing the matching operation and returning its result. Ready actions also book appointments, send Slack messages and change Shopify carts. OAuth is not supported by the OpenAPI import route.

Sourcehelp.livechatai.com/ai-actions-with-open-apiread 2026-10-20

A conversation can chain several imported API operations, passing through input collection, execution and a reply based on the result. Customers define the condition for each AI Action and a fallback message when a call fails. Connected Make scenarios supply visual branching, iteration and transformations, while an MCP backend can coordinate a longer sequence and return its summary. Those external workflow steps remain configured in the connected automation service.

Sourcelivechatai.com/ai-actionsread 2026-10-20

Business content is stored in a retrieval collection built from websites, files, text and question and answer pairs. Weekly Site Sync runs each Monday, refreshing existing pages, removing stale content and discovering new URLs, then emails a summary of the sources added, updated and removed; customers switch it on or off in Data Sources. Contact attributes can restrict which parts of the collection a given visitor's answers draw from, and source details show which page or answer a reply used.

Sourcehelp.livechatai.com/weekly-site-syncread 2026-10-20

Live Chat settings let visitors request a person and can automatically transfer a conversation after a configured number of exchanges. The agent stops its conversation handling at that limit and sends the chosen handoff message. Staff receive the request in the inbox and can reply directly to interrupt the automated exchange. Source restrictions and response instructions constrain answers, but external action calls have no general approval queue with an authorized release step.

Sourcehelp.livechatai.com/conversation-flowread 2026-10-20

Account owners invite teammates by email, assign or change their roles and remove access from the Teams page, and inbox handling is limited to members with the matching permissions. Stored content sits in isolated containers with encryption, connections are encrypted, and visitor data has its own deletion controls. The security program cites third party assessments, but LiveChatAI names no SOC 2 report or ISO certification of its own.

Sourcehelp.livechatai.com/adding-new-team-memberread 2026-10-20

The Chat Inbox preserves the full exchange between the customer, AI and human support staff. Operators work conversations assigned to them or waiting in the unassigned queue, reply in place and close an exchange, and source details identify the page or answer behind a response. Analytics summarize topics, sentiment and function success rates across conversations. An action's request and response appear only through its effect in the chat, with no per call log of inputs and outputs.

Sourcehelp.livechatai.com/inbox-for-chat-historyread 2026-10-20

The conversation carries the customer's current exchange and collected inputs into subsequent replies. A consistent visitor identifier links contact records and chat history across sessions, and defined attributes store details such as plan, language or city for identification, segmentation and inbox context. The agent does not keep its own record of what it learned about a visitor; continuity across visits comes from that contact record and its chat history, which the account holder can delete.

Sourcehelp.livechatai.com/visitor-identification-apiread 2026-10-20

The application runs on AWS servers in Frankfurt, embedded knowledge sits encrypted in a Pinecone vector store in Oregon, and Vercel delivers the application. Those locations are fixed for every account, so content and conversations span the EU and the US whatever the customer's own requirement, and no setting moves either one. The subscription has no customer cloud runtime or on premises installation.

Sourcehelp.livechatai.com/security-policiesread 2026-10-20

An AI Actions library publishes recipes for jobs such as creating HubSpot contacts from new chats, generating price quotes from Google Sheets, sending QuickBooks invoices, posting critical issue alerts to Slack, scheduling demos through Calendly and reporting Shopify order status. Several recipes hand the work to a ready scenario template on Make.com, which the customer copies, fills with its own values and connects to the bot through a webhook action. The building blocks are packaged; the customer assembles each one, and no prebuilt agent or in product template gallery ships with the bot.

Sourcelivechatai.com/ai-actionsread 2026-10-20

A visitor's incoming message can match a customer defined condition and start an AI Action automatically. The bot collects any required values, calls the configured service and returns the result in that conversation. Website widgets, WhatsApp, Slack and Zendesk give users entry points to the support agent. Automatic handoff can also trigger after a chosen number of exchanges, moving the current request into the human support queue.

Sourcehelp.livechatai.com/ai-actions-definitionread 2026-10-20

The model selector offers choices from OpenAI, Meta, DeepSeek, Google and other makers, with different credit costs per exchange. Customers save the chosen model in AI Configuration and can switch it when the task or cost target changes. Advanced and Expert accounts can connect their own OpenAI API key, moving those model charges to the customer's provider account. Premium models consume more platform credits than the standard choices.

Sourcehelp.livechatai.com/llm-model-temperatureread 2026-10-20

The current REST API uses bearer authentication with keys managed in the customer dashboard. It can create and delete agents, send messages, manage conversations, create or update contacts and maintain text, file, URL and question sources. Responses use structured JSON with standard error statuses. Advanced and Expert subscriptions include API access. Remote MCP connections add tools to the support bot separately from this interface for managing LiveChatAI itself.

Sourceapi.livechatai.com/api-reference-v2/introductionread 2026-10-20

AI Suggestions flags weak answers from real visitor conversations and pairs each original question with the agent's response. Staff edit a proposed question and answer, save it to the knowledge base and retest the fix in Preview, and unhelpful suggestions can be dismissed one at a time or in bulk. Webhook actions accept a sample payload through Send Test Data before going live. Each check is run and judged by a person; no saved test set replays conversations or scores one agent version against another.

Sourcehelp.livechatai.com/ai-suggestionsread 2026-10-20

Custom Button actions display a link whose destination can change with visitor attributes. The visitor chooses to follow the link; the agent does not click through the destination or fill its forms. Shopify operations use the connected commerce integration, while website crawling prepares material for the knowledge collection. Neither route provides a browser or desktop session that the support agent drives through a sequence of interface actions.

Sourcelivechatai.com/ai-actionsread 2026-10-20