Family balance sharing: help the parent top up the child the moment it runs out

Scenario

The child has the operator’s number. Balance runs out, the child cannot call home, pay for data, use the app. The parent learns about it when the child calls from someone else’s phone or via WhatsApp on the school Wi-Fi.

The parent opens the operator’s app, looks for how to top up for the child. The standard flow requires entering the child’s number, choosing the amount, going through 3DS. Five minutes of frustration. In the worst case — the parent fails to find how to do it, and the child stays without service the whole day.

Family balance sharing is the feature through which family members can instantly transfer funds from one account to another, without vouchers and USSD codes.

Triggers for the operator

A) Push to the parent on the child’s low balance (with the child’s / family setup consent): “Alisher’s balance is <500 UZS. Transfer 5k? [Yes]”.

B) Push to the child on low balance: “Ask a parent to top up? [Ask]”.

C) Discovery offer (ongoing): in the app the parent sees a block “Family features — set up the family plan to help each other in one tap”.

Family link setup

One-time setup: parent adds family members via an invite link. Child accepts on another device. The link is confirmed by both.

After setup all participants see a family section: balance, recent activity, transfer button.

Privacy boundaries: parent sees aggregate (balance, data usage), but not call history or message content. Child can opt out of monitoring.

Action

From the family section: tap on a family member → choose amount → confirm. No 3DS, because transfers within the family are verified together at setup.

Under the amount — quick amounts (1k, 5k, 10k) for frequent cases.

Push confirmation: child receives “Dad transferred 5k”.

What is measured

Family activation rate — what share of eligible accounts set up the family plan.

Average transfers per active family per month.

Balance reach time — how much faster the low-balance problem is solved with family vs without.

Customer satisfaction for both sides.

Stickiness — family accounts retain noticeably better than individual.

What not to do

Do not require full re-KYC when adding a family member. Use existing identity.

Do not limit family to the nuclear family — extended families (grandparents, aunts) work in practice.

Do not charge a transfer fee inside the family — that kills the feature.

Do not show the parent full call/message history without the child’s consent — that creates privacy issues, especially for teens.

How SamaraliSoft engages

Sprint Family Sharing Use Case — 6-8 weeks. Analysis of family relationship patterns, setup and transfer UX design, biller integration, pilot.

Related

• /en/insights/telecom-family-segments/ — family segments
• /en/solutions/telecom-cvm-platform/ — CVM
• /en/use-cases/telecom-topup-failure-recovery/ — top-up recovery
• /en/insights/telecom-account-hierarchy/ — account hierarchy