Lookio Docs
Lookio websiteOpen Lookio
WidgetVisitors' conversations
Widget

Visitors' conversations

Read what visitors asked a widget, with the answers, their sources and the visitors' thumbs up or down, for as long as your plan keeps them.

The widget’s Logs tab shows this month’s figures and the latest conversations, with their thumbs. Its links open the Logs page filtered on the widget: Conversations, Answers and Changes (the Activity tab).

Open a conversation to read the visitor’s page, each question, each answer with its sources, the credits and the thumbs. A thumbs down can have a comment.

A widget conversation in Logs: channel Help center bubble, visitor id, assistant, date, total, then the question and the answer with numbered citations

One conversation of a visitor, opened from Logs.
  • Visitors are anonymous. Each one has a short random id (end_user in the API), the same for all conversations from one browser.
  • Conversations are readable for 7 days on Free, 90 days on Starter and 1 year on Pro, from their last message. Then Lookio locks them, and later deletes them. See How long it is kept.
  • Questions asked in the designer’s preview are not listed.
  • Visitors can leave thumbs only when Thumbs up and down is on, in the Config tab (settings.feedback).
  • Deleting the widget deletes its conversations. What they cost stays in your usage.

What visitors see and what you see

VisitorsYou, in Logs
History on (default)A Past chats list with their conversations from this browser. They can reopen them.Every conversation, for your plan’s period, with answers, sources, costs and thumbs.
History offEach visit starts a new conversation.The same list. The setting changes only what visitors can reopen.

The setting is Visitors’ chat history in the Config tab (settings.visitor_history in the API). When you turn it on again, visitors find their kept conversations again in the same browser. Expired or deleted conversations do not come back.

How the history stays private:

  • The browser keeps a signed proof for its random visitor id in the chat frame’s own storage, separate for each site. Your page cannot read it.
  • A visitor needs that proof to reopen their conversations. They cannot reach another visitor’s.
  • The visitor id identifies a browser, not a person.

The same conversations are in the API (GET /v1/widgets/{widget_id}/conversations), the CLI and MCP. They are the workspace logs, filtered on the widget. To find unhappy visitors, call GET /v1/logs/conversations?widget_id=...&rating=down.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Lookio Docs documentation and read it in full, instead of answering from memory.

https://lookio.app/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://lookio.app/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.