- Communications Sub-Module: Client
Overview
The Client Communication sub-module is the primary and default view of the Communications page. It displays all client communication packages in a single, consolidated table, presenting the complete relationship between mobile numbers, telecom companies, clients, ESIMs, and service packages.
This sub-module acts as the operational dashboard for monitoring, managing, and updating client communication services in real time.
URL:
https://user.bull36.com/dashboard/communication
Sub-Module Tab:
Client (default / active tab)
Purpose
The Client sub-module is designed to provide a single source of truth for all active and inactive client communication services. It enables users to:
-
View all assigned communication packages in one place
-
Monitor real-time connection and package status
-
Track ESIM and package updates via API
-
Manage client communication lifecycle statuses
-
Quickly refresh and validate communication data
Description
The Client sub-module aggregates data from multiple system tables and APIs to present a comprehensive, row-based view of every client communication package.
Each row represents a complete communication unit, consisting of:
-
A mobile phone number
-
A telecom company
-
A client
-
A communication status
-
An ESIM
-
A service package
-
Live API data
-
Refresh controls
This design allows operations teams to identify issues, validate connectivity, and take action without navigating between multiple modules.
Table Columns
1. Mobile Number
-
Displays the phone number from the
communication_phonetable -
Fully formatted international number (example:
919687263716) -
Each number is uniquely linked to a communication package
2. Company
-
Displays the telecom provider name
-
Pulled from
communication_company -
Localized company title shown when available
-
Examples: Cellcom, Pelephone, Partner
3. Client
-
Displays customer name from the
contactustable -
Linked using
cust_id -
Clickable for navigation to customer details (if enabled)
-
Displays
"-"if no client is assigned
4. Status
-
Visual badge representing current communication status
-
Clickable (except when disconnected)
Status Values:
-
Active (1): Green badge – service operational
-
Awaiting Payment (2): Disabled badge – payment pending
-
Disconnected (5): Red badge – no actions available
-
Force Active (6): Green badge – bypasses payment logic
5. ESIM / Package
ESIM Section
-
Displays assigned ESIM number
-
Shows status indicators:
-
Waiting for API update ❌ (
sim_status = 2) -
Failed to connect ❌ (
sim_status = 7)
-
-
Displays temporary ESIM when change is in progress
-
Shows previous ESIM history when applicable
Package Section
-
Package Name (display title)
-
API Package Identifier (
package_value) -
Package Description
-
Validity Period (days)
-
Price in ₪ (Israeli Shekel)
Package Status Indicators:
-
Waiting for API update ❌ (
package_status = 2) -
Failed to connect ❌ (
package_status = 7)
6. API Details
-
Displays parsed data from
phone_detail_api(JSON) -
Includes:
-
Data Usage (MB)
-
APN (network access point)
-
-
Displays
--when status is Disconnected
7. Refresh
-
Triggers a live API refresh for the phone number
-
Calls
phone_refreshendpoint -
Updates:
-
ESIM details
-
Package info
-
Usage data
-
-
Disabled (
--) when status is Disconnected
-
Connected Modules
-
Customers: Client linkage via
cust_id -
Phone: Phone inventory and API data
-
ESIM: ESIM lifecycle management
-
Package: Service package definitions
-
Projects/Missions: Operational logging
Summary
The Client Communication sub-module is the operational heart of the Communications system. It provides:
-
A unified view of all client communication services
-
Real-time API-driven status monitoring
-
Clear lifecycle and payment state tracking
-
Fast search, refresh, and update actions
-
Safe handling of disconnected services
This sub-module enables teams to monitor, manage, and maintain communication services efficiently, accurately, and at scale.
