Product walkthrough

See Run-Via in action

A quick look at request intake, tracking, workflows, and admin controls — all built from the same screens your team would use on day one.

Admin walkthrough

Set up the workspace and keep operations moving

Teams, workflows, billing, settings, and reporting for managers configuring Run-Via.

Open admin walkthrough

Dashboard preview

Every team sees live counts the moment they sign in.

Run-Via Dashboard Requests Teams Reports
142 Requests this month
12 Teams active
5 Active workflows
98% SLA compliance
Request Team Status Assignee
Facility access badge Facilities In Progress J. Alvarez
New laptop request IT Approved R. Chen
Vendor onboarding Procurement On Hold Unassigned

Request detail

Full timeline, status, and assignee on every request.

Request #4821
Replace access badge — north warehouse
In Progress
Assignee: J. Alvarez Priority: Medium Due: 2 days
  1. Submitted

    Guest submission via intake form.

  2. Assigned to J. Alvarez

    Auto-routed to Facilities.

  3. In progress

    Badge print scheduled for tomorrow.

  4. Closed

    Awaiting completion.

Workflow builder

Multi-step workflows with clear status transitions.

Pending Intake received
In Progress Reviewed by team
Approved Sign-off complete
Closed Request fulfilled

Smart intake, rule-based routing, and workflow authority

Requests land in the right team the first time — and stay in the right team as they move.

  • AI intake fills the form from pasted or emailed content — priority, request type, part numbers, and dropdowns are matched server-side against the form template, not guessed on the client.
  • Routing rules override the target team or assignee at intake based on field values (for example: priority equals critical routes to on-call). Rules are stored as data, versioned with the workflow, and admins can add or edit them without touching code.
  • The workflow spec is the single authority on which team owns a request at every step. Guest, staff, API, and automation intake all sync ownership to the current workflow step, so a request cannot land in two teams at once.
  • Form authoring warns you when a template does not cover a required field of the workflow it is bound to, so gaps are caught before a request is ever submitted.

First-run orientation, help center, and quiet motion

A new admin can find their way without a training call. The app moves only when movement means something.

  • The admin dashboard opens with a first-run panel that lays out the recommended setup order — teams and access, forms, routing, then notifications and integrations. It is dismissible per user and restorable from Feature Flags.
  • Every page carries a slide-out help center — the same guidance as the instructions page, condensed into what you need on the surface you are on.
  • Motion is used as signal: status badges pulse only on real status changes, approvals draw a checkmark on confirm, transitions crossfade rather than reload, and every route change goes through View Transitions. Reduce-motion at the OS level turns all of it off.
  • Empty states across dashboard, approvals, roles, requests, and the first-run team view use hand-authored SVG illustrations in a consistent editorial style — nothing loads from a third-party CDN.

Admin panel

Feature flags and team management, all in one place.

Feature flags
SLA tracking
Approval chains
Automation rules
SAML SSO
Team management
Facilities 8 members
IT 14 members
Procurement 5 members
HR 6 members

Demo questions

Use these quick answers to choose the right walkthrough before a pilot or sales call.

Can users see how to submit and track requests?

Yes. The user walkthrough shows login, dashboard views, submitting a request, tracking progress, search, My Work, and settings.

Is there an admin setup demo?

Yes. The admin walkthrough shows command center, teams, workflow setup, billing, security, connections, and reports.

Can this demo support a sales call?

Yes. The demo page is structured as a buyer-friendly walkthrough that links to role-specific screenshot tours.

Ready to get started?

Use this walkthrough as the base flow for live demos, pilot calls, and product videos, then point buyers to the matching warehouse or ops use case page.

Recommended live demo sequence
  1. Open the landing page and frame the request problem.
  2. Submit a request or show a fresh request entering the workspace.
  3. Open the dashboard and show queue visibility.
  4. Open request detail and narrate status, assignee, and timeline.
  5. Show the admin workflow/form controls that make the process adaptable.
  6. End on request-demo or pilot CTA depending on the buyer stage.