Using the LineSquire mobile app

The native app is being evaluated through private internal and sideload test builds. It is not presented as a public store release. Keep the browser subscriber console available while a device or build has not completed the physical-device checks.

An installed build proves only that the package opened on that device. It does not prove notification delivery, payment completion, passkey association, or store approval.

The five main tabs are Today, Messages, Calls, Tasks, and More. More opens people, your agent, connections, usage, account settings, security, privacy, and Support.

A saved screen can show older information when the network is unavailable. Check the visible refresh state before acting; the app blocks changes that cannot be confirmed by LineSquire.

Messages contains caller follow-ups. Support contains conversations with the LineSquire support team. A notification uses generic wording and asks the app to refresh; it does not carry the conversation text as proof of a new item.

Selective import is the default. Full contact sync is a separate, explicit choice and reads names and phone numbers only. Turning sync off does not delete people already saved in LineSquire, and a contact missing from the phone is marked for review instead of being deleted automatically.

Hosted top-ups and account billing pages are limited to approved internal or sideload builds. A public-store build keeps hosted digital top-ups unavailable until the separate store-policy review is complete.

After returning from a hosted billing page, wait for the app to reload the current balance or subscription state. A browser return by itself does not prove a payment or account change succeeded.

Sensitive actions can ask for Face ID, Touch ID, biometrics, or the device passcode. Cancellation submits nothing. A passkey appears as connected only after LineSquire stores the completed registration; email-code recovery remains available.

Use Privacy in Settings to request an account export or deletion. Removing the app from a phone does not delete the LineSquire account or its data.

Open the current request, review the call and requested action, then confirm the exact response shown. Take Call rings only the verified phone destination; opening the screen or tapping a notification does not connect the call.

The app can explain the notification, channel, background-data, battery, and Focus settings reported by the operating system. Change only the setting you intend, then send a generic test notification and wait for the stored receipt state.

Acceptance by a notification service is different from receipt by the device. Network conditions, Focus, Data Saver, Doze, battery settings, and device software can still delay or suppress an alert, so keep time-sensitive call rules and fallback contact methods current.