Connect Verizon Carrier Sync

Use the Verizon carrier connection to sync mobile line information into FyneDesk Assets. This helps IT and operations teams track mobile lines next to the people and devices they support.

Handle carrier access carefully Carrier credentials can affect live services and billing. Only an authorized admin should connect this integration, and credentials should be entered only in FyneDesk's secure connection form.

Before you start

  • You need to be a FyneDesk Admin.
  • You need the Verizon carrier or ThingSpace credentials your organization uses for API access.
  • Decide who will review unmatched or ambiguous mobile lines after the first sync.
  • Decide whether line actions such as suspend or restore should stay off, or be enabled for authorized admins.

What the connection does

The connection syncs carrier line details into FyneDesk so mobile lines can be tracked as assets. When FyneDesk is not sure which person or asset a line belongs to, it places the line in a review queue instead of guessing.

Line actions are off by default. Keep them off unless your team is ready for FyneDesk admins to perform carrier actions that may affect service.

Step 1 — Open the Verizon connection page

  1. In FyneDesk, open Settings → Connections → Carrier / Verizon.
  2. Confirm you are using the correct FyneDesk workspace before entering any carrier credentials.
  3. Have your carrier credentials ready, but do not paste them anywhere outside the secure fields on this page.

Step 2 — Test and save the credentials

  1. Enter the required Verizon carrier credentials in the secure fields.
  2. Click Test connection. FyneDesk checks whether the credentials work before they are saved.
  3. If the test succeeds, click Save connection.
  4. If the test fails, re-check the credentials with your Verizon admin before trying again.
Why testing matters FyneDesk requires a successful test before saving so your workspace does not store credentials that cannot sync.

Step 3 — Review synced lines

  1. After saving, let the first sync run.
  2. Open the pending review queue on the Carrier / Verizon page if it appears.
  3. Match each line to the correct person, device, or asset when FyneDesk needs confirmation.
  4. Open Assets to confirm the synced mobile line records look correct.

Optional — Carrier callbacks

If Verizon asks for callback details, copy the callback URL shown inside FyneDesk and generate the callback secret from the Carrier / Verizon connection page. The secret is shown once, so store it in your organization's approved password manager.

Do not publish callback URLs or callback secrets in public documentation, screenshots, tickets, or chat messages.

Optional — Line actions

When the connection is active, FyneDesk may show a setting for carrier line actions such as suspend or restore. Leave this off until your team has agreed who is allowed to use it and how approvals should work.

Before enabling line actions A suspend or restore action can affect a real phone line. Make sure your internal process is clear before turning this on.

Manage or disconnect

  • Rotate credentials by entering the new values, testing, and saving.
  • Review last sync status on the Carrier / Verizon page if assets look stale.
  • Disconnect if your team no longer wants FyneDesk to sync carrier data.

Troubleshooting

The test fails. Check for copied spaces, expired credentials, wrong account access, or carrier-side API restrictions.

Lines are missing. Confirm the line exists in the carrier account connected to FyneDesk and that the sync has completed.

A line is in pending review. FyneDesk is asking an admin to confirm the match. Open the review queue and choose the correct person or asset.

The callback secret was lost. Generate a new secret in FyneDesk and update it with Verizon. Treat the old secret as no longer usable.

Privacy & trust

FyneDesk stores carrier credentials securely and does not show them back after saving. Keep carrier data access limited to admins who need it, and avoid putting phone numbers, account identifiers, callback secrets, or credentials into screenshots or support emails unless support specifically asks for a redacted example.