A weekly sales summary for the head of sales
Someone assembles the Monday numbers on Sunday night. The agent posts the week to Telegram on its own, on time, and short enough to read.
Easy · 10 min · once a week
What you get
a digest in the chat · once a week
Sales, week of 11-17 March Closed 4.2m ₽, 12% below last week 23 new deals, 7 won, 5 lost Worth your attention: - Petrova: below the benchmark two weeks running - Romashka, 6.2m ₽: 11 days with no contact - 6 leads from Thursday still with no owner
A sample on made-up data; your numbers will be your own.
Who it fits
- The Monday stand-up, with the numbers pulled together by hand every Sunday evening.
- A head of sales running several teams who wants the laggard visible before month-end.
When it won't work
Deals get closed in CRM in one batch at month-end, so weekly dynamics will just be noise.
How the agent does it
Set the schedule
Pick the day and hour so the summary arrives before the stand-up, not after it. Give the team line-up and the weekly benchmark we compare the actual against.
Name what matters
Say what worries you: a drop two weeks running, silence on a large deal, leads nobody picked up. The agent leaves the rest out of the summary.
Compare the first weeks
For two or three weeks read the summary next to the raw export. That shows what the agent treats as normal and what as a deviation.
What you set
Bitrix24, Telegram. From you: the weekly revenue benchmark, the team line-up, the send time, and what counts as worth your attention.
What you'll need
Starter prompt
Copy the prompt or open it straight in a chat with the agent.
Assemble the sales summary for the past week from Bitrix24 and send it to Telegram [day and time]. In the summary: closed amount and number of deals versus last week, movement on large deals, new leads and how many of them were picked up. For each manager, a short line: closed, in progress, activity. Separately name the areas of attention: whose result is falling for the second week running, who has no single contact on large deals, where the week fell outside the usual range. Don't call a one-off dip or spike a trend until it has repeated twice. Keep the summary to [15] lines, with details as a separate file on request.
Open in chatCheck the weekly summary. List: - conclusions built on a single week (they can't be called a trend); - managers whose week was off because of holiday or sick leave rather than because of their work; - deals closed retroactively and therefore counted in the wrong week; - figures that don't match the previous summary, and why; - wording about specific people that shouldn't go into a shared chat without a conversation. Whatever didn't fit the line limit, show as a separate list; don't drop it silently.
A second prompt: the agent uses it to review its own work and show what's left for you.