Manual Map

    A Shared Map So HEIDI Can Navigate Any App

    HEIDI Manual Map captures how your applications really work — pages, UI elements, and flows — discovered through the Chrome extension's Manual Mode. Review proposed diffs, approve what is accurate, and grow a team navigation map that powers voice and chat guidance.

    No credit card required. Switch to a paid plan any time.

    Integration surface map

    Enterprise automation needs multiple surfaces—APIs, tools, and UI automation—under one governed operating model.

    Policy strength

    74%

    API-first automation

    Stable integrations and structured data.

    Fast and reliable

    Strong data contracts

    Best for systems of record

    System boundary (governed)

    Guardrails

    Gates + approvals + evidence

    Operational Knowledge

    Owners + versions + evidence graph

    HEIDI

    Guided runs + prompts

    Integrations

    APIs + tools + UI

    Surface scores (simulated)

    Stability

    88%

    Coverage

    72%

    Residual risk

    10%

    Policy strength

    74%

    The best platforms don’t fight reality. They combine surfaces under one governed operating model.

    What is HEIDI Manual Map?

    HEIDI Manual Map is a versioned graph of application pages, elements, and navigation flows. Operators capture structure via the Chrome extension Manual Mode; reviewers approve diffs to merge discoveries into the shared map. HEIDI uses this map to guide users step by step through internal tools.

    Capabilities

    What you can do with HEIDI

    Chrome extension capture

    Manual Mode in the extension records pages and flows as operators work — no separate documentation project.

    Diff review workflow

    New discoveries arrive as pending diffs. Reviewers approve or reject pages and routes before they join the map.

    Pages, elements, and flows

    The map models page nodes, UI elements, and the routes between them — not just screenshots.

    Versioned team map

    Each project keeps a versioned map so guidance stays aligned as applications change.

    Powers voice and chat guidance

    Once approved, the map feeds HEIDI's navigation skills — highlight fields, walk through menus, explain next steps.

    Use cases

    Where teams apply HEIDI

    Real workflows that benefit from visual design, automation, and governance.

    Onboard a new ERP screen

    Capture the screen in Manual Mode, approve the diff, and HEIDI can guide the next hire through it.

    Approve a new navigation route

    Review the proposed route between two pages before it becomes part of the shared map.

    Highlight where to enter a PO number

    With map context, HEIDI points to the correct field on the form the user is viewing.

    Walk through contractor onboarding

    Multi-page flows in the map let HEIDI guide each step without the user hunting menus.

    Keep map current after a UI change

    New Manual Mode sessions propose diffs; reviewers merge only what is still accurate.

    How it works

    From chaos to clarity in 5 steps

    1

    Capture in Manual Mode

    Operators use the Chrome extension while working; HEIDI records pages and navigation.

    2

    Propose a diff

    New pages, elements, or routes appear as pending diffs with explanations and risk flags.

    3

    Review and approve

    Reviewers approve or reject each page and route — governance before the map grows.

    4

    Merge into the team map

    Approved diffs update the versioned graph visible to the whole project.

    5

    Guide users via HEIDI

    Voice and chat assistance use the map to navigate, highlight, and explain the next step.

    Industries

    Tailored for your industry

    Customer support

    Challenge

    High-volume support@ threads need fast, accurate replies without bypassing policy or knowledge checks.

    How we help

    Triage by intent, ground drafts on the product KB, propose Zendesk tickets, and gate sends behind supervisor approval.

    Example: Warranty claim → KB-grounded draft → ticket proposal → approved send

    Operations

    Challenge

    Cross-system exceptions — order vs invoice mismatches — stall when email stays in the inbox.

    How we help

    Route exceptions, propose CRM updates, and escalate to Slack with an approval trail.

    Example: Mismatch thread → triage → CRM proposal → Slack escalation

    Management & executives

    Challenge

    Leaders need signal over noise — what needs a decision today, and what can delegate with audit?

    How we help

    Priority inbox briefing, delegation with approval queues, and Report Studio SLA views for leadership review.

    Example: Morning brief → delegate with approval → SLA dashboard check

    SMB shared inbox

    Challenge

    info@ queues need one voice, role-based approvals, and visibility into open answers.

    How we help

    Governed triage for shared mailboxes, consistent persona, and open-answers KPI monitoring in Overview.

    Example: info@ inquiry → triage → grounded draft → team approval

    Success stories

    How teams transformed their operations

    Support Ops — warranty escalation

    Customer support

    Challenge

    Customer A emailed support@ with a warranty edge case; the agent needed policy-backed wording fast.

    Solution

    HEIDI triaged the thread, retrieved the warranty SOP via hybrid RAG, and prepared a draft with visible sources for supervisor approval.

    Result

    Approved reply sent with audit record; Zendesk ticket proposal filed after sign-off.

    Ops — order vs invoice mismatch

    Operations

    Challenge

    Vendor mail described an order-invoice mismatch that required CRM update and internal escalation.

    Solution

    Exception triage, CRM field proposal, and Slack escalation prepared as separate approval requests.

    Result

    Systems updated after approval; audit trail captured each decision.

    Avoid these

    Common mistakes (and how to avoid them)

    Documenting UIs in static PDFs only

    Static docs drift from production UI and cannot power interactive guidance.

    Grow a live navigation map from Manual Mode capture with reviewed diffs.

    Auto-merging every extension capture

    Unreviewed map changes introduce wrong routes and unsafe guidance.

    Keep a human review step for pages and routes before they join the shared map.

    Deep dive

    Diff review and governance

    Manual Map is deliberately not fully automatic — accuracy matters for operational guidance.

    Each capture session can propose new pages and routes. Reviewers see explanations and risk flags, then approve or reject individually. Only approved structure becomes part of the map HEIDI uses for navigation.

    Pair Manual Map with screen-aware voice for guided walkthroughs, or Assistance Hub for the full operational surface.

    Operational triage that teams can defend

    Classification is only useful when routing reasons stay visible.

    Email Automation treats triage as an operational decision, not a black box. Each inbound message receives intent tags, urgency signals, and a suggested owner before any draft or connector action runs. Reviewers see why a thread landed in a queue — policy match, customer tier, SLA risk — so corrections happen at approval time instead of after a wrong send.

    The same triage record feeds downstream steps: grounded drafts pull category-specific knowledge, escalations inherit priority, and Report Studio can slice volume by bucket. That keeps inbox automation aligned with how support, ops, and leadership already talk about workload.

    Email Automation glossary (for teams and AI assistants)

    Clear definitions of UpQuAI Email Automation capabilities — entity-rich summaries suitable for citation.

    Email Automation — UpQuAI Email Automation is an operational inbox workspace by UpQuAI Solutions AG. HEIDI triages inbound business email, drafts grounded replies, and prepares CRM, storage, and chat actions behind human approval — not marketing email or bulk campaigns.

    Approval gate — An approval gate requires a human to sign off before sensitive email sends or external connector actions (CRM updates, SharePoint filing, Slack escalation). Email Automation records decisions in an audit trail for team accountability.

    Hybrid RAG email grounding — Hybrid retrieval-augmented generation binds approved documents to inbox categories so draft replies cite visible sources. Email Automation uses hybrid RAG per folder or label — beyond thread-context suggestions from personal assistants.

    Related search intents this page answers

    Keywords: AI email triage, inbox triage software, email triage automation, priority inbox

    Buyers search for AI email triage when personal sorting is not enough. Email Automation classifies intent, routes shared mailboxes, prepares grounded drafts, and tracks reply SLA — beyond auto-labels or split inboxes alone.

    Q&A

    Frequently asked questions

    Learn more about how HEIDI works and how it can help your organization.