Customer Success

Customer Success is typically the first department that receives calls from customers. It is your first line of defense that will take the hit when something goes wrong.

Therefore notifying them and streaming all the necessary customer information before customer calls to their communication channels and software APIs is important.

Drop in user signups

The following pipeline example helps to retrieve all signups from today, compare the number of them with the target, and notify the customer success team if it is lower than expected:

Drop in user logins

The same monitoring can be implemented for user logins. Just the query needs to be based on a different field:

Monitor customers stuck in the onboarding

Customers stuck in the KYC process for too long

One special modification of the previous example is the monitoring of customers who got stuck in the KYC process for too long.

If your data source supports such differentiation, you can even automatically detect if the root cause is on your side, your customers' side, or if the problem is related to your KYC provider.

Customer engagement summary report

// Simple SQL to get data
  COUNT(*) as cnt,
FROM customer_success.users
GROUP BY status
ORDER by cnt DESC;

The result can be sent once per time (usually per week) to your customer success team.

Last updated