• Web app at epicone.hearken.ai — the full experience: chat, screen recording, settings, and admin access.
• Mobile app — chat, voice, and uploads, sharing the same conversation history as the web app.
• Text message — a full conversation with Epic One over SMS when you’re away from a computer.

Sign in with your registered email and password. Admins can reset a teammate’s password, and anyone can request a password reset directly in chat.

• Type a message, or use the microphone button — voice is auto-transcribed.
• Toggle the speaker icon for text-to-speech replies.
• Pick an avatar (Andy, robot, dog, cat, or human), choose its position, or hide it entirely.
• Presence dots in the header show which teammates are online right now.
• An environment chip in the header shows the active ERP system, color-coded.

Things you can just ask:

• “What do you know about Acme Corp’s pricing?” — searches the knowledge base.
• “Search past transcripts for the kickoff meeting” — searches saved transcripts.
• “Send Stacey a message that the report is ready” — relays it in-app or by SMS.
• “Who’s online right now?” — checks presence.
• “Show me my screenshots” — displays the latest recording’s frames.

Epic One understands natural language, so exact wording never matters. Here’s what it can do, grouped by kind of work.

Documents & downloads

Recordings & screenshots

Knowledge & memory

Epicor & ERP (Epicor mood; E2 JobBoss² in General or Migration)

Teaching Epic One

Media & article search (Law mood)

Team

Account & preferences

Migration (Migration mood)

Switch moods from Settings or with a chat command like “switch to marketing mood.”

Starting a recording

1. Click the recording button in the chat header.
2. Choose a purpose: teach Epic One a process (saves a reusable step-by-step procedure, named for the system, e.g. “E2 JobBoss”), generate an End User Guide (a formatted training document with screenshots), or log a customer work session (internal log or client-ready).
3. Click Record Screen, or Upload File for an existing video.
4. When the browser prompts you, select Entire Screen, not a single browser tab.
5. A 5-second countdown gives you time to switch over to the application you’re demonstrating.

While recording

The control bar in the chat header gives you:

• Snap (⌘⇧S / Ctrl+Shift+S) — captures the exact screen; it’s added to the timeline and never filtered out.
• Timed snap (⌘⇧D / Ctrl+Shift+D) — captures the screen 3 seconds after the click, useful for right-click menus and dropdowns.
• Pause / resume (⌘⇧P / Ctrl+Shift+P) — paused time never appears in the final video; snapping still works while paused.
• Pop-out — a floating panel that stays on top of every app or tab, so you can snap and pause without switching back (Chrome or Edge required).
• Stop — ends the recording and uploads it automatically.

Keyboard shortcuts work as long as the Epic One tab or the floating panel has focus. Automatic screenshots also trigger on screen changes like menus and dialogs; near-identical frames get pruned, and you approve the final set before any document generates.

Click capture extension (optional)

Captures a screenshot at every click and right-click, including context menus and “Open With” ERP tabs.

1. Download the extension and unzip it.
2. In Chrome or Edge, open chrome://extensions, enable Developer mode, and click Load unpacked, then select the folder.
3. Open the Epic One site while logged in, click the extension icon, toggle Capture clicks, and list your ERP site addresses (e.g. epicorsaas.com).

Without the extension, timed snap and automatic capture cover the same ground manually — the extension just makes it effortless.

Epic One asks conversationally, one question at a time. The type of Q&A depends on what you’re building:

• EUP recording — process name, client, department.
• Work-session recording — customer, and what you worked on.
• Uploaded transcript or meeting recording — which documents, and which customer.

Natural language answers work fine, and one message can answer several questions at once. You can interrupt with an unrelated question at any point — Epic One answers it, then picks the Q&A back up. Cancel anytime by saying “never mind, skip the document.”

Before generating a document with embedded screenshots — End User Guide, Work Session, Discovery, Planning, or Design Spec — Epic One shows you every captured frame and waits for approval.

1. After the document questions, Epic One shows every screenshot it captured.
2. Click a frame to view it full size.
3. Use Replace to upload a better image, which swaps into the document set.
4. Click Approve & Generate (or reply “approve”) to build it, or Cancel to skip.

You can review the current set anytime by saying “show me my screenshots.” Blank loading screens and shots of the Epic One window itself get filtered out automatically; manual snaps are always kept.

Upload process

1. Click the upload button in the chat header and select one or more files: a transcript (.txt, .docx, .pdf, .vtt, .md), a meeting recording (.mp4, .mov, .webm, .m4a, .mp3, .wav), or both together.
2. Epic One reads them, gives you a summary, and asks which documents you want and which customer they’re for.
3. If screenshots were captured and the document uses them, it shows them for approval first.
4. The finished document posts as a download card in chat, and saves permanently to Dropbox → transcript-pipeline/output.

Recordings without a transcript get auto-transcribed (longer meetings take a few minutes). Given both a video and a transcript, Epic One pulls the text from the transcript and the screenshots from the video, and embeds both in whichever document you chose. To re-download something recent, say “show my recent documents” — the server keeps 5 days of download cards, and Dropbox keeps them forever.

Document types

The design-spec trick

During a planning session:

1. Say “start design spec” out loud.
2. Discuss the design.
3. Say “end design spec.”

When it builds the planning document, Epic One detects those markers and automatically writes a separate design spec from whatever was discussed in between. You can mark several sections in one meeting.

Learned formats (admin)

Discovery, Planning, and Design Spec documents copy their structure from memorized examples. An admin drops one example per type into Dropbox → transcript-pipeline/templates (the filename names the type, e.g. Discovery Example.docx) and tells Epic One “learn my templates.” Any new example file becomes a new document type, with no code changes.

Choose the work-session option from Screen Recordings, then answer two questions: the customer name, and what you worked on.

Style options

• Internal log — factual and specific: systems touched, records changed, exact values, issues, and workarounds.
• Client-ready summary — polished and value-oriented, safe to send to the customer directly.

Every document includes

• Customer, your name, date, and session length (pulled from the recording).
• A task-by-task narrative with screenshots.
• A Follow-ups & Next Steps section.

It posts as a download card in chat (5-day retention) and saves permanently to Dropbox → transcript-pipeline/output. The session is also saved to Epic One’s memory under the customer’s name — later you can ask “what have we done for Acme this month?”

Creating a guide

1. Record the process (Screen Recordings, End User Guide option).
2. Answer the Q&A.
3. Review the screenshots.

Epic One writes a formatted Word document with numbered steps grouped by task, one screenshot per section, and a metadata table. It posts as a download card in chat and saves to Dropbox → transcript-pipeline/output.

Running a saved procedure

Procedures Epic One has learned can be executed, not just read. In Epicor mood, for example: “Add a new customer: Lud, Ludwig Solutions LLC, terms Net 30.”

1. Epic One asks for any missing fields.
2. It shows an approval card with the exact changes, plus estimated cost and time.
3. Once approved, it does the work — directly through Epicor’s interface where possible, or by driving the browser step by step with screenshot updates.

Your active environment

Many companies run more than one environment (Live, Pilot, test). Epic One shows the active one as a colored chip in the chat header, and stamps replies with a matching badge showing where the action happened.

• Live — red
• Pilot — amber
• Other — a color you choose

Click the chip to switch. Reads and writes always stay on the active environment — outside Migration mode, Epic One never crosses environments; if you ask it to touch a different one, it prompts you to switch first. Migration mode is the one deliberate exception, working across two environments with a read-only source and a write target pinned.

Connecting Epicor

Add Epicor environments in Settings. Each signs in based on your company’s setup — username and password, an API key, OAuth, or Epicor Identity single sign-on. Multiple environments (Live, Pilot) are added separately, each with its own color for the header chip and badge.

With Epicor connected, you can:

• Look up live data — “how many open orders does customer X have?”
• Drive Epicor screens in the browser for tasks the data interface can’t handle.
• Run saved EUP procedures.
• Get human approval on every change — the approval card shows the exact change and estimated cost and time, and waits for your OK before writing. Reading is instant; changing always waits.

E2 JobBoss² (and other web ERPs)

• Save the site login in Settings → Credentials.
• Ask Epic One to read screens, fields, and dropdowns.
• The session stays open between requests, and re-logs in automatically if it expires.
• Hotspots — save a named field set (e.g. “daily open orders”), then run it anytime or export it to CSV in Dropbox. Available in General and Migration moods.

Moving records between environments has its own guardrails — see Data Migration below.

In Migration mood, Epic One moves records between two Epicor environments with guardrails: it reads from the source (read-only) and writes to the target.

Setting up a migration

Say “migration setup” to pin the source and target environments. From then on, every read comes from source and every write goes to target.

The field mapping screen

Migration mode includes a visual field-mapping screen for lining up fields between systems:

• Search any dataset — type part of a name (e.g. “cust”) and pick from every matching dataset.
• Ready-made defaults — Epicor-to-Epicor moves come with roughly 2,483 pre-mapped datasets using an identity default, every field copied as-is. Pick a dataset and it’s ready; edit and save only if you need to customize it.
• Manual mapping where needed — set a target field from a source field or a fixed constant; required fields are flagged, and a running count shows what’s still unmapped.

Every write goes through an approval card with estimated cost and time, and a dry-run previews the entire import before anything commits.

• From recordings — teach-mode recordings become reusable procedures.
• From chat — “remember that Acme’s payment terms are Net 45.”
• From websites (Marketing mood) — “learn from acme.com,” including sites that need a login, using saved credentials.
• From Dropbox — point it at a folder of documents, and check progress with “what’s the learning status?”
• NotebookLM (Marketing mood) — send documents through Google NotebookLM and query the results.

Available in Law and Marketing moods. Save outlets first in Settings → Media Sources.

Save credentials once for login-gated outlets, and Epic One signs in automatically when it searches them.

• Presence — header dots show who’s online across web and mobile.
• Relay messages — “tell your teammate the pilot environment is back up” delivers it in-app, or by SMS if they’re offline.
• Shared knowledge — whatever one teammate teaches Epic One, the whole company benefits from.

• Avatar & voice — pick a character (or None to hide it), set its position, and choose a text-to-speech voice.
• Mood — switch between the six moods.
• Epicor environments — your company’s environment list, plus your personal Epicor login. Each has a color (a smart default like Live=red, Pilot=amber, changeable) driving the header chip and badge, and supports API key, OAuth, Epicor Identity, or classic username and password. Adding one unlocks Epicor mood.
• Site credentials — logins for E2 JobBoss² and other sites, with a test-connection button.
• Company Dropbox — connect a Dropbox account for document delivery.
• Notifications — SMS and email toggles.
• Profile — name, email, password.

Path: /admin, for admins only.

User management

• See every user, grouped by company, with online status.
• Edit user details, reset passwords, and toggle notifications.
• Force-log out a user’s web session, mobile session, or both.

Document formats (in chat)

1. Drop one example per type into Dropbox → transcript-pipeline/templates.
2. The filename names the type — any new file becomes a new document type.
3. Tell Epic One “learn my templates.”
4. It replies with exactly what it learned.

Learning never happens automatically, and non-admins can’t change formats — everyone can still generate documents.