WHMCS Telegram Bot
Customer support + sales over Telegram, native in WHMCS
The WHMCS Telegram Bot connects WHMCS to Telegram so customers can check invoices, view services, open tickets, request renewals and pay without leaving the chat. Admins get push notifications for new orders, ticket replies, payments and overdue services, and can search, reply and suspend from Telegram. It runs as WHMCS hooks in plain PHP, with no separate server process to host.
What the WHMCS Telegram Bot does
It gives customers and staff a Telegram interface to the WHMCS actions they use most.
For customers
- Commands: /invoices, /services, /tickets, /domain, /renew and /pay.
- Inline payment buttons, so a customer can pay an invoice without leaving Telegram.
- Markdown-formatted invoice and ticket replies that are easy to read on a phone.
- Replies in the customer's language, following the locale set in WHMCS.
- Account linking through a one-time code from the WHMCS client area, with per-event notification preferences.
For admins
- Commands: /search, /assign, /reply, /suspend and /unsuspend.
- Push notifications for new orders, ticket replies, payments received and overdue services.
- Per-admin alert channels, so sales alerts go to one group and abuse reports to another.
- A broadcast composer to message customers by language, product or group.
- Rate limiting and flood control to stay within Telegram's API limits.
Routing matters once alerts start flowing. Sending orders to a sales group, abuse to an operations group and ticket replies to the support team keeps each channel readable, and the right person sees the right event first.
Who it is for
The bot is for hosting, VPS, IPTV and digital service businesses whose customers already use Telegram daily. A renewal reminder or ticket update in Telegram is harder to miss than an email that lands in a spam folder.
It is just as useful for small support teams. Alerts arrive on staff phones, and an admin can answer a ticket or unsuspend a service from Telegram without opening the WHMCS admin area.
How it works in WHMCS
Setup takes a bot token and a webhook, and customers opt in from the client area.
- Create a bot with @BotFather in Telegram and copy the bot token.
- Install the module in WHMCS and paste the token into the bot settings.
- Run the webhook setup command. If you have no HTTPS endpoint, use long-poll mode instead.
- Set command permissions for admins and route alert types to the right Telegram groups.
- Customers link their Telegram account with a one-time code from the client area and choose which notifications they want.
- From then on, WHMCS events trigger Telegram messages, and commands sent to the bot run against WHMCS.
Customers who never link Telegram are not affected. Their email notifications keep working as before.
Requirements and compatibility
The bot is built for WHMCS 8.13 on PHP 8.1 or newer.
- An HTTPS endpoint for webhooks, or long-poll mode if HTTPS is not available
- A Telegram bot token from @BotFather
Webhook and long-poll modes mean it also works behind cPanel firewalls. The spec sheet lists support back to WHMCS 7.10; on an older release, ask us before installing.
Licensing, updates and support
The Regular license is $59 one time for a lifetime license, and an Open Source edition is available for $199.
Both include one year of updates and support, with optional renewal at $29 per year after that. You get an instant download and a license key, and a 7-day refund window applies.
Related modules and services
Running a community on Discord instead? See the WHMCS Discord bot with role sync. For a broader view, read how Telegram and Discord bots improve WHMCS support, or compare the multi-channel notifications module if you want several channels from one module. Custom bot work is available through our WHMCS hooks development service.
Key features
- Customer commands: /invoices, /services, /tickets, /domain, /renew, /pay
- Admin commands: /search, /assign, /reply, /suspend, /unsuspend
- Push notifications: new order, ticket reply, payment received, service overdue
- Inline payment buttons - customer pays without leaving Telegram
- Multi-language: bot follows customer's locale set in WHMCS
- Per-admin alert channels - sales alerts to one group, abuse to another
- Markdown-formatted invoice and ticket replies
- Subscriber linking via one-time code from client area
- Rate limiting + flood control
- Webhook + long-poll mode (works behind cPanel firewalls)
Why customers buy this module
- →Customers see Telegram messages sooner than email
- →Admins get alerts on their phone
- →Fewer 'is my server back yet?' tickets: status is one command
- →Renewal reminders that don't land in spam folders
Frequently asked questions
Do I need to host a separate Node.js or Python service?
No. The bot runs as WHMCS hooks in pure PHP, with no extra processes or hosting.
Can customers pay invoices inside Telegram?
Yes. Inline payment buttons let customers pay an invoice without leaving Telegram.
Can admins reply to tickets from Telegram?
Yes. Admins can search, assign and reply to tickets, and suspend or unsuspend services, using bot commands.
Can I broadcast to all customers?
Yes. Admins can compose a broadcast by language, product or group, with rate limiting to respect Telegram's API limits.
Does the Telegram bot work without HTTPS?
Yes. Webhook mode needs an HTTPS endpoint, but long-poll mode works without one.
What if a customer does not use Telegram?
Nothing changes for them. Email notifications keep working as before, and the bot is purely additive.
How much does the WHMCS Telegram Bot cost?
$59 for a Regular lifetime license or $199 for Open Source, each with one year of updates and support and optional $29 yearly renewal.
Technical specifications
- supportedVersions
- WHMCS 7.10 through 8.13
- installation
- Create bot at @BotFather, paste token, run webhook setup command
- requirements
- PHP 8.1+, WHMCS 7.10+, HTTPS endpoint for webhooks (or long-poll mode if no HTTPS)
- adminUI
- Bot settings, command permissions, group routing, broadcast composer
- clientUI
- Link Telegram from client area; per-event notification preferences