Tasks and notes

Tasks and notes keep the work next to the customer. A task says what has to happen and by when; a note records what was said or decided. Both attach to records, so the next person picks up exactly where you left off.

Tasks#

Open Tasks from the sidebar for everyone's to-dos, or the Tasks tab on any record for that record's. A task carries:

Create one with New Task: type a title, then add a due date, assignees and a linked record. Switch on Create more to add several in a row.

Tasks written by workflows#

Most tasks shouldn't be typed at all. In the demo brokerage, workflows create them when:

• a claims case breaches its SLA — SLA breached on Claims Saathi: case assessment;
• a customer's KYC is about to expire;
• a telecalling callback falls due today;
• a renewal is 90 days out.

Each one lands on the right person's list with a due date and a link back to the record. Nobody has to remember to remember.

Notes#

Notes are freeform text on a record: what the customer said, what was agreed, what's blocking. Tag them — escalation, kyc, renewal — and they're easy to find in the Notes view, which lays them out as cards with author and time.

In the inbox, internal notes sit between messages in a conversation. The customer never sees them; your teammates always do.

Through the API#

Tasks and notes live under /docs/api/tasks and /docs/api/notes. Create a task:

POST /api/v1/tasks

{  "title": "Send renewal quote to Ananya",  "text": "Family floater — include her mother.",  "status": "Todo",  "priority": "High",  "dueDate": "2026-09-18",  "assignees": ["USER_ID"]}

Update one with PATCH /tasks/{id} (same fields), and list with GET /tasks, paged with limit and cursor. A note is created from its text: POST /notes with { "text": "…" }.

Reading needs tasks:view or notes:view; writing needs tasks:use or notes:use.