Skip to main content

Tasks

design

Overview

A task is the representation of an asset and its state.

In general, a task is something that someone has to do but can be much more than that.

✏️ The Cotalker platform, digitalizes a real-life task or asset and places it within a lifecycle or process.
♺ This lifecycle or process is known in Cotalker as a workflow.
🪜 Each step of the process or workflow is called a state.

Here are just some examples of tasks and their possible states within a workflow:

Asset/TaskStates
AssignmentOpen, Closed
Job postingScouting, Interviews, Position Filled
ClientLead, First Meeting, Deal Closed
IssueOpen, Verified, Fixed
ContactPending, Responded
MachineWorking, broken, At maintenance
StoreGood, Average, Bad
info
  • Tasks are created within task groups.
  • Every task group is the representation of a workflow group.
  • A workflow group can contain one or more workflows.

Example

In the image below, tasks are displayed in kanban view, one of the many forms to view tasks in Cotalker:

task manager

The image above displays the tasks that were created in a specific workflow. The tasks are sorted according to the state or status they are currently in. This workflow was configured with three states: backlog, doing, and ready.

Features

  • Users can access tasks to view and interact with them.
  • Users can create tasks.
  • Tasks can be filtered and sorted in the display.
  • The task workspace includes:
    • Files: Displays shared files and notes. Notes can also be edited from here.
    • Chat: Accesses the chat area which displays user and system messages, survey forms, and shared files.
    • Details: View and edit task settings.
  • Tasks count with different levels of user access.
  • Automations can be set to create or update tasks through survey forms or bots.
  • Automations associated with tasks can carry out a vast amount routines enabling companies to automate entire processes.
  • Start and end dates along with SLAs can be configured on a task to give programmed responses or notifications according to established deadlines.

This amplitude of functions gives tasks the versatility to adapt to each organization's needs and beyond.

info
  • To view or modify a task, users must be associated with the task and count with the corresponding permissions and task roles.
  • Admins can set permissions that allow unassociated users to follow or edit tasks within a task group.


  • Step-by-step tutorials: