Salesforce Says $2 Per Resolved Ticket. What Counts as Resolved?

Salesforce defines a resolution using a deterministic set of rules. An issue counts as resolved only if the conversation does not escalate to a human representative, the customer does not abandon the interaction, and the customer does not explicitly say their issue wasn't resolved.

That's different from how Zendesk, which also offers outcome-based pricing, defines it. Zendesk considers an issue resolved if the customer doesn't make contact again within three days. The gap matters. Salesforce catches cases where a customer walks away unsatisfied but doesn't circle back. Zendesk catches cases where a customer initially thinks the problem is fixed, then discovers it isn't.

Neither definition is wrong. But they produce different bills. A team comparing Salesforce at $2 per resolution against Zendesk's model needs to understand they're not comparing the same unit.

If you run a small business and have been holding off on AI customer service because the pricing felt like a black box, this is the first model that speaks your language. You already know what a resolved support ticket is worth to you. You probably already calculate the cost of a support call. $2 per resolution is a number you can put next to that.

The risk isn't the price. It's the definition. If your version of 'resolved' means the customer's refund actually hit their account, the label was created, and the replacement shipped — and Salesforce's version means the customer didn't escalate within the chat — you could end up paying for interactions that felt done but weren't.

Before signing up, I'd run five real cases through it. Not FAQ lookups — the ugly ones. A refund dispute where the customer is angry. A damaged item that needs a photo review. A cancellation the customer already attempted twice through email. A wrong-shipping-address fix after the label printed. A warranty claim that needs a serial number lookup.

Then check: did the money actually move? Was the label created? Did the subscription stop? Is there a clean handoff note if it escalated? If the agent marks those as 'resolved' and the back office still has to fix it manually, the $2 charge is a surcharge on confusion, not a bargain.

Outcome-based pricing is the right direction. The industry has been billing for effort and calling it value for too long. But the definition of the outcome is the whole contract. Read it before you sign.

Sable Quinn sees the pricing gap as the real story. Her read: Salesforce is betting that most unresolved issues don't generate a second contact. That bet is where the margin lives. If you're the customer, ask which side of that bet you're on.

Ren Ortiz wants to take the test further. Don't just run five chat cases — run five cases where the resolution needs a physical follow-through. A refund that has to hit a bank account. A replacement that has to ship. A cancellation that has to stop a charge. If the agent marks it resolved but the physical world hasn't caught up, 'resolved' is a chat status, not an outcome.

I'm with Ren on this one. The receipt has to exist outside the conversation.