Skip to content

Cards in chat (Slack & Teams)

User guide

Telha shows up in Slack and Microsoft Teams as one bot. You ask questions, answer the occasional confirmation, and get notified when things you care about change, all as cards. This page shows the actual cards you will see and what to do with each, grouped by role. Everything comes to your own direct message, and you only ever see what you are allowed to see.

Rolling out

The ask, answer, and clarification cards are live today. The analyst watch and saved-answer cards are rolling out. If you do not see them yet, ask your Telha administrator.

Everyone: ask, and get a verified answer

Ask Telha a question in chat. It answers from your organisation's actual state, shows the sources behind the answer, and tells you it checked each claim.

T
TelhaApp 10:12 AM

Meridian's liability cap is EUR 5,000,000, raised from EUR 2,000,000 by the 2026 amendment, effective 1 April 2026.


📎 Evidence
Meridian_MSA_Amendment_2026.pdf · clause 11.2
"...the aggregate liability cap shall be EUR 5,000,000..."
✅ 3 claims verified against source
Open full trace Watch this
  • The green line means Telha broke the answer into individual claims and checked each one against the sources it was allowed to use.
  • Open full trace shows every claim, its verdict, and a click-through to the exact source text.
  • Watch this (analysts, below) tells Telha to notify you when this changes.

Everyone: answer when Telha asks

Sometimes Telha meets a fact it cannot pin down: a date that reads "next quarter", two conflicting figures, an undated scan. It makes its best guess at lower confidence and asks the right person to confirm. That person might be you.

T
TelhaApp 9:41 AM
Quick check on the Meridian contract

The renewal clause looks like it takes effect next quarter, but the document is not explicit. When should it be in force from?


📎 Evidence · Meridian_MSA_2026.pdf, page 4
1 April 2026 1 July 2026 Pick another date This isn't right

One tap is all it takes. Your answer is recorded as evidence under your verified corporate identity (not just a chat name), and Telha corrects the fact from then on while keeping the old belief reconstructable. Important facts ask two people before they are treated as settled.

When you have several open questions

Telha batches them into one digest rather than pinging you repeatedly:

T
TelhaApp
You have 3 open clarification questions

When did the Northwind SLA take effect?

1 Jan 20261 Feb 2026

Which figure is the correct penalty cap?

EUR 50,000EUR 75,000

Analysts: stay ahead of change

Set a watch ("tell me when anything about Meridian changes", or tap Watch this on any answer) and Telha tells you when the state moves. You never get spam: changes are coalesced into one notification per window.

A watch fired. What changed, by kind, with a way into the evidence:

T
TelhaApp 2:03 PM
Memory changed · Meridian
Facts changed
2
New source versions
1
Clarifications resolved
1
🕑 Over the last hour · watch: "Anything about Meridian"
View evidence Show timeline Stop watching

Your weekly brief. The habit: what moved in your corner of the world, once a week, deduplicated so a change never shows up three times.

T
TelhaApp Mon 8:00 AM
Weekly Memory Brief · Supplier risks
Facts changed
14
Clarifications resolved
3
Answers gone stale
2
Conflicts for review
1

Meridian exposure raised · Northwind contract superseded · 2 undated incidents clarified
Open changes

A saved answer went stale. An answer you kept knows when its evidence moved, and tells you exactly which claims changed, old value to new:

T
TelhaApp 4:20 PM
A saved answer is now partially stale

"What is our exposure to Meridian?" has changed since you saved it.


🧾 What changed
Liability cap
EUR 2m → EUR 5m
Effective-date clarification
has now bound
Refresh answer View changed claims Keep original

Refresh answer re-runs the question with the new evidence (it asks you to confirm first, since it spends generation budget). If your role cannot generate, you still get View changed claims and a link, never a dead end.

Stewards: resolve what others cannot

When a clarification cannot reach anyone who may answer it, or when two answers conflict, it comes to a steward. The card names the document and workspace and the reasons it was skipped, but never quotes source text, because you may not have read rights on the underlying document.

T
TelhaApp 11:07 AM
Clarification needs steward review

A clarification could not be delivered to any candidate and needs steward review.

Document: Meridian_MSA_2026.pdf (your Telha workspace).

alex@acme.com
no read access
sam@acme.com
no verified identity

🔧 Review with: telha clarify show <id>

Your resolution is itself recorded as evidence, with your name on it. When people disagreed, all of their answers stay visible; you are choosing which one becomes the in-force fact, not erasing the others. See the steward guide for the review queue and override rules.

What every card guarantees

  • You only see what you may see. Delivery re-checks your access at the moment it sends. A card you are no longer allowed to receive is simply not sent.
  • Your identity is verified. Answers and confirmations are bound to your corporate identity, not a chat display name.
  • Nothing lands in a channel. Every card is a direct message. A team watch sends a separate DM to each authorised member; it never posts to a channel, because channel membership is not a Telha permission.
  • Everything has receipts. Answers link to the exact source; corrections and resolutions are recorded append-only and stay reconstructable.