Run each project as its own campaign, and give that campaign an entry point: the team, group, branch or agent that sells the project. In Whispyr AI, a real estate CRM in Arabic and English, every new lead from that campaign enters at that point, and the split you set there (round robin, weighted shares or by hand) picks the agent. Whispyr routes on the campaign, so the campaign is how you tell it which project a lead belongs to. Automatic assignment comes with the Growth plan, at EGP 80 a seat a month (checked 3 November 2026).
Here is the setup, step by step, and what happens when a lead isn't worked.
Step 1: one campaign per project
Give every project its own campaign name wherever leads come from:
- Meta: a separate campaign per project in Ads Manager.
- Google Sheets: a campaign name column, filled per project by the agency.
- Your website or another system: the campaign name sent with each lead.
Keep the name the same everywhere. "Zayed Launch" in Meta and "Zayed Launch" in the agency's sheet end up in one campaign; "Zayed Oct" and "zayed-oct-2" are two different names until you join them.
Step 2: set up the campaigns in Whispyr
On the Campaigns settings page, create a campaign for each project. A new lead joins a campaign when its campaign name matches, ignoring capital letters and extra spaces.
Campaign names in real life drift. On the same page you can group the names that mean one project into one campaign, and the leads already in the CRM join it. When you merge one campaign into another, new leads that arrive under the merged campaign's name land in the one you kept.
On the Intelligence plan, Whispyr's AI also matches names that are close but not identical, such as "Zayed Oct" to "Zayed October", and can create a campaign for a new name it doesn't recognise.
Step 3: point each campaign at the project's people
Open a campaign and choose its entry point. It can sit at any level of your company:
- a branch, if you run branches
- a director group
- a manager group
- a team
- one agent
Every genuinely new lead from that campaign enters there, from any source: Facebook, Google Sheets, your website or the API. You can set the same entry point for several campaigns at once, which helps when one team sells three projects.
If the team or group you picked is later deleted, that campaign's leads go back to arriving the normal way, and the campaign shows its entry point is no longer usable, so you can pick a new one.
Step 4: decide how each level splits its leads
Think of your company as a tree: company, then (in larger companies) director groups and manager groups, then teams, then agents. A lead moves down one level at a time from where it entered. At each level you choose how leads are divided among the groups or people just below:
- Round robin: one lead each, in turn.
- Weighted: by shares you set, such as 70% to one team and 30% to another.
- Manual: the split stops here, and the team leader or manager hands leads out by hand.
You can leave people out of the split, such as a new agent still training. With round robin, you can also cap how many new leads a team or an agent takes per day or per week. Once they hit the cap, the next lead goes to the others.
So the "Zayed Launch" campaign can enter at the Zayed team, and inside that team leads go round robin to its five agents.
Leads with no campaign
A lead with no campaign, or with a campaign that has no entry point, takes your company's normal path: it starts at the top and moves down through the same splits.
A buyer who is already in the CRM
The entry point is for new buyers. A buyer who is already in the CRM follows your duplicate rules instead: usually back to the agent already working them, or moved only under rules you set. That keeps one buyer with one agent, even when they fill in a second project's form.
When a lead isn't worked
Routing gets the lead to the right team. These keep it moving:
Arrival timers. Set "open the lead within" and "call within", in minutes. A lead nobody opens or calls in time moves on.
Rotation rules. For leads in chosen stages with no activity for a set time. Each rule picks where the lead goes:
- to the next agent inside the same team, so a project's lead stays with the project's team
- to an agent in another team
- up to the agent's own team leader, or to the team leader of another team
- back to the lead pool
A rule can also limit how many times one lead is handed on, and say what happens after that.
The lead pool. Agents claim leads from it themselves, a set number at a time, with a wait between claims and a maximum per 24 hours. By default an agent has to act on the leads they claimed before they can claim more.
Branches. If you run branches, leads that arrive at company level can be split between branches by turn or by share. They can also wait in the company pool, where each branch admin pulls a batch into their branch.
Seeing where every lead went
Admins can open the assignment log and see every hand-off: when it happened, who it went to, and whether it was by hand, automatic, by rotation or a claim from the pool. A lead's timeline also shows when it entered through a campaign's entry point.
One form for several projects
If one form collects buyers for several projects, those leads share one campaign, and the campaign can only point to one place. Give each project its own form and campaign, or let a team leader assign those leads by hand from the project field on the lead.
What it costs
Automatic assignment comes with Growth. The Free plan doesn't assign leads automatically. Prices from Whispyr's live price list, checked 3 November 2026:
| Plan | Per seat a month | 10 users a month | 20 users a month |
|---|---|---|---|
| Growth | EGP 80 | EGP 800 | EGP 1,600 |
| Intelligence | EGP 250, then 235 from 10 seats and 220 from 20 | EGP 2,350 | EGP 4,400 |
Start with your biggest project: one campaign, one entry point at its team, round robin inside the team. Check the assignment log after a week.