When you want to further analyse your overall commercial picture, understand what the system is doing, make bulk updates, or steer it in a particular direction: that is where Evo Researcher comes in, beyond the day-to-day elements your revenue management system (RMS) is already optimising, automating, and processing.

With the revenue management connector enabled, Evo gives you a conversational window into the system across five capability areas: pricing and recommendations, competitive rate intelligence, forward performance and budget, demand events and forecast signals, and multi-property management. Ask what is happening on a specific date, check how your rates sit against the competitive set, log a demand event and share it across your group, or set a strategic guardrail, all without opening a single screen.

As with other connectors available across Access products, you can also bring your own documents, reports, and data into the same conversation. Drop in a raw export, a budget spreadsheet, or a set of meeting notes and ask Evo to work with them alongside your live data, in your format, for your audience, without reformatting anything first.

You need an active Evo Researcher subscription with the revenue management connector enabled. The connector covers five modules: Pricing Management, Rate Shopper, Status Screen, Events Calendar, and Budget. Access to each depends on your hotel's module permissions. Evo will only surface data and actions available to your property.

Your RMS holds a significant amount of intelligence about your property: pricing recommendations, competitive position, forward occupancy, budget performance, and demand signals. Evo surfaces all of it through conversation, without you needing to navigate screens or pull reports.

You can also bring your own context into the conversation. Upload your own market research, event calendars, strategy documents, or historical data and ask Evo to cross-reference them against your live data. If your team works to a specific report format or stakeholder template, upload it and ask Evo to produce the output in that structure. Evo adapts to how you work.

Try asking:

The RMS makes most decisions automatically. The connector is there for the moments when you want to shape the space it works within, respond to something it cannot know about, or manage the data that informs its forecast. Every action is confirmed by Evo before it is applied.

View the live pricing grid, check what the system is recommending versus what is actually set, and apply overrides or guardrails when you want to steer it. A guardrail sets a minimum and maximum price within which the system continues to optimise freely: you define the boundaries, it does the rest. You can also apply a bulk price update across multiple segments and date ranges in a single instruction rather than updating cells one at a time.

Try asking:

See how your rates sit against the competitive set, day by day across a 61-day window, or drilled into a specific date for a competitor-by-competitor breakdown. Use this alongside your own market research to understand your position in context, not just in isolation.

Try asking:

Get the on-the-books performance dashboard for the coming months, check budget versus actual for any year or month, and drill into daily budget data when you need it. Upload your own budget templates or completed spreadsheets and ask Evo to update budget values directly, with no reformatting required.

Try asking:

The forecast is only as good as the demand signals it has to work with. Use Evo to view what is already logged, create new events when you learn about something the system cannot know about, such as a conference, a local festival, or a recurring pattern, and share them across your property group in a single step. You can also review external events of interest surfaced by the system and assign impact or dismiss them in bulk.

Try asking:

List hotels in your business group, transfer demand events across properties in one step, manage events-of-interest country subscriptions per property, and upload or download budget templates across your portfolio, all through conversation.

Try asking:

Use it to understand before you act. The system is making decisions continuously. Before applying an override or guardrail, ask Evo to show you the current pricing grid, the competitive position, and any demand events logged for the dates in question. One question gives you the full picture.

Keep the demand calendar current. The system can only factor in what it knows about. When you learn about a local event, a conference, or a pattern that is not yet logged, create it in Evo and transfer it to your group properties in the same conversation. The forecast updates from there.

Use guardrails rather than overrides where possible. Setting a minimum and maximum price lets the system continue to optimise within a range you are comfortable with, rather than locking a price that may become stale. Remove the guardrail when conditions normalise.

Drop data in as it is. Budget spreadsheets, performance reports, meeting notes: give them to Evo in whatever format they are in and ask it to work with them. You do not need to clean or reformat anything first.

Work in your own formats. If your team produces a specific weekly report or uses a template your stakeholders expect, upload it and ask Evo to produce the output in that shape. Evo works to your standards, not its own.

Verify after every write action. Ask Evo to confirm the updated pricing grid, guardrail status, or demand calendar after any change. Evo always confirms what it is about to do before acting.