> For the complete documentation index, see [llms.txt](https://faq.droam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.droam.com/onboarding-guide/optional-settings/8.-notifications.md).

# 8. Notifications

Our platform provides a few types of notifications, allowing you to stay informed about key updates and service changes. Here's how they work for different service types and how you can customize them to fit your needs.

<table><thead><tr><th width="154">Type</th><th width="204">Levels</th><th>Description</th></tr></thead><tbody><tr><td>Notifications</td><td><p>Organizations</p><p>Companies<br>End Users</p></td><td>Automatic alerts are sent to end users or companies. They can be categorized as mandatory and optional</td></tr><tr><td>Webhook Notifications</td><td><p>Organizations</p><p>Companies<br>End Users</p></td><td>Automatically send real-time updates to your system through webhooks. This allows seamless integration with your internal processes.</td></tr></tbody></table>

### <mark style="background-color:blue;">1.</mark> <mark style="background-color:blue;"></mark><mark style="background-color:blue;">**Prepaid Services Notifications**</mark>

For Prepaid services, end users will receive reminders when their balance is about to expire:

* **10 days remaining**: "You have 10 days left, and your balance will expire."
* **5 days remaining**: "You have 5 days left, and your balance will expire."

These notifications help end users avoid service interruptions by giving them enough time to top up their accounts.

### <mark style="background-color:blue;">2.</mark> <mark style="background-color:blue;"></mark><mark style="background-color:blue;">**Subscription and PAYGO Services**</mark>

For subscription and PAYGO (pay-as-you-go) services, you can choose where notifications are sent:

* Set a **default email** where notifications will always be delivered.
* Send notifications to specific emails within the company.
* Use the **end user’s email** if needed.

This ensures that both internal teams and customers are informed at the right time.
