Boni Tasks
Give work an owner, deadline, source and completion evidence; connect subtasks, dependencies and existing AI chats.
Canonical work queue
Boni Tasks is the durable place for work that must survive a chat or agent session. A task can carry an owner, status, due date, function, checklist, source references, related customer or project, and completion evidence.
Use Tasks when
- a person or agent owns a next action;
- a commitment has a due date or follow-up;
- a workflow needs visible retry, blocked, or completed state;
- CRM, Calendar, Accounting, or another module needs one shared work item instead of a private reminder.
Find and review your work
Open My work to review assigned tasks and follow-ups. Use + Task for work that needs an owner and completion evidence, or + Follow-up for a next contact or check.
Where your workspace permits it, All tasks shows the wider team's work. Filter by status, priority, category or owner, and search for a specific task. Switch between List and Calendar to see work by its due date. The view follows your access; it does not give you access to another workspace.
Clear an overdue backlog
Choose Clear backlog to review one task at a time. Mark it Done only when the work is actually finished. Otherwise choose a realistic date, Still on it, Drop or Skip. Dropping work is a deliberate decision, not evidence that it was delivered; moving its date does not complete it.
Answer a question without taking over the work
When a task shows What it needs from you, read the specific question or approval needed. If an answer is requested, use Send answer & unblock to save your reply and return the task to the work queue. Answering a question is not completion of the task, and it does not replace a separate payment, sending or access approval.
Assistant actions
The Assistant can list, create, and update Tasks when the current workspace grants those actions. It should ask for the exact task when a request is ambiguous and preserve the source context that explains why the work exists.
Calendar events and Tasks can be connected without becoming duplicate sources of truth: Calendar owns time; Tasks owns the durable work state.
Related work, subtasks and AI chats
Use Work and sessions to split independently tracked work, link dependencies and associate existing AI chats. Related Tasks, subtasks and AI chats explains the controls and the difference between Task state and execution state. Linking does not start an agent or share private conversation content.
For measurable business targets and source-backed results, use Planning, goals and KPIs. Completing work does not by itself update a business result.