Salebot report: chatbots, conversations and deals

A chatbot report for clients

Salebot is a chatbot builder with a built-in CRM. Businesses use it to build bots for Telegram, VK and other messengers, sell through them, and let managers answer customers in a shared inbox. There is plenty of data inside, but it is shaped for operators rather than reports. The client wants three answers: how many people came into the bots, how the conversations went and how they ended.

Reportkey connects to the Salebot API and builds a section of a recurring report from the project data, sent as a link or PDF on schedule next to ads and site analytics.

Connecting Salebot: project API key

Create the key in Salebot project settings under Integrations, Add API key, and tick two permissions: reading client information and reading CRM information. With those rights the key only reads; Reportkey cannot send a message or change a deal or variable. Enter the key once on the integrations page and choose which bots the project report should include.

New bot subscribers

The first block covers audience inflow. Every Salebot client has a creation date, a messenger and the bot that brought them in. From that Reportkey builds:

• new subscribers for the period by day, week or month;
• total subscribers at period end;
• a messenger split, showing where the bot gathers more people;
• a bot split when the project has several bots.

Salebot returns clients in batches of up to 500, so a large base loads in several steps without affecting the report.

Conversations and manager work

The second block describes messaging. Message history shows how many messages were exchanged in the period, how many were not delivered and why, and how many replies each manager sent. Where sales happen in chat, that measures team workload and service quality. Undelivered messages suggest checking whether users blocked the bot or a broadcast failed.

Deals in the Salebot CRM

The third block is the outcome. The built-in CRM sorts deals into active, won and lost. The report shows the count in each status and a messenger split, and adds amounts when the bot scenario writes them into deal variables. Salebot keeps the current status, not a log of transitions, so the report shows the funnel as of the build date.

Client sources: tags and UTM

The fourth block shows where people come from, using client tags and variables the bot saves, most often UTM tags from the entry link. With tags in place, the report shows new clients and won deals per source, and next to ad spend that gives a clear cost per client.

Salebot next to ads and the website

A chatbot usually ends an ad funnel. Add VK Ads and Yandex Direct campaigns that lead into the bot, VK community statistics and site visits from Yandex Metrica. For VK mailings, use the Senler report. See all social media integrations. AI insights and branding are not on every plan. Browse the SMM agency demo report and pricing.