| Starting point | Describe the recurring job, deliverable, systems, controls, success measure, and human owner in plain language. | Open a visual workforce builder and assemble triggers, agents, conditions, tools, and connections. |
|---|
| Who designs the system | The business owner defines the responsibility and boundaries; Linkence configures the coworker and its operating model. | Subject-matter experts or AI builders clone or create agents, write tool and connection instructions, and design the workforce. |
|---|
| Agent handoffs | A coworker can hand work to another approved coworker when the responsibility crosses roles, while staying inside defined guardrails. | Builders explicitly connect agents and tools, choose natural-language or forced handoffs, and configure approval modes and auto-run limits. |
|---|
| Learning and iteration | Each dedicated team can receive a customized model. The coworker learns from completed work and reviewed feedback, with proposed improvements kept reviewable. | Relevance AI describes workforces that learn from feedback, while builders retain direct control over agent instructions, tools, connections, and versions. Confirm how learned changes are applied in your deployment. |
|---|
| Control and cost | Set the coworker's spend budget, trigger, approvals, prohibited actions, and named escalation path against one responsibility. | Configure approval behavior and maximum auto-runs at connections. Usage is measured through actions plus model or vendor credits, with BYOK available on paid plans. |
|---|
| Deployment boundary | Managed SaaS or customer-controlled cloud or VPC, with team-level separation for training and inference. | Public enterprise materials describe single-tenant or private-cloud deployment, plus SSO, RBAC, version control, and audit logs. Confirm the exact architecture and feature availability. |
|---|