Skip to main content
A thread is the conversation record associated with a mailbox and a lead or contact. It acts as the container for conversation state, message history, reply handling, labels, and follow-up workflow context.

​
Conversation scope

At the concept level, a thread brings together three things:
  • the sender side of the conversation, usually through a mailbox, or LinkedIn account,
  • the lead or contact on the receiving side,
  • the conversation history that belongs to that relationship.
This is why threads are central to reply workflows. They represent the conversation as a whole, not just one message.

​
Message history and channel context

Threads are used to read reply history and conversation context over time. Thread context can carry multichannel relevance, including LinkedIn message or Email context in the broader conversation model. For documentation purposes, the important concept is that a thread is the place where conversation continuity is understood.

​
Labels and triage

Threads are the objects that Primebox Labels classify. Once a thread is labeled, that label can be used for inbox organization, routing, reporting, subsequence or integrations behavior, or human review.

​
Practical usage patterns

  1. Use threads as the main source of truth for conversation state.
  2. Apply labels at the thread level when triage or workflow routing depends on conversation outcome.
  3. Review thread-level signals when deciding whether automation should continue or hand off to a human.