Request specialist help and review deliveries
LenGrowth supports a specialist delivery flow inside the task detail panel.
When to use this
Use the specialist flow when the task needs more than a simple status update. It is the right path if:
You need a human specialist to take over the work
The task is waiting on your reply
The specialist has delivered something and you need to review it
You want to post the actual delivery result before marking the task complete
You need to keep the work moving without leaving the task thread
If you only need to move a task between basic queue states, the task list or pipeline may be enough. If the work needs coordination, use the delivery panel.
Step-by-step
Inside the task detail panel, LenGrowth shows a "Delivery path" section. That section tells you whether the task is platform-led, specialist-supported, or waiting for a specific handoff. It also shows the current execution state, the assigned specialist, and what is expected next.
Depending on the task and your role, the panel can show different controls. You may see:
"Request Specialist"
"Claim Specialist Work"
"Accept Specialist Assignment"
"Update Specialist Status"
"Submit Result"
"Approve delivery"
"Request changes"
Not every user sees every button. The available controls depend on the task state, the current stage, and your role.
Open the task detail panel.
Look for the "Request specialist help" section.
Add an optional request note if you want to give extra context.
Click "Request Specialist".
The request note is optional, but it is useful when you want to explain the outcome you need, the deadline, or any constraints that should be respected.
After you submit the request, the task stays in the same workflow and the specialist delivery path becomes visible in the task detail panel.
If you are in a growth or admin role, the panel can also show assignment recommendations.
Open the task detail panel.
Read the "Assignment Recommendations" section.
Review the eligible candidates.
Look at the matched capabilities and the brief recommendation notes.
Click "Assign Specialist" when the right person is obvious.
In some cases, you may see other controls such as "Claim Specialist Work" or "Accept Specialist Assignment". Those actions appear when the workflow is already in a claimable or assigned state.
If there are blocked candidates, the panel tells you why they are not currently available. That helps you understand whether the issue is a capability mismatch or just current load.
Once a specialist is on the task, the delivery path can show the current stage and the next expected update.
Open the task detail panel.
Review the current "Execution state".
If you are allowed to manage the task, choose a new stage from "In progress", "Needs customer input", "In review", "Delivered", or "Completed".
Add a short update message if needed.
Add the next expected update text if you want the handoff to stay clear.
Click "Update Specialist Status".
This is the part of the flow that keeps the task thread useful. Instead of leaving the team to guess where the work stands, the stage and the next expected update make the current state visible.
If you try to mark a task as "Delivered" or "Completed" before a delivery result has been submitted, LenGrowth will tell you that the result still needs to be posted first.
When the task is delivered, the panel may show "Delivered for your review" or "Review this delivery".
Open the task detail panel.
Read the latest progress update and delivery notes.
Decide whether the delivery is ready to approve.
Click "Approve delivery" if the work is ready.
Click "Request changes" if something still needs follow-up.
If the task is waiting for customer review, the review buttons appear directly in the delivery section. That keeps the approval step in the same place as the delivery context.
If the task can be finished manually, the detail panel can show a "Submit result" button. When specialist delivery is involved, the button may read "Submit Result" or "Submit delivery result".
Open the task detail panel.
Click the result submission button.
Fill out the summary.
Add details if you want to explain what changed.
Add links or files if they support the outcome.
Choose whether the result should appear in the customer-facing task view.
Decide whether to save the work to Assets Hub or update an existing linked asset.
Submit the result.
The result submission dialog asks for:
Summary
Details
Links
Files
Customer-visible result toggle
Asset Hub options
If the task has a checklist, the dialog shows checklist progress too. If you try to complete the task before the checklist is done, LenGrowth will stop you and ask you to finish the checklist first.
The task detail panel includes an "Open discussion" action. Use it when the work needs a reply instead of a status change.
Open the task detail panel.
Click "Open discussion".
Reply in the thread with the missing context or the next decision.
This matters most when the delivery path shows "Needs customer input". In that state, the task is paused until someone replies in the discussion thread.
After you request specialist help, submit a result, approve a delivery, or request changes, LenGrowth updates the task state and keeps the task record in the same workflow.
You should expect:
The task card status to change
The delivery path to update
The discussion thread to record the new message or result
The task list and pipeline to reflect the new stage
If a task reaches "Completed", the specialist flow is finished, but the discussion and timeline remain available for review.
That can happen if the task is not in the right stage, if your role does not allow specialist management, or if your current plan does not include specialist support. In some cases, LenGrowth shows an upgrade card with a link to https://lengrowth.com/subscription instead of the specialist controls.
Open the discussion and respond there. The task can remain paused until the specialist gets the input they need.
The result submission dialog only allows one of those paths at a time. Choose either "Update an existing linked asset" or "Save to Assets Hub", not both.
Common problems
The review buttons only appear when the task is waiting for review. If the task is still in progress, you may need to wait for the delivery update first.
If the checklist is incomplete, completion is blocked. Finish the checklist items first, then submit the result again.
Related articles