Task
What It Is
A task is the customer’s continuing record of work to be managed. Calling a member, preparing a meeting packet or reviewing an application can each become a task. The title identifies the work for staff, while description, type, priority and dates supply context. The task’s identity persists when that context changes or when the related person or organization is removed.
A coordinator can create work directly, request a follow-up while logging an interaction, or receive work created through an application process. The task can identify a related contact and organization and, for application work, a subject record in another part of Rhythm. A person can hold it, it can wait in a queue, or it can be offered to holders of a security role.
What It Is Not
A task is distinct from an activity. It tracks work and its closing decision rather than recording an interaction. The reminder for an overdue task is another presentation of its condition and grants no task authority. A workflow may create or close work, but the workflow step and its execution remain owned by the application process.
A queue and a role offer both route tasks, but serve different purposes. Queue routing shares work without asking Platform to evaluate the candidate role. An unqueued role offer asks Platform to confirm eligibility at claim time.
How It Is Used
Workers start with personal or shared views, inspect a task in its drawer and decide what to do next. Coordinators assign colleagues or place work in queues. Claiming reserves shared work for one successful requester when several people act together. Release makes work available again without discarding its queue place or retained role offer.
Completion and cancellation record deliberate closing decisions. Reopening restores editable work and clears the previous closing stamps. A stale screen cannot silently undo a newer closing action when the required version is supplied. Assignment remains weaker where callers omit a version, and valid-looking user references are not yet checked for workspace eligibility.
Its Facets
Classification and priority. Task types describe the kind of work, while priority helps staff distinguish urgency. The baseline catalog provides a starting point for customer configuration.
Status and closing attribution. Open, Waiting for someone else and Deferred remain work in progress. Completed and Cancelled close it. Closing attribution records actor and time, but does not provide a full history of all task edits.
Task and due dates. The task date supplies a calendar position. The optional due day supports ordering, timeline placement and overdue classification in the workspace calendar.
Holder and assignment. The holder identifies who has the work, with assignment actor and time supplying accountability. A service can perform an assignment without becoming the holder.
Queue and arrival. Queues are routing facets of Task. Their names, active settings and list order support customer teams. Each queued task retains its arrival time, which changes when it moves to another queue.
Claim, release and role offer. Shared reservation prevents simultaneous winners. A candidate role can remain after claim so release reoffers the task. The console does not yet provide role-offer discovery.
Responsibility. Queue responsibility supplies an overdue audience for unclaimed work when attention is enabled. Responsibility does not itself grant permission to claim or edit a task.
Subject and workflow origin. Related records provide context. A workflow creation reference prevents duplicate task creation; later workflow actions are evaluated from current task state rather than a retained delivery identity.
How It Relates
Related contacts and organizations place work on their timelines. Activity logging can create a follow-up. Platform security supplies role evaluation, responsibilities identifies shared oversight, attention handles overdue items, and workflow execution delivers service requests. The task remains CRM’s record through those collaborations.
What It Could Become
The product should decide whether tasks need complete revision history and how role holders discover offered work. It should settle inactive configuration behavior and finish assignment eligibility checks. Queue distribution and escalation need an actual contract before their current controls can be treated as product behavior. Live reminder delivery and workflow integration also require proof beyond the local task tests.