Reception is your server's safe front door. It is a set of public pages that people outside can use. They can book a time, fill in a form, hand you a file, or answer an approval. Your own server serves the pages. They never go through Recued's cloud. A visitor needs nothing but the link.
#What you can publish
- Reception pages: pages you build from blocks. A block can be text, a form, or links.
- Scheduling links: offer time slots and take bookings.
- Intake forms: a form with set fields. It collects a request from a client or someone you work with.
- File drops: a place where someone can hand you a file.
- Approval links: let one chosen person answer a question you sent to them.
- Customer sign-offs: share an exact quote and scope, then review its task and invoice before releasing work. See Customer sign-offs.
#Make a page from a template or a sentence
There are two ways to make a page. Both give you the same kind of page. You can pick a template from the gallery and fill in its slots. Or you can say what you want in one sentence and let AI suggest the page. A template is built from its slot values the same way every time. AI can make the words better and guess at optional defaults. But AI is never needed. A server that is offline, or has no model set up, can still publish every first-party template. Either way, you look at the suggested page and fix it before it goes live.
#Requests wait for you
By default, Reception works like this: you review first, then you approve. When someone sends something in, nothing runs. The request becomes a held action. It waits at the same gate as everything else. It lands in your inbox. There you can see what was sent. You can fix the details if they need it. Then you approve or decline. Nothing a visitor sends runs before you decide.
#Attachments
A file a visitor sends lands in your warehouse, like any other file that comes in. The warehouse is the place on your server that keeps your data. The file stays attached to the request. You can add scanner packs. They can check a file and add a note about it before you open it. The note is advice only.
#Reachability
A public page needs a public name. See Reachability. The name points straight at your server. The page, the things people send, and the files never pass through the cloud.
#Related
- Grants and approvals: the gate that holds requests that come in.
- Selling access: a reception page can hold the link to a seller's checkout.