Bonsho sends the WHMCS events you actually want to hear about to the places your team already watches: Discord, Slack, Telegram, ntfy, or any signed JSON webhook. It is named for the temple bell: it rings, then it stops.

Events

• Orders: accepted, flagged as fraud.
• Billing: invoice paid, invoice unpaid, payment reminder and overdue notices.
• Support: ticket opened, client replied.
• Clients and services: new client, cancellation requested.
• Provisioning failures: create, suspend or terminate failed, with the server's error.
• A daily summary of orders, payments and revenue.

Choose which events go to which channel, and edit the wording of each message with placeholders and a preview.

Built so it never gets in the way

• Nothing blocks a customer: every notification is queued first, so a chat service that is down cannot slow down checkout, a ticket or provisioning.
• Retries that end: failed deliveries are retried over five attempts, then kept as dead letters you can see and retry. Rate limits are respected.
• A delivery log shows every attempt, its result and how long it took.

Your data

• Bonsho only connects to the channels you add. No telemetry, no licence check, nothing sent to us.
• Privacy on by default: client names become Client #1041 and email addresses are stripped, including addresses in ticket text and provisioning errors.
• Webhook URLs and bot tokens are encrypted with your WHMCS encryption key and never shown back in full. The delivery log keeps the outcome of each delivery, never the message.

Free and open source (MIT) from Liquid Monks.