You split the list across your agents and let each one run a campaign from their own WhatsApp. In Whispyr AI, a real estate CRM, each agent connects their personal WhatsApp, and a campaign sends one message at a time, spaced out by the delay setting you pick. At the normal setting one agent gets through about 95 people in Whispyr's default sending hours, so about a dozen agents reach 1,000 people a day between them. Every person gets a slightly different message, every reply lands on a lead, and the owner sees all of it.
Everything below was checked in Whispyr's product on 3 November 2026.
Step 1: put the list where the team can share it
There are three places a campaign's people can come from:
- Your leads. An agent picks leads they already hold and sends to them.
- An uploaded file. An agent uploads a sheet of up to 100 people. Every column in the sheet can be used inside the message, so a "project" or "unit" column fills in per person.
- The company's shared numbers. An admin turns the company's data files into a shared pool of numbers, and agents pull from it. This is how one big list gets split across the team.
For the shared pool, the admin sets the rules per agent:
- Persons per pull: how many people an agent takes each time they start a campaign, up to 100.
- Weekly campaign limit: how many campaigns the agent can start in a week, from any source.
- Which files, projects and areas an agent can pull from, and which data quality levels.
- Unlock timeout: how long the people an agent pulled stay theirs before going back to the pool.
When an agent pulls, Whispyr hands them people nobody has pulled yet first, then the ones pulled longest ago. People already held by another agent are skipped, so two agents never message the same person from the same pool. The admin can also lock, unlock or delete people in the pool by hand.
Step 2: write one message, send a different one to each person
The agent writes one primary message. It can greet each person by name, and an image, video or PDF up to 10 MB can go with it.
With AI variations switched on, Whispyr rewrites the message for each person, so 95 people do not receive the same words. It keeps every number you typed. You can add instructions, such as "keep the tone formal" or "don't change project names". With AI variations on, the message can also address each person as Mr or Mrs. AI variations use AI credits, which Intelligence includes every month.
If you want to see every message first, turn on Review messages before sending. Whispyr prepares every variation, and you edit and approve each one before anything goes.
Step 3: choose the hours and the delay
Every campaign has sending controls:
- Daily window. Messages only go out between the hours you set, in your time zone. The default is 8:00 to 22:00. A campaign still running at the end of the window waits and continues when it opens the next day.
- Delay mode. Two choices, exactly as Whispyr sets them:
| Delay mode | After each message | Batch size | Between batches |
|---|---|---|---|
| Normal delay | 3 to 6 minutes, random | 3 to 7 messages | 15 to 30 minutes |
| Really long delay | 10 to 20 minutes, random | 3 to 5 messages | 45 to 75 minutes |
Before you start, the campaign shows an estimated completion time from these averages. By that same estimate, 100 people at Normal delay take about 14 hours 38 minutes. In the default 14-hour window, one agent gets through about 95 people a day at Normal delay, or about 28 at Really long delay.
Step 4: the math for 1,000 a day
At Normal delay, 1,000 people a day means about 11 to 12 agents. For example:
- Load the list into the shared pool.
- Set persons per pull to 85 for 12 agents.
- Each agent starts one campaign in the morning with AI variations on.
- By the end of the window the team has messaged about 1,000 people, each from the agent who will handle the reply.
Pushing one agent's number harder is not an option: the delay modes are the only speeds Whispyr has.
Step 5: replies land on the lead
When someone answers a campaign:
- If they are already a lead, the reply joins that lead's WhatsApp chat.
- If they are not, and the campaign has Auto-create leads on replies on, Whispyr creates a lead assigned to the agent who sent it, with the reply as the lead's first note. Your duplicate rules still apply, so a number that matches someone else's lead can be held for an admin to decide.
On Intelligence, an admin can also switch on AI reading of buyer replies. If the buyer promises a time ("call me Sunday"), it goes on the agent's calendar, and facts like budget go on the lead.
Then you can start a second campaign from the first one and pick who to message: everyone, only those who replied, or only those who didn't. You can also exclude anyone who was in campaigns you pick, so nobody gets the same offer twice.
What the owner sees
- Every campaign. Admins see every agent's campaigns, and team leaders, managers and directors see their own people's. Each campaign shows its progress, its replies and its next send. Each person on it shows as pending, sent, not on WhatsApp, failed or cancelled.
- The chats. You choose who can read agents' WhatsApp chats with leads: only the agent, the agent and their managers and admins, or admins only. Anyone who can read a chat can also reply in it, from that agent's WhatsApp.
- Control. A campaign can be paused, resumed or stopped. Sends that failed can be retried for 3 days after the campaign finishes. If an agent's WhatsApp goes offline mid-campaign, the campaign pauses and carries on when it is back. It never moves to someone else's number.
What it costs
Prices from Whispyr's live price list, checked 3 November 2026:
| Plan | Per agent a month | 12 agents a month |
|---|---|---|
| Growth, with a WhatsApp number for each agent | EGP 80 seat + EGP 200 WhatsApp = EGP 280 | EGP 3,360 |
| Intelligence, WhatsApp number included | EGP 235 a seat from 10 seats | EGP 2,820 |
On Growth, each agent can run campaigns to their own leads and their own uploaded files. Campaigns from the company's shared pool and the AI reading replies come with Intelligence.
Start with one file in the shared pool and two agents, and read the replies before you scale to twelve.