# Missed-call follow-up

> Review unanswered attempts, investigate the route, and organize an appropriate callback. Explore the workflow with Lead Source.

Canonical page: https://getleadsource.io/use-cases/missed-call-follow-up/

For Missed-call follow-up

## Find the unanswered call. Make the next step visible.

Review unanswered attempts, investigate the route, and organize an appropriate callback.

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

Missed-call follow-up Illustrative journey

- 01 Source Incoming campaign call

- 02 Conversation Receiving team did not answer

- 03 Next step Callback reviewed and arranged

One inquiry. Its context stays connected.

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

Built around your day

### Start with the way you work.

An unanswered call is a signal to investigate, not a reason to guess. Check when it arrived and how it was routed, then arrange a follow-up where the person's contact permissions and available details allow it.

01

#### Inspect the call path

Review the attempted destinations and the working-hours setup. Find out whether the issue was availability, configuration, or something else.

02

#### Prepare a useful callback

Check the lead history and contact permissions before calling. Use the available campaign context to understand why the person may have reached out.

03

#### Close the operational gap

Update the recorded outcome after follow-up. If the pattern repeats, review receiving coverage and fallback behavior.

The question worth asking

### Was this a one-off missed attempt or a recurring coverage problem?

Use alerts and call timelines to identify patterns. Keep the follow-up with the lead while the team responsible for routing addresses any recurring issue.

Bring these details into the review

01 Unanswered attempt times

02 Fallback behavior

03 Callback outcomes

The tools behind the workflow

### Bring the right details together.

[Alerts & monitoringMonitor unanswered calls, low balances, and failed deliveries so your team can investigate.Explore feature](https://getleadsource.io/features/alerts-monitoring/)[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/)[Callbacks & appointmentsOrganize callbacks, follow-up tasks, and appointments around the inquiry that started them.Explore feature](https://getleadsource.io/features/callbacks-appointments/)

Before you start

### A few useful details.

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

Does an alert call the person back automatically? +

No. The workflow helps your team identify the issue and organize follow-up. Review the appropriate action and contact permissions.

Can we see why a call was missed? +

The call timeline can show attempted destinations and connection results. Use that information with receiving-team availability when investigating.

[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/)