> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usebila.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Track Business Alerts
> Monitor, search, and interpret your SMS delivery logs to verify alerts are reaching your team and customers.
The **SMS Logs** dashboard gives you a full audit trail of every alert your business sends - from payment confirmations to low balance warnings.
***
## Watch: Tracking Your Business Alerts
***
## Step 1: Open SMS Logs
Click **SMS Logs** in the left sidebar.
The dashboard displays a table of all outgoing messages:
| Column | Description |
| -------------- | ---------------------------------------------- |
| **Date** | Timestamp of when the alert was triggered |
| **Recipient** | The masked phone number or email address |
| **Event Type** | The business activity that triggered the alert |
| **Status** | Current delivery state of the message |
## Step 2: Search and Filter Logs
| Tool | How to Use |
| ------------------------- | -------------------------------------------------------------------- |
| **Search bar** | Search by event name or message text |
| **Status / Event filter** | Filter by a specific delivery result or alert category |
| **Date range** | Select a Start date and End date to view logs from a specific period |
Combine filters for precision - for example, filter by `payment.failed` events within a specific date range to investigate a batch of failed transactions.
## Step 3: Understand Alert Event Types
| Event Name | What Triggered It |
| ------------------- | ------------------------------------------------------ |
| `auth.otp.request` | A security code was sent for login or verification |
| `payment.receive` | An incoming payment was successfully detected |
| `payment.complete` | The final processing of a payment is finished |
| `payment.failed` | An attempted payment was unsuccessful |
| `withdrawal.comp` | Funds were successfully moved to a destination account |
| `withdrawal.failed` | A requested payout could not be processed |
| `low.balance` | Account funds dropped below your configured threshold |
| `stock.low` | Inventory hit 5 units remaining for a tracked product |
| `order.paid` | A customer order has been fully settled |
Events like `payment.failed` and `withdrawal.failed` are the most operationally critical. Ensure high-access roles have Detailed Alerts enabled so these are never missed.
## Step 4: Check Delivery Status
| Status | What It Means |
| ----------- | -------------------------------------------------------------------------- |
| `QUEUED` | The message is scheduled and waiting to be sent |
| `SENT` | The message has left Bila and is with the mobile network or email provider |
| `DELIVERED` | The recipient's device or inbox confirmed receipt |
| `FAILED` | The message was not delivered |
Common reasons for `FAILED` status:
* Incorrect or inactive phone number
* Recipient's inbox is full
* Network or carrier signal error
A `SENT` status does not guarantee delivery. Always check for `DELIVERED` to confirm the recipient received the message. If a critical alert shows `FAILED`, verify the recipient's contact details in their admin or cashier profile.
## Step 5: View Detailed Log Entries
1. Click the **eye icon** in the **Actions** column next to the log entry.
2. A side panel opens with the full delivery record, including the exact timestamp, masked recipient, and message preview.
Recipient contact details are masked in logs for privacy. To update a recipient's phone number or email, navigate to their profile in **Admins** or **Cashiers**.
## Next Steps
View a complete log of every action and API request on your account.
Manage who receives alerts and at what access level.