The conversation is operational work.
Good service starts with an answer.
Bring connected email and enquiry forms into a shared inbox. Keep the original conversation, review a drafted reply and turn a verified request into the right next step.
In the product today
Gmail and Resend connections, embedded forms, conversation triage, saved responses, editable AI reply drafts and reviewed booking creation. Provider connections and optional Bookings access must be configured.
See what’s nextThe shared Inbox with a conversation list, the app's email thread and a reply composer. Choose a conversation or inspect form submissions.
Current workspace layouts with sample data. Nothing is saved or sent.
04 · Work area
Inbox
Triage email conversations and structured form submissions in separate governed queues.
Sarah Hughes · Unassigned
Sarah Hughes
Receivedsarah@example.com · to enquiries@example.com
Hi, we have tickets for Friday's comedy night. Could we book a table for four at 6pm before the show? Thanks, Sarah
Try writing a reply. This sample cannot send email.
Based on the current Inbox workspace. Search and switch views using sample records. Nothing is saved, sent or charged.
On the other side of the shift
Less friction. More getting on with it.
- 01
See which conversations need a reply now.
- 02
Keep every response attached to its delivery evidence.
- 03
Turn verified booking requests into governed actions.
What’s included
Made for the job.
The practical details behind the promise. Built around the people doing the work, and connected to the information they need.
- 01
Your Gmail, inside the operation
Connect an authorised Gmail mailbox, sync conversations and send replies through the same account. Resend inbound routing is also supported.
- 02
Forms that become work
Build and publish embedded enquiry forms, then move submissions through New, Reviewing, Qualified and Closed without losing the original answers.
- 03
Replies with a human in charge
Write a reply, load a saved response or review an AI draft. Attach useful files and keep the provider’s reported send status beside the conversation.
- 04
From enquiry to booking
Review the guest’s date, party size and live availability, then confirm through Bookings when that product and the operator’s permission are enabled.
- 05
A queue the next shift can read
Keep assignments, needs-reply triage, open conversations and closed threads together. Customer context can join when CRM is enabled.
Part of the bigger picture
The context comes with it.
The guest, the venue, the team. Useful information should follow the work. Inbox connects to shared records, with access controlled for your organisation and your people.
A clear picture
Today. And what’s next.
Gmail and Resend connections, embedded forms, conversation triage, saved responses, editable AI reply drafts and reviewed booking creation. Provider connections and optional Bookings access must be configured.
Sending email and creating bookings require the configured provider and the operator’s permissions. This sample workspace cannot perform either action.
Good questions
Inbox FAQs.
Is Inbox part of CRM?
No. Inbox is its own separately entitled module. CRM may contribute customer context when both modules are enabled, but it never grants Inbox access.
Can Inbox work without Bookings?
Yes. Conversation triage and replies stand alone. Booking actions appear only when the organisation and operator also hold the required Bookings authority.
Where do replies send from?
Gmail replies return through the connected Gmail account. Resend replies use the configured sender. Soupy shows the status each provider actually reports; acceptance is not a guarantee of delivery.
Will AI reply or book without approval?
No. AI prepares editable proposals. An authorised operator sends the reply or confirms the booking, and live availability is checked again before a booking is created.
Start with the pressure point