Skip to main content
Unetwork Club
Menu
Unetwork app running on a phone

Live Unetwork task

Caller ID CLI Testing

Earn rewards by verifying call delivery across live carrier networks using your device.

SIM required?
Yes
Answer required?
No
Reporting window
Within 24 hours
Phones supported
iOS and Android

What ULOs do

Verify that a real call reached your phone.

CLI means Caller Line Identification. In this task, Unetwork sends or assigns a real inbound test call to a ULO phone.

The task checks whether the call reached your device and whether the caller ID details can be reported in the app. That helps Unetwork understand how live carriers perform across real countries, networks, and devices.

Why caller ID tasks matter

Caller ID quality can change by:

  • Country
  • Mobile operator
  • Signal quality
  • Phone type
  • Call route
  • Time of day

Reports from ULO devices show what actually happens on live networks, not just in lab tests.

Operator requirements

You need an active SIM or eSIM that can receive calls.

The test call is delivered through your mobile carrier. If your SIM cannot receive normal incoming calls, the task cannot be verified.

Active SIM or eSIM

Required. Your phone must have a working number that can receive normal incoming calls.

Incoming calls enabled

Your line must be reachable on the mobile network. Wi-Fi alone cannot receive a test call.

Unetwork app notifications enabled

Allow notifications and background activity so you see task alerts and can report quickly.

Phone powered on

If the phone is off, the SIM is disabled, or the network is unavailable, the call may not be received.

Does Wi-Fi matter?

Wi-Fi helps keep the app connected, but the call itself comes through your mobile number. SIM or eSIM service is required.

iOS and Android support

Caller ID CLI Testing supports both iOS and Android. On iPhone, PoW may show offline because of iOS background limits, but CLI tasks can still be available.

Reporting workflow

Missed calls can still count.

CLI tasks include a reporting window so ULOs can submit the requested details after a call is received or missed. Use the task window shown in the Unetwork app.

  1. 1

    A test call is sent to your phone

    It looks like a normal incoming call. The task checks whether the call reaches your device.

  2. 2

    You do not need to answer

    Letting the phone ring or missing the call can still be valid. Follow the report flow in the app.

  3. 3

    Report within 24 hours

    If you miss the call, open the Unetwork app and submit the report within the reporting window.

  4. 4

    Submit what your phone shows

    Enter the call details exactly as shown. If something looks wrong, report that instead of guessing.

Task availability

Task volume can be different for each ULO.

This is normal. Calls are assigned based on customer requests, countries, mobile carriers, and active testing campaigns.

  • Your country and mobile carrier
  • Current customer demand
  • Regional coverage needs
  • Active testing campaigns

Why a call may be missed

These settings or line issues can stop your phone or app from seeing the event:

  • Phone powered off
  • Battery optimization blocking the app
  • Notifications disabled
  • Poor mobile signal
  • SIM inactive or out of balance
  • Manufacturer background restrictions

Good setup

Keep your phone reachable and ready to report.

  • Keep your phone powered on and charged
  • Keep an active SIM or eSIM in the phone
  • Make sure incoming calls work normally
  • Allow Unetwork notifications and background activity
  • Avoid strict battery-saving modes during testing
  • Submit reports within 24 hours
  • Keep the Unetwork app updated

Frequently asked questions

Fast answers for CLI operators.

Do I need to answer CLI calls?

No. The task checks whether a real call reaches your device. Answering is not required.

Can I participate on iPhone?

Yes. Caller ID CLI Testing supports iOS and Android. On iPhone, PoW may look offline because of background limits, but CLI tasks can still work.

Is Wi-Fi enough?

No. Wi-Fi can keep the app synced, but the call arrives over your mobile network. You need an active SIM or eSIM.

Can I use my everyday phone?

Yes. You can use your everyday phone if it has an active SIM or eSIM and can receive incoming calls.

Why do some operators receive more tasks?

Task volume varies by country, carrier, customer demand, and active campaigns. It is normal for ULOs to see different volumes.

If I miss a call, is the task automatically lost?

No. Missed calls may still be reportable. Open the app and submit within the 24-hour window shown for the task.

More details

The key points stay simple.

The CLI Deep Dive slides explain the same operator basics: use a real device, keep an active SIM, you do not need to answer, report within the window, and expect task volume to vary by location and carrier.

Slide 1 of 3

What is a CLI task?

A quick overview of Caller Line Identification and why real devices matter.

Open full-size
CLI Task Deep Dive introduction and explanation of what a CLI task is

Slide 2 of 3

Requirements and task availability

The active SIM, device readiness, and task distribution basics for ULOs.

Open full-size
CLI Task Deep Dive operator requirements and task availability guidance

Slide 3 of 3

Best practices and FAQs

Simple setup tips and answers about missed calls, iOS support, and rewards.

Open full-size
CLI Task Deep Dive best practices, frequently asked questions, and summary

Ready to participate

Keep your phone active and report what you receive.

Caller ID CLI Testing helps verify call delivery on real carrier networks while giving ULOs another way to earn rewards.

Get a License Code