Notifications

Told once, in both places.

Task assignments, comments, Slack mentions, and finished reports all run through a single call that writes the in-app notification and fires the browser push together — so one can never show up without the other.

dispatch path
1dispatch path
trigger types
4trigger types
destinations
2destinations

Triggers

  • Task assigned
  • Task commented
  • Slack mention
  • Report ready
notify_user()

RESK · now

Chrome

Task assigned to you

Confirm scope with Dana Ruiz — Harborview Logistics

Notifications

4

Priya assigned you “Confirm scope with Dana Ruiz”

Task assignedIn-app + push

2m ago

You were mentioned in #harborview-onboarding

Slack mentionIn-app + push

18m ago

Weekly report drafted for Northwind Retail Co.

Report readyIn-app + push

1h ago

Marcus commented on “Import driver roster”

Task commentedIn-app only

3h ago
How it works

The path a record actually takes.

  1. 01

    Something happens worth knowing

    A task is assigned or commented on, you are mentioned in Slack, or a project report finishes.

  2. 02

    One call handles it

    Every trigger funnels through the same function, rather than each one remembering to notify on its own.

  3. 03

    Both destinations, together

    The notification row is written and the browser push is dispatched in the same step. Neither can exist without the other.

  4. 04

    It opens the record

    Clicking a notification marks it read and takes you to the task or project it came from.

What you get.

Single dispatch

One implementation every trigger calls, so the two channels cannot drift.

Browser push

Delivered through a service worker, so it reaches you with the tab closed.

In-app inbox

Scoped to you, with unread counts and mark-all-read.

Slack mentions

Being mentioned in a project channel reaches your RESK inbox too.

Task events

Assignment, status change, and comments each notify the right person.

Report ready

You are told when a draft is waiting on your approval.

Keep going.

Projects & tasks

Built automatically the moment a lead is won.

Read more

AI reports

Drafted from real project state, approved by a human.

Read more

Roles & visibility

Module gates and row-level scope on every request.

Read more
Start hereYour next won deal

Never rebuild the same project twice.

We set up your workspace and your first admin. Your team joins by invite, and the next deal you close arrives as a project that is already moving.

  • We set up your workspace
  • Your team joins by invite
  • Bring the pipeline you have

Prefer to talk first?

  1. Deal marked Closed/Won

    One status change

    01

  2. Project, milestones, 5 tasks

    Drafted from the conversation

    02

  3. #harborview-onboarding

    Channel opened, kickoff posted

    03

  4. Owner notified

    In-app and browser push

    04

Every step above runs from one status change.