Skip to main content

How are sales from WhatsApp campaigns analyzed in the Bots Report?

How are sales from WhatsApp campaigns analyzed in the Bots Report?

This article explains how to interpret a sales metric within the Inbound Report: Bots Section in Atom, how the customer journey is visualized in the flow, and what information is considered to measure the performance of the bots.

❓Frequent question or initial context

How are sales generated from WhatsApp campaigns counted within Atom?

As shown in the Bots report, it does not represent actual purchases, but rather shows how many conversations were classified as "Sale" by an agent or automatically within the flow. This classification must be configured as "Sale" type in the system.

🤓 Explanation

The Inbound: Bots Section report was designed to analyze the performance of bots built in Flowbuilder, their traffic, assignments to agents, and the path customers follow.

📌 TheSalesmetric counts conversations that ended with a "Sale" type classification.

This can happen because:

  • Assignment to an agent who classifies the conversation as a sale.

  • An automatic action within the flow that applies a classification of the same type.

An integration with e-commerce or payment systems is not required to register it as a sale: it is an internal definition based on the closing classification.

⚙️ Troubleshooting: Step by step

To analyze sales within the bots report:

  • Go toReports > Inbound > Bots Section.

  • Apply filters according to the period, channel, origin type and bot name.

  • In theResults tab, observe:Conversations startedAssigned to agentSales(classified as such)Performance by botDistribution and summary of classifications

  • Conversations started

  • Assigned to agent

  • Sales(classified as such)

  • Performance by bot

  • Distribution and summary of classifications

  • For a more detailed analysis, use theBots Flowtab, where the following is shown:First option chosenFlow completion (assignment, abandonment, automatic completion)Classification and tag journeyLast message before abandonment

  • First option chosen

  • Flow completion (assignment, abandonment, automatic completion)

  • Classification and tag journey

  • Last message before abandonment

✅ Possible solutions

📌 How to configure or review a "Sale" type classification?

  • Verify in the Atom configuration if the classifications are correctly classified.

  • Make sure that agents and flows use these classifications consistently.

  • Remember that sales are only reflected if the conversation wasassigned and classified.

📌 Why might sales be missing from the report?

  • If a conversation ended without classification or was classified with a different type (for example, Positive end), it will not be counted as a sale.

  • If the conversation was managed only by the bot without reaching a final classification, it will not be reflected either.

📝 Additional notes

  • The report only includes bots created in Flowbuilder.

  • Themetric ofconversations startedhas no time limit if there is no classification. Therefore, it is essential to classify all conversations to obtain real data.

  • The value of "Sales" is not connected to payment systems, but depends on the assigned classification.

  • The system displays up to2,000 recordsin the platform view. The download allows up to 1,000,000records in.csv,.xlsx or.json formats.

  • For specific analyzes by flow, it is recommended to use theBot Namefilter with a single option to obtain a clear visualization in the flow tab.

Did this answer your question?