Affiliate and Creator Management overview

#How Affiliate works

TK Copilot Affiliate is not a bulk-message tool. The Agent continuously discovers and evaluates Creators, prepares outreach and follow-ups, organizes replies, and advances collaboration. Your team defines product facts, business goals, and authority boundaries, while retaining the final decision on important actions such as Samples and external commitments.

WORKFLOWThe complete Affiliate workflow from Campaign outreach or direct Creator contact, through one-BD ownership, to AI and human workbench routing. It distinguishes policy-held Pending Proposals, Agent-created Escalations, and staff-owned work for protected Creators or Human-only BDs.

The three human paths in this diagram are intentionally different: a policy match sends an operation to Pending review; an issue the Agent knows it cannot handle becomes an Escalation under Pending handling; protected Creators and Human-only BDs bypass AI and go directly to the Manual Workbench. The sections below explain where each boundary is configured and what staff do next.

The operating loop has five parts:

1. Product Knowledge supplies product facts, Q&A, and creative direction.
2. Campaigns define what to promote, whom to find, and what offer is available.
3. The Agent performs discovery, evaluation, message preparation, and follow-up.
4. Approval Policies and Agent Workbench determine which AI actions can run automatically and which must wait for a person.
5. Creator Relationships and Analytics preserve outcomes so the team can improve the rules.

If the Shop is not yet Authorized and enabled, begin with Shop Management. To prove one minimum loop first, follow Affiliate quick start.

#1. Configure the Shop runtime

Open Shops, select the Shop, then choose Affiliate. The top of the page shows service status, the handling device, run profile, tools, and model scope.

APP CAPTUREThe English light-theme Affiliate settings, whose section navigation covers service status, Agent access, model diagnostics, decision thresholds, post-fulfillment follow-up, and Business Instructions.

Check these items first:

• Handling device: bind a Desktop that will remain online. Work that depends on the local runtime cannot advance while that device is offline.
• Run profile and tools: the built-in Affiliate profile is a safe starting point. Change tool access only when its effect is understood.
• Model scope: use this diagnostic to confirm which model settings Affiliate work will use. To change a provider or model, go to Models, devices, and run profiles.

#2. Set volume and decision boundaries

Continue down the same Shop page to configure the daily Creator outreach limit, minimum expected sales, and Sample performance follow-up.

APP CAPTUREThe English light-theme Affiliate decision thresholds and low-performance Sample follow-up settings.

Daily Creator outreach limit

This is the Shop-level safety ceiling. A Campaign can set a lower daily target, and actual delivery still depends on sending windows, platform safeguards, and qualified candidates. Begin with a small number so the team can inspect match quality and review load.

Minimum expected sales

The Agent uses this threshold as one business signal when evaluating Creator value. It is not a sales guarantee and does not replace explicit hard filters in a Campaign.

Low-performance Sample follow-up

When enabled, define a low-order threshold and one to three delayed follow-up stages. Give each stage one clear purpose: ask about the production plan, offer creative guidance, or confirm whether the Creator still intends to publish.

#3. Write Affiliate Business Instructions

Affiliate Business Instructions add operating rules known by your team that the Agent must apply when making decisions.

APP CAPTUREThe English light-theme Affiliate Business Instructions editor.

Good content includes:

• brand voice and communication restrictions;
• which benefits may be offered and which require a human handoff;
• priorities by market, Creator type, or product;
• rules for follow-up frequency, ending contact, and sensitive requests.

Keep specifications, claims, and common questions in Product Knowledge instead of duplicating product facts here.

#4. Configure Team and Approval Policies

Shop settings define how one Shop runs. Team & Channels defines who owns Creator relationships, who uses each WhatsApp and Outlook account, which relationships AI may take over, and which account-wide actions require approval.

APP CAPTUREThe English light-theme Affiliate Team page, showing responsible people and connected work accounts.

Open Safety & approvals to create Approval Policies for:

• sending a message;
• reviewing a Sample application;
• managing a Creator tag;
• deciding that no action is needed.

APP CAPTUREThe English light-theme Affiliate Approval Policies page with account-level policies and the recommended-policy action.

The Agent makes its decision and submits the operation normally; the system then evaluates Safety Policies independently. When an enabled policy matches, the system holds the operation as an Action Proposal under Pending review in Agent Workbench. Without a match, the operation can execute automatically. The Agent does not decide whether policy matches. For a first launch, apply the recommended policies so all four action types are reviewed, then relax one boundary at a time after the team validates the results.

Policies can narrow their scope with Manual Tags, Sample Tiers, Campaigns, or Product IDs when the action supports those conditions. For example, review Samples only for high-cost products instead of treating every Sample alike.

For the complete BD working-mode, Creator-protection, channel-ownership, and policy setup, see Team & Channels.

#5. Distinguish review from handling

• Review an Action Proposal (Pending Proposal): the Agent has decided and submitted a specific operation, and the system has held it because policy matched. A person approves, rejects, or requests a revision under Pending review.
• Handle an Escalation: the Agent recognizes that the issue exceeds its capability, tools, or authority and actively hands it to an owner. A person takes over under Pending—for example, deciding and arranging a replacement for a lost Sample.

Both appear in Agent Workbench, but the first is reviewing an action and the second is handling an issue. Review is not an Agent request for help; handling is not approval of a ready-made action. All Agent work provides the audit and history view for AI work.

Work for protected Creators or Human-only BDs does not enter the AI workflow first. Staff use Manual Workbench to centrally process Sample Applications and Creator messages. See Agent and Manual Workbenches for the complete distinction.

#Go-live checklist

• The Shop is Authorized and Affiliate is enabled.
• The handling device is online, with a usable run profile and model.
• Outreach limits, expected-sales threshold, and follow-up stages fit team capacity.
• Business Instructions contain executable operating rules.
• Owners and work accounts are clear.
• All four important action types have the intended Approval Policy.
• At least one Product Knowledge set is ready; next, create the first Campaign.