xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse 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
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/Resource Presence — entity reference
REFERENCE · Last reviewed

Resource Presence — entity reference

The durable presence and capacity configuration for one Resource in Omni-Channel routing - one row per resource, upserted by the routing service. Holds the availability status with an optional reason, total capacity in work units (maxWorkItems) and optional per-channel caps as JSON. Live load is not stored here: it is computed from the resource's open ResourceWork items.

Fields

FieldLabelTypeRequiredWhat it does
LastChangedOnLast Changed OnDateAndTime
MaxPerChannelJsonMax Per ChannelTextOptional per-channel capacity caps stored as a JSON object, layered on top of the overall maxWorkItems total.
MaxWorkItemsMax Work ItemsNumberYesTotal capacity in work units (default 5). The router only assigns new work when the agent's current load (sum of open ResourceWork capacityWeight) plus the new item's weight fits within this cap.
ResourceIdResourceLookup → Resource, uniqueYesThe Resource this presence row belongs to - one row per resource, enforced by upsert in the routing service (setting presence updates the existing row rather than adding another). The underlying user is the resource's UserId.
StatusStatusPickListPresence vocabulary: Available, Busy, Away, Offline, with statusReason carrying the optional why. This is the agent-declared state; actual load is computed from open ResourceWork items. Values: Available, Busy, Away, Offline.
StatusReasonStatus ReasonText

Actions

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