Skip to content

Sunday for IT and support

Give every request a clear path to resolution.

Turn incoming requests into owned, visible work with the context and controls your team needs to support people well.

Start free See the request path

Support request flow

External intake
Sunday table view with owners, status, priority, and dates.

Start with a controlled request path

External intake

Turn controlled public forms into structured work without exposing the workspace, so every request starts with the context your team needs.

See external intake

What this gives an IT team

  • The details needed before support work begins
  • Structured requests without exposing the workspace
  • A visible owner, status, and next step for every request

Keep the response path dependable

A support system that stays controlled as it moves.

The request, its automation, and the permissions around connected work stay together from intake through resolution.

Automations

Move support work and connected actions from validated status rules.

See automations

Permission checks

Authorize actions as the acting user and scope them to the workspace or board.

See permission checks

MCP & API

Give approved agent clients and integrations the same validated capability layer.

See MCP & API

From incoming request to resolution

Make support work easier to start and easier to finish.

Every request enters with the right details, goes to an accountable owner, and remains visible until the work is resolved.

  1. 1

    Receive a complete request

    Collect the needed context through a controlled request path.

  2. 2

    Route it with clear ownership

    Use the request details and rules to move the work to the right next stage.

  3. 3

    Resolve with a visible trail

    Keep status, ownership, and follow-through clear until the request is complete.

Sunday for IT and support

Make every request easier to support.

Start with a controlled support flow that keeps the request and the resolution on the same plan.

Start free