Workplace Request Operations

Relay

Route every internal request to the person who can move it.

A hierarchical workplace request desk with typed intake, reporting-line routing, confidential escalation, threaded resolution, analytics, and org-chart visibility.

Reporting-line-aware routing
Confidential escalation controls
Threaded ownership and resolution
Built for People operations, Workplace teams, Multi-location organizations
How it works

From setup to useful output

Connect the systems you already use, configure your context, and turn each workflow into a repeatable operating advantage.

01

Model the organization

Set reporting lines, locations, request types, and the people responsible for each workflow.

02

Raise a request

Choose a type and location, confirm the proposed owner, add context, and attach supporting files.

03

Resolve in one thread

Collaborate with assignees, update status, and keep every decision beside the original request.

04

Improve the flow

Use analytics and org views to find overloaded teams, overdue work, and recurring request patterns.

Capabilities

What Relay does

01

Requests routed by organization context

Use reporting lines, locations, and configurable request types to preview and select the right owner at intake.

02

A focused request inbox

Move between assigned, raised, team, and watched work with search, status filters, and clear queue counts.

03

Threaded work with attachments

Keep discussion, supporting files, assignees, status changes, and the final resolution inside the request.

04

Manager and subtree visibility

Managers can see requests owned across their reporting subtree without flattening the organization into one global queue.

05

Confidential escalation

Sensitive requests can skip the direct manager and remain visible only to the requester, assigned people, and authorized Relay administrators.

06

Operations analytics and org charts

Compare new versus resolved work, monitor overdue queues, and understand ownership through people and location views.

Integrations & data sources

  • Juniors organization directory
  • Reporting lines
  • Enterprise locations
  • In-app notifications
  • File attachments

On the stack

  • Your own PostgreSQL database
  • Your own object storage
  • Role-based product access
  • Real-time request updates
  • Actor-attributed history
  • No LLM required
Relay FAQ

Relay - common questions

Routing starts from the request type, selected location, and the requester's reporting line. Relay previews the likely owner before submission, and authorized users can adjust assignees when needed.

Ready to run Relay on your infrastructure?

See how Relay can fit your workflow. Book a conversation or send us your use case and we will map the right rollout path.

See Relay in action