← OneStudio Guides

Websites

Fire Extinguisher Service Request Form: Fields That Matter

Build an extinguisher service form around site, service type, unit count, deadline, urgency and multi-location needs without turning the website into inspection software.

Overview

A good fire extinguisher request form should help the office answer:

Current extinguisher providers already use this pattern.

The form should qualify the request.

It should not perform the inspection.

  • Where is the site?
  • What service is needed?
  • Roughly how many units are involved?
  • Is there a deadline?
  • Is the request routine or urgent?
  • Is this one property or a portfolio?

Field 1: Organization

Collect:

Examples:

  • business or organization name;
  • account type when useful.
  • property management;
  • retail;
  • school;
  • warehouse;
  • construction;
  • restaurant;
  • industrial;
  • municipality;
  • other.

Field 2: Requester

Collect:

Useful roles include:

  • name;
  • role;
  • phone;
  • email.
  • facility manager;
  • property manager;
  • business owner;
  • safety manager;
  • construction manager;
  • purchasing;
  • school/facility administrator.

Field 3: Service address

Make this required for field work.

Useful inputs:

This lets the contractor confirm territory and route the request.

  • property/site name;
  • street;
  • city;
  • state/region;
  • ZIP/postcode.

Field 4: What do you need?

Useful choices can include, where offered:

Always include Not sure / review my site.

  • routine extinguisher inspection/service;
  • recharge;
  • hydrostatic testing;
  • replacement;
  • new extinguisher supply;
  • correction work;
  • construction-site service;
  • emergency lighting;
  • not sure.

Field 5: Approximate extinguisher count

Useful ranges:

Do not force exact inventory before the technician visits.

  • 1–10;
  • 11–25;
  • 26–50;
  • 51–100;
  • 100+;
  • multiple locations;
  • not sure.

Field 6: Number of buildings / locations

For portfolio accounts:

This helps identify commercial account complexity.

  • one building;
  • multiple buildings on one site;
  • multiple addresses;
  • statewide/regional portfolio.

Field 7: Existing service date or deadline

Ask what the customer knows:

Do not use this field to declare the site out of compliance.

  • inspection/tag due date;
  • insurer deadline;
  • property-management deadline;
  • construction milestone;
  • correction deadline;
  • not sure.

Field 8: Correction notice or deficiency list

If the customer has an external notice or list, allow:

The service team should review the actual document.

  • notice available;
  • report available;
  • photo available;
  • not applicable.

Field 9: Urgency

Options:

For true urgent service, show the verified phone path.

  • routine;
  • due soon;
  • correction deadline;
  • equipment out of service;
  • active business opening / construction deadline;
  • urgent;
  • not sure.

Field 10: Preferred service window

Useful options:

Do not promise the slot until the office or field system accepts it.

  • weekday;
  • early morning;
  • afternoon;
  • after-hours if offered;
  • flexible.

Field 11: Site access

Ask at a high level:

Do not collect sensitive access codes in a public form.

  • normal business access;
  • gated/security-controlled;
  • construction site;
  • school-hours restriction;
  • occupied public site;
  • multiple floors/buildings.

Field 12: Existing service provider / takeover

Optional:

This can help route account onboarding.

  • current provider;
  • new account;
  • multi-site consolidation;
  • not sure.

Field 13: Photos

Optional photos can help with:

Do not use photos to perform a remote compliance determination.

  • damaged unit;
  • tag;
  • cabinet;
  • access condition.

Field 14: Notes

Prompt:

Tell us what you need, how many units or locations are involved, any deadline, and anything the service team should know before scheduling.

What the form should not decide

Do not ask the public form to determine:

Those belong to qualified service review.

  • compliance status;
  • required extinguisher type;
  • placement;
  • testing interval;
  • recharge eligibility;
  • hydrostatic due date;
  • final unit inventory;
  • inspection pass/fail.

Booking vs request-first

A small recurring inspection may be bookable when:

Use request-first for:

  • geography is known;
  • unit count is limited;
  • duration is predictable;
  • real technician capacity is represented.
  • multi-location accounts;
  • unknown unit counts;
  • correction work;
  • large facilities;
  • urgent work;
  • mixed services.

Confirmation message

Use:

Thanks. We received your fire extinguisher service request. Our team will review the site, service type, approximate unit count, deadline and urgency and contact you about the next step.

Avoid:

Your annual inspection is confirmed.

until it is actually scheduled.

Collect enough to schedule intelligently without pretending the inspection is complete

A useful form turns a vague request into a service-ready conversation.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask

Should extinguisher count be required?

Ask for an approximate count, but include not sure.

Should customers upload current tags?

Optional tag photos can help the office understand the request, but technical determination remains with the service team.

Can customers book an inspection online?

Yes when the contractor can expose trustworthy availability. Larger or multi-site jobs usually benefit from review first.

Does OneStudio generate inspection certificates?

No. Keep official inspection records and certificates in specialist fire-service software.