Skip to content
be-human.ai
← Back to the journal

AI by industry

Elevator Maintenance Companies: Superintelligence Prep for Callbacks

Which callback histories, inspection due dates and building contacts an elevator firm should structure first, and why technicians approve safety findings.

Be Human typographic cover with the title: Elevator Maintenance Companies: Superintelligence Prep for Callbacks
Conceptual illustration created with AI · Be Human

Elevator maintenance companies preparing for superintelligent agents should structure three records first: callback histories linked to each individual unit, inspection due dates tied to each jurisdiction and certificate, and building contacts with clear access and authorization rules. With those records in place, an agent can answer dispatch and follow-up questions from facts instead of from whatever a senior technician remembers. Safety findings stay with qualified technicians, and the system should be designed around that boundary from the first day.

Key takeaways

  • Structure callback history per unit, not per customer account, because repeat faults hide inside individual equipment records.
  • Track inspection due dates by unit and by authority, and let the agent flag them without ever declaring a unit compliant.
  • Store building contacts with access rules, after-hours paths and the person who can authorize repair work.
  • Give agents read access to service records and draft-only access to findings. A named technician approves every safety conclusion.
  • Measure the work with an observable criterion, such as whether every callback in scope has a logged cause, a named technician and a closed follow-up.

What an agent needs before it can help dispatch

Elevator work is a relationship business with a heavy paper trail. A dispatcher knows that a freight elevator in one warehouse trips whenever the door operator runs hot, and the lead technician remembers the last adjustment that seemed to help. None of that knowledge reaches an agent in a usable form. Preparing for agents means turning what people remember into records with stable identifiers, dates and named owners, so that a question about one unit can be answered from the unit's own history.

This is the same discipline that observability practice applies to software systems. A signal is only useful when it carries context, a timestamp and a reference to what it relates to. The [OpenTelemetry observability primer](https://opentelemetry.io/docs/concepts/observability-primer/) describes telemetry in those terms, and the same logic applies to a service log that has to explain why a unit came back.

Which callback histories to structure first

A callback is a return visit for a fault that was supposed to be resolved. Callbacks are among the most valuable records a firm holds because they show where repairs do not hold. They are also the records most often stored in a way that makes them hard to read: the first visit lives on one ticket, the return visit on another, and the link between them exists only in a technician's head. Fix that link before anything else.

For each unit, keep these fields in separate, searchable form:

  • Unit identifier, building, and equipment type as recorded on site
  • The symptom in the caller's words, kept apart from the technician's finding
  • Any fault or error code shown on the controller at the time of the visit
  • Visit date, technician, and whether a part was replaced
  • A reference to the earlier visit when the call is a callback
  • A closure note stating what was verified and what was not verified

The closure note matters most. A note that says the door was adjusted tells the next technician almost nothing. A note that says the door operator was adjusted, the closing speed was measured against the procedure, and the fault was not reproduced during a test cycle gives an agent something it can compare against the next callback. For a deeper look at how dispatch and callback records support agent work, see Superintelligent agents for plumbing companies: dispatch and callbacks.

Inspection due dates and the rules behind them

Inspection schedules depend on the jurisdiction, the equipment type and the certificate a building holds. Those rules change, and they differ between authorities, so the firm should confirm every schedule with the relevant local authority and record the source. An agent should never reconstruct a due date from memory or from a general rule of thumb. It should read the due date from the register and report where that date came from.

Each unit needs an inspection record that includes the authority, the certificate reference, the last inspection date, the next due date, and the person responsible for booking the visit. With that register, the agent can produce a rolling list of what falls due in the coming weeks. The decision rules for that list should be written down before the agent runs:

  • Due within the booking window: the agent drafts a scheduling request to the building contact and leaves it for the office to send.
  • Due date missing or conflicting with another record: the agent flags the unit to the office manager and does not guess a date.
  • An inspection failed or a condition was noted: the agent routes the unit to a technician and holds any customer-facing summary.
  • The governing rule is unclear: the agent asks a human to decide and records the question.

The same flag-and-route pattern appears in quality work, where open nonconformances need an owner and a due date. The approach is described in AI for quality management: nonconformances and audit prep.

Building contacts, access and who can authorize work

Callbacks often stall for a reason that has nothing to do with the equipment. Nobody on the building side knows who can open the machine room, who can approve a shutdown, or who pays for a repair above a certain value. Technicians learn these answers the hard way, one call at a time. An agent can only help if the answers are stored.

For each building, keep the property manager, the on-site contact, the key holder, the after-hours path, and the person authorized to approve repair work. Keep the person who receives the invoice in a separate field, because that person is often not the one who can let a technician in. Access instructions are sensitive, so they should be visible only to the tasks that need them. The [OWASP Authorization Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html) describes the general principle: each actor should receive only the access its function requires, checked at the point of use.

Why technicians must sign off on safety findings

A safety finding is a professional judgment that a unit is safe, unsafe, or safe with stated conditions. That judgment belongs to a qualified technician who examined the equipment and carries the responsibility for it. An agent can summarize the technician's notes, format the report, and show that a sign-off is still pending. It should never state that a car is safe to run, and it should never send a finding to a building owner without a named technician's approval recorded in the system.

This boundary is a governance choice, not a limitation to be engineered away later. The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) treats human oversight and clear accountability as part of managing AI risk across its lifecycle. In practice, every approval should show who signed, when they signed, and which evidence they reviewed. If an agent drafted part of the report, the record should say so. That way an auditor, an insurer or a building owner can see exactly where the human judgment entered.

A practical plan for the first month

The work below is a sequence a firm can run without new software. Each step produces a record that the agent can later use.

  • Choose a small set of units with the most return visits, so the first records address real repeat problems.
  • Export those callback records and link each return visit to the earlier visit it follows, using the unit identifier as the key.
  • Build the inspection register for the same units, with authority, certificate reference, last and next due dates, and a named owner.
  • Add building contacts for the same buildings, including the access path, the after-hours route and the person who can authorize work.
  • Write down what the agent may read, what it may draft, and what it may never do, such as declaring a unit safe or sending a finding without approval.
  • Review a sample of agent drafts each week against the source records, and log every correction.
  • Define the success criterion before launch: every callback in scope has a logged cause, a named technician and a closed follow-up.

Be Human designs this kind of setup as a first engagement that defines one useful role, the memory and tools that role needs, the approval boundaries and an observable success criterion. Managed operations can then cover monitoring, recurring evaluations, permission reviews, integration maintenance and controlled changes when building contacts or inspection rules change. The work runs remotely, in English or Portuguese, and the firm keeps control of the records and the approvals throughout.

An illustrative scenario: the callback that came back twice

Illustrative scenario: a mid-rise office building has a hydraulic passenger elevator that a technician adjusted after a door complaint. Two weeks later the same error code appears, and the dispatcher books it as a new call because the first ticket has no link to the second. The technician who answers the second call does not read the first closure note, which says only that the door was adjusted.

With linked records and a defined role, the agent flags the second call as a repeat within the same unit, pulls both closure notes, lists the error code from each visit, and drafts a summary for the lead technician. The draft states what the records show and what they do not show. It does not recommend that the unit return to service, and it does not contact the building owner. The technician reviews the draft, decides the next step, and signs the finding. The office then sends the building contact only what the technician approved.

The firm's managed review then checks whether repeat calls are being linked correctly and whether drafts stay inside the written boundary. If you want to find the first task in your own operation that is worth handing to an agent, take the free Be Human AI diagnostic.

Frequently asked questions

Can an AI agent decide whether an elevator is safe to run? No. A safety finding is a professional judgment made by a qualified technician who examined the equipment. The agent can organize notes, draft a summary and show that approval is pending, but the decision and the signature stay with a named person.

Which record should we fix first if our data is messy? Start with the unit identifier and the link between each callback and the original visit it follows. Without those two elements, repeat faults look like new problems and no agent can reliably find patterns. Inspection due dates come next because they drive scheduled work.

Do we need to give the agent access to our full customer database? No. Give each task only the records it needs, such as one unit's history or the list of upcoming due dates. Permission reviews should run on a regular schedule so that access does not grow quietly over time.

How do we know the agent is actually helping? Choose a criterion you can observe, such as whether every callback in scope has a recorded cause, a named technician and a closed follow-up. Review a sample of agent drafts against the source records on a recurring basis, and log every correction so the next review shows whether the errors are falling.

Your next step

See where an AI agent fits in your company first.

Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.

Less busywork. More room for you.

Bring us the work you wish you had time for.

Book a call to try a personalized AI agent free for 7 days ↗Or take the free AI diagnostic →