Notifications
What this screen is for
The first screen that opens when a browser notification is clicked, and it carries exactly one purpose: read what the notification carries and send the reader to the right place. The decision is made in this one place, because the service worker that shows the notification carries no copy of this routing logic.
When you would use this
When a business owner clicks a BookThing notification in the browser, the browser opens this screen first and it forwards to the real destination right after.
Who sees it
Anyone who clicks a BookThing notification passes through this screen; the screen itself never checks whether the session is still valid — the screen it forwards to enforces its own access rule.
Where it lives
The screen exists on the web panel only; on the mobile app, clicking a notification goes straight to the matching screen and never passes through an in-between routing screen.
What you can do here
Send a messaging notification to the conversation
A notification announcing that a new conversation has started routes explicitly to that conversation on the messages screen.
Send an appointment notification to the appointments screen
Request, approval, rejection, cancellation, edit, reschedule, and no-show notifications — whichever side they were addressed to and whatever reminder interval sent them — all route to the business appointments screen.
Send an order notification to the orders screen
An order notification routes to the orders list; it does not open the specific order the notification was about, whichever order that was.
Send a business notification to the appointments screen
A notification about the business as a whole — suspension, suspension being lifted, or a change to the appointment rule — also routes to the business appointments screen; since the panel has no separate account screen, this is where an owner sees the business's status.
What the server accepts and refuses
A notification type this build does not recognise sends the reader nowhere blank
When the notification carries a type this build does not know, or a link with no business id on it, the screen routes to the business picker instead of leaving a blank page; clicking a notification and having nothing happen is treated as worse than landing in the wrong place.
The back button returns to before the notification, not to this screen
The redirect replaces this screen in the browser history instead of adding to it; pressing back after a notification returns the reader to wherever they were before it, not to this in-between screen.