Communications Sub-Module: Phone
 

Overview
 

The Phone sub-module is responsible for managing all mobile phone numbers within the Communications system. It provides full lifecycle control over phone numbers, including creation, verification, API synchronization, suspension handling, refresh operations, and bulk imports.
 

This module is deeply integrated with external telecom provider APIs, allowing the system to validate phone numbers, retrieve live usage data, manage suspension states, and keep phone information synchronized in real time.
 

URL:

https://user.bull36.com/dashboard/communication/phone
 

Sub-Module Tab:

Phone
 

Purpose & Scope
 

The Phone sub-module acts as the single source of truth for phone numbers used across the Communications system. Every phone number that appears in Client Communication packages, ESIM assignments, or Package matching flows originates from this module.
 

Its scope includes:
 

• Managing unassigned phone numbers

• Verifying phone numbers via external APIs

• Tracking suspension and activation status

• Synchronizing live telecom data

• Enabling bulk onboarding through Excel/CSV imports
   

Functional Description
 

The Phone sub-module enables users to:
 

• Add new phone numbers with automatic API verification

• Edit existing phone records

• Delete unused phone numbers

• Suspend or unsuspend phone numbers via telecom APIs

• Refresh phone data to retrieve the latest usage and package details

• View real-time API information such as ICCID, data usage, APN, and package

• Import large volumes of phone numbers using Excel or CSV files
   

The system ensures that every phone number is validated, synchronized, and accurately represented before it is used elsewhere in the platform.


 

Table Layout & Columns
 

1. Mobile Number
 

• Displays the full phone number

• Stored in communication_phone.phone_number

• Example format: 919687263716
   

2. Company
 

• Displays the telecom provider associated with the phone

• Loaded from communication_company

• Supports localization
   

• Examples:
   

  • Cellcom

  • Pelephone

  • Partner
     

3. Status
 

• Indicates whether the phone is currently active or suspended

• Derived from the suspended column

• States:

  • Active: Phone is operational (suspended = 0)

  • Suspended: Phone is blocked by provider (suspended = 1)

• Clicking the status opens the Change Status modal
   

4. API Details
 

• Displays parsed data from phone_detail_api JSON
   

• Includes:
   

  • Data Usage: Total usage in MB

  • APN: Network access point

  • ICCID: SIM identifier

  • Package: Current telecom package
     

• Data is updated automatically on refresh or status change
   

5. Refresh
 

• Allows users to manually refresh phone data from the external API

• Calls the phone_refresh endpoint

• Updates usage, package, ICCID, and suspension status

• Displays success or error messages based on API response
   

6. Actions
 

• Edit: Opens phone edit modal

• Delete: Removes phone after confirmation
  
  
   

  Import Functionality
   

  Bulk Upload Support
   

• Excel (.xls, .xlsx)

• CSV (.csv)
   

• Import Flow:
   

• Upload file

• Map columns

• Validate data

• Insert phone records

• Refresh list
   

• ---

  Connected Modules
   

• Client Communication: Phones assigned to clients

• Company: Provider selection

• Package: API package matching
   

• ---

  Summary
   

  The Phone sub-module delivers:
   

• Complete phone number lifecycle management

• Reliable external API integration

• Real-time status and usage synchronization

• Robust suspension and refresh workflows

• Bulk onboarding via Excel/CSV

• Secure, organization-aware access control
   

• This module forms the foundation of all telecom-related operations in the Communications system, ensuring accuracy, consistency, and real-time visibility of phone data across the platform.