Resource Workflow
Search the knowledge base first from the admin console. If the article resolves the question, the case closes without a ticket. If a ticket is required, open it from the Support tab while signed into My Verizon so that the master-account number, tier and admin scope attach automatically. Severity-one outages also hit 1-866-477-3929 in parallel. Platinum and Diamond accounts use the named account-team liaison for the relationship cadence rather than per-case support.
Self-Service Knowledge Base
The Verizon knowledge base covers every admin workflow across wireless, Fios, 5G, IoT and unified-communications products. Verizon articles walk through common admin tasks such as adding a wireless line, uploading a tax-exempt certificate, swapping a device on an existing line, porting a number in or out, provisioning a Verizon Fios circuit and enabling MFA on a secondary admin. Each Verizon article links to the specific admin-console surface where the workflow completes, with screenshots scoped to the current Verizon portal theme. Verizon refreshes screenshots every release cycle so the article tracks the live console.
Search is scoped against the signed-in master's subscribed products. A master that does not hold IoT lines will not see IoT articles surface in the default result set, which reduces noise and shortens time-to-article. A universal toggle reveals articles outside the subscribed-product set for admins researching an upcoming migration. The result set is ranked by article freshness, average resolution-rate and cross-admin vote score.
Deep-link coverage is intentional. A knowledge-base article about MFA enrolment links directly to the My Verizon login surface and the admin-profile MFA section. An article about business-account enrolment links to the enrolment flow. The goal is that a single click from article to action closes the loop without an admin having to navigate the console from the top.
Trouble-Ticket Workflow
Verizon tickets open from the Support tab inside the admin console. An authenticated Verizon ticket carries the master-account number, admin scope, product line and affected circuit or line identifier, which shortens Verizon triage. The Verizon severity picker sets the SLA clock: severity-one (service down), severity-two (degraded), severity-three (intermittent) and severity-four (information request). Severity-one Verizon tickets trigger the on-call rotation inside the response organisation and also post to the Verizon 24/7 business line. Verizon sev-one escalations also page the regional liaison. Verizon tracks mean-time-to-restore per severity tier.
Ticket history is visible inside the admin console with every update, attachment and owner-change logged. Admins with ticketing-scope permissions can comment on the case, attach packet captures or trace files and close the ticket once resolved. Customer-satisfaction surveys post on resolution and feed back into the annual vendor-scorecard exchange that Mid-Market and higher tier accounts run with their account team.
Escalation Paths & Account-Team Liaison
Escalation moves through the Verizon tier structure in predictable steps. A stalled tier-one Verizon ticket escalates to a senior Verizon engineer within the response organisation; from there to the account-team liaison for Platinum and Diamond; from there to executive escalation for severity-one cases that exceed their restoration target. Every step writes to the Verizon ticket history and is visible inside the admin console, which means the Verizon customer always knows which queue currently owns the case. Verizon ticket ownership always names an engineer rather than a queue, which matters when a sev-one case needs a call-back. Verizon retires the ticket only when the customer acknowledges resolution.
Platinum accounts hold a named account-team liaison who runs the relationship cadence including quarterly business reviews, capacity-planning sessions, upcoming-change walkthroughs and service-improvement discussions. Diamond accounts add on-site support commitments and an executive sponsor. Liaison work is distinct from per-case support: the liaison does not answer sev-one tickets directly but does ensure the response organisation is resourced to meet the SLA.
Proactive Notifications & Status Updates
Verizon admins subscribe any admin contact to region-scoped outage notifications inside the admin profile. Verizon notifications post to email and SMS in parallel and include the impact window, affected Verizon circuits or cell sectors and the current restoration estimate. Verizon planned-maintenance windows also post through the same channel with a 14-day lead time. Verizon status-page content is replicated on the My Verizon status widget so that a signed-in Verizon admin sees the same picture as the Verizon notification subscription delivers. Verizon publishes an RSS feed of the status page for ingestion into downstream monitoring. Verizon also supports webhook delivery on Platinum and Diamond tiers.
Notifications respect the admin's role-scope. A finance admin who is not on the network-ops distribution will not receive circuit-outage pings; a regional admin scoped to a single geography will only receive alerts inside that footprint. The per-admin subscription is granular by product (wireless, Fios, 5G, voice, IoT), by geography and by severity level.
Issue Routing Reference
Canonical channel and SLA per issue category. Start times are business-hour response for non-severity-one cases.
| Issue Category | Channel | SLA |
|---|---|---|
| Wireless line down | Admin console ticket → 1-866-477-3929 | Sev-1: 1 hour response |
| Fios circuit outage | Admin console ticket → 1-866-477-3929 | Sev-1: 1 hour response, 4 hour restore target |
| Billing dispute | Billing portal dispute form | Net-30 dispute window from invoice |
| MFA reset / admin lockout | Business-care queue | Same business day |
| Port-in / port-out | Admin console port wizard | 2-4 business days typical |
| Platinum/Diamond escalation | Named account-team liaison | 30 min sev-1 / 1 hour sev-2 |