Author
The DialerBee Team
The byline on every article and glossary entry on this site. It is the product, engineering, carrier and compliance people at BroadNet Technologies who build and run DialerBee, writing about the work they do.
Quick answer
Who writes the DialerBee blog? Articles are published under the byline DialerBee Team, which is the group that builds and operates the product: product and engineering, carrier and SIP operations, and the compliance side. DialerBee is the multilingual AI contact center platform, built by BroadNet Technologies, a telecom company founded in 2004 with 22 years in the industry, headquartered in Beirut with offices in Dubai, London and New York and presence across 13 countries. Articles are written from the platform as it runs today, capabilities that are not built yet are named as planned, and the compliance guides describe published regulator rules rather than giving legal advice.
Who publishes this
DialerBee is a product of BroadNet Technologies. BroadNet has been in telecom since 2004, which is where the platform gets its carrier side: BYOC SIP routing on your own carrier contracts, caller identity handling, and its own messaging infrastructure for WhatsApp and SMS rather than a third party sitting in between. The platform is multi-tenant and language-aware across 11 languages, including Arabic dialects and right-to-left agent interfaces.
- Publisher
- DialerBee
- Built by
- BroadNet Technologies
- Founded
- 2004
- Years in telecom
- 22
- Headquarters
- Beirut, Lebanon
Where the team works
Four primary offices, with presence across 13 countries.
Beirut, Lebanon
Headquarters
Engineering, AI research, product development and platform operations.
Dubai, UAE
Commercial HQ
Enterprise sales, MENA partnerships and compliance operations.
London, UK
Europe office
European sales, carrier partnerships and GDPR compliance.
New York, USA
Americas office
North American sales, TCPA compliance and enterprise accounts.
What the team writes about
Five subjects, drawn from the work of building and running the platform.
- Outbound dialing
- Preview, progressive, power and predictive campaigns, pacing and the abandon governor, list hygiene and the metrics a client review turns on.
- Answering machine detection
- Classifying the transcript of what was said rather than listening for a beep, across 11 languages and Arabic dialects, with agent feedback.
- Carrier and SIP
- BYOC trunking on your own carrier contracts, caller identity and number pools, and adding campaigns to a phone system you keep.
- Compliance-supporting controls
- DNC, consent with revoke, calling hours and frequency rules, and the outbound rules published by regulators across the Gulf, MENA and the United States.
- Contact center operations
- Queues and routing, supervisor tooling, QA scorecards, surveys, and the reports a BPO reports from.
How the articles are written
- Capability claims describe the platform as it runs today. Anything not built yet is named as planned, in the article and on the feature pages.
- Compliance guides summarise rules published by the regulator named in the article. They are written for operators, not as legal advice, and they do not make your calling lawful on their own: that still depends on your consent basis, your configuration and your process.
- Performance figures are labelled with the conditions they were measured in, and articles avoid numbers that cannot be reproduced.
- Posts carry the date they were published and, where they have been revised since, the date of the last update.
- Corrections are welcome. Write to the team and the article gets fixed with its update date changed.
Read what the team publishes
Compliance guides by market, operations practice, the technology under the call, and guides written natively in Arabic.