For businesses

One Inbox for Every Customer Conversation

Mosey · 22 September 2026 · 3 min read

A venue's messages arrive from everywhere: a question about a booking, a note on an order, an enquiry about a party of twelve, an applicant asking about a shift. On most systems those live in four places and at least one of them goes unread for a week.

Mosey puts them in one inbox.

Everything in one thread list

Customer chats, reservation messages, private hire enquiries and job applications all arrive in the same list, each tagged with where it came from. You reply in the same place regardless.

The single most useful control is the needs reply filter: threads where the customer spoke last and nobody has answered. That is the list that costs you money, and on a busy week it is the only one worth opening.

Saved replies

The same six questions arrive every week. Write the answer once and it is a tap.

Parking. The accessible entrance. Whether you do a proper gluten-free kitchen. Last orders on a Sunday. Whether the dog can come in. Big tables on a Friday.

Saved replies are shared across every kind of thread, so an answer you wrote for a booking question also serves an applicant asking about the same thing.

Conversations that carry their context

A message about an order arrives attached to that order. A question about a booking carries the booking. You are not asking "which Tuesday?" — the thread already knows, and so does whoever picks it up after you.

Who can see it

Access follows your team's roles, so a manager and a staff member see what you decided they should. The thread history stays with the venue rather than with whoever happened to answer, which matters the week that person is on holiday.

Why answering fast is the whole thing

An unanswered message is not neutral. Somebody asked whether they could bring a buggy, got nothing, and booked the place that replied. The needs-reply filter exists because that is the single cheapest revenue on this page.

Setting it up

Open Inbox in your sidebar — it is on from the start.
Turn on messaging for customers so a "message us" option appears on your profile.
Write four saved replies before you need them: parking, access, dietary, big groups.
Filter to needs reply and make that the habit rather than scrolling the whole list.
Check who on your team has access, so cover exists when you are off.

What it connects to

Reservations — a booking question arrives with the booking attached.
Order Ahead and delivery — an order question arrives with the order.
Gatherings — a private hire enquiry is a thread that ends in a quote.
Jobs — applicant messages and interview scheduling land in the same list.
Outreach — the inbox answers; outreach starts the conversation.

Questions

Common questions

What is the Mosey inbox?

One place for every customer conversation — booking messages, order questions, private hire enquiries and job applicants — each tagged with where it came from.

What is the needs-reply filter?

It shows only threads where the customer spoke last and nobody has answered. On a busy week it is the only list worth opening.

What are saved replies?

Answers you write once and reuse — parking, access, dietary handling, last orders. They are shared across every kind of thread.

Does a message tell me what it is about?

Yes. A question about an order arrives attached to that order and a booking question carries the booking, so you are not asking which Tuesday they mean.

Can my staff use it?

Yes, following your team roles. History stays with the venue rather than with whoever answered, which matters when that person is away.

Do customers need the app to message me?

Customers message from the Mosey app. Enquiries that arrive by other routes still land in the same inbox.

Can I turn messaging off?

Yes. Messaging is something you enable, and you can switch it off if you would rather not take questions.

Does it cost anything?

No. The inbox and saved replies are included.