Your industry · Your work OS
Your maintenance service, one question away.
Customers find your services and submit a service request with the specified details. Your team reviews it and confirms the next step; private history access is scoped separately.
What customers can do with your application.
What customers browse: Your maintenance and support services and their published conditions.
What you receive: The service, description of the need, agreed equipment fields and contact details.
Your benefit: Prepare enquiry triage using the information received.
What maintenance contracts or services do you offer?
I would like to report a need for a service visit.
Could you call me to arrange maintenance?
Illustrative examples of the journey to configure. A submitted enquiry is not an accepted service order or a confirmed appointment.
No automatic diagnosis or guaranteed response time. Private equipment history requires specific access, and the CMMS retains its role.
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: Intervention history, outstanding parts, access, follow-up visits and responsibilities.
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.
Maintenance: preserve what remains unresolved
On this page
Resume the right history
A new request may concern an incident already reported. The technician retrieves authorized exchanges, interventions and findings before deciding whether they are relevant to the current situation.
Make the dependency visible
A repair may await a part, access or approval. The mission keeps that reason with the customer and owner, instead of reducing follow-up to “call back”.
Coordinate the second visit
The appointment connects a time slot to available preparation information. Office staff and the technician retrieve commitments made to the customer and the next update to communicate.
Learn from interventions
An authorized group can preserve reusable procedures and feedback. Recurrences help prepare a professional review; they do not by themselves establish the cause of a fault.
Professional scope and responsibilities
AlefOS does not replace the CMMS, maintenance records, parts inventory or safety procedures. Diagnosis, compliance and technical closure remain professional responsibilities.
The next technician starts with the intervention history
A customer reports a recurring fault by phone, sends a photo and agrees on an access window. The next technician needs the earlier diagnosis, the missing part, the access conditions and the promise made to the customer. The shared record brings together the material received through the configured channels.
A booking questionnaire can collect the site details before the visit. Ask: “What was tried last time, what is still missing, and which team procedure applies?” Review the available record and shared knowledge. AlefOS complements the agreed workflow; this does not imply that every asset-management, stock or field-service feature is included.
Make the next service request easier
A customer describes an issue from your plugin instead of searching old messages for a phone number. The journey collects useful details and sends the request for follow-up.
An identified customer can retrieve the documents you make available for their equipment. Your team controls the response, scheduling and confirmation of the intervention.
Keep the installation record close at hand
Give the customer access to shared equipment references, service reports and manuals. Present the next intervention with SalesOS and organise any documents to sign with SignOS. The personal space supports follow-up between visits.
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 ↗