Managed Hermes agent onboarding

Start with how your team actually works.

Share the workflows, systems, and approval boundaries that matter. We’ll use this intake to prepare an isolated managed Hermes agent around your existing operation.

Step one

Your business and point person

Give us enough context to name and scope the client environment correctly.

1 / 4

●

Keep secrets out of this form. Never enter passwords, API keys, bot tokens, OAuth codes, bank details, or private customer records. We handle credentials separately after approval.

Client or organization name *

Business name if different

Preferred assistant name *

Business website or desired domain

Primary contact *

Primary contact email *

Primary contact phone

Primary timezone *

Telegram username if already used

Telegram numeric user ID optional

Step two

What the agent should help with

Focus on repeated work, information handoffs, and decisions that currently depend on someone remembering every detail.

2 / 4

Day-one services *Select every system the first useful workflow may need.

Email / GmailSearch, triage, draft, or follow-up support. CalendarAwareness, preparation, or approved scheduling. Drive, Docs, SheetsDocuments, operating records, and reporting. CRM or business systemCustomer, project, sales, or service workflows. WebsiteApproved page updates or structured intake. Local filesPDFs, spreadsheets, scans, and working folders.

Three workflows that would matter most * Plain language is best.

Other systems or integrations

Where the useful information lives *

Step three

Accounts and approval boundaries

We separate what the agent can read, what it can prepare, and what still needs a person to approve.

3 / 4

Google account to connect email only, no password

Google account type

Can a Workspace admin help with setup?

Starting action tier *

What must always require human approval? *

Anything else we should know?

Step four

Review and submit

We’ll save this intake for 828 Pros review. Nothing connects to your accounts from this form.

4 / 4

✓

Your intake is in.

828 Pros will review the scope before any environment is created or any account is connected.

01Review We confirm the workflow, access tier, and approval boundaries.

02Build start After approval, the isolated environment is scaffolded without credentials.

03Secure connection Account authorization and bot credentials happen separately through controlled setup links or restricted handoff.