Elevator Service Request Form: What to Ask Before Service Follow-Up

Overview

An elevator service request form should help the office understand who is contacting the company, where the elevator is located and what kind of follow-up is needed.

It should not try to inspect an elevator, diagnose a fault or replace emergency procedures.

The best first form is short enough for a property manager to complete quickly and structured enough to keep the request from arriving as a vague message such as "elevator broken, call me."

Start with separate request types

Elevator companies often handle several distinct workflows.

A useful first question is:

What do you need help with?

Possible options, only when the company actually offers them, include:

This single field can route the enquiry before the office reads a paragraph of free text.

• Repair / service
• Maintenance proposal
• Modernization
• New installation
• Residential elevator consultation
• Accessibility lift enquiry
• Inspection follow-up
• General question

Keep emergencies out of the normal form

A normal website form is not an emergency dispatch channel unless the business has a verified system and approved procedure making it one.

If someone is trapped, injured or facing an immediate life-safety situation, the page should prominently direct them to the company's approved emergency instructions and emergency services where appropriate.

Do not promise that a website submission will be monitored instantly.

For urgent service that is not a life-safety emergency, the business may choose to show a phone number or other approved urgent-service channel.

Field 1: requester name

Ask:

Full name

This identifies the person responsible for the request.

Avoid asking for unnecessary personal details.

Field 2: company, property or organization

Elevator work is often connected to a building rather than an individual consumer.

Useful field:

Company / property / organization

Examples may include:

The user can type the real organization instead of choosing from an overly long dropdown.

• property management company;
• condominium association;
• building owner;
• general contractor;
• facility;
• hotel;
• hospital;
• school;
• private homeowner.

Field 3: requester role

Role helps the service team understand context.

Possible options:

Do not use this field to assume legal authority.

It is only a routing clue.

• Property manager
• Building owner
• Facility manager
• Building staff
• General contractor
• Condominium / HOA representative
• Homeowner
• Consultant
• Other

Field 4: phone and email

Collect the contact methods the company actually uses.

Fields can include:

For an urgent repair path, phone may be the more important field.

For planned modernization or maintenance proposals, email may be important for written follow-up.

Do not promise a response time unless the business has approved it.

• Phone
• Email

Field 5: service address

Ask where the elevator is located.

A useful structure is:

This helps the company check territory and identify the site.

If a precise address is not needed for an early sales enquiry, city and postal code may be enough.

• Street address
• City
• State / province / region
• ZIP / postal code

Field 6: property or building name

A dedicated field can be useful for organizations that manage multiple properties.

Ask:

Property / building name

This can reduce confusion when the billing company and service location have different names.

Field 7: request type

If request type was not chosen before the form, collect it here.

Examples:

Do not include a service the company does not actually provide.

• Elevator repair
• Maintenance proposal
• Modernization
• New installation
• Home elevator
• Accessibility lift
• Other

Field 8: number of elevators or lifts

Ask:

How many units are involved?

Keep it simple.

For a repair request, the answer may be one.

For a maintenance proposal, the number can help the office understand the size of the property.

Do not force the visitor to inventory every unit in the first form.

Field 9: elevator or lift type, if known

A visitor may know the type, or they may not.

Possible choices:

Always include Not sure.

The form should not make nontechnical users guess.

• Passenger elevator
• Freight elevator
• Hydraulic elevator
• Traction elevator
• Home elevator
• Platform / accessibility lift
• Other
• Not sure

Field 10: manufacturer or brand, if known

Ask:

Manufacturer / brand, if known

Make it optional.

This can help the service team prepare for follow-up without blocking users who cannot identify the equipment.

Field 11: model or identifying information, if known

Optional field:

Model / unit information, if known

Do not require technical numbers from a building manager standing in a lobby.

If the company has an approved process for collecting equipment identifiers later, use it.

Field 12: observed issue

This is one of the most useful fields.

Ask:

What are you observing?

The visitor might report:

The form should record symptoms, not diagnose causes.

Avoid labels that tell the visitor what component has failed unless they already know.

• elevator not running;
• doors not closing;
• unusual noise;
• leveling issue;
• intermittent operation;
• call button issue;
• display issue;
• maintenance concern;
• modernization question.

Field 13: unit status

A simple status field can help triage.

Options might include:

Do not use a website answer to declare equipment safe or unsafe.

That determination belongs to the appropriate professionals.

• Operating normally but service requested
• Operating with an issue
• Out of service
• Not sure

Field 14: people trapped or immediate danger

Do not turn this into a normal form field that someone has to complete before getting help.

Instead, place a visible notice near the repair path:

If someone is trapped or there is an immediate emergency, do not rely on this form. Follow the property's approved emergency procedure and contact emergency services where appropriate.

The exact wording should be reviewed by the elevator company.

Field 15: maintenance relationship

For a maintenance-proposal form, useful optional context may include:

Do not ask for confidential contract documents in a casual public form.

The company can request documents later through its approved process.

• Current maintenance provider
• Contract renewal timing
• Number of properties
• Reason for reviewing service

Field 16: modernization context

For modernization enquiries, useful fields can include:

Do not ask the website visitor to determine code deficiencies or technical modernization scope.

• Building type
• Number of elevators
• Approximate elevator age, if known
• Main goal
• Planned timeline
• Budgeting / planning stage
• Whether an assessment or proposal is requested

Field 17: preferred timing

For ordinary service, ask:

Preferred date or timing

Possible options:

Make the status clear:

Preferred timing is a request, not a confirmed appointment or technician dispatch.

This wording prevents the form from creating false expectations.

• As soon as possible
• This week
• Within two weeks
• Planned / flexible
• Specific preferred date

Field 18: site access contact

For commercial properties, the person submitting the form may not be the person who can open the machine room or meet a technician.

Optional field:

On-site contact

This can include a name and phone number if the business needs it.

Do not collect more personal information than necessary.

Field 19: access notes

A public request can collect high-level access constraints that help the office prepare for follow-up.

Useful examples can include:

Do not ask for gate codes, lockbox combinations, alarm codes, passwords, key locations or other access credentials in a public form.

If sensitive access details are required for an accepted job, collect them later through the elevator company's approved secure process.

• parking or loading restrictions;
• security-desk check-in required;
• escort required;
• construction-site access procedure;
• tenant or building hours;
• whether after-hours access must be arranged.

Field 20: additional notes

Use one open text field:

Anything else we should know?

This catches details that structured fields miss.

Keep the form structured first and open-ended second.

What about inspection reports, photos and documents?

Some elevator companies ask clients to share inspection reports, equipment labels or other documents.

Do not assume the website platform supports secure technical-document exchange unless that workflow has been verified.

A safer public form can ask:

Do you have an inspection report, photo or document available?

Options:

The office can then provide the company's approved handoff instructions.

This avoids turning a marketing form into an unverified document-management system.

• Yes
• No
• Not sure

What confirmation should the user receive?

A good confirmation is simple.

It can tell the requester:

Do not say "technician dispatched" unless that is actually true.

• the form was received;
• the team will review the information;
• the company will confirm service availability and next steps;
• a requested date is not automatically confirmed;
• urgent or emergency situations should follow the company's approved urgent-service procedure.

Should the form ask for billing information?

Usually not at the first public step.

A service request is for qualification and routing.

Billing contacts, purchase orders, tax information and contract details can be collected later through the company's normal process.

Reducing early friction usually improves completion.

Should the form ask for elevator serial numbers?

Only if the company genuinely uses them early and customers can reasonably provide them.

For many public requests, manufacturer, model and property are enough to start.

Serial numbers can be collected later.

Should a maintenance request use the same form as an emergency repair?

Usually no.

A maintenance proposal may need property count, unit count and contract timing.

An urgent repair request needs location, contact, issue and a fast path.

Separate forms reduce unnecessary fields.

Should modernization use the repair form?

Modernization is usually a planned project and deserves its own path.

Its form can focus on:

Repair questions such as "is the unit currently operating?" are less central.

• property;
• unit count;
• approximate age;
• goals;
• planning stage;
• desired timeline;
• contact.

How OneStudio can fit the public intake layer

OneStudio publicly supports website content, contact forms/enquiries and client records, with additional service-business tools depending on the plan and configuration. See OneStudio features and pricing.

For an elevator company, that can make the website and customer-contact layer easier to keep together.

Do not describe OneStudio as:

Those functions should remain in the specialist systems the company already trusts.

• elevator dispatch software;
• inspection software;
• maintenance-contract software;
• work-order software;
• elevator asset management;
• regulatory compliance software;
• technician routing;
• parts inventory;
• emergency monitoring.

A practical first version of the form

A concise repair/service form can start with:

A maintenance proposal or modernization form can add the few extra fields relevant to that journey.

Start small. Add fields only when they improve routing or reduce back-and-forth.

1. Full name
2. Company / property
3. Phone
4. Email
5. Service address
6. Request type
7. Elevator type, if known
8. Manufacturer / model, if known
9. Observed issue
10. Unit status
11. Preferred timing
12. On-site contact, if different
13. Additional notes

Turn vague elevator enquiries into useful service conversations

A strong elevator request form does not try to solve the technical problem online.

It gathers enough context for the right team to follow up safely and efficiently.

Use OneStudio to improve the public website, enquiry and client-record experience while keeping technical service, inspections, dispatch and compliance in the systems built for those jobs.

Explore OneStudio features and pricing.