A call list for a new sales rep: the first four weeks

Give a new sales rep three things on their first day: a patch of their own, a short list of businesses to call each morning, and one line on why each one is on the list. Keep the list short (fifteen to twenty-five names), put the most promising first, and add only businesses nobody on the team is already talking to. An AI employee can build that list every weekday, so the rep's time goes on calls, not on research.

This is for sales managers and founders bringing a new person into a field or phone sales role. It covers what a good starter list looks like, how to read it as the rep's first weeks go on, a made-up example in Johannesburg, the mistakes that slow new reps down, and the blocks that do the work.

What a starter call list is

A starter list is not the whole market. It is a daily slice of it, chosen so a new person can make good calls before they know the product inside out. Each line on it holds:

• the business's name, type, address, phone and website;
• its rating and number of reviews, which tell the rep how established it is;
• a fit score from 0 to 100 and a one-sentence reason, written by xMap AI from what the flow found;
• where one is known, the person to ask for;
• a short call note: what to open with and what to ask.

The patch matters as much as the list. A rep who knows their area learns faster, and nobody calls the same business twice.

How the list should change over four weeks

A suggested rhythm, not a rule. Adjust it to your sales cycle.

The first week is about confidence. Start with businesses the scoring is most sure of, so early calls go well. From the second week, widen the range so the rep learns what a weaker fit sounds like on the phone.

A worked example

A made-up case with invented numbers: a company that supplies card payment terminals takes on a rep in Johannesburg and gives them the northern suburbs.

1. The manager draws the rep's patch in Area of interest. If there are several reps, Split by territory shares a whole city into compact areas of about the same size, so each rep gets a fair patch.
2. Nearby places finds restaurants, cafes and small shops in the patch, with phone or website.
3. Match with my table keeps only businesses not already in the company's customer table, so the rep never calls an existing customer.
4. xMap LLM scores each one as a prospect for card terminals and writes a reason and an opening line.
5. Sort and limit keeps the best 20 by score.
6. Email sends the list to the rep at 07:30, and Google Sheets keeps a copy where the rep notes each call.

In this invented first morning the flow finds 160 businesses in the patch, 31 are already customers, and the rep gets the 20 best of the rest. Twelve have a phone that answers; four agree to a visit. The manager reads the reasons with the rep that afternoon and changes one line of the AI's instructions: takeaway-only places rarely want a terminal at the table, so they score lower from then on.

Mistakes that slow a new rep down

• A list too long to finish. Eighty names a day teaches a new person to skim. Twenty they can actually call teaches them the job.
• No patch. Without an area of their own, two reps call the same restaurant and both lose credibility.
• Calling existing customers. Always remove your customers before the list goes out; one call to a happy customer as if they were a stranger costs more than it seems.
• Hiding the reason. A score without a reason trains the rep to trust numbers they cannot check.
• Keeping track of calls in xMap. Results in xMap Flows are found, scored and shown; they do not carry call outcomes. Keep those in the sheet or CRM the rep already uses.

How to do it with an AI employee

Start from Morning call list with decision makers and call notes or, for several reps, Split my city into fair sales territories. The blocks, in order:

1. Schedule, every weekday before the rep starts.
2. Area of interest: the rep's patch.
3. Nearby places for your types of business.
4. Only new, so a business already sent is not sent again.
5. Match with my table, keeping only businesses not in your customer table.
6. xMap LLM to score, write the reason and a call note.
7. Sort and limit for the best 20.
8. Email to the rep, and Google Sheets for the call log.

For field reps, add Route planner after the list to put the day's visits in a sensible order. What lands in the rep's inbox is one email: the day's businesses, best first, each with its reason, its call note and a map link.