Lifecycle and Types
Statuses, prefixes, channels, and how ThinkWork models different kinds of work in one thread system.
Threads
A thread is the fundamental unit of work in ThinkWork. Whether work starts from a chat, automation, email, or connector event, it lands in the same thread model.
That is one of ThinkWork’s strongest ideas. You do not have one system for chat, another for workflows, and another for inbound integrations. You have one durable record of work.
What threads give you
Section titled “What threads give you”Threads provide the shared container for:
- message history
- status tracking
- channel identity
- metadata from the source system
- auditability and replayability
Why threads matter
Section titled “Why threads matter”Threads are the backbone that connects the rest of the platform:
- Agents respond inside threads
- Memory is assembled from thread history and retained context
- Automations create
AUTO-threads for every run - Connectors map inbound systems onto the same thread model
- Control uses thread activity for usage, budgets, and audit trails
Routing and Metadata
Channel-specific metadata and routing context for connector and app-originated work.