Chat basics

Chat is where you ask questions about your data in plain language and get a structured answer back. You do not need to write SQL.

What chat is for

Ask a business or operational question about your data, and STYD turns it into a controlled, read-only query against your connected data source, checks it, runs it, and returns an answer you can read and trust.

You can also ask a general question, ask for advice, or ask for a draft email or message. That answer comes from general knowledge and carries the source chip “General knowledge”. See General questions and advice.

Choose the right workspace and connection

Each chat thread belongs to one workspace and uses one connection, so the data context stays clear.

Confirm the workspace selected in the header is the one you mean.
Open or create a chat thread.
Check the connection badge so you know which data source you are asking about.
Ask your question.
A thread uses a single connection. Start a new thread when you want to ask about a different database or Odoo source. The workspace's uploaded documents can be joined into the same answer.
Threads are private by default, only you can see a thread you create, until you share it with specific workspace members.

Asking good questions

Ask in your own business language. Clear questions, with a timeframe, the entity you mean, the metric, and any filters, help STYD build a more accurate query.

What an answer can include

Depending on the question, an answer may be a short summary, a number or metric, a table of rows, or a draft with a Copy button. An answer from your data can end with a short part labelled General knowledge, after a divider. Some answers also show small tags and a plain-language explanation of how the answer was produced.

The exact shape of an answer depends on your question and your data, so not every answer looks the same.

If an answer looks wrong

Check the connection badge, make sure the thread is on the right data source.
Open “How I found this” to see the logic, filters, and data used.
Rephrase with more detail (timeframe, entity, metric, filters).
Use thumbs-down feedback to flag what went wrong.

For a full tour of the chat interface, see the Website UI Guide → Chat page.