WTask

All of your team's work in one panel: WTask

WTask is the team work management module of the WApps business management ecosystem. Tickets, tasks and the daily board live in one place, so who owns a piece of work, what stage it is at and how long it took are all visible on one screen. Add WSupport when you want to give your own customers a portal that feeds straight into this flow.

Start your 30-day free trial

Web based·One WApps account·8 key outcomes·Page updated: 25 July 2026

Product video1:33

Interface previewWTask / WApps

15-second product tour

Collect your team’s work in one shared queue, see status, priority, customer and owner, then move it through resolution from the panel.

Interactive mini demo

Try it now:Open the “Payment page will not open” ticket and mark it as resolved.

Support operationsSearch…

Tickets

Manage and track tickets

All 18Assigned to me 6Awaiting reply 4Priority 3

Search tickets…Status Priority

TicketPriorityStatusAge

Core workflow

How does WTask work in three steps?

Who uses it?: Team leads, operations and support teams
What goes in?: Work item, customer/brand, priority, status and assignee
What becomes visible?: A current ticket list or Kanban workflow

01
Queue the work
Add the incoming request or new task to a queue the whole team can see.
02
Give it an owner and a priority
Keep status, priority, brand and assignee current on the record.
03
Close it and measure
Mark completed work and keep open workload and time spent current.

What is WTask?

WTask is a web-based work management tool that brings team tasks and tickets into one panel. Tasks, tickets and the daily board live together, so an item's owner, its stage and how long it has taken are visible on one screen. It is part of the WApps suite and pairs with WSupport when you want to give customers their own request portal.

Problem and approach

What WTask handles — and what it doesn't

WTask owns making a team's work visible: opening tickets and tasks, assigning them, moving them through states you define, breaking them into subtasks, logging time spent, tracking them on a daily board and putting repeating work on a schedule. What it does not do is equally clear: it does not give customers a portal (that is WSupport), build proposals (WProposal), issue invoices (WFinance) or manage leave and shifts. When customers need to see the request themselves, you run WTask together with WSupport.

Every piece of work has an owner and a stateA daily board instead of a status meetingTime spent is measured

Impact on the workflow

Every piece of work has an owner and a state

Tickets and tasks land in one queue, get assigned to a team member and move through states you define yourself — you name, order and colour them. Nothing goes unowned.

A daily board instead of a status meeting

The team starts the day with a shared board showing who is finishing what. The status meeting is replaced by looking at the board.

Time spent is measured

Each ticket takes time entries recording how long it took, who worked on it and on which date. The hours allocated to a customer each month become comparable against the hours actually spent.

Implementation notes

Tickets, tasks and a daily board

Work is opened as tickets and tasks inside the product, then assigned, prioritised and tracked on the daily board, whose previous days are retained.

Your own status flow

You define ticket statuses yourself: name, colour, order and which stage group (open, in progress, completed) each belongs to.

Time logging

Time entries are added to each ticket, storing duration, description, date and user together. Monthly allocated hours are held on the customer record.

Task templates and recurrence

Frequently repeated work is defined as a template; a weekly or monthly recurrence produces tickets automatically and keeps the next run time.

From WhatsApp to ticket

A WhatsApp connection is built in; direct messages and messages from configured groups can be converted into tickets, with the source message kept on the ticket.

Continue exploring

Frequently asked questions

01What is the difference between WTask and WSupport?

WTask is the panel your team works in and is billed per user. WSupport is the panel your customers log into and is billed only per customer portal you open. WTask works perfectly well on its own.

02Can we add people from outside the team?

Everyone you add to WTask is a user. If you want your customers to follow their own requests, you open a WSupport portal for them instead of adding them as users.

03Which channels can we collect requests from?

Next step