HR

How HR teams use Harriet for day-to-day employee support and admin tasks.

Create tickets, follow threads, and keep employee requests organized.

Structure the Knowledge Base around employee questions, owners, and plain language so Harriet cites the right material.

Publish separate knowledge documents with the right groups and geography metadata for each audience.

Give managers who need global context membership in a narrow group that can see reference documents without opening them to all staff.

Personalisation comes from HRIS-backed attributes and roles—balance helpful defaults with least data exposure.

Open a ticket for human follow-up, escalations, or anything that needs a tracked thread beyond a chat answer.

Review tickets, chat themes, and search misses to decide what to publish next in the Knowledge Base.

A step-by-step introduction to building a real workflow—using new starter onboarding to cover triggers, authoring agent steps, assigning skills, reaching out to stakeholders, and pausing for replies.

Keep workforce questions scoped, aggregated, and aligned with what managers are allowed to know about their teams.

Harriet workflows are configured by your team—there are no locked-in templates, but common patterns for onboarding, leave, and data collection are straightforward to set up.

Workflows can be started by a new ticket, a chat request, a scheduled time, or a webhook from an external system—choose the trigger that fits your process.

Workflows automate multi-step tasks with triggers, agent steps, and optional human checkpoints—separate from ad-hoc chat.

Some workflow actions pause until an approver confirms them—often on the linked ticket—then the run continues automatically.

A ticket can trigger workflows, host approvals, and collect replies that resume a paused run—without duplicate noise loops.

Running a workflow from chat may create a support ticket by default; many other triggers reuse an existing ticket or run without one.

Workflows can pause for approvals, ticket replies, external replies, scheduled time, or sub-tasks—each resumes automatically when its condition is met.

Combine clear questions, ticket threading, and explicit resume behavior so pauses feel predictable to employees and HR.

Start with one configurable agent step when plain-language instructions and skills are enough; open Advanced mode (canvas editor) when you need multiple separate automated phases or branching. Delegation runs one conversation at a time.

The configurable agent step runs an AI agent inside a workflow—you write plain-language instructions, assign skills, and the agent completes the task, pausing where it needs human input.

Use the data-gathering agent step to have Harriet reach out by Slack DM or email, ask follow-up questions, and return a structured summary when the conversation is complete.

A workflow agent can hand off a bounded sub-task to a specialist sub-agent, wait for it to complete, and use the results to continue—enabling sophisticated multi-step automation without losing oversight.

Scheduled workflows run automatically at set times—useful for regular reports, proactive reminders, and recurring compliance checks.

Workflow agents maintain full conversation history within a run, so context from earlier steps is always available when the workflow resumes after any pause.

Complex workflows combine a trigger, one or more agent steps with skills, pause mechanisms for human input, and clear error paths—designed in layers and tested before going live.