Plumbing software + business growth · Early access in Canada

FLOR PLUMBING · CANADA

Emergency Plumbing Dispatch Workflow

Keep response, availability, approval and arrival promises separate when a request is urgent.

AT A GLANCE

An emergency plumbing dispatch process captures the reported problem and location, checks genuine provider availability, gets a response, and records the customer’s decision. Urgency does not turn an unconfirmed request into a booked visit. Response windows and arrival estimates must remain separate.

WORKFLOW EXPLAINED

A request becomes a job after approval

Office / request

Issue + locationCheck the service area
No eligible provider?
Keep it unconfirmed.

Provider

Review offer3-minute response window
Send estimateScope + amount + proposed arrival

Customer

Review estimateAccept or skip before expiry
Accepted jobA named provider owns the work
Flor Plumbing’s demonstrated request workflow. The response window is separate from arrival time; the public demo uses fictional records.

Start with a clear service-call record

Capture the customer’s description, location and a reliable way to respond. Ask only what is needed to route the request appropriately. The office should follow its established emergency escalation procedure when the report indicates immediate danger; a software workflow is not a diagnosis or a substitute for emergency services.

Use the service-call intake worksheet to agree on the required information. A Vancouver, BC sample should have a postal code, a service-area check and a visible unconfirmed status.

Keep three clocks distinct

Different times answer different questions
ClockQuestion answeredFlor demo example
Provider responseHow long does the provider have to respond?Three minutes
Estimate validityHow long can the customer accept these terms?Ten minutes
Arrival indicationWhen does the provider expect to arrive?Proposed separately by the provider

Neither a response deadline nor an estimate expiry is an arrival guarantee. Use clear labels in the office and customer view so a fast software response is not confused with a technician at the door.

Design the unavailable-provider path first

Test what happens when the selected provider declines, does not respond or no eligible provider remains. The customer should see that the work is still unconfirmed. A reassuring animation or a request reference does not establish coverage.

Flor’s demonstrated flow can move an unanswered or declined offer to the next eligible provider before acceptance. Accepted work stays with the chosen provider; later reassignment needs a separate resolution. Include that boundary in the office’s handoff notes.

Read the estimate before confirming the work

Check the scope, amount in CAD, exclusions, tax notes and proposed timing. A published starting rate is not the same as a provider-approved estimate for the actual problem. If the scope is unclear, the customer needs a way to ask before agreeing.

Practice the expired-estimate and skipped-provider cases as well as a successful acceptance. The office should be able to identify the current terms and the actual job owner in each case.

Review the outcome after the shift

Inspect unconfirmed requests, unanswered offers and accepted work with an unresolved next action. Name an owner for each item. Count real accepted jobs separately from enquiry submissions and demo interactions so the report does not inflate dispatch performance.

The public Flor Plumbing demo uses fictional providers and prices. Real dispatch depends on verified provider onboarding and local coverage. This guide is for plumbing businesses evaluating operations; it does not advertise nationwide emergency service availability.

Common questions

Does a three-minute response window mean a three-minute arrival?

No. It limits the provider’s response time in the demonstrated workflow. Arrival is proposed separately and depends on actual availability.

What should happen if no plumber is available?

Keep the request unconfirmed and explain the situation. Do not create a fabricated booking or arrival promise.

Bring your workflow to the demo

Explore the fictional request-to-approval journey, then discuss the capabilities your business needs.