Kandrex.
A business communications platform and OTP workspace, with separate customer accounts, wallets and order workflows.
Purpose. Architecture. Delivery.
Explore the work and its current development stage below.Less fragmentation. More clarity.
Business communications and SMS verification involve provider dependencies, access permissions, billing and time-sensitive status changes. The challenge is to make those moving parts usable and recoverable.
Define the useful core.
I build and operate Kandrex through CustomWebX. The web platform includes customer and admin tools for calling operations, messaging, recordings and account management. A separate OTP service handles quotes, number purchases, wallets, code delivery and supplier-confirmed refunds. An Android companion is available as an early-access build.
What is established
- Live public website and customer/admin workspaces
- OTP number purchases, code tracking and wallet/refund workflows
- Android companion with separate service sessions and protected updates
- Customer support cases and operational account tools
Keep the boundaries visible.
- Native Android calling and background ringing
- Push notifications and further device acceptance testing
How the pieces fit together.
A high-level view of the project’s approach. This describes the workflow and design considerations, rather than a claim that every listed component is currently available.
- 01
Separate dialer and OTP sessions
- 02
Customer and administrator interfaces
- 03
Provider adapters and activation polling
- 04
Wallet reservations and idempotent settlement
- 05
Web and Android delivery
- 06
Deployment, monitoring and recovery
What this does—and what needs care.
Android is an early-access build. Native Android calling and push notifications remain in development. Country, service and messaging availability depend on supplier support and account configuration.
Build on what we can verify.
Building the product has meant working beyond the interface: matching supplier outcomes to individual orders, preventing duplicate credits, protecting active sessions during updates and preserving useful customer state when upstream systems fail.
No traffic, revenue, client-satisfaction or delivery metrics are claimed in this case study. Genuine project materials can be added when their accuracy and sharing permissions are confirmed.
Related services
Discuss a communications or integration project.
Tell me what you need. We’ll review the requirements, agree the scope and work out a practical way forward.