Skip to main content

Check your phone number's health score before carriers flag it as spam

See which of your team's calling lines show risky patterns, such as too many calls, a low answer rate, very short calls or wrong numbers, and when to change how you call or rotate the line.

Carriers can flag a phone number as spam when its calling patterns look unhealthy, and a flagged number gets fewer answers. The health score shows how each of your team's numbers is doing, so you can spot a risky line and adjust how you call, or rotate the line, before its performance drops.


Limitations

  • A number gets a health score only once it has 50 calls over its last 30 days with calls. Until then, it shows a dash (–) instead of a score.


Prerequisites


Core lesson

Phase 1: Check the score of every number

  1. Go to Settings → Call settings.

    The Phone settings list shows a health score out of 100 for each of your team's numbers.

  2. Spot the numbers that need attention.

    A low score means the number shows risky calling patterns. Start with the numbers that have the lowest scores. A dash (–) means the number doesn't have enough call history for a score yet.

Phase 2: Open a number's health details

  1. Click the score of the number you want to review.

    ✅ Verify: the page shows the number's score out of 100, with the Health score over time chart next to it.

  2. Choose the period to review.

    Use Date and Filters at the top of the page. Every chart on the page follows the period you select.

Phase 3: Read the score card

The score card sums up the number's health:

  • The score out of 100, with a rating (for example Excellent) and a short recommendation (for example Nothing to report, keep the current pace and scripts.).

  • Score 7 days ago: the score one week earlier, so you can see whether the number is getting better or worse.

  • Calls per day (avg): the average number of calls placed per day from this number, against the daily limit (for example 16/100).

  • Answer rate: the share of calls that were answered, against the target (for example 75.0% (target 8%)).

Phase 4: Find the pattern that lowers the score

Health score over time shows how the score moved during the period. To find out why it dropped, check the chart that matches each risky pattern:

  • Too many calls: Call volume shows the calls placed per day, their running average, and the 100/day limit line.

  • Low answer rate: Answer rate shows the daily answer rate, its running average, and the 8% target line.

  • Very short calls: Short calls (<6s) shows the share of calls that lasted under 6 seconds.

  • Repeated calls to invalid numbers: SIP 404 · wrong number shows the share of calls placed to numbers that don't exist.

Phase 5: Act on a risky number

  1. Adjust how you call from that number, based on the pattern you found in Phase 4.

  2. Rotate the line if needed. If the score stays low, move your calls to another number. To change which teammates use a number, see Manage your phone number in lemlist.


Practical example: find out why a number's score dropped

  1. Go to Settings → Call settings and find the number with the lowest score.

  2. Click its score to open the health details.

  3. In Health score over time, find the day the score started to drop.

  4. Check Call volume, Answer rate, Short calls (<6s) and SIP 404 · wrong number around that day to see which pattern changed.

  5. Adjust how you call from that number. If the score doesn't recover, rotate the line.


Troubleshooting and pitfalls

Issue: A number shows a dash (–) instead of a health score, or its details show Not enough call history.

  • Root cause: The number doesn't have enough call history. A health score needs 50 calls over the number's last 30 days with calls.

  • Fix:

    • Click the dash to open the number's details. The message shows how many calls the number has and how many more it needs, for example This number has 0 — 50 more to go.

    • Keep calling from the number. The score appears once the number reaches 50 calls over its last 30 days with calls.


If your case is different

Did this answer your question?