Requests

Stop chasing people to fill sessions.

Handle availability changes, declines and replacement requests without endless messages.

teamstack.app / requests
Teamstack requests inbox showing pending assignments, replacements and accept or decline actions

Someone cancels. Now what?

A last-minute cancellation should not turn into a scavenger hunt. Most teams still rely on messages, phone calls and hope that somebody replies in time.

  • Cancellations arriving minutes before a session
  • Managers messaging whoever they can think of
  • No shared view of who is available
  • Nobody knowing whether the session is covered

Without Teamstack

  1. Tutor cancels at 10:14
  2. Manager messages 7 people
  3. 3 don't reply
  4. 2 aren't available
  5. Nobody knows whether the session is covered

How Teamstack solves it

Teamstack does it differently

Central request inbox

See operational requests in one place.

Session responses

Members can accept or decline assignments.

Replacement workflow

Find another available member when somebody cancels.

Clear status

Every request has an obvious state: Pending → Accepted → Resolved.

Product showcase

One inbox for the operational mess other tools leave in chat.

Pending assignments, emergency cover and replacement requests sit together with a status you can act on.

Pending tasksReplacementAccept or declineClear status
teamstack.app / requests
Teamstack pending tasks inbox with assignments, replacements and accept or decline actions
Teamstack mobile requests screen for taking a session

Before / after

The same cancellation. A different afternoon.

Without Teamstack

  • WhatsApp
  • Phone calls
  • Spreadsheets
  • Manual chasing

With Teamstack

  • Request created
  • Available members identified
  • Replacement assigned
  • Schedule updated

How it works

From a cancellation to a covered session.

Create the request, identify who can take it, assign cover, and the schedule updates.

  1. 01

    Request created

    A decline or cancellation opens a request automatically.

  2. 02

    Available members identified

    See who can take the session without starting a group chat.

  3. 03

    Replacement assigned

    Cover is confirmed and the schedule updates.

Connected workflow

Requests keep the schedule honest.

Acceptances, declines and replacements feed straight back into scheduling, attendance and payroll so the operation never drifts from the calendar.

Outcome

What changes for the team

Less chasing

Stop messaging seven people to fill one session.

Faster cover

Available members see the request and can take it before the session starts.

Certainty before the session

Managers know whether the slot is covered without reconstructing a chat history.

Connected product

Everything works together.

Scheduling, requests, attendance and payroll share the same sessions. Availability feeds the rota. The mobile app is how members stay in the loop.

Availability
Mobile App

Connects the people doing the work to every module above.

Run your team without the operational mess.

Bring scheduling, requests, attendance and payroll together — then let the people doing the work stay in the loop from their phone.