Skip to main content

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.

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

Click SMS Logs in the left sidebar. The dashboard displays a table of all outgoing messages:
ColumnDescription
DateTimestamp of when the alert was triggered
RecipientThe masked phone number or email address
Event TypeThe business activity that triggered the alert
StatusCurrent delivery state of the message

Step 2: Search and Filter Logs

ToolHow to Use
Search barSearch by event name or message text
Status / Event filterFilter by a specific delivery result or alert category
Date rangeSelect 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 NameWhat Triggered It
auth.otp.requestA security code was sent for login or verification
payment.receiveAn incoming payment was successfully detected
payment.completeThe final processing of a payment is finished
payment.failedAn attempted payment was unsuccessful
withdrawal.compFunds were successfully moved to a destination account
withdrawal.failedA requested payout could not be processed
low.balanceAccount funds dropped below your configured threshold
stock.lowInventory hit 5 units remaining for a tracked product
order.paidA 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

StatusWhat It Means
QUEUEDThe message is scheduled and waiting to be sent
SENTThe message has left Bila and is with the mobile network or email provider
DELIVEREDThe recipient’s device or inbox confirmed receipt
FAILEDThe 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

Audit Trail

View a complete log of every action and API request on your account.

Team Members

Manage who receives alerts and at what access level.