Real estate · Facilities management
Give tenants and contractors a facilities receptionist that understands their request, asks for the right details, and connects the conversation to your building operations. Atlas helps your team spend less time repeating questions and more time managing the property.
Atlas can look up caller profiles, building and unit affiliations, and associated active work orders. It confirms identity before discussing linked orders and asks callers to select the relevant location or request when there is more than one.
Collect the proposed work, location, dates, and tenant or contractor contact details through a guided conversation. Atlas turns the scope into a clear title and description, checks configured rules, and creates an open work order when the required information is complete.
Read the latest status of an associated work order or guide the caller through an extension request. Atlas checks the proposed end date against your configured policies, refreshes the order, and asks for confirmation before saving the change.
Match a reported symptom to an organisation’s configured fault guide and ask one check at a time. Atlas clarifies ambiguous symptoms, records the caller’s answers, and stops the checks if the caller cannot continue or reports a hazard.
When a fault remains unresolved, confirm the affected unit or unit group and the issue before submitting a report. The record includes the troubleshooting outcomes and conversation reference. Atlas reads back the fault reference only after the report is saved.
For unsupported requests or questions it cannot answer, Atlas can offer a facilities-team callback. It confirms consent and contact details, then saves the request and its context for staff follow-up.
From conversation to action
Identify the caller’s relationship to the property, confirm the relevant building or unit, and distinguish a fault, work-order request, status enquiry, or question.
Use your facilities knowledge, work-order rules, and fault guides. Ask for missing information and check the proposed action against the rules before submission.
Confirm the details that matter and save the supported request. A failed or uncertain save is not announced as a successful action, and retries are designed to avoid duplicate submissions.
Share the saved reference, current status, or confirmed update. Where the request needs a person, capture an agreed callback request with the context your team needs.
A practical example
Atlas clarifies the symptom and confirms the affected unit. It follows the fault guide your team has configured, asking one question at a time and waiting for the caller’s answer.
If the checks do not resolve the issue, Atlas confirms the details, saves a unit fault report with the outcomes, and returns the report reference. Your team receives a structured record of the issue and what the caller has already tried.
Illustrative report contents
For the facilities team
The facilities workspace supports work-order review and status updates. Case records retain status, versions, and transition history, with building, tenant, and unit references that help staff understand where a request belongs.
Configurable work-order risk screening can flag potentially high-risk work and provide a short reason for review. Assessments are advisory: they do not approve or reject work, change its status, or certify that it is safe.
Maintain the operational rules, facilities knowledge, and troubleshooting guides that Atlas uses. Agree who reviews applications, handles callbacks, and arranges attendance so each recorded request has an owner.
No. A new work order is an open application. Your facilities team retains responsibility for approvals, contractor access, and permission to start work.
Operational work-order rules and fault guides are configured for the organisation. Advisory risk criteria can be configured for an individual building. The setup should reflect how your property portfolio is organised.
Atlas uses the configured troubleshooting guide, if appropriate, and asks for the outcome of each check. If the issue is resolved, it does not file a fault report. Otherwise, it confirms the fault and location before saving a report. Reporting records a request; your team manages attendance and access.
Common-area requests that cannot be represented by the unit-fault workflow can use the consent-based callback path. The team can then review the location and decide how to handle the request.
The workflows described here record and update requests. Contractor dispatch, staff notification arrangements, and callback timing need to be agreed as part of your operating process.
Choose the buildings and caller groups to support, prepare your facilities information and work-order rules, and define the fault guides and staff follow-up process. We can then map those requirements to an Atlas workflow with your team.
Tell us about your buildings, the requests your team handles, and the rules that matter. We’ll help you define where Atlas fits into your facilities operation.
Talk to the Atlas team
