What goes on it
Put the usual asks where clients can reach them
Some requests arrive the same way every month: a change to last month's report, a quick question about an invoice, a new engagement that always starts with the same five questions. Each one costs an email to you and a request your project manager types up by hand. Put those on Front Desk and the client starts them directly, with the form you would have sent anyway, while the bigger, messier work still starts with you.
Services clients can order
One-off services with a fixed price, subscriptions with packages and billing cycles, and custom work that starts as a request and gets priced in your quote. Each service has its own order page with add-ons and an order form, and you decide which of them appear on Front Desk and in what order.
Requests that cost nothing to send
Not everything on Front Desk is for sale. A request type like "Support ticket" can sit there as its own tile, and the form the client fills in becomes a request your team picks up like any other. For visitors who don't have an account yet, a "Submit request" button offers only the few types you pick, such as a pre-sale question, while logged-in clients keep seeing the request types they already have access to.
One link for one service
Not every client needs the whole page. Every service has its own order link that works whether or not the service appears on Front Desk, so the "Kick-off workshop" can go straight into a proposal or a chat message. The full Front Desk lives at your workspace address, or on your own domain, under /order.
Shown to the clients who use it
Front Desk is a choice you make per client, not a switch for everyone. Leave it out of the sidebar for clients who never buy through the portal, put an "Order service" button on the dashboard of the ones who do, and give that button a label that fits them.









