Assign work to the first teammate matching a short name.
Agents and MCP / Task assignment reviewers
Before / afterResolve a workspace member before proposing ownership
Use member discovery to distinguish a unique intended teammate from similar names before a task ownership proposal.
People discovery resolves identity; it does not establish availability or permission to assign work. Keep an ambiguous name unresolved until the intended person is confirmed.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Compare the decision quality
Illustrative before / afterIllustrative case: two teammates share a first name, and an agent suggests assigning a task from a chat message.
Resolve the intended member, confirm responsibility and review the task proposal before a write.
Discover candidates
Owner role · Agent
Evidence: tb_search_people returns candidates in the authenticated workspace.
Clarify the intended person
Owner role · Requester
Evidence: The correct member is identified without guessing from name similarity.
Confirm responsibility
Owner role · Task lead
Evidence: The actual teammate agrees to the bounded work and timing.
Decision to make: Resolve the intended member and confirm responsibility before any write call.
Filled illustrative planning example
Invented planning text. Adapt it to your evidence and confirmed owners.
Synthetic candidates: Alex in release operations and Alex in interface design. Request: review the release recovery evidence. Context identifies the operations colleague; that colleague must still confirm responsibility and timing. Discovery performs no assignment.
Put the outline to work
- Read member candidates in the authenticated workspace without selecting by list position.
- Use relevant role or project context to ask which candidate the requester means.
- Confirm the bounded work with the actual teammate and review the exact ownership proposal before any separately authorized write.
From a useful outline to team work
Explore TeamBoostAI for your team
Use this manual outline alongside scoped TeamBoost task or people discovery. Confirm the authenticated workspace and requested action; discovery does not authorize a product write. Confirm the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Questions about this workflow
Does people search assign a task?
No. It is discovery; task writes have a separate purpose and authorization.
What if the name is ambiguous?
Ask with the returned candidates rather than choosing the first match.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.