# 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:
Pipeline example
Query task
Condition task
Notification task
## 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
Example pipeline
Query task
CSV report as a result
## 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
Pipeline example
```sql
// Simple SQL to get data
SELECT
COUNT(*) as cnt,
status
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.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.ylem.co/use-cases/industry-specific-use-cases/customer-success.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.