at work — Workspace and Meeting Booking for Central Pattana

Central Pattana's at work business leases desks and meeting rooms, but booking went through staff — so customers could only book in office hours, and staff spent their day taking bookings instead of running the space.

The harder requirement was fitting in. The system had to live on the CPN Application Platform: their corporate identity, their security standards, their DevSecOps practice, and the ESD department's zero-training policy, which holds that people should be able to use it without being taught — so that it integrates with the rest of the ecosystem rather than sitting beside it.

And the destination was a branch that opens without anyone on the desk.

Two web applications, not an app anyone installs.

Customers book the whole thing themselves

Desks and meeting rooms booked, bookings checked, payment taken and the feedback form filled in — start to finish. Built to feel like a mobile app while opening from a browser, on a phone or a computer.

Staff get a management system

Meeting rooms and bookings managed, reports read from whichever angle is wanted. Built to feel like desktop software, because this is work done all day on a large screen rather than picked up on a phone.

Two audiences, two front doors

Customers sign in through Amazon Cognito; staff through the organisation's Microsoft Entra ID. The two sets of permissions are separated at the identity layer rather than by a condition somewhere in the code.

Wired into what CPN already runs

It connects to the O2O commerce system for orders and payment, requests each branch's at work WIFI credentials from AIS on the customer's behalf, and sends mail through the corporate SMTP — rather than rebuilding any of it.

Branches that run unattended

Each site has a small on-premises controller driving the equipment. Customers get in by scanning a QR at the reader, while the electronic shelf labels and signage update centrally. Somebody who finishes booking on their phone can walk in and start working.

Running on the client's own infrastructure

All four components are containerised onto CPN's own Kubernetes cluster on their private cloud, sharing a SQL Server database, with logs flowing into CPN's own analysis stack — so their team can keep it running with the tools they already use.