Modern operations, migrated carefully
Billing, subscribers, and payments moved off the legacy system without losing a record or a customer. The old system keeps running until the new one has earned trust.
AI implementation · Lebanon · Telecom & ISPs
AI for ISPs and telecom operators in Lebanon.
For a Lebanese ISP, the AI worth building first sits on the subscriber side: a bot that answers balance, renewal and outage questions in Arabic, French and English, reading live billing data instead of guessing. We have replaced a 25-year-old billing platform for an ISP here and kept it in production. Fixed price after a short discovery.
An ISP in Lebanon runs on work nobody outside the building ever sees. Subscribers message on WhatsApp asking whether their payment landed, when the line comes back, and why the speed dropped, in three languages, usually at the same hour the power went. Support retypes the same four answers all day. Renewals get chased by hand, one name at a time. And the billing system holding it together is often older than half the staff, with one person who genuinely understands it.
We build the subscriber layer first, because that is where the hours actually are: a bot on WhatsApp or Telegram answering balance, renewal and outage questions from live billing data, provisioning that stops being a manual step, and renewal reminders that go out without anyone remembering to send them. We have done the hard version of this. We replaced a 25-year-old billing platform for a Lebanese ISP with roughly 2,000 subscribers, synced it to their existing RADIUS stack rather than asking them to abandon it, and put a customer bot on top. It has been in production since, and the client keeps sending us the next thing they want.
What we build for Telecom & ISPs here.
Customer service on the apps they use
Balance, renewals, outage updates, and plan changes over Telegram or WhatsApp, with payments handled in the chat.
An operations view that’s actually current
Live dashboards for collections, usage, and network issues instead of a spreadsheet someone updates on Thursdays.
3 months
to replace a 25-year-old system. A Lebanese ISP with ~2,000 customers ran billing on software older than its staff. It now runs on a platform we built, with a customer bot their subscribers actually use.
Questions
Do we have to replace our billing system to get anything out of this?
No, and usually you should not start there. The fastest payoff is a layer on top of what you already run: a subscriber bot reading your live data, and automated renewals. Replacing the core is a bigger project we can do later, and only if the numbers justify it.
Can it actually read our RADIUS and provisioning stack?
Yes. We have integrated directly with a production RADIUS setup over a secured tunnel for a Lebanese ISP, syncing subscriber and billing state both ways. We build around the stack you have rather than requiring a migration first.
Our subscribers write in Arabic, French and English, sometimes in one message.
That is the normal case here and the bot is built for it. It replies in whichever language the subscriber used, including mixed messages, and answers from your real account data rather than a generic script. Anything it should not answer goes to a human with the context attached.
Other industries in Lebanon.
See what we’d build for your business first.
The free AI audit maps your operations and shows the three systems we’d build first, in plain language, with a fixed price to start.
