inMobiles RBT

A three-portal ring-back-tone platform: the operator aggregator CMS, the content-provider portal that feeds it, and the subscriber self-care web portal. The full screen inventory of a production CRBT deployment, running on synthetic data with no backend required.

Portal 1 · Operator

Aggregator CMS

The operator back-office. Customer care with a full subscriber 360, content moderation queues, catalogue and category maintenance, reporting, charging logs and role-based access control.

  • 36 screens across 6 menu groups
  • Subscriber 360: tunes, albums, gifts, schedule, groups
  • 38-section permission matrix
Open CMS
Portal 2 · Content provider

CP Portal

What a music label or aggregator partner sees. Upload single tunes or bulk manifests, track the approved / pending / rejected queues, maintain rights and reconcile the monthly payout.

  • Library split by moderation state
  • Single + bulk upload with validation
  • Copy rights, email rules, revenue-share report
Open CP portal
Portal 3 · Subscriber

Dial Tune Web Portal

The consumer front end. Browse the catalogue by tune, bundle, category or artist, preview and set a dial tune, then manage the subscription from the logged-in My Dial Tune area.

  • Home rails, categories, popular artists
  • MSISDN login with masked phone input
  • My tunes, albums, gifts, schedule, contacts, wishlist
Open portal
Demo data only. Every subscriber number, artist, content provider and transaction in this suite is synthetic. Re-skin for a specific operator by editing the token block at the top of assets/tokens.css and the BRAND object in assets/data.js.