Skip to content
Help Center
Submit a request Sign in

Plan and complete case work in Task Center

Tasks make the next action on a case explicit. Task Center brings work across cases into one place so a specialist can review their commitments and a lead can spot overdue dependencies. Each task belongs to a case; the case remains the source of customer context and communication. Task Center shows task details and actions. Use Open Case or Open Activity when you need the surrounding activity history.

At a glance

For: agents, specialists, team leads, and approvers. Applies to: Supportbench Core.

Start here: App header → Tasks → Manage Tasks → Task Center

Choose a useful Task Center view  ·  Create a task on the right case  ·  Manage the task through completion  ·  Write tasks that support customer commitments  ·  Track one specialist dependency from creation to completion  ·  Resolve task problems

Choose a useful Task Center view

  1. In the app header, select Tasks. This opens the compact Tasks drawer. Select Manage Tasks to open Task Center.
  2. Use My Day or My Open for your work; review Team Open, Overdue or Due Soon for upcoming customer commitments.
  3. Other available views include Approvals, Important, Pinned, Created by Me, Unassigned and Recently Completed. All Open requires additional permission.
  4. Open the task’s case or activity before acting. Confirm what the customer was told and whether a colleague already completed the dependency.
Task Center with My Open selected, task view navigation, Filter Tasks, Priority sort and No Tasks in this view.
Select the view that matches the work you need. This demo has no tasks in My Open while Overdue shows a separate count; an empty personal view does not mean no other tasks exist. Open this workspace from the header Tasks drawer using Manage Tasks.

Create a task on the right case

You do not need an existing Tasks tab to create the first task. A case with no tasks hides that tab. Start a task through the activity composer:

  1. Open the correct case. Review its Company, Contact, status, owner or queue, and the latest customer commitment. A task belongs to this case and must be understandable to someone who did not handle the original conversation.
  2. Select Activities, then New in the activity toolbar. If a Grab case prompt appears for a queued case, choose deliberately: Leave in queue retains queue ownership; Assign to me takes the case. Creating specialist work should not accidentally change who owns the customer response.
  3. Open Activity type and choose Task. Confirm that Task options appears and the final action reads Create task. If Task is unavailable, check your case access and activity-creation permission with an administrator.
  4. Write a specific Subject, such as “Compare the failed export with the last successful run.” In Message, record the evidence to use, the deliverable, and the checkpoint. For example: “Record the error message, product version and last successful export time. Compare the failed request with a successful request, then record the difference and next diagnostic step before the customer review.” Do not describe unknown facts as already confirmed.
  5. Review Task owner. Select the agent responsible for the deliverable, or deliberately choose -- unassigned -- only when your team has an agreed process for taking that work. Show all agents broadens the owner choices; it does not grant an agent access to the case. Use Task team when appropriate, and confirm the person can open the underlying case.
  6. Set Due date to the agreed checkpoint. Task due in offers relative intervals as an alternative; choose Use exact due date when entering a specific date and time. Review the displayed due value before saving. Leave enough time for the case owner to review findings and prepare the customer update.
  7. Use Approval required only when the work must follow your approval process. Approval tasks have different completion rules; do not enable it merely to mark ordinary work as important.
  8. Review To, Cc and Bcc. The composer warns that the activity stays internal in Supportbench but its contents and attachments will be emailed to the listed recipients. Internal visibility is not a promise that no email will be sent. Leave recipients empty when you do not intend that delivery, and check any files before attaching them. Assigning a task and addressing an email are separate decisions.
  9. Select Create task when the deliverable, ownership, due date, recipients and approval choice are correct. To abandon an example, select Cancel and confirm the cancellation; do not create a task merely to test the form.
  10. Verify the saved task on the case. The Tasks tab is available once tasks exist. Open Tasks → Manage Tasks from the app header, select the relevant Task Center view, and confirm the subject, owner, due date and state. The task must appear in a view that actually matches its assignment and status; an empty My Open view does not prove that no team tasks exist.

Creating tasks and basic complete/reopen actions require case access and permission to create activities. Reading a case or opening a task view does not grant permission to change its tasks. Task Center checks authorization for its actions separately.

A task can reopen a closed case

Creating a task on a closed case reopens it. Check that reopening is appropriate before selecting Create task. A task keeps follow-up work attached to the case lifecycle; it is not a detached personal reminder.

Task activity composer showing an export-comparison subject, empty email recipients, unassigned Task owner, Task team, Due date, Task due in and Approval required.
Task options are part of the new activity composer. This unsaved training example has no recipients and an unassigned owner to keep the illustration anonymous. Before creating real work, choose the responsible owner or agreed unassigned-work process, confirm the deadline, and review the email warning.

Manage the task through completion

  1. Read the task and its case context. Use the available actions to pin, rename or take unassigned work when permitted.
  2. Record material findings on the case or in the appropriate internal discussion. Keep the task description focused on its deliverable.
  3. Complete the task after the deliverable is done, then verify its state. Reopen it only when further work is needed and that action is available.
  4. Use the configured approval process for approval-required tasks. They cannot be completed or reopened through the normal agent actions.
  5. Send a separate customer update when needed. Completing a task does not itself confirm that the customer received an update.

Write tasks that support customer commitments

Unclear taskActionable task
Check integrationCompare the failed webhook payload with the last successful delivery and record the request IDs before Thursday’s customer update.
Ask billingConfirm the contracted support tier with the account team and record the answer on the case.
Follow upContact the customer’s deployment lead after the maintenance window and record whether the service recovered.

Use a task scenario for a repeatable set of tasks. Administrators configure those reusable sets separately; Task Center is where agents work the resulting case tasks.

Track one specialist dependency from creation to completion

A customer needs an answer after a maintenance window, and a specialist must compare two request examples first. A task should describe that deliverable and when it is needed, while the case keeps the wider customer conversation.

  1. Open the correct case and review its current status and owner. If it is closed, decide whether reopening is appropriate: creating a task reopens a closed case.
  2. Select Activities → New, choose Task as the Activity type, and write a concrete deliverable, such as “Compare failed and successful export requests and record the difference before the customer update.” Include the evidence location. The Tasks tab may be absent until the first task exists.
  3. Set Task owner, the appropriate Task team and the agreed Due date. Make the due time support the actual customer commitment rather than simply copying the end of the day. Review approval requirements and email recipients, select Create task, and verify the saved task on the case.
  4. Open Task Center and the appropriate personal/team view. Confirm the task appears under the intended scope and that the responsible colleague can access the case.
  5. When the work is performed, record material findings on the case or appropriate internal activity. Complete the task only when the deliverable is done. Approval-required tasks follow their separate approval route.
  6. Send the customer update through the case’s communication workflow. Completing the internal task does not prove that the customer was told. If new work is needed, reopen the task only when permitted or create the appropriate new action.

Pinning a task helps you return to it; it does not change the customer promise. If a task is blocked, record the dependency and next checkpoint. Marking it complete merely to clear an overdue list hides the work from the team.

Resolve task problems

ProblemCorrection
The Tasks tab or Create task is missingA case with no tasks hides the Tasks tab. Start at Activities → New and choose Task in Activity type. If those controls are unavailable, check case access and activity-creation permission.
A task is absent from a viewCheck owner, due date, completion or approval state, selected view, any Filter Tasks text and access to the related case. A task assigned to a colleague need not appear in My Open; select the appropriate authorized team or other view.
Completion is unavailableCheck approval requirements, current task state and case permissions.
An overdue task is blockedRecord the dependency and next checkpoint; do not mark the deliverable complete merely to clear the overdue list.
A closed case reopenedTask creation reopens a closed case. Review the customer commitment and resulting case state.

Was this article helpful?