Your industry · Your work OS
Your construction company, accessible in ChatGPT.
Present your construction services in your company’s application. Prospects can explain a project and submit an enquiry; site communications and documents remain within their authorised scope.
What customers can do with your application.
What customers browse: Your services and the project enquiry information published by your company.
What you receive: The type of work, location when requested, stated constraints and contact details.
Your benefit: Receive project context to prepare the initial sales discussion.
What types of construction work do you undertake?
I would like to discuss a renovation project.
How can I request a conversation before a quote is prepared?
Illustrative examples of the journey to configure. A submitted enquiry is not an accepted service order or a confirmed appointment.
The base application does not calculate quotes, quantities or construction schedules. Technical studies, commitments and quotes remain your responsibility.
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: Site decisions, meetings, changes, dependencies, responsibilities and authorised documents.
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.
Customer space · In practice
You have delivered. The record stays useful.
Camille finds her installation, documents and your company. A new request starts with the right reference.
01HandoverShare what will remain useful.
The company adds equipment references, the manual and service report to the information intended for Camille.
02ReviewFind it without asking again.
Camille returns to her personal space to review the manual and see what was installed.
03New requestReturn with the right context.
She prepares a maintenance request for the relevant equipment. The team resumes the record with its references.
Hello Camille.
Your installation · your documents · your follow-up
Heating installation
Entered brand · model · reference
Request maintenance ↗
Company view
The shared record stays separate from internal work.
The team resumes with the relevant reference rather than rebuilding the record.
- Manual and report shared
- Team notes stay with the team
- Maintenance request linked to the installation
Fictional journey and presentation example, not a product screenshot. Content and steps are configured for your company.
Construction: connect decisions to site dependencies
On this page
One site, several responsibilities
The client, design or project team, contractor and subcontractors own different decisions. Authorized context should identify who is involved, who awaits a response and what blocks the next phase.
Client changes and site meetings
A requested change must stay linked to what was discussed and the expected decision. An available report can contribute to a mission or group; it is not automatic technical or contractual approval.
Dependencies and site preparation
An intervention may depend on another trade, access, a part or a document. The calendar organizes the visit; missions explain what must be ready and who is responsible.
Documents, photos and shared experience
A document or photo mentioned in an exchange must stay associated with its purpose and authorized file. The official document system retains reference versions.
Approved procedures can be shared in a group. Experience from another site must not expose its confidential context.
Languages and operational review
Translation can help explain a request, subject to professional review. A manager retrieves blockers and actions within their scope without inferring official progress percentages from messages alone.
Professional scope and responsibilities
AlefOS does not produce plans, quantities, budgets, delay calculations or safety decisions. It does not approve work, changes, compliance or subcontractors. BIM, ERP, scheduling, purchasing, inventory, payroll and document control keep their role; technical decisions remain with qualified professionals.
Hand over a record that remains useful
Present the work and budget with SalesOS, then organise the agreed document signing with SignOS. Share installation references, equipment brands, manuals and reports in the customer space. Your customer finds what was installed and can contact you about the right equipment.
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 ↗