Why did my Bland batch place fewer calls than my list?

The Bland help pages give 4 common reasons. The first to rule out: One bad row in a calling list can stop the whole list from being accepted, so no calls from it are placed.

Reach · Are people seeing me?

Is it broken, or just quiet?

A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Bland help pages give, and how to check each one yourself.

What causes it?

  1. One bad row in a calling list can stop the whole list from being accepted, so no calls from it are placed.

    In the Bland help: A CSV with one bad row is rejected whole. Batch Calls, read 2026-11-12.

  2. Repeated numbers and numbers on your do-not-call list are skipped when the batch dials, so a batch can place fewer calls than its list has rows.

    In the Bland help: Duplicates and numbers on your do-not-call list are different: those are dropped at dial time and the rest of the batch runs. Batch Calls, read 2026-11-12.

  3. A batch that was stopped ends before every call is placed, as Bland's docs explain.

    In the Bland help: The batch ended early, usually because you stopped it. Batch Calls, read 2026-11-12.

  4. Bland spaces out calls to the same number, so repeated calls to one number in quick succession can be refused.

    In the Bland help: Calls can only be sent every 10 seconds to the same number. Send Call, read 2026-11-12.

How do I check it myself?

  1. Read the message from a rejected upload, since it names some of the bad rows and says how many more there are.

    In the Bland help: The upload checks every number before the batch exists, names up to three of the bad rows, and counts the rest. Batch Calls, read 2026-11-12.

  2. Check whether the batch is still waiting on calls set for a later start time, since those have not been placed yet.

    In the Bland help: The batch is waiting for calls with specific start times to be executed. Batch Calls, read 2026-11-12.

How does Bland work with Feder?

  • Connect Bland to Feder and it joins your Reach apps.
  • When you connect Bland, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See whether you can trust the numbers in Bland, one of your Reach apps. Feder only reads. It never changes anything in Bland.

Where do these answers come from?

Every cause and check on this page comes from the Bland help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.