What is the difference between Notes and Tasks in Sonar?

Notes document context on the account; Tasks capture action items with owners and due dates. Both live on the subscriber record, so the next agent picks up where the last one left off.

Can account changes happen automatically on a future date?

Yes. Scheduled Events queue changes like plan upgrades, status changes, and address moves to fire automatically at a later date, which reduces manual cycle-end work.

How do Task Templates help field work?

Task Templates apply defined objectives to jobs with modifiable parameters per job type, so technicians always know what a completed job requires.

Does Sonar keep an audit trail of completed work?

Yes. Tasks log against the account with ownership, timestamps, and completion notes, which also lets onboarding reference real completed work instead of tribal knowledge.

Sonar 2026 · Tools · Tasks

TASKS

Notes. Templates. Scheduled events.

Account-level tasks, Task Templates for Jobs, and Scheduled Events that run on their own.

Book a meeting Watch the Platform Tour

Tasks

IncompleteComplete

TaskTask GroupEntityDue DateUser

Complete ▾

Follow-ups slip without a record

Action items in spreadsheets and inboxes go missing. Tasks tied to records do not.

Verbal follow-ups.

Agent says 'I'll follow up.' Then they don't, because there's no record.

Tribal knowledge dependencies.

When the person who knew the workflow leaves, the workflow leaves with them.

Manual cycle changes.

Plan changes scheduled for next month live in someone's calendar, not the system.

Capabilities

Notes, templates,
and timed events.

Sonar's task-related features live across modules: account-level Notes & Tasks, Task Templates applied to Jobs, and Scheduled Events that automate timed account changes.

Notes and Tasks tied to the subscriber record.

Notes and Tasks at the account level document communications and capture action items. Tied to the subscriber record so the next agent picks up where the last one left off.

Account-level Notes for context
Account-level Tasks with due dates and assignees
Visible to the next agent on the account

Account-Level Tasks’s flow

From follow-up needed to closed loop

01
Note captured
Agent logs the call or context against the account.
Accounts
02
Task created
Action item assigned with due date.
Tasks
03
Task completed
Owner closes the task with resolution notes.
Tasks
04
Timeline updated
Completion shows on the account record.
Accounts

A documentary photograph that captures the operational reality behind Sonar's TASKS module.

Inside TASKS

Verbal follow-ups.

Frequently asked

Common questions about tasks.

What is the difference between Notes and Tasks in Sonar?: Notes document context on the account; Tasks capture action items with owners and due dates. Both live on the subscriber record, so the next agent picks up where the last one left off.
Can account changes happen automatically on a future date?: Yes. Scheduled Events queue changes like plan upgrades, status changes, and address moves to fire automatically at a later date, which reduces manual cycle-end work.
How do Task Templates help field work?: Task Templates apply defined objectives to jobs with modifiable parameters per job type, so technicians always know what a completed job requires.
Does Sonar keep an audit trail of completed work?: Yes. Tasks log against the account with ownership, timestamps, and completion notes, which also lets onboarding reference real completed work instead of tribal knowledge.

Explore related