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

Resource Work — entity reference

One Omni-Channel routing work item: a unit of work pushed to a Resource, polymorphic via workEntityName/workRecordId so any entity - cases, chats, calls, leads - can be routed, not just cases. Carries the queue it came from (queueId), the channel, the capacity it consumes (capacityWeight) and the routing timeline (pushedOn, acceptedOn, closedOn). A resource's live load is computed from the open rows here against the capacity configured on ResourcePresence; the assigned user is reached through the resource's userId.

Fields

FieldLabelTypeRequiredWhat it does
AcceptedOnAccepted OnDateAndTime
CapacityWeightCapacity WeightNumberYesHow many capacity units this work item consumes against the resource's maxWorkItems (default 1) - heavier work can be modeled by a larger weight rather than a separate cap.
ChannelChannelPickListThe channel the work arrived on: Email, Chat, Voice, SMS, messaging apps or Web. Carried through decline re-routes and transfers. Values: Email, Chat, Voice, SMS, messaging apps, Web.
ClosedOnClosed OnDateAndTime
PushedOnPushed OnDateAndTimeWhen the item was pushed (defaulted on insert). Also the RoundRobin tiebreaker: that model picks the eligible agent with the oldest last-pushed time, so this field drives rotation fairness.
QueueIdQueueLookup → QueueThe Queue the work was routed through; null when it was assigned directly to a resource. Pending items are counted per queue for the supervisor backlog view.
ResourceIdResourceLookup → Resource
StatusStatusPickListRouting lifecycle vocabulary: Pending, Assigned, Accepted, Declined, Closed, Transferred. Open (non-terminal) rows are what count against the resource's capacity. Values: Pending, Assigned, Accepted, Declined, Closed, Transferred.
WorkEntityNameWork EntityTextThe entity name of the routed record (Case, Call, ...) - pairs with workRecordId as a polymorphic reference. Case work gets special treatment on accept: the case's AssignedToId/OwnerId are stamped from the accepting resource's user.
WorkRecordIdWork RecordLookupYesThe id of the routed record; interpret it against workEntityName.

Actions

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