Typed Messages
A typed message is a message that carries a structured kind — question, decision, task, approval, and so on — instead of being an undifferentiated blob of text. The type drives how the system routes, prioritizes and searches it.
In most chat tools, a message is just text with reactions and a thread bolted on. The application has no idea whether it's a question waiting on an answer, a decision that should be remembered, or a routine update nobody needs to act on — so every message gets treated roughly the same: it sits in a channel, waiting to be read.
A typed message fixes that by attaching a kind to the message itself at write time: message, question, answer, decision, update, task, approval, alert, doc, event, or celebration. That type isn't cosmetic — it's the field everything else is built on. Routing, notification priority, search facets and analytics all key off it.
Typing is usually AI-suggested and always author-overridable; a good implementation never blocks send while it decides what type a message is. The alternative — asking humans to categorize every message by hand — never survives contact with a busy channel, so the type has to be inferred, cheaply and fast, without becoming a gate.
Typed Messages, in the product
Aanty's 11 typed objects (message, question, answer, decision, update, task, approval, alert, doc, event, celebration) are the substrate the whole product is built on. Classification happens as post-send enrichment — never on the blocking send path — and a message's type is always human-overridable. Type drives the decision ledger, the needs-you queue, and every search facet.
Related terms and pages
See Typed Messages in a real workspace
Bring a channel from wherever your team works today. In fifteen minutes we'll show what typed messages looks like on a real conversation, not a slide.