1. Scenario overview
SIM lookup is finding one SIM, or a batch, by the conditions you set. SIM status monitoring is the fleet dashboard and the exception alerts. Support, operations, and the business team need the status, usage, plan, and ownership of a specific SIM. Type an ICCID or MSISDN, or filter by project or customer. Results stay in sync with the operator, and a batch can be queried and exported.
A web console and a REST API are both available. People look up a SIM in the console. Systems use the API. Monitoring is watching the fleet. This page retrieves one SIM, or a batch, when you need it.
2. Core capabilities
Exact lookup and filters
ICCID: a full or partial ICCID finds one SIM, which is what support uses on a fault report and what operations uses on a single-SIM issue. MSISDN: search by the mobile number when that is what the caller gives you. Filters: combine project, customer, ownership, agent, device type, activation time, and plan type, and export the result for a batch review.
What the result shows
Status (not activated, active, suspended, or cancelled), the current plan, this month’s usage and what remains, the project and customer it belongs to, activation time, and last-used time. One refresh pulls the latest from the operator.
Batch lookup and export
Upload an ICCID list or choose filters, pull the details in bulk, and export Excel or CSV. That is the path for reconciliation, a stock count, or a migration.
REST API and security
Query by ICCID, MSISDN, project, and similar dimensions, so support systems, ticketing, and your own systems can call it. The API supports authentication, rate limits, and masking. Sensitive fields, such as a full ICCID or a mobile number, can be masked by permission.
3. Lookup and status monitoring
The two jobs stay separate. The differences:
| Dimension | SIM lookup | SIM status monitoring |
|---|---|---|
| How you use it | On demand: enter conditions and retrieve one SIM or a batch | A dashboard you watch: the fleet by project or customer |
| Typical use | Support lookups, operations troubleshooting, reconciliation and stock counts | Highlighted exceptions, alert rules, a status overview |
| What you get | One SIM’s detail, or a batch export | A dashboard list and alert notices |
| Relation to SIM management | Search by condition | Fleet status and alerts |
A lookup does not bill, warn, or suspend and resume. It only retrieves information. With SIM management, management supplies groups, tags, and batch actions, and lookup supplies search by condition.
4. Where teams use it
- Support lookup: A caller gives a SIM number or a mobile number. Support types it in and reads status, usage, and plan.
- Operations troubleshooting: When a device misbehaves, look up the SIM number and confirm status and usage.
- System integration: Support and ticketing call the API so the lookup and the ticket stay linked.
- Reconciliation and stock counts: A batch export is the input for reconciliation and analysis.
5. What changes in daily operations
Lookup is how support, operations, and the business answer a high volume of “which SIM is this?” Live sync keeps the answer current. The API connects support and ticketing. Batch export feeds reconciliation and analysis. Masking hides sensitive fields by permission.
6. How to put it in place
Use one lookup entrance and one permission model, and mask sensitive fields. Connect the API to support and ticketing so a lookup can start from a ticket. Batch lookup exports for reconciliation and stock counts. Exact lookup covers ICCID and MSISDN, and filters combine. Results stay in sync with the operator, and one refresh pulls the latest. The web console and the API cover a person at the desk and a system calling in.