Your industry · Your work OS
Your building management firm in ChatGPT.
Give property owners and prospects access to your services and contact journey. Your firm receives the subject and useful contact details without opening private building records.
What customers can do with your application.
What customers browse: Your services and the firm’s general contact instructions.
What you receive: The requested service, the building voluntarily identified, the purpose and the requester’s contact details.
Your benefit: Identify the subject before arranging a conversation with the relevant person.
What services does your firm provide?
I would like a proposal for our building.
How do I contact your team about an intervention?
Illustrative examples of the journey to configure. A submitted enquiry is not an accepted service order or a confirmed appointment.
Accounts, meeting records and residents’ information are not available through a public enquiry. The assistant does not vote or make co-ownership decisions.
Your initial scope and extensions.
The Customer AI Application includes your company identity, an authorised offer catalogue, conversational search, contextual enquiries, an administration dashboard and WebApp, plus initial configuration and launch testing.
Additional team workflows: Incident reports, interventions, decisions and manager handovers under existing access rules.
Booking journeys, business integrations, private documents and the internal workspace are defined separately, according to available features and the quote. They are not automatically added to the customer application.
Workflow example
An incident continues across several people.
A resident reports an incident in a shared building.
The contractor’s response requires a committee or authorized owner decision.
The building group keeps the report, decision and next owner connected.
The next manager continues the incident history rather than opening an unrelated request.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
Building management: continue each incident after the report
On this page
Preserve a useful incident report
An occupant reports a problem in a shared area. Context should identify the building, location, contact person, reported observation and useful access information. Uncertain information still needs checking.
Coordinate the next step
The manager retrieves earlier interventions, the expected approval and relevant provider. The calendar organizes the time; the mission keeps what needs preparing and who is responsible.
Prepare handovers
An available report can contribute to the building’s or team’s authorized group. A change of manager must not erase commitments made to occupants.
A resident’s private information does not need to become visible to every provider.
Review recurring issues
Find comparable reports, previously discussed work and recurring blockers. This helps prepare a human decision; it does not replace technical analysis or formal deliberations.
Professional scope and responsibilities
Co-ownership decisions, accounts, votes, regulatory obligations and technical approvals remain in specialist procedures and software. AlefOS preserves authorized coordination context; it does not certify that an incident is resolved.
Your team’s tools
Explore features, connections and access rules in the AlefOS documentation.
Explore the documentation ↗Continue exploring
This workflow uses capabilities configured in your company’s environment, under your brand. Your team can use a compatible assistant to consult authorized context through its configured MCP connection. Understand your AI connection ↗