# Alerts & monitoring > Monitor unanswered calls, low balances, and failed deliveries so your team can investigate. Explore the workflow with Lead Source. Canonical page: https://getleadsource.io/features/alerts-monitoring/ [Alerts & monitoring Spot the call problems worth a closer look. Monitor unanswered calls, low balances, and failed deliveries so your team can investigate. Explore the walkthrough](https://getleadsource.io/features/#reporting)[See pricing](https://getleadsource.io/pricing/) Reporting & monitoring · Built for US call workflows Lead Source Illustrative example 01 Choose what to monitor 02 Open the underlying record 03 Resolve and verify Sample activity Signal Mon Tue Wed Thu Fri Unanswered calls ### Choose what to monitor Focus on the call, balance, or delivery conditions relevant to your work. Sample activity Review Mon Tue Wed Thu Fri Receiving number and hours ### Open the underlying record Review the call timeline or delivery details associated with the alert. Sample activity Action Mon Tue Wed Thu Fri Test the updated route ### Resolve and verify Make the appropriate correction and check the next result. Explore the steps above. Sample details show the workflow, not a live account. [What you can do](https://getleadsource.io/features/alerts-monitoring/#capabilities)[The workflow](https://getleadsource.io/features/alerts-monitoring/#workflow)[Common questions](https://getleadsource.io/features/alerts-monitoring/#questions)[Related features](https://getleadsource.io/features/alerts-monitoring/#related) Reporting & monitoring ### What changes in your day. A missed call and a failed event delivery are different problems, but both can interrupt a useful workflow. Bring operational signals into view and connect each alert with the records needed to understand it. 01 #### Watch for unanswered calls Identify call-handling issues and inspect the route behind them. Use the signal to check receiving numbers, schedules, and fallback behavior. 02 #### Keep balance problems visible Review low-balance conditions before they become a recurring routing problem. For pay-per-call workflows, funding and credit rules can affect buyer eligibility. 03 #### Investigate failed deliveries See when information did not reach a connected system. Review the delivery and use the available retry workflow after addressing the cause. From setup to review ### Put it to work. - 01 #### Choose what to monitor Focus on the call, balance, or delivery conditions relevant to your work. - 02 #### Open the underlying record Review the call timeline or delivery details associated with the alert. - 03 #### Resolve and verify Make the appropriate correction and check the next result. A closer look ### Useful answers before you start. Explore the workflow above, then bring your own requirements to an early-access conversation. Do alerts guarantee an issue will be fixed automatically? + No. An alert makes a condition visible. Your team should investigate the cause and verify the result of any correction. Will every alert arrive as an email digest? + Do not assume that. The monitoring workflow and an email summary service are different. Review available alert destinations during setup. Connect the next step ### Works with the rest of your call workflow. [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/)[Buyer balances & credit limitsReview buyer funds and credit limits as part of the commercial call workflow.Explore feature](https://getleadsource.io/features/buyer-balances/)[Webhooks & event deliverySend call and lead events to your own systems, inspect deliveries, and retry failed attempts.Explore feature](https://getleadsource.io/features/webhooks/) [Browse all features](https://getleadsource.io/features/)[Find your use case](https://getleadsource.io/use-cases/)[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/)