Agent Types & Templates
When you create a new Digital Employee, you choose a template that pre-fills the department, role title, introduction message, scope description, and system prompt. You can customize everything after creation — templates just give you a head start.
Built-in Templates
HridaDoc Agent
The official Hrida.ai documentation assistant. Pre-configured with a system prompt that instructs the agent to always use its documentation tools before answering.
| Field | Value |
|---|---|
| Department | Documentation |
| Role | Documentation Assistant |
| Scope | Hrida.ai product documentation |
| Escalation | support@hrida.ai + GitHub issues link |
| Tool behavior | Always calls search_docs → get_docs_page → cites page paths |
When to use: Deploy this to replace the old single-instance HridaDoc agent, or alongside it.
Documentation Agent
A generic documentation assistant for any product or internal docs site.
| Field | Value |
|---|---|
| Department | Documentation |
| Role | Documentation Assistant |
| Scope | (customize to your docs) |
When to use: Internal wikis, product documentation, runbooks.
HR Agent
Handles employee queries about policies, benefits, leave, onboarding, and compliance.
| Field | Value |
|---|---|
| Department | Human Resources |
| Role | HR Support Specialist |
| Scope | Policies, benefits, leave requests, compliance |
When to use: Self-service HR queries. Configure access to restrict to employees only.
IT Support Agent
Troubleshoots software, hardware, access, and infrastructure issues.
| Field | Value |
|---|---|
| Department | IT |
| Role | IT Support Engineer |
| Scope | Software, hardware, access requests, infrastructure |
When to use: First-line IT support. Handles common questions before escalating to the service desk.
Sales Agent
Qualifies leads and answers product/pricing questions.
| Field | Value |
|---|---|
| Department | Sales |
| Role | Sales Development Representative |
| Scope | Product overview, pricing, lead qualification |
When to use: Customer-facing or SDR support. Restrict access to the sales team or make it public.
Legal Agent
Explains contracts, policies, and compliance requirements.
| Field | Value |
|---|---|
| Department | Legal |
| Role | Legal Assistant |
| Scope | Contracts, policies, compliance, regulatory requirements |
When to use: Internal legal queries. Always configure strict access control — restrict to relevant teams only.
Custom Agent
Blank slate — fill in everything manually.
When to use: Any function not covered by the above templates. Finance, Marketing, Operations, Customer Success, etc.
Template Defaults
The templates pre-populate the following config fields:
| Template | introduction | scope_description | handoff_contact | system_prompt |
|---|---|---|---|---|
| hridadoc | ✅ | ✅ | support@hrida.ai | ✅ (full prompt) |
| documentation | (empty) | (empty) | (empty) | (empty) |
| hr | (empty) | (empty) | (empty) | (empty) |
| it | (empty) | (empty) | (empty) | (empty) |
| sales | (empty) | (empty) | (empty) | (empty) |
| legal | (empty) | (empty) | (empty) | (empty) |
| custom | (empty) | (empty) | (empty) | (empty) |
Only the HridaDoc template ships with complete defaults. For all other templates, fill in the Identity fields before running Setup.
Writing Effective Config
Introduction message
The introduction is sent as the first response in every new conversation with the agent. It should:
- Say the agent's name and department
- State one or two things it can help with
- Keep it to 2–3 sentences
Good example:
Hi! I'm the HR Agent for Acme Corp. I can help you with benefits information,
leave requests, onboarding questions, and HR policies. What would you like to know?
Scope description
Injected into the system prompt so the LLM knows what it is and isn't allowed to help with. Be specific.
Good example:
Acme Corp HR policies and procedures including: annual leave and sick leave,
benefits (health insurance, pension, EAP), onboarding and offboarding checklists,
performance review process, and compliance with the Employee Handbook.
Topics NOT covered: payroll, tax, individual employment contracts.
Escalation contact
Shown in the "Need more help?" block when the agent detects it cannot answer. Can be an email address, Slack channel name, or a URL.
Examples:
hr@acme.comSlack: #it-supporthttps://helpdesk.acme.com
System prompt
The system prompt is only needed if you want to override the default behavior injected by the filter. Most agents don't need a custom system prompt — the filter handles role scoping automatically.
If you do provide one, it's appended after the filter's injection.
Adding a New Template Type
Template types are defined in the backend at GET /api/v1/digital-employees/types. Admins cannot add new built-in templates via the UI — but you can configure any fields manually on the Custom Agent type.
If you need a company-wide standard template, contact your instance administrator to add it to the backend.