Import numbers into the local pool
After selecting a number file, App B imports recognized numbers into a local data pool. The interface can show file name, mode, total rows, extracted count, and duplicate status.
The import area should support both click-to-select and drag-and-drop so users can process TXT or CSV files quickly.
Dedupe before extraction
If the same number appears in multiple files, direct package export may deliver duplicates. Dedupe first, then review available count before random extraction.
A deduped pool is better for fair distribution and reduces repeated handling by the team.
Set random extraction count
Random extraction is useful when the user needs a fixed count, such as 5,000 numbers per run. The app should show the available data count and prevent values above the limit.
If authorization fails or the network is disconnected, the app should show a login, renewal, or reconnect prompt instead of silently failing.
Package export and remaining export
Package export creates multiple TXT files by package size. Remaining export keeps the unused data for future processing.
TXT should be the default because many delivery workflows only need plain phone numbers. CSV is useful when additional fields are needed.
Authorization and subscription
App B uses the same account system as App A. Advanced access unlocks all functions inside App B. If an account has Top from App A, App B can also display the Top status.
Heartbeat checks should be spaced reasonably. When disconnected, users should be asked to reconnect and check network, VPN, or external browser access.
FAQ
Does App B require Python installation?
No. The packaged portable build should not require users to install the Python runtime.
Which export format is preferred?
TXT is preferred for plain number delivery. CSV is useful when fields or spreadsheet processing are needed.
Can features be used without login?
They should not. Authorized features should verify account status and show login or renewal prompts when needed.