Use Tattva from Manas

Manas can ask Tattva for you. The question runs exactly as if you had asked it in Reasoning: same projects, same definitions, same checks. Manas shows you the answer and links back to it in Tattva.

Who can ask

You need the Member role or above in a Tattva project. Viewers can read answers in Tattva but can't ask, from Manas or anywhere else. See Permissions.

If Manas says "your email isn't a Tattva user" or "You aren't a member of any Tattva project", ask an Owner to add you to the project in Settings › Workspace.

Choosing a project

Tattva decides which project a question goes to, in this order:

1. The project you name, for example "net revenue last month in Kapiva Decisions".
2. The default project. For you, that's Default project for Manas in Settings › Profile & memory (see Account & profile). For a Slack channel, it's the channel's default project (see A channel's default project).
3. Your only project, if you can ask in just one.

Otherwise Manas replies Which project? with a numbered list of the projects you can ask in, for example:

Which project? Reply with a number or the name:
1. Kapiva Decisions (kapiva/kapiva-decisions)
2. Ops Sandbox (ops/ops-sandbox)

Reply with the number or the name, and Manas asks your question in that project. To skip this question, set a default. Tattva never picks a project from what the question is about.

In Manas web chat

Pick the Tattva agent and ask your question in plain English, as you would in Reasoning.

The reply has:

• The answer with its text and tables exactly as Tattva wrote them. Links inside it (for example "review it" on a conflict note) open in Tattva, in the answer's workspace and project.
• One status line: whether the self-audit sent an earlier attempt back and it was redone, and whether any figure is provisional (recent days not settled yet) or incomplete (data it needs doesn't exist yet, so the figure will change).
• Chart images under the answer, one per answer table, the same chart Tattva shows by default.
• Open in Tattva: a link to the answer in Reasoning, where you can read the Trail and change the chart type.
• The Tattva project line at the end, for example Tattva project: Kapiva Decisions (kapiva/kapiva-decisions) · conversation tattva_conv_1f0c…. See Following up.

In a Slack DM or with /manas

Send Manas a direct message, or use /manas in any channel. Manas acts as you: it uses your projects, your role and your PII clearance. The answer is only shown to you (in a DM) or posted where you used /manas, so think about who else can see it before asking about personal data.

In a Slack channel

@mention Manas in a channel to ask on the channel's behalf. Here Manas acts as the channel, not as you:

• A project Owner or Admin has to connect the channel first, in Settings › Workspace › Slack channels. See Slack channels.
• The channel can only ask, read, and say whether an answer was right. It can't upload, review or change anything.
• Personal data is always masked in a channel's answers, whoever asked.
• Nothing asked in a channel is saved to project memory.

If the channel isn't connected, Manas replies: "This channel isn't connected to a Tattva project. A project admin can add it in Tattva (Settings › Workspace › Slack channels), or ask me in a DM."

When Tattva asks you something

Sometimes a question has more than one reading, for example which product you mean. Tattva then asks a clarification question instead of answering, with numbered choices:

A 'full P&L' can mean different things. Which line items should be included?
1. Revenue only (Gross Revenue → Net Revenue after RTO)
2. Revenue + COGS (Gross Profit / Margin)
3. Revenue + COGS + Discounts + Tax breakdown + Logistics costs (full waterfall)

Reply with a number or the name.

Reply with the number (2), the choice's name (capitals and spaces don't matter), or your own words if none fits. In Manas web chat, reply in the same chat; in Slack, reply in the same thread. Manas passes your reply back, Tattva takes the choice you named and carries on in the same project and conversation.

In a Slack channel, anyone in the channel can answer, because the conversation belongs to the channel. In web chat, a DM or with /manas, only you can.

When Tattva doesn't answer something yet

Your analytics team decides what Tattva answers in each project. If you ask about a topic they have marked as not answered yet, or a kind of question they have switched off (such as forecasts), Tattva replies with their reason and questions you can ask instead, the same as in Tattva itself. Ask "What can you answer?" or "Do you do ROAS?" to get the same list of what this project answers that Tattva shows. See Ask a question.

Dashboard links and earlier answers

When your project's Repeat questions setting is on, Manas gives the same replies as Tattva: a link to a registered dashboard that covers your question, or a recent identical answer starting "Answered on …; the data has not changed since." Manas has no Answer here instead or Ask again button. To get the full answer, click Open in Tattva at the end of the reply and use the button there. See Ask a question.

Following up

Every reply from Tattva ends with a line naming its project and conversation:

Tattva project: Kapiva Decisions (kapiva/kapiva-decisions) · conversation tattva_conv_1f0c2a7e-…

A follow-up in the same chat or thread ("and for July?") continues that conversation in that project, so Tattva knows what "July" refers to. In Slack, Manas only sees the messages in the thread, not earlier replies it got from Tattva, so this line is how it knows where to continue; leave it in the thread.

Tattva's ids always start with tattva_conv_ (a conversation) or tattva_run_ (one answer), so they can't be mixed up with Manas's own chat and message ids. Tattva only accepts its own ids in that form.

To ask in another project, name it ("and in Ops Sandbox?"). That starts a new conversation there.

Only whoever started a conversation can continue it: you for your own questions, the channel for a question asked in a channel.

Saying an answer was right or wrong

Tell Tattva's team when an answer was right, or what is wrong with it. They see it in Ontology › Maintain › Feedback, the same list as the Satisfied / Not satisfied buttons under an answer in Tattva (see Work answer feedback). Feedback changes no answer by itself: the team reviews it and fixes the definition or rule behind it, so everyone gets the corrected answer.

In Manas web chat, a Slack DM or with /manas, just say it in the chat, for example "that's wrong, we report net revenue after GST" or "this is right". Manas passes it to Tattva for the answer you mean, with your words, and tells you the team will review it. It is saved under your name. Saying it again about the same answer updates what you said.

In a Slack channel you can do the same in the thread; there the feedback is saved as the channel's. Manas finds the answer from the Tattva project: line in the thread and rates the latest answer in that conversation, so leave that line in the thread.

The 👍 / 👎 buttons under an answer from the Tattva agent also reach Tattva's team, in Slack (a channel, a DM or /manas) and in Manas web chat. The reasons you pick, and anything you type, go with it. The team sees the reasons as:

The reasons are also kept word for word, and what you typed is shown to the team as what was wrong. A 👍 reason in Manas web chat (for example "Accurate and Reliable") is kept as a note.

If you can use the answer's Tattva project (matched by your email), the feedback is saved under your name; otherwise it is saved under whoever asked (in a channel, the channel), with your email noted on it. Each rating is one piece of feedback: changing 👍 to 👎, adding reasons or adding a comment later updates it. Feedback from Manas web chat reaches Tattva within a few minutes.

Long questions

Most answers take one to four minutes. If an answer isn't ready after about 4½ minutes, Manas gets a run id (tattva_run_…) instead and can fetch the answer later. Ask Manas to check on it; the run keeps going in Tattva meanwhile, and the answer also appears in Reasoning.

Links

• Open in Tattva switches Tattva to the answer's workspace and project and opens the conversation.
• An answer asked in a Slack channel opens read-only for members of the project, marked Asked in #channel via Manas. Click Ask a follow-up to start your own conversation from it.
• People who aren't members of the answer's project can't open it: Tattva stays on a project they can use and the conversation doesn't load. The answer is still in Manas or Slack.
• Chart image links work without signing in, so Slack can show them. They expire after 7 days.

What Manas can't do yet

From Manas you can ask questions, answer Tattva's clarifications, ask follow-ups, look up metric and term definitions, and say whether an answer was right. Use Tattva itself for everything else:

• running raw SQL
• the review queue
• editing the ontology
• uploading sources
• reports and trackers

Related

• Ask a question
• Workspaces & members
• Permissions
• Sensitive data