xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Side Conversation — entity reference
REFERENCE · Last reviewed

Side Conversation — entity reference

A private sub-thread kept on a case (or another record) for a focused exchange, for example with a vendor, whose messages are Side Conversation Message rows. The case's Start Side Conversation action creates one; Reply Side Conversation adds a message and Close Side Conversation sets it to Closed. The record is stored only: messages are not sent by email or any other channel, and privacy comes only from ordinary record security. The standard case page does not show these actions or a list of conversations, and the entity is in no app, so threads are managed through the data API or a customised case layout. Conversations are numbered from the SCV document-name series and move to the surviving record when duplicates are merged.

Fields

FieldLabelTypeRequiredWhat it does
ChannelChannelPickListEmail or Internal, defaulting to Email. A label only: neither value sends anything. Values: Email, Internal.
RecordIdRecordLookup → CaseYesThe id of the record the thread belongs to, usually a case. Only the id is stored, not the entity name. Merging duplicate records moves the thread to the surviving record.
StatusStatusPickListOpen or Closed. New threads are Open; Close Side Conversation sets Closed. A closed thread still accepts replies and is never reopened automatically. Values: Open, Closed.
SubjectSubjectTextOptional subject of the thread, as passed to Start Side Conversation.

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
EditInLineEditEditInlineEdit in page.
  • Case — looks up via CaseId