The metric nobody measures: conversations that ended in a sale

Your support team closes 200 tickets a day. CSAT is 4.2/5. Average resolution time is 8 minutes. Everything looks great on the dashboard.

But there's a question nobody is asking: how many of those 200 conversations ended in a sale?

If you can't answer that, you're measuring activity, not impact.

Support's vanity metrics

I'm not saying CSAT and resolution time don't matter. They do. But they're process metrics, not outcome metrics.

CSAT (Customer Satisfaction Score)

A CSAT of 4.5 feels good. But what does it really tell you? That the customer didn't get angry. It doesn't tell you if they bought. It doesn't tell you if they'll return. It doesn't tell you how much money that interaction generated.

We've seen stores with 4.8 CSAT that lose customers constantly. Why? Because they resolve inquiries "pleasantly" but never convert the conversation into a sale. The customer leaves happy but empty-handed.

Resolution time

"We resolve in 5 minutes on average." Great. But what did you resolve? If a customer asks "do you have size M?" and you respond "no" in 30 seconds, your resolution time is excellent. But did you offer size L? Suggest a similar product? Notify when it's back in stock?

Resolving fast without generating value is like running fast in the wrong direction.

Tickets closed

200 tickets closed per day. Feels productive. But a closed ticket isn't necessarily a satisfied customer, and definitely isn't a sale. It's just a conversation that ended. How did it end? With a purchase or a goodbye?

Measuring tickets closed is like counting how many people entered your store without knowing how many bought something.

Introducing: Conversation-Influenced Revenue

The metric we propose is simple in concept and transformative in practice: how much money did your support conversations generate?

Conversation-Influenced Revenue (CIR) measures sales that occurred during or within 24 hours after a support interaction. It includes:

• Direct sales: the customer asked about a product and bought in the same conversation.
• Cross-sell: the customer came for support and bought something additional.
• Retention: the customer had a complaint, it was resolved, and they bought again within 30 days.
• Recovered carts: conversational follow-up recovered an abandoned cart.

How to measure CIR

You need to connect three data points that most companies keep siloed:

1. Customer identification

Every conversation must be linked to an identifiable customer (email, phone, account ID). Without this, you can't connect the conversation to the purchase.

2. Influence window tracking

Define an attribution window. We recommend 24 hours post-conversation. If the customer buys within that window, the conversation "influenced" the sale.

3. Connection to the sales system

Your conversation system must be connected to your e-commerce. When a customer buys, the system checks: "did this customer have a conversation in the last 24 hours?" If yes, that conversation is marked as "revenue-influencing."

With VENDAQ, this is automatic. Every conversation has a "influenced revenue" field that updates in real time.

What you discover when you measure CIR

Companies that start measuring CIR discover surprising things:

Discovery 1: Your support generates more revenue than you think. When a customer asks "do you have free shipping?" and you tell her yes over $60, and she adds $15 more to qualify — that's support-influenced revenue.

Discovery 2: Some agents sell more than others. CIR reveals which agents (human or AI) are best at converting support into sales. Not by speed metrics, but by real impact.

Discovery 3: Voice conversations generate more CIR. Customers who send voice notes are 3x more likely to buy. If you don't process voice, you're losing your most valuable conversations.

Discovery 4: After-hours support has the highest CIR. 10 PM to midnight is the highest-conversion window — and it's exactly when most teams aren't operating.

CIR changes how you think about support investment

When you measure support as cost, you want to reduce it. When you measure support as revenue, you want to scale it.

Example: a store spent $3,000/month on support. They measured CIR and discovered their support generated $18,000/month in influenced revenue. The ROI was 6x. Suddenly, "reduce support costs" changed to "how do we invest more in support?"

That's the transformation. It's not a tool change — it's a mindset change.

The metrics that actually matter

Beyond CIR, these are the metrics we recommend for a revenue-oriented support dashboard:

• Total monthly CIR: total revenue influenced by all conversations.
• CIR per agent: who generates the most impact (human or AI).
• CIR by hour: when the most valuable conversations happen.
• Support conversion rate: % of conversations that end in a sale.
• Cross-sell rate: % of conversations where something additional was sold.
• Post-complaint retention: % of customers who returned after a complaint.
• Cost per conversation vs revenue per conversation: the real ROI of each interaction.

Stop celebrating CSAT. Start celebrating revenue.

CSAT tells you if the customer didn't get angry. CIR tells you if the customer bought. One makes you feel good. The other pays salaries.

We're not saying ignore CSAT — a dissatisfied customer won't buy. But CSAT is the baseline, not the goal. The goal is for every conversation to generate value. For the customer and for your business.

VENDAQ measures CIR natively. Every conversation has visibility into its revenue impact. Because we believe the most important question isn't "did we close the ticket?" but "did we close the sale?"