Event-Driven

Quick definition

An architecture of systems and processes oriented by events, where each action or change in a customer's state triggers an immediate response. Within MCI, it is the technical and strategic capability to react to intentions in real time through webhooks and data streams, eliminating delays and latency in the buying journey.

In plain English

Imagine a company that doesn't need to "go look" for information or run spreadsheets to know what is happening. Instead, the company "listens" and reacts instantly. If a customer clicks a link, abandons a cart, or shows a specific doubt in a conversation, the system "wakes up" and delivers the exact response in that millisecond. It is moving from managing "static photos" (yesterday's reports) to managing a "live movie."

Why this concept exists

The Event-Driven concept solves the Decision Gap. In the traditional model (Batch Processing), companies process data in batches: the list of leads who downloaded a material today only reaches the salesperson tomorrow. The problem is that customer intention has a short shelf life. Event-Driven exists to ensure the company operates at the same speed as the consumer's mind, taking advantage of the decision "momentum" before interest cools down.

Instructive metaphor

Think of a sophisticated presence sensor in a smart home versus a manual switch. In the traditional model, you need to enter the dark room and search for the switch (the system depends on a manual or programmed action to fetch the data). In the Event-Driven model, the house detects your heat and the movement of your step (the event) and, even before you think about the darkness, the lights turn on, the air conditioning starts at your preferred temperature, and your music begins to play. The system doesn't wait to be asked; it reacts to your existence.

Practical example

An Explorador (Archetype) is browsing a SaaS software pricing page (Contexto). They open the chat and ask: "Do you have integration with CRM X?".

• The Event: Sending the message with the keyword "integration" combined with the "pricing" URL.
• The Event-Driven Reaction: The system doesn't just answer "Yes," but the Guardião do Ciclo (IAm) receives an immediate webhook, consults the conversational memory, and already presents a specific use case of that integration for that company's segment.
• Result: The decision to move to the Comparison state occurs in seconds, not in days of back-and-forth emails.

Anti-example

Do not rely on "Schedules" (Cron Jobs) as if they were Event-Driven. If your system runs a routine every midnight to update which customers haven't bought in 30 days, that is batch processing. If the salesperson receives an email report every Monday with last week's leads, that is the opposite of Event-Driven; it is an operation based on posthumous memories.

How it appears in operations

• Active Webhooks: Conversational systems sending data to the CRM at the exact moment a tag is applied.
• Contextual Push Notifications: The customer enters an interest zone and receives relevant content.
• Decision State Transition: The Conversation Score reaches a threshold and the lead is automatically "overflowed" to a human with all the context in the Bandeja de Contexto.
• Low Latency: The customer's perception that the company is "omnipresent" and highly responsive.

How to apply in MCI

In MCI, Event-Driven is the backbone of the Dynamic Journey.

1. Contexto and Convenience (8Cs): Use events to simplify the customer's life. If they have already provided data in a conversation, that event should update their profile globally so they never have to repeat the information.
2. Generative AI (IAm): The AI needs to be fed by event streams so that its responses are not generic, but based on the user's "now."
3. End of Operational Amnesia: Each event is a record in the Conversational Memory, ensuring the next touchpoint knows exactly what triggered the current interaction.

Related metrics

• Response Time: The time between the event and the company's action.
• Conversion Momentum: The conversion rate of leads approached in less than 5 minutes after a critical event.
• Webhook Throughput: Volume of events successfully processed without integration errors.
• Time-to-Value (TTV): Reduction in the time the customer takes to perceive value after an interest trigger.

Diagnostic questions

• How much time passes between a customer showing clear intent and our system/team reacting?
• Does our tech stack "push" the data (Push/Webhook) or do we need to "pull" the data (Pull/API Polling)?
• If a customer changes behavior now (e.g., searching for cancellation), how long does it take us to alert CS?
• Are our automations based on fixed times or real behavior triggers?

Related terms

• Webhook: The technical messenger that transports the event.
• Dynamic Journey: The route that shapes itself from events generated by the customer.
• Guardião do Ciclo: The role/IAm that monitors events to ensure the customer doesn't get stuck.
• Memory Gap: What happens when an event occurs, but the system "forgets" to notify other touchpoints.

Executive Mode

For the C-Level, Event-Driven means Organizational Agility. It is the transition from a reactive company, which analyzes the past to try to predict the future, to a responsive company, which captures revenue the moment it manifests. It reduces opportunity cost and increases CAC (Customer Acquisition Cost) efficiency by focusing energy where intent is hot.

Operational Mode

For managers, it means Management by Exception and Triggers. Instead of looking at 1,000 leads, the manager focuses on the 10 who just generated a "High Intent Event." This allows the sales or service team to act with surgical precision, increasing conversion rates and customer satisfaction (CX), as the approach feels "magical" and extremely timely.

Technical Mode

Architecture based on Publish-Subscribe (Pub/Sub) or Streaming Architecture. It involves configuring outgoing Webhooks in conversational platforms, ingesting this data in real-time into an event bus or Serverless architecture, and immediate processing to trigger actions in target systems (CRM, ERP, IAm) without the need for heavy synchronous requests or cyclical database queries.

Playful Mode

Imagine you are in a luxury restaurant. In the common model, you need to raise your hand and wait for the waiter to pass by (Batch). In the Event-Driven model, the sommelier observes from afar; the moment your glass reaches the last centimeter of wine (Event), they are already by your side with the correct bottle, without you needing to say a word. They didn't guess; they reacted to the exact event.

Executive summary

Event-Driven is the central nervous system of Marketing Conversacional Integrado. It transforms passive behavior signals into active business actions in real time. Operating in an event-oriented way is the only way to eliminate Memory and Decision Gaps, ensuring the company is as fast as its customer's intention. It is technology at the service of opportunity.