Skip to content
Notifications

People find out about work without being chased

Every workspace has a notification centre in the app, switched on from the first day with nothing to configure. WhatsApp is a second channel you can add for people who are not at a screen. The record of the work stays in TaskIt either way.

No card required. Free for 30 days.

The problem

Work gets assigned and nobody knows it happened

Assignment and telling someone about it are usually two separate acts, and the second one is the one that gets forgotten.

  • A task is raised on Friday afternoon and discovered on Tuesday, because nothing told anyone.
  • The manager becomes the notification system — a message per assignment, sent by hand.
  • Work handed to a department sits unclaimed because none of the eligible people were told it exists.
  • A task quietly goes past its due date and is found when a customer asks about it.

How TaskIt handles it

Two channels, one record, no manual chasing

A notification is raised by the event itself, so telling people is part of the action rather than a thing to remember afterwards.

  • In-app: a bell with an unread count, a full notification history, and each entry linking to the task it is about.
  • Each notification arrives as it happens over an authenticated live connection — no refreshing, no polling a list.
  • WhatsApp: an optional module that sends task alerts and scheduled reports from your own paired number.
  • Both channels point at the same task. Nothing is decided in a notification; the record stays in TaskIt.
What changes

What you get

Every workspace is notified out of the box

The in-app centre needs no add-on, no gateway and no configuration. A workspace that never buys the WhatsApp module still tells people when work is assigned to them, handed to them, completed, or waiting for their review.

The alert and the work are one click apart

A notification opens the task it refers to, rather than telling you something happened and leaving you to search for it. Reading the notification and acting on it are the same journey.

A channel for people who are not at a desk

Field staff, drivers and shop-floor teams do not watch a web app all day. WhatsApp reaches them on the application they already have open, while the system of record stays in TaskIt.

Unread is a queue, not a feeling

The bell carries a count, the history has an Unread filter, and mark-all-read clears it in one action. What you have not yet dealt with is a list you can work through.

Step by step

How it works

In the order a person using it meets them.

  1. 1

    Nothing to switch on in the app

    In-app notifications are part of every workspace from the first sign-in. Each person sees only their own: notifications are stored per user, and the list is scoped to the signed-in person.

  2. 2

    Read them from the bell or the full page

    The bell shows recent notifications with an unread count. The Notifications page lists the full history with an All or Unread filter, mark-all-read, and the ability to delete your own entries.

  3. 3

    Add WhatsApp if you need it

    Pair your own WhatsApp number, choose which events send and to whom — the assignee, a group, or both — and edit the message templates. It is a paid module after the trial, so a workspace that does not need it does not carry the cost.

  4. 4

    Let the reports go out on their own

    On top of event alerts, a scheduled daily, weekly or monthly report can be sent over WhatsApp, with a preview, a test send and a delivery history.

Worked example

A Friday afternoon job that used to be found on Tuesday

A services business with twelve office staff and six engineers in the field. Nobody has bought the WhatsApp module yet.

  1. 1

    Friday 16:40 — raised for a department

    A customer reports a fault. The coordinator raises it for the service department rather than naming an engineer. Every eligible member is notified in the app.

  2. 2

    Friday 16:41 — claimed

    An engineer accepts from his phone. The other eligible members see the task move to claimed on their own screens without refreshing, so nobody drives to the same job.

  3. 3

    Monday 09:10 — reviewed

    Work is submitted. The coordinator gets a review notification, opens the task from it, and approves.

  4. 4

    Later — WhatsApp is added

    The engineers ask to be told on WhatsApp instead of opening the app. The module is switched on, delivery is set to the assignee, and the in-app centre keeps working exactly as before.

The result

Nobody was chased. The Friday job was claimed on Friday, and the only thing that changed later was which screen the alert appeared on.

What actually raises an in-app notification

These are the events that create one today. The list is deliberately finite: a notification for everything is a notification for nothing, and an unread count nobody trusts gets ignored within a week.

  • A task is assigned to you, or raised for a department you belong to
  • A task is handed over to you, or someone accepts, joins or leaves a department task you are eligible for
  • The task’s creator adds a note for you, or a task is completed
  • Work is waiting for your review, and a task of yours goes overdue
  • A recurring schedule is created, paused, resumed or disabled — and separately, if one exhausts its retries and stops
  • Trial, renewal, payment and expiry notices, which go to the people responsible for the subscription

Live, not polled

The app holds an authenticated connection to the server for as long as you are signed in. A notification is pushed down it the moment it is created, so the bell updates and the alert appears without the page being reloaded. The same connection keeps the task views current — see below.

In-app and WhatsApp carry different amounts

They are not two copies of one feed, and it is worth knowing which is which before you decide whether you need the module.

  • In-app covers the full event list above, for every workspace, at no extra cost
  • WhatsApp covers task creation, handover, completion and reopening — each one switchable — plus deadline alerts, a daily list of each person’s pending tasks and scheduled reports
  • WhatsApp messages are built from templates you edit, and can carry a link that opens the task
  • Account-security codes and billing notices are sent whether or not the WhatsApp module is bought: recovering a locked-out account is not a paid feature

Who can see what

A notification is addressed to a person, stored against that person, and readable only by them. Deleting one deletes your own copy. Nothing in the notification system widens what someone may see: opening the task it points at still passes the same permission check as any other visit, and a person without access to that task sees that they do not have it.

What each channel carries
In the appOn WhatsApp
IncludedEvery workspace, no configurationOptional paid module after the trial
Task assigned or raised for your departmentYesYes, when task creation is switched on
Handover to youYesYes, when handover is switched on
Task completedYesYes, when completion is switched on
Work waiting for your reviewYesNot sent
Deadline coming up, or overdueYes, when overdueYes, as configurable task alerts
Department claim, join and leaveYesNot sent
Recurring schedule paused, resumed or failedYesNot sent
Scheduled summary reportNot sentDaily, weekly or monthly
FAQ

Frequently asked questions

No. Every workspace has an in-app notification centre with no add-on and nothing to configure — assignment, handover, completion, reviews, overdue work, department claims and recurring-schedule events all raise one. WhatsApp is an optional second channel for people who are not at a screen.

Yes. While you are signed in the app holds an authenticated live connection to the server, and a notification is pushed down it as soon as it is created. The bell and its unread count update in place.

Yes. Task creation, handover and completion are each switchable, and one workspace setting decides whether they go to the assignee, a WhatsApp group, or both. The message wording comes from templates you edit. In-app notifications are not configurable in the same way — they cover the full event list and are part of the product.

No. A notification is addressed to one person and stored against them, and opening the task it points at runs the same permission check as any other visit. Someone without access to that task is told they do not have access.

No. TaskIt notifies in the app, and on WhatsApp if you add that module. Email is not a notification channel in the product today, and the site does not claim one.

Yes. Individual notifications can be marked read or deleted, and mark-all-read clears the unread count in one action. The Notifications page also filters to unread only, so the list can be worked through as a queue.

Keep reading

Where to go next

The capabilities either side of this one, and the problems it is bought to solve.

Stop being the notification system

Raise a week of real work and see how much of the chasing disappears when assignment tells people by itself.