# Water & fire restoration

> Track restoration campaigns and review how urgent calls reach the people responsible for intake. Explore the workflow with Lead Source.

Canonical page: https://getleadsource.io/use-cases/restoration/

For Water & fire restoration

## See the path from an urgent inquiry to your team.

Track restoration campaigns and review how urgent calls reach the people responsible for intake.

[Explore the walkthrough](https://getleadsource.io/demo/)[See the workflow](https://getleadsource.io/use-cases/restoration/#workflow)

Water & fire restoration Illustrative journey

- 01 Source Water-damage search campaign

- 02 Conversation Caller describes an urgent problem

- 03 Next step Intake team reviews the request

One inquiry. Its context stays connected.

[Your workflow](https://getleadsource.io/use-cases/restoration/#workflow)[What to reviewThe tools](https://getleadsource.io/use-cases/restoration/#review)[Common questions](https://getleadsource.io/use-cases/restoration/#questions)

Built around your day

### Start with the way you work.

An urgent restoration call needs a clear receiving path. Keep the source, call route, and recorded request connected so you can investigate missed attempts and understand what your advertising brought to the intake team.

01

#### Make urgent call paths explicit

Check the receiving number and fallback behavior for campaigns advertising urgent help. Test the out-of-hours path as well as the normal one.

02

#### Review the service request

Use available recordings and transcripts to distinguish water, fire, or other inquiries. Keep the actual request visible to the person following up.

03

#### Separate routing problems from traffic quality

An unanswered call may indicate coverage or scheduling issues. Review that before deciding the campaign itself brought poor-quality leads.

The question worth asking

### Did the urgent inquiry reach the team expected to answer?

Follow the routing timeline and inspect the connection result. Then review the request and next step rather than assuming a routed call became an accepted job.

Bring these details into the review

01 Time of incoming inquiry

02 Answered and fallback attempts

03 Recorded intake outcomes

The tools behind the workflow

### Bring the right details together.

[Business hours & fallback routingUse schedules and fallback handling to match incoming calls with the team's availability.Explore feature](https://getleadsource.io/features/business-hours/)[Alerts & monitoringMonitor unanswered calls, low balances, and failed deliveries so your team can investigate.Explore feature](https://getleadsource.io/features/alerts-monitoring/)[Call recordingReview recorded calls with their campaign, routing details, and saved outcomes.Explore feature](https://getleadsource.io/features/call-recording/)

Before you start

### A few useful details.

Fit the setup to your actual campaigns, receiving team, and follow-up process.

Does this provide emergency response or dispatch? +

No. Lead Source tracks and routes phone inquiries. Your business remains responsible for staffing, response, and any field dispatch.

How should water & fire restoration judge campaign performance? +

Use the source, connection result, and the outcome your team records together. Review real conversations before treating every incoming call as the same kind of opportunity.

[Explore all use cases](https://getleadsource.io/use-cases/)[Browse all features](https://getleadsource.io/features/)[Compare platforms](https://getleadsource.io/compare/)

Meet your next growth tool

### Let’s connect the dots on your calls.

Get an early look at Lead Source, built for the way your business handles calls.

[Explore the walkthrough](https://getleadsource.io/demo/)[Explore the platform](https://getleadsource.io/platform/)