Data Pool Management

Step 1 — Manage Services: Data Pool Section

Manage Services page with Data Pool tab selected

Description

The user logs into the Enterprise Portal and navigates to Manage Services from the top navigation. The page shows the enterprise account context (company name, user name, IT account number) and two panels: Account Self Service (with action tiles like Activate New Line, Buy Product, etc.) and Account Service Request.

Below the account-level panels, a tab bar provides access to: Mobile, M2M, Fixed Line, and Data Pool. The user clicks the Data Pool tab.

Under the Data Pool tab, two sections appear:

• Self Service — action tiles: Buy Plan, Add Dependent, Remove Dependent
• Service Request — for raising Data Pool specific SRs

Below these, four history tabs are shown: OPEN SRs (count), CLOSED SRs (count), SELF SERVICE HISTORY, and TRANSACTION HISTORY, with a search bar and date-range filter.

Fields

Validations

• User must be authenticated and linked to an enterprise IT account to access this page.
• Data Pool tab should only appear if the enterprise account has Data Pool feature enabled.
• SR counts (Open/Closed) must reflect real-time data.

Step 2 — Buy Data Pool Plan: Choose Master Number

Step 1 of Buy Data Pool Plan — Master Number selection with type-ahead search

Description

User clicks Buy Plan from the Data Pool self-service section. The system opens the "Buy Data Pool Plan" page. The first step asks the user to choose a Master Number.

As the user types in the search field, matching master numbers appear in a dropdown (type-ahead). After selecting a number and clicking Continue, the "YOUR SELECTION" panel on the right updates to show the selected master mobile number.

Fields

Validations

• Master Number is mandatory. Continue button stays disabled until a valid number is selected.
• Only master numbers belonging to the logged-in enterprise account should appear in the dropdown.
• If a master number already has an active data pool, the system should indicate this (or restrict re-purchase depending on business rules).

Step 3 — Select Data Plan

Step 2 — Available plans displayed with plan code, name, price, description, and validity

Plan selected (Super Plus 350) — YOUR SELECTION panel updated with product details

Description

After selecting the master number, Step 2 loads a list of available data plans. Each plan shows its Plan Code, Plan Name with price, Plan Description (data, SMS, voice details), and Validity period. The user can select only one plan at a time via radio buttons.

On selecting a plan, the YOUR SELECTION panel updates to show the Master Mobile Number and Product Details (plan name, price, description, validity).

Pagination is available if plans exceed the page size (e.g., "Showing 1 to 10 of 30 rows" with Prev/Next controls).

Fields

Validations

• Only one plan can be selected at a time.
• The Continue button (at page bottom) is enabled only after a plan is selected.
• Plans with long descriptions should show a "read more" expandable link.
• Plan list is fetched from backend API; if no plans are available, show an appropriate message.

Step 4 — Plan Confirmation & Security Deposit Prompt

Plan Selected modal — shows plan details, security deposit amount, and payment/waiver options

Description

After selecting a plan and clicking Continue, a confirmation modal appears titled "Plan Selected". It displays the plan name, plan details (data, validity, price), and the Security deposit requirement amount.

The user has two paths from here:

1. Pay Now — Click the "Pay KES XXX" button to proceed to the payment gateway.
2. Request Waiver — Click the link "Don't want to pay security deposit. Contact our customer support team" to raise a Security Deposit Service Request instead (see Step 8).

Clicking "Cancel" returns the user to the plan selection screen.

Fields

Validations

• Security deposit amount is calculated by the backend based on account outstanding amount, overdue amount, and plan price.
• The Pay button must clearly show the exact amount to be charged.
• Modal should not be dismissible by clicking outside (only via Cancel or Pay action).

Step 5 — Payment Gateway

Payment page — Smartcash selected, plan purchase summary on right

Description

User is redirected to the Airtel payment gateway. The page title is "How will you pay". Payment methods are listed as tabs on the left side: Smartcash, Credit / Debit Card.

For Smartcash, the user provides their email (for receipt) and phone number (pre-filled, used for OTP). A Plan Purchase summary on the right shows the plan name, description, and total amount.

The user clicks PROCEED to initiate payment or CANCEL to go back.

Fields

Validations

• Email must be a valid email format.
• Phone number must be pre-filled and non-editable (or editable with validation for valid Airtel number).
• The user is warned: "Please ensure sufficient balance to avoid failure."
• All payment data must be transmitted over HTTPS/TLS.
• PROCEED button should be disabled until all mandatory fields are filled.

Step 6 — Payment: PIN Entry, Success & Failure

SmartCash PIN entry modal — leads to successful or unsuccessful transaction

Description

After clicking PROCEED with Smartcash, a PIN entry modal appears titled "Enter SmartCash PIN". The user enters their 4-digit PIN in masked input fields.

Two outcomes:

1. Successful transaction — redirects to the Payment Success page (Step 7).
2. Unsuccessful transaction — displays an error. The user can retry or return to the Data Pool section.

Fields

Validations

• PIN input must be masked (dots/asterisks) for security.
• PIN must be exactly 4 digits.
• On failure, a clear error message must be shown with retry option.
• Maximum retry attempts should be enforced (backend-driven).
• Session timeout should apply if PIN entry is left idle.

Step 7 — Payment Success Confirmation

Payment Successful page with transaction summary and provisioning indicator

Description

On successful payment, the user sees a confirmation page with:

• "Thank You / Payment Successful!" message.
• A note: "We have received your payment, please wait till we provision the plan for your account." with a loading spinner indicating provisioning is in progress.
• A Payment Summary panel showing the transaction confirmation for the MSISDN, Transaction ID, and date/time.
• A "BACK TO DATA POOL" link to return to the Data Pool section.

After successful payment and provisioning, the user can proceed to add dependents to the data pool.

Fields

Validations

• Transaction ID must be generated and displayed immediately upon payment confirmation.
• The provisioning spinner should remain until backend confirms plan activation (or timeout with appropriate message).
• The transaction must be logged in the Transaction History tab for future reference.

Step 8 — Security Deposit Service Request (Alternate Path)

Security Deposit SR form — pre-filled account and plan details with waiver reason input

Description

If the user does not want to pay the security deposit upfront, they click the "Contact our customer support team" link from the Plan Confirmation modal (Step 4). This opens a Security Deposit service request form.

Most fields are pre-filled and read-only. The user only needs to provide the Reason for security deposit waiver and click Submit. A Service Request is created with status "Pending" and can be tracked on the SR detail page (Step 11).

Fields

Validations

• "Reason for security deposit waiver" is mandatory. Submit button should remain disabled if empty.
• All pre-filled fields must be read-only and not editable by the user.
• On Submit, a Service Request is created with SR Type = "Security deposit" and status = "Pending".
• User should receive a confirmation with the SR number after submission.
• Cancel button closes the form without creating an SR.

Step 9 — Add / Remove Dependents

Description

Once a Data Pool plan is active, the user can manage dependent numbers from the Data Pool section. Two actions are available from the Self Service panel: Add Dependent and Remove Dependent. Each supports both individual and bulk operations.

9a. Add Dependent — Individual

User clicks "Add Dependent" and enters a single mobile number to add to the data pool.

9b. Add Dependent — Bulk Upload

Visible as "Add Dependents Number/Upload Bulk" in the Buy Plan flow (Step 3). User uploads a file (CSV/Excel) containing multiple dependent numbers.

9c. Remove Dependent — Individual

User clicks "Remove Dependent" and selects a number currently in the pool to remove. A confirmation dialog appears before execution.

9d. Remove Dependent — Bulk

User uploads a file (CSV/Excel) of numbers to remove in bulk.

Fields

Validations

• Dependent number must be a valid Airtel number.
• Dependent must not already belong to another active data pool (for add).
• There is a maximum dependent limit per pool (e.g., 50). If the limit is reached, adding more should be blocked with a message.
• Bulk upload must validate all numbers and report success/failure count.
• Bulk file must be CSV or Excel format. Reject other formats with an error message.
• Removal requires a confirmation prompt before execution.
• All add/remove operations (individual and bulk) must be logged in the Self Service History tab for status tracking.

Step 10 — Data Pool Deactivation

Deactivation request raised — confirmation with SR number, accessible from the Actions menu

Description

On the Data Pool listing page, each active pool entry shows the master number, line type (Postpaid), status (Active), plan details, data usage, expiry information, and dependent count (e.g., "10/50 numbers added").

An Actions menu (three-dot/kebab icon) is available per entry with options: Buy Plan, Add Dependents, Remove Dependents, and Deactivate Data Pool.

Clicking "Deactivate Data Pool" immediately raises a Service Request. A confirmation dialog appears showing:

• "Deactivation request raised" with a green checkmark.
• Message: "Your request to deactivate data pool master line has been submitted."
• The assigned SR Number (e.g., "SR No: 12340513").
• A "Close" button to dismiss the dialog.

A "Download Dependents" button is also available on the page to export the current list of dependent numbers.

Fields

Validations

• Deactivation is not immediate — it always creates a Service Request for back-office processing.
• SR number must be generated and shown in the confirmation dialog.
• The deactivation SR must appear in the Open SRs tab and be trackable on the SR detail page.
• Only active data pools should show the "Deactivate Data Pool" option in the actions menu.

Step 11 — Service Request Detail Page

Service Request detail page — Security Deposit SR showing status, creator, remarks, and attachments

Description

The user can view details of any Service Request (Security Deposit, Deactivation, etc.) by clicking the SR from the Open SRs or Closed SRs tab. The SR detail page shows all relevant information about the request.

Breadcrumb navigation is available: Dashboard > Manage Services > Contact Us.

Fields

Validations

• All fields are read-only on the SR detail page.
• Status badge color should reflect the current state (e.g., orange for Pending, green for Resolved, red for Rejected).
• Attachments must be downloadable by clicking the file name/icon.
• Breadcrumb navigation must be functional for easy back-navigation.
• SR detail page must be accessible from both the Open SRs and Closed SRs tabs.

End of Document
Data Pool Management — Requirement Document — Version 1.0 — 13 April 2026