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.
Overview
The SMS Logs dashboard gives you a full audit trail of every alert your business sends — from payment confirmations to low balance warnings. Use it to verify delivery, troubleshoot failed messages, and keep your team and customers informed.Step 1: Open SMS Logs
- Select SMS Logs from the left sidebar navigation.
| 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
Narrow down your results using the built-in tools at the top of the dashboard:| 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
Every alert is triggered by a specific activity in your business. Use this reference to identify what each event means:| 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 |
Step 4: Check Delivery Status
The Status column shows exactly where a message is in its delivery journey:| 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 — see common causes below |
FAILED status:
- Incorrect or inactive phone number
- Recipient’s inbox is full
- Network or carrier signal error
Step 5: View Detailed Log Entries
To inspect the full details of a specific alert:- Click the eye icon in the Actions column next to the log entry.
- A side panel opens with the full delivery record, including:
- Exact timestamp of when the alert was triggered
- Masked recipient number or email address
- Message preview — the exact text that was sent
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.
Delivery Status Flow
Understanding how a message moves through the system helps you diagnose issues faster: If a message stays inQUEUED for longer than expected, this may indicate a system delay. If it reaches SENT but not DELIVERED, the issue is on the recipient’s end.