Sales where no lead ever goes cold

The agent picks up CRM leads, runs follow-ups, builds quotes and pipeline forecasts while you close deals.

Get started
@amoCRM show the sales funnel and where we lose deals
amoCRM

1 in 8 leads becomes a deal; qualification is the main leak

19 deals worth RUB 5.1 million won; another RUB 8.2 million is in negotiation.

Sales funnel · May

Document · XLSX
Bottleneck action plan

Leads from CRM, telephony, and chats in one pipeline

All integrations
amoCRM
Bitrix24
RetailCRM
Megaplan
Wazzup24
Mango Office
Avito
YCLIENTS

Leads never slip through CRM

Sorts new leads from Bitrix24 and amoCRM, qualifies them, creates tasks, and flags deals gone quiet.

Qualify the new Bitrix24 lead and create a task for the manager

Done. This is a hot lead (A): the budget and profile fit. The qualification brief is attached and the manager has the call task.

Lead qualification brief

Document · DOCX

Follow-ups without reminders

Writes personal emails after calls and meetings, runs touch sequences, and logs every reply in the deal card.

Quotes and invoices in minutes

Builds a proposal on your company template with current pricing and terms tailored to each client.

Prepare a proposal for the Wholesale Fasteners deal in amoCRM

Done: I prepared a RUB 412,000 proposal, attached it in amoCRM and moved the deal to Approval.

  • Items: 6 products from the price list, wholesale prices −12%
  • Discount: 8% for volume, approved under the deal rules
  • Delivery: 5 business days, shipped from the warehouse

The PDF is attached to the deal. Send it to the customer on WhatsApp?

Proposal: Wholesale Fasteners

Document · PDF

Pipeline forecast and report

Calculates a weighted forecast by stage, surfaces bottlenecks, and sends the digest to your head of sales.

Closing forecast: the calculation
weighted

Forecasting the quarter close: reading the Bitrix24 pipeline and weighting deals by stage and historical conversion rates.

  • Read open deals and stages from Bitrix244 sec
  • Checked conversion rates by stage over six months3 sec
  • Calculated the forecast using each deal's probability3 sec

Weighted forecast: RUB 8.94 million against a RUB 7.2 million baseline. Four deals are at risk, with no activity for over 14 days.

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.Build a proposal for deal [number or deal name in Bitrix24], using template [link to document]. Take the legal details, contact person and scope of work from the deal card, prices from [price list], payment terms and the discount by the rules: [rules]. Don't fill blanks with plausible text: if CRM has no deadline, volume or contact person, leave a [to clarify] marker in the document and collect all such spots in a separate list at the end. Don't round or recalculate prices yourself. Output: a document following the template's structure, without extra blocks, followed by a list "what to clarify before sending".Find open deals in Bitrix24 that have no active task or no activity for longer than [N] days, across pipelines [list of pipelines]. For each: amount, stage, owner, date and type of the last contact, date of the nearest task, if there is one. Count as contact only real activity: a call, an email, a meeting, a comment. Don't count a stage change or an automatic field update as contact and don't use it as a sign that the deal is alive. Group by manager, and within that by amount. Separately pull out deals with no owner and deals whose close date has already passed. At the end: how many deals in total and for what amount are stuck.Find deals in Bitrix24 where a proposal was sent more than [N] days ago and there's no reply from the client, and prepare a draft follow-up email for each. Before the email, gather the context: what was in the proposal, what was agreed on the last call, which objections have already come up. Take the reason for writing from the communication history. If there's nothing in the correspondence to hook onto, don't invent the client's interest and don't refer to a conversation that never happened; write a short neutral email and mark it "no context". Don't offer discounts or new terms, only [permitted reasons]. Output a table (client, amount, days of silence, email subject) and the text of each email up to 120 words as a draft, without sending.
Build the [quarter] sales summary from Bitrix24 and amoCRM and compare it with [the previous period]. Give plan versus actual on revenue overall and by [breakdown: line of business / manager / region]: plan, actual, variance. For each manager: closed amount, number of deals, average deal size, share of the total actual. Separately: the five largest won and five lost deals with the stated loss reason. Don't add up deals from the two systems until you show that their stages and statuses are comparable; count what isn't comparable separately and say so. Build the forecast for the next quarter from open deals with a close date inside it, honestly stating the share of deals with no date. Output XLSX: "Plan vs actual", "Managers", "Deals", a totals line.Find open deals in Bitrix24 and amoCRM above [threshold] that have been sitting at their stage longer than the norm: [stage: period; stage: period]. For each deal: amount, stage, how many days it's been sitting, owner, last contact, whose court the ball is in (ours or the client's). Take the reason it stalled from comments and correspondence. If it isn't there, don't infer the reason from the stage and the amount; write "reason not recorded" and set "find out the status" as the first action. For each deal propose one specific action for this week and state what you need from me. Don't calculate stage conversion percentages: a list of deals is what's needed. Sort by amount, with what can be closed before the end of [the period] on top.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.Reconcile the payment promises from Bitrix24 deals against actual receipts in 1C as of [date] and find clients with no payment for longer than [N] days. For each: the promised date and amount, who recorded it and when, what actually arrived, how many times the deadline was pushed, the date of the last conversation, the owning manager. Link client and payment by legal details. If a payment arrived without a link to a deal, don't assign it to the nearest one by amount; move it into "unidentified payments". Don't reconstruct promises that aren't in CRM by logic: write "agreement not recorded". Sort by amount. For each client propose the next step: a call, an email, escalation or handover to receivables collection.

FAQ

Where data is stored and how access is protected is covered separately: security overview

Bitrix24 and amoCRM via API. It reads and updates deals, moves them through stages, assigns tasks to reps, and pulls in call and message history on its own.

It drafts emails and messages for your acceptance. With permission it sends follow-ups on triggers, say, a day after a meeting with no reply.

From CRM data: deal size, stage, probability, and momentum. It produces a weighted forecast, highlights stalled deals, and flags risks to the plan.

No. It takes the routine (emails, quotes, reports, reminders), so reps spend their time talking to clients and closing deals.

Ready-made use cases

All use cases
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.

Build a proposal from your template

Every proposal starts as a copy of the last one, carrying another client's prices along. The agent fills your template from the Bitrix24 deal.

Find stuck deals in the CRM and follow up

Two hundred open deals in the pipeline, and half have not moved in a month. The agent lists the forgotten ones per manager, with amount and last contact.

Write follow-ups to clients after a proposal

You sent twenty proposals and three people replied. The agent writes the rest a note built on what was actually discussed, not a generic nudge.

Build a weighted pipeline forecast

The quarterly review costs two days in Excel before the meeting. The agent pulls plan against actual, who contributed what, and the open-deal forecast.

Find bottlenecks in the pipeline by stage

A stand-up needs specific deals, not pipeline theory. The agent names the ones sitting past the norm for their stage and says what is holding each.

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.

Find clients who haven't paid in over 30 days

Before the call round you need to know who is merely late and who has moved the date twice. The agent matches Bitrix24 promises against 1C receipts.

Guides on this topic

A pipeline that runs itself

Connect your CRM in minutes and hand leads, follow-ups, and reporting to the agent, so your team can focus on deals.

Get started