From territory to an approved list.
Book meetings with distributors from the imported list.
Updated August 2026·4 min read
The situation
An industrial distributor has 240 companies in a spreadsheet and three reps to work them. The list has been sitting there for months. The first fifty contacts went well; the rest waited. It is not a matter of effort: contacting 240 companies evenly, inside working hours and without messaging anyone twice, is operations work, not selling.
The goal here is concrete and measurable: book meetings with distributors from that list. Not “generate interest” — meetings on the calendar, with enough context for the rep to arrive prepared.
What the campaign starts with
A campaign does not start from a sentence in natural language. It starts from three concrete things, and your team defines all three before the first message goes out.
- The list. 240 companies imported by CSV. Striker does not invent the base: it works the one you already have, and every record keeps where it came from.
- The approved template. The agent does not write the cold opener. It comes from a template your team reviewed and approved before the campaign was switched on.
- The window and the cap. 9:00 to 18:00, 40 contacts a day. The clock starts paused: each organization switches on its own sending.
How it operates
With those three inputs the campaign is executable, and from there it moves without a person pushing it. The agent makes contact inside the window, respects the daily cap and answers whoever replies — by email in this case, because that is the channel the campaign declares.
What it does not do is improvise. Every fact it states comes from a document of yours: the current catalogue, the delivery terms, the price list. If the answer is not there, the agent says so and hands off instead of inventing it.
The diagram is the whole case in one line: the inputs on the left, the agent and its channel in the middle, and what ends up resolved on the right.
Case context
List of 240 companies imported (CSV)
Approved first-contact template
Sending window 9:00-18:00 · cap 40 per day
Striker agent
Next step
Meeting created with real slots from the connected calendar.
Controls it respects
- Approved templates only for the first touch
- Immediate opt-out, suppressed from the campaign
- No final pricing over chat
The controls
The controls are not a review queue somebody works through every day. They are conditions the campaign respects on its own, which is why they are defined once.
- Approved templates only for the first touch. The agent writes the replies inside the conversation, not the cold opener. You wrote that one.
- Immediate opt-out, suppressed from the campaign. Anyone who asks to leave leaves right then, and stays suppressed: no later campaign touches them again.
- No final pricing over chat. The agent quotes terms and ranges from the current document. A closed price is a conversation for a person, and the thread is flagged so a rep picks it up.
The conversation
A prospect replied that they already work with another supplier. That is the point where an automated sequence falls over and a conversation keeps going. The full thread, with what Striker did at each step:
Striker agent
Hi, I'm Ferrocentro's sales assistant. Interested in our hardware distribution line? Reply STOP to opt out.09:14Striker agent
Our 2026 catalog lists weekly delivery and distributor margins for electrical and plumbing. How many branches do you run?09:32Striker agent
Yes, both. Shall we review terms in a short meeting? Tuesday at 10:00 or Wednesday at 15:30 works.09:41Fictional examples based on real product flows.
What is left
The meeting was created from real availability on the connected calendar, not as a proposal somebody has to confirm by hand afterwards. The rep receives it with the whole thread: what was asked, what was cited, and that the prospect runs two branches and cares about delivery.
That is the work the list of 240 companies was not getting: even contact, answers with grounding, and a handoff that arrives with the history inside it.