epoches
Schedule A Call
AI Employees

AI roles with owners, permissions, gates, and logs.

Epoches AI employees are scoped workflow operators for support, sales, operations, knowledge, admin, and document-heavy teams. They work inside your tools, follow your rules, and escalate when judgment matters.

Which role should we build first?Explore the roster
8launch roster examples
4initial operating departments
0unbounded autonomous roles

Every role is configured after the audit. The roster is a menu of workflow patterns, not a promise that one generic bot fits every business.

Roster

Choose the job family. The audit defines the actual job.

These examples show what can be built once the workflow, data, approvals, and value case are clear.

Support

Support triage coordinator

Classifies requests, drafts replies, retrieves approved answers, routes edge cases, and updates the ticket system.

ZendeskGmailDocs
Human gate
Approves sensitive replies
Primary metric
Response time
Sales

Lead qualification assistant

Scores inbound leads, enriches context, drafts follow-up, updates the CRM, and alerts the deal owner.

HubSpotCalendarEmail
Human gate
Approves outreach
Primary metric
Speed to lead
Operations

Operations reporter

Collects updates, checks anomalies, compiles summaries, and prepares decision-ready weekly reports.

SheetsSlackLooker
Human gate
Reviews anomalies
Primary metric
Reporting time
Knowledge

Knowledge assistant

Retrieves approved company context, keeps answers cited, and refuses to answer outside the knowledge base.

NotionDriveConfluence
Human gate
Approves new sources
Primary metric
Answer accuracy
Operations

Document processor

Intakes documents, extracts fields, classifies records, flags missing data, and prepares validation queues.

DriveOCRDatabase
Human gate
Validates exceptions
Primary metric
Processing time
Admin

Admin coordinator

Schedules handoffs, sends reminders, follows up on approvals, and keeps operational tasks from stalling.

CalendarSlackEmail
Human gate
Approves external sends
Primary metric
Missed follow-ups
Knowledge

Research assistant

Builds competitor briefs, market scans, and source-backed summaries for sales, strategy, and delivery teams.

WebNotionSheets
Human gate
Reviews sources
Primary metric
Brief quality
Sales

Website concierge

Answers visitor questions from approved site content, qualifies intent, and routes serious buyers to the audit flow.

WebsiteSupabaseEmail
Human gate
Rate limits sessions
Primary metric
Qualified bookings
Where they work

Hire once. They cover voice, chat, and email.

Every role in the roster runs on the same operating contract, so the channel changes but the owner, rules, and approval gates never do.

Calls get answered, routed, and logged with natural conversation. Anything needing judgment escalates to a human before promises are made.

A man taking a phone call
Anatomy

Not a chatbot. A scoped operator with a job to do.

The difference is the operating contract: who owns it, what it can touch, what it cannot do, what it must log, and where a human takes over.

Purpose: one business role, not a general chatbot.Context: approved docs, data, and workflow rules.Tools: only the integrations needed for the job.Approval: humans review sensitive actions.Logs: important actions are auditable.Rollback: the system has known failure modes and recovery paths.
An AI employee contract listing allowed actions, forbidden actions, and escalation rules
Deployment model

From job description to live workflow in three steps.

01

Write the job description

Define the workflow, trigger, inputs, outputs, integrations, allowed actions, exclusions, and success metrics.

02

Build the operating loop

Connect tools, approved context, prompts, logging, approval gates, and evaluation checks into one bounded system.

03

Deploy with oversight

Launch in a limited production window, train the team, monitor outputs, and move into Managed AI Ops.

Governance contract

Every AI employee ships with controls, not vibes.

Classified and drafted work passing through a human gate before being sent or escalated

If a workflow cannot be evaluated, monitored, escalated, or rolled back, Epoches does not deploy it as an autonomous AI employee.

Role and owner

The workflow owner, purpose, user group, and escalation contact are defined before implementation.

Allowed actions

Each employee gets written permissions, forbidden actions, data boundaries, and tool access limits.

Human gates

Sensitive replies, external sends, financial changes, and edge cases are routed to human approval.

Evaluation loop

Happy paths, edge cases, hallucination checks, latency, cost, permissions, and rollback are tested.

Next step

Which role would you hire first?

Start with the audit. We will identify the workflow, score the opportunity, and recommend the first AI employee only if it can be governed and measured.

Schedule A CallSee the service ladder