An opportunity links a date to a specific hotel offer
A date in the calendar alone is not enough. The radar shows why the topic matters, when to start work and which information it uses.
Local festival date announced
The event will take place two kilometres from the hotel, and the website features a weekend package with late check-out.
Topic ready to schedule
AI identifies the audience, related package, suggested channel and latest safe date to begin preparations.
- event source and date
- link to the hotel’s offer
- content preparation date
Timely reasons to create content
Radar gathers opportunities from the seasonal calendar, the local area and changes to the hotel website. Internal plans can be added through additional sources if the team makes them available.
Monitors the local area
Detects relevant dates, events and public changes related to the hotel’s location and offering.
Links to the offering
Identifies a service, package or experience that naturally matches the opportunity detected.
Keeps track of deadlines
Calculates when content preparation should begin so the publication does not appear too late.
How does a signal become a publishing opportunity?
Reading the sources
AI checks the calendar, hotel website, local events and shared internal sources.
Assessing relevance
It verifies the date, location and possible relevance to the audience and offering.
Setting priorities
It organises opportunities by urgency, relevance and the time needed for preparation.
Adding to the plan
It creates a card with the rationale, channel, deadline and links to the sources.
Every opportunity has a date and a source
AI should not build a plan around an unconfirmed event or an outdated offer. The opportunity card shows the source, the date it was checked and any missing information.
What does AI use?
- seasonal calendar and local events
- indexed hotel website content
- offers, packages and key dates
- optional plans and internal materials
What does the team receive?
- prioritised opportunity queue
- link to the offering and audience
- source, deadline and suggested channel
The team decides what fits the brand
A current topic is not always right for the hotel. A team member can approve an opportunity, change its priority, reject it or add context.
The team chooses which sources and region to monitor, verifies uncertain events and decides which opportunities enter the calendar.
The module does not write posts, create graphics, build a complete calendar or publish content.
Fewer topics noticed too late
Dates, events and changes to the offering are visible in one place.
The team knows when to start work, not just the date of the event itself.
Each opportunity identifies an offering or experience the hotel can communicate.
The hotel website is the foundation; internal sources extend it
Website integration helps detect public changes to the offering. An additional index and context interview can add promotions, plans and events not yet published on the website.
Related process elements
Frequently asked questions
What opportunities does the radar detect?
Seasonal dates, local events, changes to the offering on the website and, once connected, approved internal hotel plans.
Does an event have to be public?
No, if the hotel shares it through an additional source. The card always shows where the information came from.
Does the radar add topics to the calendar automatically?
No. It prepares an opportunity queue, while the team or the Content Calendar module decides on the plan.
Does the radar publish posts?
No. Generation and publishing belong to separate subsequent modules.