One inbox for everything a visitor did
If you run a small place, the day arrives in fragments. A question through the contact form. A table booked at nine in the evening. An order for two mugs while you were closed.
Those are three different modules with three different jobs, and until now they were three different screens. They are now also one list.
How it works
The inbox merges enquiries, bookings and orders per site, newest first, filtered and searchable. Read state is tracked separately from archiving, so marking something read does not make it disappear.
Every row still opens the real record it came from. A booking row opens the booking, with its lifecycle and its guest. An order row opens the order, with its items and its payment. Nothing is flattened into a summary you cannot act on.
Why not just email
Email is a copy, not a record. It arrives, it gets buried, and there is no state on it beyond whether you happened to leave it bold.
Submissions are always stored regardless of whether email is switched on. The inbox is the thing that is true; the email is a notification about it.
Make one page tonight.
An account, a starting point, and a form that sends you a real email. Nothing is public until you say so.
