SQL (Sales Qualified Lead)

Quick Definition

A SQL is a contact that has demonstrated clear buying intent and possesses the ideal profile to be approached by a sales consultant. It represents the moment when the lead leaves marketing nurturing and enters the sales pipeline for direct negotiation. In MCI, this qualification evolves into a real-time analysis of the probability of transaction (pT).

How the market understands this concept

In traditional marketing and sales, the SQL is the "handover" between departments. After being filtered by marketing (MQL), the lead is subjected to qualification criteria (such as the BANT framework: Budget, Authority, Need, and Timeline). If approved, the sales team accepts this lead, transforming it into a real opportunity in the CRM for a salesperson to initiate contact.

Why this concept matters

SQL is the filter that ensures the operational efficiency of the sales team. Without it, salespeople waste time on window shoppers or contacts without fit, which raises the Customer Acquisition Cost (CAC) and demotivates the team. A high volume of SQLs with a good conversion rate is the primary indicator that demand generation strategies are aligned with revenue goals.

The limits of the traditional view

The conventional view of SQL is static and binary: a lead is either an SQL or they are not. In a multichannel world with non-linear journeys, this definition ignores response time (speed-to-lead) and interest volatility. A lead might be an SQL now, but if the company takes 24 hours to respond, they lose context and urgency. Furthermore, manual qualification via long forms creates friction, driving the customer away even before the "delivery" to sales.

How MCI expands this concept

MCI replaces the static "SQL" label with the dynamic reading of Estado de Decisão combined with pT (Probabilidade de Transação). Instead of waiting for a form to be filled out, IAm agents monitor the conversation in real-time to identify buying signals, urgency, and authority. The concept of "qualified" ceases to be a status in the CRM and becomes a flow condition: if the context indicates high pT, the AI delivers the "Bandeja de Contexto" to the human immediately, eliminating the decision gap.

Practical example

A customer interacts with an IAm agent via WhatsApp asking about software technical compatibility. Instead of just answering, the AI consults the history (Conversational Memory), identifies that the company fits the ideal profile (ICP), and through tone of voice and depth of questions, detects that they are in the "Selection State." The AI calculates a high pT, alerts the salesperson via CRM, and schedules the demo, delivering to the human a summary of the entire previous conversation.

Common error

Treating SQL as an "all or nothing" process. Many companies discard leads that do not meet all immediate prerequisites, ignoring that a lead's status can change in minutes during a well-conducted conversation. Another error is interrupting the experience: the lead is highly engaged in chat and the company says "a consultant will call you in 2 business days," killing the sales momentum.

In the dynamic journey

In the dynamic journey, SQL is not the end of a funnel, but a point of acceleration. The MCI system identifies the customer's "paradigm shift" moment. If the context changes or the customer demonstrates a new pain point during the conversation, the AI can reclassify the lead instantly, adjusting the priority in the human service queue without the customer needing to restart their story.

Relationship with the 8Cs

• Context: SQL in MCI only exists if there is context. Having a good profile isn't enough; the timing and intent captured in the conversation validate the qualification.
• Convenience: Qualification occurs where the customer is (e.g., Direct, WhatsApp), without forcing them to leave their preferred channel to fill out external forms.
• Confidence: The handover to the salesperson is fluid because the AI has already established a foundation of technical help, reducing the resistance common in cold commercial approaches.

Related metrics

• pT (Probabilidade de Transação): A dynamic score indicating the chance of closing.
• Time-to-SQL: The time it takes for a lead from the first contact until being considered qualified.
• Conversation Score: The quality of the interaction that led to qualification.
• SQL Acceptance Rate: The percentage of qualified leads that actually generate proposals.

Connected MCI terms

• IAm (Integrated Artificial Intelligence): The agent that qualifies the lead in real-time through dialogue.
• Bandeja de Contexto: The data set the salesperson receives when taking over an SQL.
• Decision Gap: The interval that MCI tries to reduce by identifying an SQL instantly.
• 6 Decision States: The map that defines if the lead is ready to be an "SQL" or if they still need education.

Executive Summary

SQL has evolved from a static database category to a dynamic state of intent. In Marketing Conversacional Integrado, one does not "declare" an SQL based on profile alone; the opportunity is identified through context and conversational flow. Qualifying a lead is now an act of instant intelligence that joins profile data with real-time behavioral signals, ensuring the human salesperson intervenes exactly at the peak of the customer's interest.