Skip to content
DaneshyarDocs
Sign in
  • Introduction
  • Quickstart
  • What is Daneshyar?
  • The Apps page
  • Inside an app
  • Workspace: files and chat
  • Sharing and members
  • Notes and dictation
  • Language practice
  • Appointment booking
  • Automations
  • The file reader
  • Your profile
  • Customer chats
  • API keys
  • Authentication
  • Apps, workspaces, resources
  • Ingestion
  • Chat and sessions
  • Citations
  • Skills
  • Conventions
  • Workspaces
  • Resources
  • Chat
  • Skills
  • Errors
  • Customer support assistant
  • Internal knowledge base
  • Documentation chatbot
  • Academy tutor
  • Embedded widget
  • Widget configuration
  • Framework guides
  • Security
  • Troubleshooting
  • FAQ
  1. Docs
  2. User guide
  3. Customer chats

Customer chats

Read what visitors asked the chat window on your website, one conversation at a time.

When you put the widget on your website, visitors talk to it and you normally never see those talks. Widget chats is the page where you read them — to learn what people ask, and to check the answers.

Workspace page → the Customer chats button at the top (on a phone, in the ⋯ menu). Only the workspace owner sees it.

What this page is for

Every time a visitor starts a conversation in your widget, it is saved here. You can use it to:

  • see which questions people really ask;
  • check that the answers are good;
  • find a missing topic and add a file for it.
Example: a dental clinic sees that many visitors ask “Do you take insurance?”. The answer is not in any file, so the owner uploads a page about insurance — and the next visitor gets a proper answer.

Open a chat

  1. 1

    Open the list

    On the workspace page, press Customer chats. You see every conversation, newest first, with the first question, how many messages it has, and its date.

  2. 2

    Search if you need

    Type in the search box. It looks at the title and at everything said inside the chats.

  3. 3

    Press a chat

    You see the whole conversation in order: the visitor's messages and the assistant's answers, with the time of each.

Only the owner can open this page. Members with view or edit access do not see the button, and the address does not work for them.

How a chat looks

The conversation is shown the way the visitor saw it:

  • answers keep their bold, lists and links (links open in a new tab);
  • tables are drawn as tables — a wide one scrolls sideways;
  • Persian and English text each read in the right direction, even in the same message.
Only chats started after this page was added are listed. Older widget chats are not shown here.

Telegram and Bale chats

The same page also shows what people said to your Telegram and Bale bot. Above the list you will find three tabs: Widget, Telegram and Bale. Pick one and you get that channel's chats, opened the same way.

  • each connected chat is one conversation, with the person's messages and the bot's answers in order;
  • in a group, only messages that mention the bot or reply to it are kept — the rest of the group's talk is never saved;
  • the bot's own booking and reminder messages in that chat are kept too.
Example: a salon connects its Telegram bot. Opening the Telegram tab, the owner sees that many people ask “Are you open on Fridays?” and adds the opening hours to a file.

Who sees it

  • A visitor is shown as a short code, not a name. Daneshyar does not know who they are.
  • These chats are read-only. You cannot change or answer them from here.
  • Visitors' questions use your credits, the same as any widget answer.

Read next

Workspace: files and chatThe heart of Daneshyar: upload files, ask questions and get answers with their sources.Sharing and membersBring other people in: add colleagues as members, or make a link so anyone can ask questions.The Apps pageThe first page after you sign in: what an app is, how to create one and how to manage it.
PreviousYour profileNextAPI keys

On this page

  • What this page is for
  • Open a chat
  • How a chat looks
  • Telegram and Bale chats
  • Who sees it

Every example on this site runs against the live API. If one doesn't, tell us — that's a bug in the docs.

ServicesAboutTalk to us