Working a Task
How to read the queue, claim work, send outreach, and record what happened.
The work queue
The Growth workspace opens on the work queue, a table (or, on a phone, a stack of cards) of every open task, sorted with overdue items first and then by due date. Each row shows:
- Client opportunity: who it's for, why the task exists, and what type of workflow generated it.
- Status: the task's current status, explained in full in Task Status and Lifecycle.
- Owner: the role or specific person responsible, or "Generated by Nabu" if it's automated.
- Due: when the task is due, highlighted if it's overdue.
- Value: the estimated value of the opportunity.
- Action: a button that opens the task, labeled with whatever's actually left to do next.
Above the table, quick view tabs let you narrow the list to My tasks (claimed by you), Due today, Overdue, Next 7 days, or Waiting (anything sitting in Waiting for client or Follow-up scheduled). A search box and a filters panel let you narrow further by workflow type, assigned role, priority, channel, or minimum value.
Claiming and releasing
Any task assigned to a role, rather than a specific automated send, can be claimed. Claiming puts your name on it and moves it from Not started to Claimed, so the rest of the team knows you've got it. If two people try to claim the same task, Nabu only lets one of them through, so you never end up with two staff members reaching out to the same client at once. If you claim something by mistake, or need to hand it off, releasing it puts it back to Not started so someone else can pick it up.
Opening a task
Clicking anywhere on a row or card opens the task. What you'll see:
- Why this task exists: a plain-language explanation of what triggered it, written for a person, not a summary of raw data.
- Recommended action: the suggested channel, plus a suggested message for SMS, or talking points for a phone call.
- Email, if the task's channel is email: a full composer with a subject line, body, and your location's signature attached automatically, so what you see is exactly what the client will receive. You can preview it as the client will see it, or switch to edit it directly.
- Record outcome: where you log what actually happened.
- Client context: last visit, last service, provider, whether they have a future appointment, and lifetime value.
- Activity history: a timeline of every outreach attempt and status change on this task.
On a wide screen, the client context and activity history sit in a column on the left, and the action (the email composer, the SMS script, the outcome form) takes up the wider column on the right, so you have real room to work instead of a cramped box.
Sending an email
If a task's channel is email and nothing has been sent yet, you'll see a composer with a suggested subject and body already filled in. You can send it as written or edit it first. Before sending, check the preview: it shows the body and your signature together, exactly as the client will receive it. Once you send it, the task automatically moves to Waiting for client, the opportunity stays open, and there is nothing further to review, only a reply to wait for and eventually log (see Task Status and Lifecycle for why Growth can't detect that reply on its own).
Some tasks require review before sending, particularly ones referencing a specific price. On those, you'll see a note explaining why, and you're expected to read the draft before it goes out rather than send it blind.
Recording an outcome
Recording an outcome is how you tell Growth what actually happened, and it's the only thing that closes a task and updates the underlying opportunity. Options include: the client booked, declined, or wasn't reached; you left a voicemail or spoke with them directly; they asked to be followed up with later (you'll be asked for a new date); their contact information was wrong; the situation should be escalated; or the client asked not to be contacted again. Each one is deliberately specific. Growth doesn't offer a generic "done" checkbox, because "done" doesn't tell anyone, including you next month, whether the outreach actually worked.
Do-not-contact
If a client has an active do-not-contact flag, the task modal shows a clear warning, the suggested SMS and email actions are disabled, and the only thing you can meaningfully do is review the situation or confirm the flag in the outcome form. This check runs automatically on every task, regardless of workflow or channel.