Subscriber 360 v2: from profile to action, and why version 1 rarely works

TL;DR

Subscriber 360 as a platform is infrastructure, not a commercial product. Most operators that launch a Subscriber 360 v1 project end up 12-18 months later with a pretty profile in one screen and a dashboard nobody opens. ARPU did not rise, churn did not fall, retention efficiency did not improve. The reason — Subscriber 360 v1 is built as “let us collect data”, without an operating model that turns data into action. Version 2 starts not from data architecture but from the description of five-to-ten concrete decisions that have to improve, then back-designs from those decisions to the data, processes, ownership and tools needed. This changes both the order and the very success criteria.

A Subscriber 360 v1 test

Take 5 random customers from your base and walk them through your current Subscriber 360. What can you do with these profiles that you could not do without them?

If the answer is “see the full picture” or “more convenient” — that is a sign v1 is alive. Subscriber 360 is not for “more convenient profile viewing”. It is for specific commercial decisions to be taken better — with higher conversion, higher precision, higher speed.

If the answer requires thought or reduces to “well, the contact centre agent sees more history” — that is marginal. Most of the value is uncaptured.

Many operators land here after an 18-24 month Subscriber 360 v1 build.

Where the value usually leaks

Several structural reasons why version 1 of Subscriber 360 produces no commercial effect.

The build starts from data, not from decisions. The team builds the data model first, then the profile UI, then looks for use cases. By the time use cases are formulated the architecture is set in stone, and it is optimised for the profile view, not for the decisions.

The profile exists, action does not. Marketing sees the profile but has no tool to act on it immediately. To launch a campaign targeting a segment seen in Subscriber 360 takes another month of work with CRM, marketing automation, billing.

No owner. After build, Subscriber 360 hands over to IT operations. IT runs uptime and performance but does not own the commercial outcome. When retention does not improve, nobody is accountable for the failure.

Slow updates. The profile refreshes overnight or hourly. Many commercial decisions need fresher data. Marketing launches a campaign on data that is 12 hours old and loses relevance.

Wrong segment. Subscriber 360 shows what is in the data. But real commercial decisions need data that may not exist in current source systems — competitor activity, broader behavioural signals, intent signals.

A deep look at v2

Version 2 is built differently. First, 5-10 concrete commercial decisions that have to improve are formulated. They could be:

Retention call assignment. Whom to call this week with a retention offer. Today the list arrives via a delayed CRM query with limited segmentation.

NBA in the app. Which offer to show the customer the moment they open the app. Today often a generic banner.

Cross-sell in the dealer network. What to offer the customer in the office beyond what they came for. Today the dealer is helpless — no signal about the customer.

Compensation triggers. Which customers automatically receive compensation after a network incident. Today manual and slow.

Risk segmentation for financing. Which customer can get an instalment plan with what confidence. Today on a simplified model.

Each of these decisions is the success criterion of Subscriber 360 v2. If the decision is taken better — v2 is working. If not — something is wrong in the build.

Then comes the back-design. For retention call assignment data on usage trends, complaint history, awareness of competitive offers is needed. A process is needed — who sees the list, who calls, who measures the result. An owner is needed — accountable for retention conversion. A tool is needed — a window in which the retention agent sees the context.

The profile becomes not “all knowledge about the customer” but a composition of what each decision needs. Sometimes the profile looks different for different decisions.

FAQ

If we already run Subscriber 360 v1, do we have to rebuild everything?

Not necessarily. Sometimes v1 as a foundation fits but is insufficient. The v2 build — operating model, owner, decisions, action layer — can be added on top. Sometimes some foundation elements (data latency, sources) need work, sometimes not.

How to avoid v1 mistakes when starting fresh?

Do not start with an RFP for a Subscriber 360 platform. Start with a workshop where the 5-10 decisions to improve are formulated. The RFP is written only afterwards and sets requirements that answer to the decisions.

How to measure v2 working and v1 not?

A simple test — measure conversion on the decisions that v2 should improve. Before v2 — baseline. After v2 — improvement. No improvement, v2 is not working.

Subscriber 360 without a data quality foundation — does it work?

No. If data is unreliable, any decision on it is unreliable. Data quality is the level that has to be in place before v2 build.

Is it very expensive?

Depends on scope. v2 does not necessarily cost more than v1 — it requires a different approach. Often v2 is cheaper because it focuses on 5-10 decisions, not on “everything for everyone”. Lean and focused.

When v2 is not a priority

If the operator just finished a major restructuring and has no capacity for another transformation — wait.

If v1 minimally functions and basic operating decisions are made (suboptimally), v2 is the second priority after network, billing, or other core stabilisation.

If the data quality foundation is broken, no v2 will work. Data quality first.

If retention is already strong and churn is low, v2 will yield a marginal result.

If C-level is not committed to operating model change beyond data platform, v2 will be another IT project without commercial impact.

Discussion points for the committee

Which 5-10 commercial decisions today are taken poorly or slowly? If hard to answer — that is the first work.

Who owns each of these decisions? If no clear owner — that is exactly the problem v2 will not auto-solve.

What is the data latency of current Subscriber 360 v1 (if any)? Often a critical gap.

Is the organisation ready for an operating model change, not only a tech change? Without that commitment, v2 fails.

What 12-15 month investment commitment is needed and is it there?

How SamaraliSoft can help

Subscriber 360 v2 Design — discovery of 5-10 commercial decisions to improve, back-design from decisions to data, process, ownership, tools, gap analysis from current state, operating model redesign around data, and a pilot on 1-2 decisions over 90-120 days before full rollout.

Related reading

• /en/insights/telecom-subscriber-intelligence-operating-model/ — operating model in depth
• /en/insights/telecom-event-driven/ — event-driven foundation
• /en/insights/telecom-nba/ — NBA in the action layer
• /en/insights/telecom-micro-segments/ — micro-segmentation

Sources

• Ministry of Digital Technologies — telecom infrastructure UZ
• Digital Government Portal — digital infrastructure UZ
• UzDaily — telecom market
• MNP.UZ — number portability