Replofy
Docs

Launch a controlled Replofy pilot.

Set up organization, knowledge, channels, workflows, preview answers, and a low-risk pilot before expanding automation.

Create organizationUpload knowledgeConfigure workflowsConnect inbox channels
Get started
setup checklist
docs setup
Launch pilot checklist
4 of 6 complete
Organization
Workspace
Acme Demo support
approved
created
Roles
Admin, agent, viewer
mapped
Queues
Returns, billing, technical
draft
Sources and channels
Knowledge
5 approved collections
indexed
Email
support inbox connected
test mode
Web chat
widget preview
pending
not launched
Pilot gate
Answer preview
12 checks passed
source visible
Workflow
SLA escalation rule
enabled
Launch
requires admin approval
guardrail
setup01
Configure

Create the organization, roles, queues, and source policy.

test02
Preview

Test answers and routing before public launch.

launch03
Pilot

Start with controlled channels and audit every action.

Docs overview

Get Started

Set up organization, knowledge, channels, workflows, preview answers, and a low-risk pilot before expanding automation.

How it works

setup checklist

01

Create organization

Set workspace name, support identity, teams, and admin access.

02

Upload knowledge

Add approved docs, PDFs, websites, and policies before enabling AI drafts.

03

Configure workflows

Define routing, tags, response-time warnings, escalation, and approval rules.

04

Connect inbox channels

Add Gmail, SMTP, web chat, or other channels one at a time.

Setup steps

Recommended launch order.

Step 1
01

Create organization

Set workspace name, support identity, teams, and admin access.

Step 2
02

Upload knowledge

Add approved docs, PDFs, websites, and policies before enabling AI drafts.

Step 3
03

Configure workflows

Define routing, tags, response-time warnings, escalation, and approval rules.

Step 4
04

Connect inbox channels

Add Gmail, SMTP, web chat, or other channels one at a time.

Step 5
05

Preview answers

Review Aura drafts, source citations, and low-confidence behavior.

Step 6
06

Launch pilot

Start with low-risk categories and monitor review history and handoffs.

Guardrails

Do not launch before these are true.

01

At least one approved source collection exists

02

Human handoff route is configured

03

Sensitive actions require approval

04

Operators understand draft review and override

05

Test tickets were reviewed end to end

Related setup

Where to go next.

Task

Connect channels

Page

/docs/inbox

Why it matters

Messages need owner and route

Task

Maintain sources

Page

/docs/knowledge-base

Why it matters

Aura depends on approved knowledge

Task

Build rules

Page

/docs/workflows

Why it matters

Routing and escalation need policy

Task

Set permissions

Page

/docs/settings

Why it matters

Sensitive work needs access control

Open setup path

Start with control, then expand.

Use the pilot path to verify sources, routing, and approval behavior.

Book a demo