Website information becomes part of shared knowledge
This example shows the module’s role in a hotel process. We define the source scope and available actions for each implementation.
Seasonal hours changed
The hotel updates its SPA page. Reception should not have to copy the same information manually into several assistants.
Content with its source retained
The index reads the new version of the subpage according to schedule. The AI platform can use the current section while identifying its source. The website widget uses it only after the relevant response process has been connected.
- Subpage URL
- Date last accessed
- Content ready for use
What does this module cover?
We agree which domains, languages and subpages should provide knowledge. We separate permanent information from time-limited offers. Embedding a widget is a separate part of the configuration and requires access to the website or its administrator.
Content with a URL
A response can be linked to a specific subpage rather than an anonymous copy of the text.
Controlled updates
Changed and withdrawn information is handled according to agreed synchronisation rules.
Space for widgets
An agreed script can add an interactive channel to an existing website.
How do we launch the solution?
Selecting sources
We define the URLs, languages and exclusions, such as old offers or technical subpages.
Access and testing
We check that the content, structure and currency of the materials are recognised correctly.
Making it available
We connect the sources to AI and test selected widgets on the website before launch.
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?
- Hotel website URLs
- Update rules
- Access to embed selected widgets
What does the team receive?
- Web content index
- Sources and access dates
- Prepared website channel
Permissions and decisions remain with the hotel
Before launch, we agree data access, responsible people and how exceptions will be handled.
The hotel approves the list of sources and is responsible for keeping them up to date. Conflicting hours or prices on different subpages require a decision, not an arbitrary choice by AI.
The integration does not provide access to private CMS data and does not replace a PMS or booking engine. It does not publish website changes independently and does not guarantee higher search rankings.
What changes in day-to-day work?
Several processes can use the same approved information.
The property's public knowledge provides the foundation for the first AI scenarios.
Which sources and tools do we connect the module to?
Access and embedding capabilities depend on the website technology. Dynamically loaded content or content available only after login is assessed separately.
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.
Modules that require this element
- AI platform
- Hotel guest guide
- Central Communication Hub
- Competitor analysis
- Content analysis
- Image analysis
See other connections (3)
Frequently asked questions
Do we need to build a new website?
Usually not. The scope of work depends on the CMS, how content is made available and whether a script can be embedded.
Is a website change immediately visible to AI?
Not always. The delay depends on the agreed synchronisation process. Critical information may require additional approval.