Q moves it forward
Q collects dates, cabin preferences, travel party, and available loyalty details.
WITHQ FOR CRUISE LINES · SHORESIDE
From the first cabin question to the final pre-cruise detail, Q helps your shoreside team keep the journey connected—across voice, messaging, and human handoffs.
Book a cruise demoOne conversation.
A clear next step.
We loved our midship balcony last time. Can we find something similar for February?
I can help narrow that down. Which sailing dates are you considering, and how many guests will be traveling?
Check connected inventory or send the cabin preferences to reservations.
Illustrative workflows. Actions depend on connected systems, availability, and configured policies. No real requests are sent.
ONE GUEST JOURNEY. FEWER REPEATED QUESTIONS.
Dates, cabin preferences, travel party, and open requests belong together. Q helps collect the right information and pass it to the team or connected system that can act.
SEE THE WORK, STEP BY STEP
Choose a workflow to see what Q handles and where your team takes over.
Q collects dates, cabin preferences, travel party, and available loyalty details.
Reservations receives the inquiry, or a supported connected action proceeds under your rules.
BEFORE THEY BOARD
Capture sailing dates, party size, cabin preferences, and change requests. Check connected inventory or send a complete inquiry to reservations.
Help guests navigate dining, spa, and shore-excursion questions before departure. Route requests according to your booking windows and policies.
Use available guest history and confirmed preferences to inform the conversation. Ask for missing details instead of making the guest start over.
GROUPS & CHARTERS
Q gathers preferred sailings, group size, cabin needs, and event requirements so your sales team can start with a useful brief.
Explore AI Sales CoordinatorInquiry captured. No availability or price promised.
CONNECTED TO HOW YOU WORK
Begin with cabin inquiries, after-hours coverage, or pre-cruise guest questions. Define what Q should resolve and what your team should receive.
Review your reservation and guest systems. Set the rules for reading availability, placing a hold, requesting a change, or handing off.
Test exceptions with your team. A hold, a request, and a confirmed booking stay distinct, with the right person responsible for the next step.
This page focuses on shoreside guest service and reservations before sailing. Onboard operations would need separate discovery and integration scoping.
That depends on your reservation system, live inventory, and configured permissions. Q can complete supported actions or send the details to reservations. A hold is not a completed booking.
Q supports voice, web chat, SMS, WhatsApp, and email. We’ll scope the channels and handoffs that fit your shoreside operation.
Q follows your policies and routes exceptions to the responsible team with the request context. Changes that need approval remain pending until confirmed.
We’ll review your specific reservation, guest, and sales systems during discovery. Available actions are scoped to those integrations before a pilot; this page does not imply compatibility with every cruise platform.
BRING YOUR BUSIEST SHORESIDE WORKFLOW
We’ll map the guest experience, systems, and team handoffs.