Skip to main content
Primebox labels are workspace-scoped categories used to classify conversation outcomes. They are attached to threads and help normalize how reply workflows are organized, interpreted, and routed.

​
What labels represent

At the concept level, a Primebox Label describes the current interpretation or outcome of a conversation. That interpretation might be positive, negative, complete, out of office, meeting-related, or simply not relevant to the intended recipient. The key idea is that labels turn raw conversation activity into a reusable workflow signal.

​
Built-in and workspace meaning

Salesforge supports built-in label behavior for common outcomes such as:
  • Positive
  • Negative
  • Out of Office
  • Meeting Booked
  • Meeting Completed
  • Closed
  • Wrong Contact
These built-in labels provide a shared classification vocabulary for conversation handling. Within a workspace, labels become the way teams standardize how they interpret and process thread outcomes.

​
Relationship to threads

Primebox Labels belong conceptually to threads. They are not just free-form tags. A label changes how a conversation is understood inside inbox workflows, reporting, automation, and follow-up decision-making. Because labels are attached to threads, they work as conversation-level signals rather than mailbox-level or contact-level attributes.

​
Workflow relevance

Label changes can influence downstream behavior. Depending on the workflow design, a label can affect triage, reporting, webhook events, or subsequence handling. This is why label assignment is best treated as part of conversation state management rather than as cosmetic inbox organization.

​
Practical usage patterns

  1. Map labels to meaningful business outcomes in your integration model.
  2. Apply labels when automation or human review determines the current conversation outcome.
  3. Use thread labels as routing and reporting signals rather than as display-only metadata.