Ticket

Quick definition

A ticket is the formatted record of an interaction or request initiated by a customer, used to organize, track, and resolve demands. Traditionally, it functions as a control unit that moves between departments. In the MCI, it ceases to be just a protocol and becomes an intelligence node within a continuous conversational flow.

How the market understands this concept

In the traditional market, the ticket is the backbone of Help Desk and Service Desk systems. It is viewed as a "call" or "occurrence" with an associated protocol number, possessing a status (open, in progress, resolved), priority, and an assigned owner (human or bot). It is the standard tool for measuring support team productivity and ensuring that no request is forgotten.

Why this concept matters

The ticket is vital for operational efficiency and data governance. Without it, companies lose control over the volume of demands, which directly impacts retention (Churn) and customer satisfaction (CSAT). It allows management to identify recurring bottlenecks in the product or service, transforming individual problems into intelligence for process improvement and cost reduction.

The limits of the traditional view

The conventional view treats the ticket as an isolated and static entity. The biggest problem arises in the "silo effect": when a customer opens a support ticket, Sales and Marketing areas rarely know about it. Furthermore, the traditional ticket often suffers from a "context vacuum": every time the ticket changes agents or status, the customer has to repeat their story, generating friction and the feeling that the company doesn't know them.

How MCI expands this concept

In Marketing Conversacional Integrado, a ticket is a Conversation with Memory. It is not an end in itself, but a state within the journey. The MCI integrates the ticket with the Crachá de Contexto, ensuring that, regardless of the channel, the Bandeja de Contexto accompanies the request. If an AI agent or a human takes over the ticket, they already possess the full history, recent behavior, and the Conversation Score. The ticket stops being a "number in the queue" to become a fluid step in building trust.

Practical example

An e-commerce customer interacts via WhatsApp asking about a delivery delay. The AI Agent identifies the intent, checks the order status, and automatically generates a ticket, attaching the Crachá de Contexto (VIP customer, last purchase 10 days ago, preference for express delivery). If the customer decides to call the center hours later, the human agent doesn't ask "how can I help?", but rather says: "I see here that you contacted our WhatsApp regarding the delay of order X; I have already verified that it is out for delivery now." The ticket served as the link of continuity, not as an obstacle.

Common mistake

Treating the closing of the ticket as the end of the conversation. Many companies focus so much on the SLA (response time) for closing that they ignore whether the issue was resolved in the customer's eyes or if that problem generated a new sales opportunity or upsell.

In the dynamic journey

In the dynamic journey, a ticket can change nature in real-time. What began as technical support (error ticket) can be transformed into an expansion opportunity (sales ticket) if the AI detects that the customer is trying to use a feature that is not part of their current plan, moving them through the 6 States of Decision without interrupting the flow.

Relationship with the 8Cs

• Context: The ticket must carry all the previous baggage of the journey to avoid a "reset" in the experience.
• Continuity: The ticket ensures the conversation does not die, maintaining the narrative line between different channels and sessions.
• Confidence: The fast and contextualized resolution of a ticket is the greatest asset for transforming a problem into loyalty.

Related metrics

• FCR (First Contact Resolution): Percentage of tickets resolved on the first contact.
• TTR (Time to Resolution): Average time to solve the ticket.
• Conversation Score: Evaluation of the quality and fluidity of the interaction within the ticket.
• Ticket-to-Leads: Number of support requests that were converted into new business opportunities.

Connected MCI terms

• Crachá de Contexto and Bandeja de Contexto: Elements that prevent the ticket from being a blank page.
• Operational Amnesia: What the ticket tries to avoid by recording what was said.
• Guardião do Ciclo: The role that monitors whether the ticket is advancing in the journey or stalling the customer.

Executive summary

For the MCI, a ticket is not a complaint protocol, but the materialization of corporate memory regarding a customer's need. It must function as a guiding thread that carries contextual data between channels and silos, eliminating operational amnesia and transforming a moment of friction into an opportunity to reinforce convenience and trust.