> For the complete documentation index, see [llms.txt](https://lern.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lern.sunbird.org/use/developer-guide/notification-service/features-core-capabilities.md).

# Features/Core Capabilities

#### Key Features:

1. Sends notifications to specified users identified by phone number or email or device id/topic/ role of the users.
2. Can be used to send synchronous or asynchronous notifications
3. Has NO understanding of the executing workflow or action involved.
4. Only the structural integrity of the payload is verified. If an invalid phone number/email is passed, the service will not validate; the end result will just be a failure.
5. In case of feed notification, users will be able to click and delete the feed from UI.
6. The user will also be able to see up to 30 latest feed notifications at a time.
7.  If the user clicks any notification, it will take to the respective notification page

   <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lern.sunbird.org/use/developer-guide/notification-service/features-core-capabilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.