Guests do not have to repeat the same story from the beginning
When contact moves from chat to a messaging app, or from AI to a member of staff, the key details and open questions move with it.
Change of arrival time
The conversation started on the website, and several hours later the guest shared a new arrival time on WhatsApp and asked for confirmation of key card collection.
Context ready for the night reception team
The module brings messages together, updates the next step and shows a brief summary to the person taking over the shift.
- contact history
- confirmed details and open questions
- owner and deadline for the next step
One need, one context and a visible next step
The module maintains continuity across channels and staff members. It only links contacts when there is a sufficient basis for identification.
Brings messages together
Groups contacts relating to the same need using an identifier, contact details and context.
Summarises the details
Separates confirmed information, open questions and the promised next step from the full history.
Keeps track of unfinished cases
Reminds the team about conversations left unanswered or handed over without an owner.
How does the system maintain conversation continuity?
Identifying the case
AI identifies the guest’s need and looks for a safe link to an existing thread.
Linking contacts
It arranges matching messages from different channels into one chronological history.
Updating the context
It extracts new details, the owner and the next step without removing the source material.
Handover or reminder
The person taking over receives a summary, while a lack of response is added to the unfinished cases queue.
Linking requires a reliable identifier or confirmation
This may be based on a booking reference, verified contact details or another agreed link. Uncertain matches should wait for a staff member’s decision.
What does AI use?
- conversation histories from connected channels
- booking or contact identifier
- confirmed details and case status
- owner and deadline rules
What does the team receive?
- shared contact thread
- summary of details and open questions
- next step, owner and reminder
Uncertain conversations must not be forced together
A staff member can approve, separate or correct a link. The system preserves the sources and shows the basis on which it linked the contacts.
The team resolves uncertain matches, changes the owner, closes the case and decides on the next response.
The module does not reply automatically, link people without a sufficient basis, change bookings or replace the judgement of the person taking over the case.
Less lost context with every handover
Guests do not have to explain the case again when the channel or staff member changes.
The team knows what was promised, who took ownership and when they should follow up.
Conversations without a response or owner go into a visible queue.
Channels meet in the Central Communication Hub
A shared history is created from chat, messaging apps, email and telephony. Booking identifiers can increase confidence in the link.
Related process elements
Frequently asked questions
How does the system recognise the same case?
It uses agreed identifiers, such as a booking reference or verified contact details, along with the conversation context.
What happens when a match is uncertain?
The thread should not be linked automatically. The system shows the suggestion to a staff member for approval.
Can staff see the full history?
Yes, according to their permissions. They also receive a brief summary of the key details.
Does the module reply to overdue conversations automatically?
No. It highlights the lack of response and the next step; a staff member or a separate approved automation module sends the reply.