Sales and reception follow the same rules
This example shows the module’s role in a hotel process. We define the source scope and available actions for each implementation.
Question about staying with a pet
Reception and a sales representative need the current rules for staying with a dog. The hotel has changed the fee and the availability of selected rooms, while the old document is still circulating by email.
An approved source instead of a random version
The environment provides up-to-date knowledge according to the user’s role. The response identifies its source. If a decision requires room availability, this requires integration with the booking system, not the language model alone.
- Source version control
- Role-based access
- Tool usage history
What does this module cover?
We configure access to models, searches across agreed sources, users and operating rules. The roadmap starts this foundation with website integration; documents, interviews and operational data extend it in later stages.
Shared context
Tools use approved knowledge instead of independent copies of procedures.
Roles and permissions
Access to a document or function depends on the role and scope of the specific implementation.
Operational oversight
Query and operation histories help check quality and explain errors.
How do we launch the solution?
Defining the first use case
We select the process, users and sources needed for the work.
Connecting knowledge and models
We configure data access, access rules and how sources are identified.
Testing and expansion
We check typical questions, data gaps and prohibited operations before adding further modules.
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?
- Approved hotel knowledge
- Users and roles
- Requirements for models and data processing
What does the team receive?
- Shared AI working environment
- Context available to further modules
- Tool usage history and rules
Permissions and decisions remain with the hotel
Before launch, we agree data access, responsible people and how exceptions will be handled.
The hotel approves sources, roles and permitted actions. Access to knowledge does not automatically grant permission to send messages, change bookings or publish content.
The foundation itself is not an autonomous agent for every department. Research, quoting, publishing and guest service require the appropriate modules and integrations.
What changes in day-to-day work?
Different tools can refer to the same current agreements.
New use cases benefit from proven access and knowledge.
Which sources and tools do we connect the module to?
The choice of models and data storage method depends on the implementation requirements. We do not assume a single provider or unlimited access to all hotel systems.
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
See other connections (27)
- Outbound analysis
- Competitor analysis
- Content analysis
- Image analysis
- Content gaps
- SEO and traffic
- Technical analysis
- Mention suggestions
- Review analysis
- Comment analysis
- Response audit
- Response comparison
- Reputation alerts
- Risk filter
- Post analysis
- Reaction analysis
- Channel comparison
- Opportunity radar
- Posting rules
- Asset library
- AI concierge
- AI chat
- AI messaging
- Email suggestions
- Missed-call recovery
- Portal suggestions
- Review chat
Frequently asked questions
Is this a ready-made CogniVis Platform?
No. This roadmap node describes the infrastructure for tailored AI implementations. The ready-made Platform is a separate product offering.
Do all data need to be connected straight away?
No. We start with the sources needed for the selected process and expand the scope after checking quality and permissions.