Use Agent and Manual Workbenches

#Two workbenches separate AI collaboration from manual operations

Affiliate provides two workbenches with different purposes:

• Agent Workbench: handle the points where AI work needs a person and inspect the full Agent work record. It contains Pending review, Pending, and All Agent work.
• Manual Workbench: centrally process Shop back-office tasks that belong to people from the start. It contains Sample Applications and Creator messages.

This separation keeps three cases distinct: an action caught by an Approval Policy enters Pending review; an issue actively escalated by the Agent enters Pending; work for protected Creators or Human-only BDs bypasses AI and is handled by staff in the Manual Workbench.

#First, distinguish review from handling

Both tabs require a person, but they represent different kinds of human work:

Concept	Trigger	Workbench tab	What a person does
Review an Action Proposal	The Agent submits an action normally, then the system finds a matching policy	Pending review	Approve, reject, or request a revision to that action
Handle an Escalation	The Agent recognizes that the issue exceeds its capability, tools, or authority and actively escalates it	Pending	Take over the issue, make the decision, or complete the work the Agent cannot do

The short version is: review a Pending Proposal; handle an Escalation. Review is not an Agent request for help, and handling is not simply approving an already-prepared action.

#Agent Workbench

1. Pending review: review an Action Proposal

This tab contains operations the Agent has already decided and submitted for execution, but the policy system has held as Action Proposals. The item might be a message, a Sample application decision, a tag change, or a “no action needed” decision.

Account-level policy determines what enters this queue. The Agent does not decide whether a policy matches and does not need to know that review will be required. After the Agent submits the action, the system independently checks the Safety Policies under Team & Channels. A match holds the Action Proposal under Pending review; without a match, the operation can execute automatically.

Review in this order:

1. Subject: confirm Creator, Product, Shop, and Campaign.
2. Evidence: compare the Agent’s reason with relationship history, Product Knowledge, and application data.
3. Action scope: verify that the message, benefit, Sample decision, or tag is authorized.
4. Language and risk: check for unsupported promises, sensitive wording, or incorrect facts.

Approve when the action is ready, reject it when it should not run, or request a revision. This queue asks a person to review a prepared Action Proposal—not to handle the entire Creator case from the beginning and not to respond to an Agent escalation.

Review a Sample action

When policy holds a Sample action, open the proposal to compare the Agent recommendation with the application, Creator performance, and relationship context.

APP CAPTUREThe English light-theme Sample action review with the Agent recommendation and evidence beside the human decision controls.

Samples have real cost. Check Product fit, previous publishing and order performance, the current Campaign offer, Sample Tier, Manual Tags, and protection rules. Approval continues the prepared Sample operation; rejection records the human decision and ends that operation.

2. Pending: handle an Escalation

Pending is comparable to an AI Customer Service escalation. The Agent recognizes that the issue exceeds its current capability, tools, or authority, so it actively creates an Escalation and asks a person to take over.

For example, if a Sample is lost in transit, someone may need to decide whether to reship, create new fulfillment, or coordinate directly with the Creator. The Agent can organize the context and hand off the case, but it cannot perform an unauthorized reshipment on its own.

APP CAPTUREThe English light-theme Affiliate Pending list with open items that require human intervention and their related context.

To handle one:

1. read the Agent’s reason and the Creator, Shop, and collaboration context;
2. perform the manual operation or supply the decision required for this case;
3. record the result and close the item;
4. when the issue repeats, add reusable guidance to Business Instructions, Product Knowledge, or policy.

Unlike Pending review, there is no prepared action waiting to run after a simple approval. A person must understand the issue, make the decision or perform the actual operation, then record the outcome and resolve the Escalation.

3. All Agent work: inspect the full work record

This tab aggregates Agent work across states and supports filtering by owner, status, type, or search. Use it to audit approved, executed, rejected, ignored, or expired actions and to reconstruct what happened for a Creator or Campaign.

It is not a duplicate of Pending review. Pending review contains only Pending Proposals currently waiting for a human decision; All Agent work provides the broader history. It is not another manual task queue.

#Manual Workbench

The Manual Workbench brings human-owned back-office tasks together across Shops. These tasks do not indicate that AI is running, and they are not Agent Escalations. Viewing or processing them does not start Agent work.

1. Sample Applications

This tab directly aggregates Sample applications that still need manual handling across Shops. A Sample can be reviewed here even when the Agent did not discover or advance it.

Before acting, check Product, Shop, expiry, Creator performance, and current platform state. Approve, reject, or ignore updates the real Shop back-office workflow.

2. Creator messages

This tab directly aggregates Creator messages that need a human response across Shops, allowing a multi-Shop team to work centrally instead of opening each Seller Center.

APP CAPTUREThe English light-theme Creator messages list with replies, related Shops, and current handling state.

When product facts are incomplete, update Product Knowledge first. When a Creator asks for commission, Samples, or terms outside the authorized offer, an owner should handle the request within the business boundary.

#Open Creator Relationship when more context is needed

A single work item shows one moment. For a costly Sample, long-running collaboration, reshipment, or unusual request, open Creator Relationship to inspect cross-Shop interactions, Campaigns, Samples, Collaborations, and Timeline.

APP CAPTUREThe English light-theme Creator Relationship timeline combining messages, Samples, Campaigns, and work history.

Relationship history provides evidence; it is not a sixth queue. After making the decision or completing the manual action, return to the Workbench and update the current item so it does not remain pending indefinitely.

#Recommended daily order

1. In Agent Workbench, handle Pending Escalations that block Samples, fulfillment, or collaboration commitments.
2. Complete Pending Proposals under Pending review that affect real operations.
3. In Manual Workbench, clear Sample Applications and Creator messages.
4. Use All Agent work to investigate anomalies or verify AI work history.
5. Feed recurring decisions back into configuration so the Agent-to-human boundary becomes clearer.