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 Message — entity reference
REFERENCE · Last reviewed

Side Conversation Message — entity reference

One message inside a side conversation, the private sub-thread kept on a case. Rows are created by the case's Start Side Conversation action (only when a body is supplied) and by Reply Side Conversation; both actions need their values passed as action arguments, which the standard case page does not send, so in practice messages are added through the data API or a customised screen. The message is only stored: nothing sends it by email or any other channel, so a saved Outbound row does not mean the message left xMatix. The standard screens have no form or list for messages, and the entity is in no app. Messages are numbered from the SCM document-name series.

Fields

FieldLabelTypeRequiredWhat it does
BodyBodyTextThe message text, stored as entered. Start Side Conversation adds a first message only when a body is supplied; replies are stored even with an empty body.
DirectionDirectionPickListOutbound or Inbound. Blank becomes Outbound when the message is saved. It is a label you choose, not a record of delivery: an Inbound message is just a reply typed in by a user or an integration. Values: Outbound, Inbound.
FromAddressFromTextSender address. Never filled by the side-conversation actions; only a direct API write or an integration sets it.
MessagingTemplateIdMessaging TemplateLookupOptional messaging template reference. Nothing reads this field: setting it does not compose or send the message.
SentByUserIdSent ByLookup → UserAccountThe user account recorded as the sender. Filled only when the caller passes it to the action; it is not taken from the signed-in user automatically.
SentOnSent OnDateAndTimeDate and time stamped when an Outbound message is first saved (unless one is supplied). Inbound messages leave it empty. It records when the row was saved, not a delivery time.
SideConversationIdSide ConversationLookup → SideConversationYesThe side conversation this message belongs to. Required. Reply Side Conversation sets it from the conversation id passed to the action and does not check that the conversation belongs to the case the action ran on.
ToAddressToTextRecipient address as passed to Start or Reply Side Conversation. Stored only; nothing sends to it.

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
EditInLineEditEditInlineEdit in page.