Respond without switching between windows
This example shows the module’s role in a hotel process. We define the source scope and available actions for each implementation.
A new message in a long thread
The organiser comes back with a question about a different conference date. Before preparing a response, the sales representative needs the previous arrangements concerning the room and number of overnight stays.
Support where the work happens
The assistant displays context from the email index and launches agreed tools, such as a summary or response suggestion. Availability checking is only available after the relevant module and system have been connected.
- Current thread context
- Editable draft
- Separate send approval
What does this module cover?
This is an AI working interface within a selected email client. The range of functions depends on its capabilities and connected modules. The email index provides the required context; transcripts can supplement arrangements discussed by phone.
The right thread
The assistant works in the context of the message the employee is handling.
Tools close at hand
Summaries, research and response suggestions can be accessed from one place.
Draft under control
The user reviews and completes the suggestion before sending it.
How do we launch the solution?
Choosing an email client
We check the available extensions, permissions and the team’s way of working.
Connecting the context
We connect the assistant to the index and tools needed for the relevant process.
Testing scenarios
We check the correct thread, cited sources and the boundary between drafting and sending.
What goes into the module and what comes out?
We separate source material from the tool’s output. This helps subsequent modules understand which context they can use.
What does AI use?
- Open message
- Email index
- Agreed support modules
What does the team receive?
- Context visible beside the email
- Suggestions and summaries
- Actions approved by the employee
Permissions and decisions remain with the hotel
Before launch, we agree data access, responsible people and how exceptions will be handled.
The employee selects the function and checks the result. Automatic sending, if it is to be implemented at all, requires a separate process and approval conditions.
The assistant is not an autonomous quoting agent. It does not gain access to the PMS, CRM or rates simply because it operates within email.
What changes in day-to-day work?
The thread content does not need to be copied manually into a separate tool.
Further support functions are brought into an interface familiar to sales representatives.
Which sources and tools do we connect the module to?
We confirm whether the assistant can be embedded for the email client version in use. Not every application offers the same range of functions.
Related process elements
Its place in the implementation journey
These links come from the roadmap. Requirements form the basis of each node, while enrichments extend its capabilities. This does not mean that all subsequent modules must be launched at once.
Required foundations
Additional context and capabilities
Modules that require this element
- Lead research and qualification
- Lead follow-up questions
- Follow-ups
- Contact history summary
- Phone call summaries
- Response suggestions
See other connections (2)
Frequently asked questions
Does the assistant reply to guests on its own?
Not in the standard support scenario. It prepares the material, while the employee decides on its content and whether to send it.
How is it different from a response suggestion?
The assistant is a workspace. Response suggestions are one of the features that can be made available within it.