How many people are in the building today?
Are there any new support tickets?
What should I do if I lose my access card?
None of these questions is especially complicated. But answering them through traditional software can require users to know which area of the platform to open, which report or record to find, or where the relevant building policy is stored.
Oracle gives authorized BluSKY users another way to work. Start with a question in plain language, while BluSKY handles the appropriate information and permissions behind it.
Software interfaces are organized around screens, menus, reports, records, and workflows. That structure gives users control, but it also creates knowledge they have to acquire before they can use the system efficiently.
Consider a basic occupancy question. A user may know exactly what they want to learn without knowing which report contains the answer. Getting there can mean finding the reporting area, locating the right report, configuring it, and reviewing the output.
The user’s real objective is much simpler: find out how many people are in the building.
The same disconnect can appear elsewhere. Someone looking for a support case may need to understand how tickets are organized. Someone with a policy question may need to know which document contains the answer.
With Oracle, users can state the request in natural language instead of first translating it into the structure of the software.
Watch how Oracle reduces the software steps between a user’s question and the BluSKY information they need.
Start with a simple question: “How many people are in the building today?”
Oracle analyzes the request, determines what information is needed, verifies the user’s permissions, and retrieves the appropriate data. It provides a summary along with the option to view or download the full report.
Users who already know what they want can also ask Oracle to run a specific report, such as the Person Status Report. Oracle can run the 100+ reports available in BluSKY.
The interaction does not have to end when the report appears. After seeing the occupancy result, the user asks for a list of tenants and the number of people associated with each. Oracle uses the report already in context to generate the breakdown.
The underlying report remains part of the workflow. What changes is the amount of system-specific knowledge required to reach it and continue working with its information.
Support records provide another example.
A user asks Oracle to “List any new support tickets.” Oracle searches the relevant records and returns the results. The user then asks, “Give me the details of ticket 02703,” and moves directly from the list to the specific case.
Without that natural-language path, the same task may require opening the support area, applying filters, scanning the results, locating the correct ticket, and opening the record.
Those controls remain available when users want to browse or manage information directly. Oracle adds a more direct option when they already know what they are looking for.
The same experience can support questions about ticket statistics, trends, categories, or overall system health. Instead of beginning with the structure of the support system, the user can begin with the information they need.
Not every friction point comes from navigating software.
Someone who loses an access card may need to know where to get a replacement, when the office is open, whether there is a fee, and what steps to follow.
That information may already exist in a building-specific policy. But accessing it can still require searching through documents, navigating a portal, or contacting property management for an answer.
With Oracle, the user can ask directly. Oracle can retrieve the relevant building policy and provide applicable replacement instructions, office hours, fees, and other facility-specific details.
Routine self-service can reduce repeat information requests while leaving property management, security, and support teams responsible for the work that requires their involvement.
It also extends the value of natural-language interaction beyond system data. Policies, procedures, and other approved building knowledge can become easier for authorized users to access when they need them.
Security teams, property managers, and facility operators still need expertise in their buildings, policies, risks, responsibilities, and operational priorities. They should not also need to memorize where every report, record, or procedure sits inside the software.
Oracle reduces that application-specific knowledge while staying within each user’s authenticated BluSKY context and permissions. Natural language does not expand what a user can see or replace the reports, records, and controls behind an answer.
People open building software to understand something, investigate something, or complete a task. Oracle lets authorized BluSKY users begin closer to that outcome instead of first translating it into a series of software steps.
Explore a more natural way to work with BluSKY by starting with the question instead of the software path.
