FlowsBook a callSign inCreate free accountSign up
Workflows by industry

How SDRs prioritise a morning call list of local businesses

Put the best calls first: rank new and existing local businesses by fit score and freshness, cap the list at what one rep can dial, and have it waiting at 8 am.

Part of the guide Workflow automation

By the xMap team · · 5 min read

A morning call list is prioritised by two things at once: how well each business fits what you sell, and how fresh the reason to call is. Score every business on fit from 0 to 100, lift the ones that opened or changed recently, then cut the list to the number of calls a rep can really make before lunch. The top of the list is then a short set of strong fits with a reason to ring today, not the whole database in alphabetical order.

This piece is for sales development reps and the managers who hand them their day. It covers what a good ranking looks at, how to keep yesterday's leads from crowding out today's, a worked example, the traps that make a list feel random, and how an AI employee in xMap Flows builds the ranked list before the rep logs in.

What decides the order

Most SDR teams already know who their ideal customer is. The trouble is that a raw list of local businesses has no order that reflects it. A ranking that holds up on the phone usually blends four signals:

  • Fit. Does this kind of business, at this size and in this place, buy what you sell? A clear written description of your best customer turns into a fit score.
  • Freshness. A business that opened last month, or that was found for the first time this morning, has a reason to talk now. One that has been on the list for half a year has had its chance.
  • Reachability. A place with a phone number and a website is a call you can make. One with neither is a visit or an email, so it belongs on another list.
  • Signals of size or change. Many reviews, a chain or a single shop, a company posting jobs: each says something about budget and timing.

Fit is the anchor; the other three break ties and push a handful of urgent names up. A list ranked only on freshness fills up with tiny businesses that will never buy. A list ranked only on fit shows the same big names every day until the reps stop reading it.

Keeping today's list about today

The most common complaint from reps is that the list repeats. Yesterday's unanswered calls come back, and the genuinely new names sit at the bottom. Two habits fix this.

First, separate what is new from what is known. A flow that lets through only places it has not found before gives a short, clean list of first-time names each morning. Older names can still be worked, but from the rep's own pipeline, not from the morning list.

Second, cap the list. If a rep can make about twenty-five useful calls before noon, the list should stop at twenty-five. Anything past that is noise that pushes the rep back to a spreadsheet. The Sort and limit block orders by the fit score and keeps the first N.

A worked example

Here is a made-up example. An SDR in Melbourne sells booking software to health and beauty businesses. Overnight, the flow searches her territory for physiotherapy clinics, beauty salons and day spas, and finds 180 places. Of those, 41 were never seen before.

  1. The 41 new places are read by xMap AI against a short description of the best customer: independent, two or more treatment rooms, open six days, with a website.
  2. Each gets a fit score and a one-line reason, such as "Independent spa with three therapists listed and online booking missing from its site".
  3. Places without a phone number drop to the email list.
  4. The remaining places are sorted by score, and the top 20 go to the rep at 7:45 with the reason next to each name.

The rep starts with a spa scored 91 that opened in the spring, then a physio practice scored 88 with many reviews and no booking link. She does not touch number 20 until she has worked the first ten. The made-up figures matter less than the shape: a short list, ordered, each line with a reason.

Mistakes that make a call list feel random

  • A vague scoring brief. "Score how good a lead this is" gives soft, middling numbers. Name the size, the kind, the signals you trust and the ones that disqualify.
  • No reason next to the score. A rep will not trust a 74 without knowing why. Always ask the AI to write the reason in a sentence the rep can open the call with.
  • Mixing new and known names. The rep cannot tell which name is a first contact and which is the fifth attempt.
  • Calling businesses that already buy from you. Check the list against your customer table before it reaches the rep.
  • Treating a score as a promise. A score ranks; it does not close. Expect some top names to say no and some low ones to surprise you.

How an AI employee builds the list each morning

In xMap Flows the list is the daily work of one AI employee. A typical order of blocks:

  1. Schedule: every weekday at 6:30 in the rep's time zone.
  2. Area of interest: the cities or districts of the territory, or a shape drawn on the map.
  3. Nearby places: the kinds of business you sell to, from xMap's places database.
  4. Only new: only names this flow has not found before.
  5. Match with my table: keep only the places not already in your customer table.
  6. xMap LLM: a fit score from 0 to 100 and a reason, from your written brief.
  7. Sort and limit: highest score first, keep the first 20 or 25.
  8. Apollo (optional, with your own Apollo account): the decision maker at each business.
  9. Email or a Slack message to the rep.

What lands in the inbox is one email: the ranked names, each with its score, reason, phone, website and a map link, and a CSV download. In the Team inbox the AI employee also leaves a short daily note of what it found. The Morning call list with decision makers and call notes template is close to this shape; New places every morning, only new is the lighter version without scoring.

If you split a city between several SDRs, add Split by territory before the sort so each rep receives their own compact patch, ranked.

Questions

How many names should a morning call list have?

As many as a rep can call well before the first break, often 15 to 30. Set it as a fixed number in the flow so the list never grows into a database.

Should the list include businesses we called before?

Usually not. Keep the morning list to first-time names and work follow-ups from your own pipeline, so reps always know whether a call is new.

Can the AI see whether a business already buys from us?

Yes, if you give it your customer table. Match with my table drops or marks places already in it before scoring.

What makes a good scoring brief?

Name the kinds of business, the size signals you trust, what disqualifies a lead and the reason you want written next to each score.

Templates that do this

IndustriesB2B sales

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.