Guided workflows

    Step-by-Step Guidance Inside the Browser

    HEIDI guided workflows help operators complete operational tasks without leaving the application — natural-language workflow editing, task mining capture, controlled execution, and SOP onboarding invites. Each path respects approvals and keeps humans in control.

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

    Guide → workflow compiler

    Capturing steps is the start. Compile guides into governed execution with approvals, exceptions, evidence artifacts, and version logs.

    Governance strength

    62%

    More governance = stronger decision points, clearer ownership, better audit readiness.

    Compiler stages

    Capture steps

    Find decisions

    Attach governance

    Generate artifacts

    Compile options

    Approvals

    Owners + gates at decision points

    Exceptions

    Controlled bypass paths with rationale

    Evidence artifacts

    Structured records you can query

    Version log

    What/why/impact for each change

    Output score

    61/100

    Higher score = decisions produce evidence and workflows stay true under change.

    Generated artifacts

    step_map

    handoff_contract

    approval_record (who/when/why)

    exception_record + rationale

    evidence_artifact_id + metadata

    version_log (what/why/impact)

    Artifacts are designed to be queryable. That’s how audits become dashboards instead of reconstructions.

    What are HEIDI guided workflows?

    HEIDI guided workflows are in-browser assistance paths for operational work: edit automations with natural language (vibe coding), capture browser and desktop evidence for task mining, execute configured workflows via the runtime, and send SOP onboarding invites so new hires learn with HEIDI.

    Capabilities

    What you can do with HEIDI

    Vibe coding for workflows

    Describe changes in plain language; HEIDI helps build or modify workflow automations in context.

    Task mining capture

    Record browser and desktop evidence during real work to feed HEIDI and automation design.

    Controlled execution

    Run workflows through the runtime API with telemetry and approval gates — not unchecked auto-runs.

    SOP onboarding invites

    Send SOP plus HEIDI onboarding invites so new team members learn procedures with guided assistance.

    Stays in the browser

    Guidance overlays operational UIs — operators do not context-switch to separate documentation.

    Use cases

    Where teams apply HEIDI

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

    Modify a workflow by description

    Tell HEIDI what should change in the automation; review the proposed edits before they go live.

    Capture a process for task mining

    Record clicks and navigation across tabs to build evidence for process analysis and automation.

    Execute an approved workflow

    Launch a configured workflow run with full observability and recovery rules.

    Onboard with an SOP invite

    Send a generated SOP and HEIDI invite so the hire walks through the procedure with assistance.

    SOP step with exception handling

    HEIDI guides the standard path and surfaces policy when an exception requires approval.

    How it works

    From chaos to clarity in 5 steps

    1

    Open Guided Workflows

    From Assistance Hub, choose vibe coding, capture, execution, or SOP onboarding.

    2

    Work in context

    HEIDI stays aware of your project and the application you are operating in.

    3

    Propose the next step

    Edits, captures, or runs are prepared — not silently applied.

    4

    Review and approve

    Operators confirm before workflows execute or changes are saved.

    5

    Record and improve

    Telemetry and captures feed back into Operational Knowledge and future guidance.

    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)

    Running production workflows without observability

    Silent failures in operations are hard to debug and audit.

    Use the runtime execution path with step telemetry and defined recovery rules.

    Training new hires on PDFs alone

    Static SOPs do not adapt when the UI changes or exceptions appear.

    Pair SOP content with HEIDI-guided onboarding invites in the live application.

    Deep dive

    Vibe coding and task mining

    Guided workflows bridge human operation and automation design without a separate tooling silo.

    Vibe coding lets operators describe workflow changes in natural language while HEIDI proposes concrete edits to review.

    Task mining capture records browser and desktop evidence during real work — the same capture path used across the Process Designer platform for deterministic automation input.

    See Assistance Hub for the full hub and Manual Map for navigation context.

    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.