Common issues

Start with the screen showing the failure. Keep the original conversation or card, check the relevant connection and status, then retry once when safe.

Open it

On desktop or mobile, inspect the failed conversation or card first. Find account, connection, and help controls under Settings; receipts are under Home → History.

I cannot sign in or I am on the waitlist

Use the same sign-in method and email as before. Check spam for a fresh email verification message. If access is pending, follow the waitlist or invite screen shown; reinstalling does not create access. Contact support from the original account email if you are stuck.

The mobile app is locked

Use the unlock button and complete the phone's face, fingerprint, or passcode check. A cancelled check does not unlock Zinley. On supported builds, manage the local app lock under Settings → Account → Sign-in & security after unlocking. The lock is for this account on this phone; it is separate from your sign-in method. See Account and privacy.

I cannot find an old Configure setting

Current apps organize settings under Settings. Models are under Model, service connections under Apps & accounts, messaging under Chat apps, and approvals under How your agent works. The interface tour maps the current controls.

A task is waiting or a card will not accept my answer

Read Action Center → For you → Needs you. An expired or changed proposal needs a fresh review. A failed answer can be retried from the existing card. Working or waiting on another person is different from waiting for your approval. See Action Center.

Chat says Still working or No reply yet

On mobile, Still working… can remain while a detached server turn finishes and saves its reply. If No reply yet. appears, choose Reload to fetch saved history. Preserve the original conversation. Reload does not rerun the request; check the result and any external receipt before deciding whether a retry is needed.

Email or a call did not go through

For email, confirm the address, sender access, reply setting, and History. For calls, check the line status, primary number, block list, and credits. Do not retry a consequential send until you know whether the first attempt completed. See email troubleshooting or phone receipts.

A computer is unavailable or the wrong one is selected

Open the desktop app on the intended computer, sign into the same account, and review Settings → Devices. Choose the computer’s Work here action, or use Work on in mobile Chat. Powered-off hardware cannot run local work. A last-seen timestamp is not proof that a task ran. Follow cross-device troubleshooting.

The model changed, is locked, or did not save

Open Settings → Model. Current desktop and mobile apps use one saved account preference. Check the live catalog and plan, then wait for Saved or use Retry. Specialist media or voice steps may use separate compatible models. See Model and processing speed.

Credits ran out or I see repeated charges

Open Account → Plan & billing to inspect the current pools and activity. Credits reflect AI and tool usage; live calls can also have a minimum based on duration. Media, calls, long context, tools, and repeated jobs can cost more than a short answer.

Check the charge type and any automatic wallet top-up or Extra Usage settings separately. Stopping future automatic purchases does not reverse a completed charge. Read Billing and usage, then contact support if the ledger does not explain the receipt.

Health or News looks empty or out of date

For Health, check the selected person, source permissions, last sync, and whether the phone has recent readings. For News, check setup, edition status, schedule, and filters. An unavailable source is different from an empty result. Use Health setup or News preferences.

History is shorter than expected

Check the filter, source-load warning, and plan visibility window. Open original messages or transcripts where available. History's call and email window does not define every type of Chat retention. Do not treat a failed read as proof no record exists.

The problem remains

Use the support playbook to capture the exact failing step. Report reproducible faults through Report a problem; use private support for account, billing, or access problems.