Why desk booking should live inside Microsoft Teams
Organizations that run on Microsoft 365 spend their day inside Teams. Switching to a separate desk booking portal creates friction that leads to low adoption and empty desks. DeskHybrid brings the full desk booking workflow into Teams so employees can reserve desks, check attendance, and receive daily updates without leaving their primary workspace.
The Teams integration works through a bot that responds to slash commands and renders interactive Adaptive Cards. Employees interact with familiar Teams UI elements to browse floors, pick desks, and confirm bookings.
Teams bot setup
Installing the DeskHybrid Teams bot is an admin task that takes a few minutes. The admin navigates to the integrations page in the DeskHybrid dashboard, selects "Connect Microsoft Teams," and follows the Microsoft OAuth consent flow. The bot is then available to all employees in the tenant.
The Teams bot uses Microsoft's Bot Framework and requires minimal permissions: it needs to receive messages and send proactive notifications. It does not access files, emails, or call history. IT teams can review the permission manifest before approving the installation.
For organizations with strict app governance, the DeskHybrid Teams app can be deployed through the Teams Admin Center, allowing IT to control which users or groups have access to the bot.
/book and /whoisin in Teams
The `/book` command in Teams opens a booking flow rendered as an Adaptive Card. The employee selects a date, office, and floor. DeskHybrid returns available desks as a card with selection buttons. The employee picks a desk and confirms the booking with a single tap.
If smart desk suggestions are enabled, the available desks are sorted by colleague affinity, placing desks near frequent collaborators at the top of the list. The sorting is transparent: the card indicates why a desk is suggested, such as "Near 3 teammates" or "Your usual floor."
The `/whoisin` command returns a formatted list of colleagues who have booked desks for a given date. The response is grouped by team and includes floor information. Like the Slack version, it accepts date parameters: `/whoisin tomorrow` or `/whoisin 2026-04-03`.
Adaptive Card interactions
DeskHybrid uses Microsoft Adaptive Cards to render rich, interactive booking interfaces inside Teams. Adaptive Cards support dropdowns, buttons, and structured layouts that make the booking experience feel native to Teams rather than a bolt-on.
When an employee books a desk, the confirmation card includes the desk name, floor, date, and a cancel button. If the employee needs to change their booking, they can tap "Cancel" directly on the card and rebook without navigating elsewhere.
Adaptive Cards also power the daily digest. The morning notification arrives as a card with the employee's booking details, a summary of who is in the office, and a quick-book button for employees who haven't reserved a desk yet. The card layout adapts to the amount of content, keeping the notification compact and readable.
Daily digest in Teams
The daily digest is delivered as a proactive Teams message each morning. It arrives in the employee's chat with the DeskHybrid bot and includes their booking for the day, a list of colleagues in the office, and a prompt to book if no reservation exists.
Admins configure the digest delivery time and content in the DeskHybrid dashboard. Options include toggling the colleague list, the booking prompt, and team-specific attendance summaries. The digest uses Adaptive Card formatting for a clean, structured layout.
The digest complements the `/whoisin` command by providing attendance information passively. Employees who prefer to check attendance on demand use `/whoisin`. Employees who prefer a morning briefing rely on the digest. Both deliver the same underlying attendance data.
Booking parity across platforms
Bookings made through Teams are identical to bookings made through the web app, mobile app, or Slack. They appear on the floor plan, sync to connected calendars, count toward attendance metrics, and are subject to the same policy rules. There is no feature gap between platforms.
This parity means organizations can support employees who prefer different tools without creating data silos. A manager who uses the web dashboard sees the same booking data as an employee who books through Teams. Cancellations, modifications, and no-show automation work consistently regardless of the booking channel.
Internal Link Suggestions
- [Teams Integration Feature](https://www.deskhybrid.com/features/teams-integration)
- [Smart Desk Suggestions](https://www.deskhybrid.com/features/smart-desk-suggestions)
- [All Integrations](https://www.deskhybrid.com/integrations)
- [Pricing](https://www.deskhybrid.com/pricing)
- [Get Started](https://www.deskhybrid.com/get-started)
- https://officedeskapp.com/pillars/desk-booking-software-guide
- https://officedeskapp.com/pillars/hybrid-workplace-operating-system
Feature Proof Points
- feature:teams_integration
- feature:smart_desk_suggestions
FAQ
How do employees book desks from Microsoft Teams?:
Employees type `/book` in Teams. DeskHybrid responds with an Adaptive Card where they select a date, office, floor, and desk. The booking is confirmed with a single tap and a summary card appears in the chat.
Does the Teams integration require IT approval?:
The DeskHybrid Teams app can be deployed through the Teams Admin Center, giving IT full control over permissions and user access. The bot requires minimal permissions and does not access files, emails, or call data.
Can employees use both Teams and Slack with DeskHybrid?:
Yes. DeskHybrid supports both integrations simultaneously. Bookings made through either platform are synced and visible across all channels, including the web and mobile apps.
Are Adaptive Cards required for the Teams integration?:
Adaptive Cards are the default rendering format for interactive booking flows in Teams. They provide a native Teams experience with buttons, dropdowns, and structured layouts. No additional setup is needed; the cards render automatically.