Jobs
A Job defines the role, responsibilities, and authority boundaries for your AI worker within a specific domain. This helps your worker understand its purpose and stay focused on relevant tasks.
Overview
A Job represents the function and scope of your worker. It answers the question: "What is this worker responsible for and what authority does it have?"
For example:
Customer Support Agent - Handles order issues, returns, and account questions with authority to issue refunds up to $100
Sales Assistant - Handles product inquiries and pricing with authority to offer standard discounts
Technical Support Specialist - Handles troubleshooting and setup with authority to escalate to engineering
Jobs help your worker:
Understand its role and responsibilities clearly
Know the boundaries of its authority
Recognize when a conversation is within its expertise
Gracefully redirect out-of-scope requests
Provide more focused, relevant responses
Creating a Job
Navigate to Worker Setup > Jobs and click Create Manually or Create with AI.
Manual Creation
Name
Clear identifier for this job (e.g., "Customer Support Agent")
Summary
Brief description of what this job covers
Domain
The business area this job operates in (e.g., "E-commerce", "SaaS Support")
Role
A 2-4 sentence statement defining the worker's identity and jurisdiction
Responsibilities
Specific tasks and duties the worker is accountable for
Authority
What the worker can and cannot do independently
AI-Assisted Creation
Click Create with AI to open the AI authoring assistant. Describe your use case in natural language, and the assistant will help you:
Define the job name and summary
Identify the domain and role
List responsibilities
Clarify authority boundaries
Job Fields Explained
Domain
The business context in which this worker operates. Examples:
E-commerce Customer Service
B2B Software Sales
Healthcare Patient Support
Financial Services
Role
A concise statement (2-4 sentences) that establishes the worker's identity and jurisdiction. Format:
"You are a [role title] for [company/context]. Your jurisdiction is [what you own]. You operate with [stance/approach]. Your authority [includes/excludes] [key boundaries]."
Example:
"You are a Customer Support Agent for Acme E-commerce. Your jurisdiction is order inquiries, returns, and account issues. You operate with a patient, helpful stance. Your authority includes issuing refunds up to $100 and excludes approving custom pricing."
Responsibilities
List the specific tasks and duties this worker handles:
Answering questions about order status and tracking
Processing return and refund requests
Troubleshooting common account issues
Explaining product features and specifications
Authority
Define clear boundaries for what the worker can do independently:
Can Do:
Issue refunds up to $100
Apply standard promotional discounts
Update customer contact information
Schedule callbacks
Cannot Do:
Approve custom pricing
Access financial records beyond order history
Make commitments about unreleased features
Override security policies
Connecting Jobs to Topics
Jobs contain Topics. When you create a Topic, you assign it to a Job:
This hierarchy helps the worker:
Quickly identify which Job context a conversation belongs to
Access relevant Topics within that scope
Apply appropriate policies and knowledge
Best Practices
Naming
Use clear, descriptive job titles that reflect the role
Keep names concise (3-5 words)
Use consistent naming conventions across your organization
Good Names:
Customer Support Agent
Product Sales Specialist
Technical Troubleshooting Expert
Account Management Coordinator
Avoid:
"General Help" (too vague)
"Everything Customer-Related" (too broad)
"CS1" (not descriptive)
Role Definition
Be specific about jurisdiction and authority
Avoid duplicating what other modules handle (Topics, Goals, Policies)
Include escalation paths when relevant
Responsibilities
List 4-8 specific, actionable responsibilities
Use action verbs (handle, process, troubleshoot, explain)
Avoid overlapping responsibilities between Jobs
Authority
Be explicit about both what the worker CAN and CANNOT do
Include specific limits where applicable ($100 refund limit, etc.)
Define escalation triggers
Multiple Jobs
A worker can have multiple Jobs, allowing it to handle different roles:
Support Worker
Customer Support Agent, Technical Support Specialist, Billing Specialist
Sales Worker
Product Sales Specialist, Onboarding Coordinator
Internal Worker
HR Support Agent, IT Help Desk, Facilities Coordinator
When a user's question could match multiple Jobs, the worker uses context and confidence scoring to select the most appropriate one.
Impact Preview
Before deleting a Job, the system checks if it's used by any:
Active Topics
Worker configurations
Training data
If dependencies exist, you'll see an impact preview showing what would be affected. This prevents accidental disruption to your worker's configuration.
Related Documentation
Last updated