Talk about your next project
Zendesk case study

The lesson

Name the replaced system early, then use the customer’s quotes to explain both the practical pain and the reason the switch felt safer.

The move

The story opens with Prosper’s logo, the title “Prosper chooses Zendesk for innovation, fast deployment and time to value,” a short summary, and a product link for “Zendesk for Finance.” Two pull quotes from Brian Taylor come next, followed by company facts and result callouts including “+ 16 pts. CSAT (Chat),” “-50% Decrease in onboarding time,” and “+10% CSAT (Support + Chat).” The body then moves through Prosper’s business context, “Salesforce not a good fit,” “Zendesk innovation seals the deal,” “Smooth transition with implementation support and training,” “CSAT scores rise and training time decreases by 50%,” and “Predictive satisfaction indicates customers at risk.”

Why it works

  • Our readThe opening summary names the old system, the reason for change, the Zendesk products, and the outcomes before the reader reaches the narrative.
  • Our readBrian Taylor’s quotes make the vendor pain specific, with downtime, cost, relationship issues, and the admin burden stated in the customer’s own words.
  • Our readThe help center demo anecdote shows why Zendesk won the deal by making ease of deployment visible inside the sales process.

What not to copy

Don't copy Prosper’s lending context, Salesforce comparison details, or the copied-FAQ sales anecdote unless they are true to the customer. Keep the structure of old-system pain, why the new vendor won, implementation detail, and measured operating change.

More from Zendesk

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.