All use cases
SalesAutomation

Sort new Bitrix24 leads and assign tasks

Thirty new leads sit in Bitrix24 by morning and it is unclear which to grab first. The agent ranks them and assigns tasks to managers.

Easy · 10 min · every day

What you get

Hot — first contact before 12:00
1. Romashka LLC — 40 units, budget confirmed, owner Ivanov
2. Sergeev — second enquiry this month, owner Petrova
Normal — 14 leads, reply by end of day
Data missing — 3 leads: no industry, no amount,
no priority assigned, waiting on your call

A sample on made-up data — your numbers will be your own.

Who it fits

  • Leads arrive from the website, from email and from ads, and by morning nobody recalls who took which.
  • Volume has grown, triage happens on leftover time, and a big lead drowns among the spam.

When it won't work

The team has no priority rule — the agent has nothing to tell a big lead from a random one by.

How the agent does it

1

Set the rules

Describe what a hot lead looks like for you and list the managers with their areas — by industry, region or product. Say how many hours a lead may wait for its first reply.

2

Run the triage

The agent reads the new leads and sorts them by your rules. Where fields are missing it assigns no priority — those leads go into a separate queue.

3

Check the list

These tasks land in other people's day plans. So the owner list gets read before the tasks are created, not after.

What you set

Bitrix24. From you: what counts as a hot lead, the managers and their areas, and how many hours a lead may wait for a reply.

What you'll need

Битрикс24

Starter prompt

Copy the prompt or open it straight in a chat with the agent.

Prompt for the agent

Go through the new leads in Bitrix24 for [period — yesterday / the last 24 hours / since the last triage]. For each: source, what they're asking for, budget ballpark, region, contacts, whether this company is already in CRM. Assign priority by the rules: [budget above threshold / target industry / repeat enquiry]. If there isn't enough data for priority — don't infer it from the company name and email domain, mark it "not enough data" and leave it in the general queue. Flag possible duplicates of open deals, but don't merge them. Output a table: lead, priority, suggested owner, deadline for first contact. As separate lists — duplicates and leads without contacts. Create tasks only after I confirm the list.

Open in chat
Check the result

Check the lead triage. List: — leads where priority was assigned on incomplete data, and which field was missing; — leads marked as duplicates only because the company name matched; — cases where the owner was chosen by who was left rather than by the assignment rule; — leads from sources that weren't in my rules — how you handled them; — leads with a contact but no substance to the request: they can't be worked blind. Don't create tasks: show an "I suggest creating" list and wait for confirmation.

A second prompt — the agent uses it to review its own work and show what's left for you.

Related use cases