Lunch Breaks Shouldn't Break Your Service
Lunchtable shows you exactly when each person is free to go on lunch and whether every support tier stays covered. Set it up in two minutes. Share one link with the team.
Lunch breaks shouldn't be a coverage gamble
If you manage an MSP help desk, you know the feeling. Two L1s go to lunch at the same time. The queue backs up. An L2 escalation comes in and nobody's there to catch it. You find out after the fact, when a client is already frustrated.
Three steps. One shared link.
Create a workspace
Name your team, define roles (L1, L2, L3), set minimum coverage per tier, and add staff. Takes about two minutes.
Share the link
Every workspace gets a unique URL. Drop it in your team channel. Staff open it and drag themselves onto a lunch slot.
See coverage in real time
The timeline updates live. Green means safe. Yellow means thin. Red means a tier has no coverage. Adjust before it becomes a client issue.
Built for the way MSP help desks actually run
Tier-aware coverage
Set minimum headcount per role. The board tracks L1, L2, and L3 availability separately, so you always have an escalation path.
Drag-and-drop scheduling
Staff pick their own slots by dragging onto the timeline. No back-and-forth messages. No manager bottleneck. The coverage indicator updates instantly.
Day-type staffing
Monday and Friday run differently than midweek. Lunchtable adjusts staffing expectations by day so coverage targets always reflect reality.
Absence tracking built in
Mark someone as out and the coverage math recalculates immediately. You'll see the impact before it hits the queue.
Zero setup overhead
No accounts. No installs. No vendor procurement. Create a workspace, get a link, share it. Your team is booking slots in under five minutes.
Live sync across the team
The board polls every few seconds. When someone books or moves a slot, everyone sees the change. No stale views, no version conflicts.
How it works under the hood
The app is a single SSR deployment. React renders the planning board, Astro serves the HTML, and API routes coordinate bookings and absences in PostgreSQL.
Browser → SSR render → API read/write → PostgreSQL
The board polls every few seconds, so every viewer sees the same schedule without manual refresh.
Tier minimums and day-type staffing rules are applied on every timeline refresh.
MSP Lunchtable beats bloated suites and brittle spreadsheets
You can force MSP coverage into enterprise scheduling tools or manage it in Sheets. Both routes add friction. Lunchtable stays focused on coverage, lunch windows, and escalation readiness.