Onboarding Reference — Service & Delivery

Project Management & Implementation Methodology

The starting point for anyone joining a Packet Fusion project team — new hires and existing employees alike. How projects get assigned, the six-phase methodology run on every UCaaS/CCaaS implementation, and where to find the templates, checklists, and escalation contacts you'll need.

Source Cloud PM Docs 2025–26 Owner Project Management Office Status Living document

This playbook is a practical guide for internal teams planning and executing cloud solution implementations. It outlines a standardized methodology that promotes consistency, efficiency, and alignment across projects, so each deployment meets both technical requirements and business objectives.

As more of our services move to the cloud — contact center operations and broader enterprise solutions alike — this methodology helps manage complexity, reduce risk, and deliver high-quality outcomes. It centers on discovery, design, deployment, testing, training, and post-launch support, built around collaboration and continuous improvement.

§0

Team & Roles

Every project is staffed across two practices — the Implementation Team, who deliver the migration, and the Client Success Practice, who own the relationship before and after.

Sr. Project Manager
Project planning & governance, stakeholder management, budget mgmt. & cost control, risk management.
Lead Implementation Engineer(s) — UCaaS / CCaaS
Technical design & architecture, platform config & customization, technical guidance, testing & user validation.
Lead Onsite Engineer
Device deployment & install, real-time troubleshooting, user & device onboarding, testing & validation of analog devices.
Client Success Manager (CSM)
Check-ins, escalations, license review, provider navigation, solution lifecycle optimization.
Solution Architect
Cost analysis, next-gen tech trends, provider recommendations, agreements & negotiation.
Technology Strategist
Optimization, solution impact assessment, technology roadmap, training.
RACI at kickoff. Roles are formally clarified using a RACI matrix — Responsible, Accountable, Consulted, Informed — for every deliverable, so there's no ambiguity about ownership.
§1

PM Assignment Process

What happens between an order landing and a customer meeting their Project Manager.

SLA timeline · business days
StepTaskSLAOwner
1PM / Implementation Engineer assignment1 day from order receiptPMO
2Project Job created in Great Plains (GP)1 day from assignmentOrders / AR
3Project Case created in CE1 day from assignmentPM
4Customer Intro / Welcome email2 days from assignmentPM
5Internal Kick-Off (project review)5 days from assignmentPM, IE, STA, SA, CSM
6Customer Kick-Off meeting3–5 days after internal KOPM

What the PM does at assignment

  • Creates a CE case and a SharePoint project folderKeeps documentation centralized from day one.
  • Creates a OneNote from the template folder, if applicable
  • Updates the SharePoint Project Status document to add the new project
  • Schedules the internal kick-off with the AE and IE before the customer KO
  • Schedules the IE to pull legacy data prior to customer KO, if applicable
  • Reviews and confirms/calculates labor price amount and hours; compares licenses from PSA to the cloud contract
  • Requests an access/distro email via Helpdesk (e.g. zm-customer@packetfusion.com)
§1

Project Handoff Document (PHD)

The internal record that travels with a project from Sales into Implementation. Every PM should be able to complete each section before kickoff.

Account & Contacts

  • Account name, primary contact name / phone / email
  • Provider Account Executive contact info

Licensing

  • UCaaS license counts by profile (common area, conference, operator, basic/advanced user)
  • CCaaS channels (voice, email, chat, SMS, fax) and license counts (agents, supervisors, admin)

Integrations

  • SaaS/LOB/CRM: Salesforce, Zendesk, ServiceNow, MS Dynamics 365, HubSpot, custom API
  • Other: Workforce Management, Quality Management, AI Expert Assist, ZRA, ZVA, Workvio

Deployment & Hardware

  • Implementation strategy: CloudPro, Advocacy, or CloudCare
  • Site count, phases/go-lives, sold hardware (phone models, ATAs, paging), onsite services
PH-01

Kickoff

Resource Assignment

  • Assign a dedicated Project Manager, UCaaS Engineer, and CCaaS Engineer.These roles cover leadership, technical delivery for the unified communications platform, and contact center solution design and deployment.
  • Clarify roles and responsibilities using a RACI matrix.Ensures there is no confusion over who is Responsible, Accountable, Consulted, and Informed for each deliverable.

Welcome Email

  • Introduction to the Project Team.Establishes rapport and clear points of contact.
  • Overview of project phases.Outlines the journey from kickoff through optimization so stakeholders know what to expect.
  • Key contacts and escalation points.Ensures issues can be resolved quickly without delays.
  • Initial steps and required actions from the customer.Sets the stage for early collaboration and avoids bottlenecks.

Kickoff Meetings

  • Internal alignment meeting.Ensures the internal team is aligned on scope, responsibilities, and priorities before engaging with the customer.
  • External kickoff with stakeholders — project goals, timelines & milestones, communication/reporting structure, risk identification.

Implementation Plan

  • Timeline and milestones.Provides a roadmap for tracking progress.
  • Resource assignments.Matches expertise to tasks for efficiency.
  • Dependency and risk assessments.Identifies prerequisites and potential delays.
  • Communication and reporting cadence.Ensures ongoing alignment with stakeholders.

Porting Documents & Stakeholder Meetings

  • Gather current carrier information and complete LOAs; validate porting requirements and timelines.
  • Weekly project meetings — status updates, upcoming tasks, issues/risks/mitigation.
  • Technical meetings scheduled immediately post-kickoff to validate technical requirements, confirm integrations (CRM, IVR, Ticketing), and establish security/compliance requirements.
  • Customer tenant invitation — initiate tenant setup with admin access for key stakeholders.
  • Awareness outreach — educate end-users on upcoming changes, timelines, and impact.

Sample Technical Data Discovery Agenda

  • Objectives — Implementation Engineer admin access to tenant
  • Current state assessment — network readiness, data source inventory, existing integrations, workflows/dependencies
  • Data requirements & compliance — retention, privacy, security, regulatory needs
  • Migration readiness — data quality/completeness, gaps or risks
  • Integration planning — key data flows, API/connector requirements
  • Next steps & deliverables — data maps, discovery findings, timeline/roles for follow-up
PH-02

Discovery

Network Assessment

  • Bandwidth analysis.Ensures capacity for additional UCaaS/CCaaS traffic.
  • Firewall configurations.Confirms access for required services.
  • Latency and QoS evaluations.Guarantees voice and video quality.

Call Flow Gathering & Design

  • Document existing IVR structures, routing paths, and queue configurations.
  • Design optimized call flows — efficiency & CX, skill-based routing, omnichannel (voice, email, chat, SMS).

Customized Plan & Communication

  • Tailor the implementation plan with a milestone-based approach and clearly defined deliverables/checkpoints.
  • Develop a communication plan — channels, update frequency, roles & responsibilities.

Database Freeze

  • Set a specific date to freeze current databases.Ensures data integrity during migration and minimizes disruption to operations.
PH-03

Implementation

  • Deploy tenant configurations.Activates the production environment.
  • Implement integrations (CRM, ticketing systems).Ensures systems work seamlessly together.
  • Execute user training — administrators, supervisors, end-users.Prepares teams to operate effectively.
  • Initiate data migration based on previously identified requirements.Moves required data into the new environment.
PH-04

Validation

  • System testing and User Acceptance Testing (UAT).Confirms the solution meets requirements.
  • Call quality and routing efficiency assessments.Ensures operational performance.
  • Integration performance evaluations.Verifies integrations are functional and reliable.
PH-05

Go-Live

  • Final data migration.Completes the move to production.
  • Real-time monitoring and immediate issue resolution.Provides stability during transition.
  • Dedicated support resources during the Go-Live period.Ensures prompt response to any issues.
PH-06

Optimization

  • Monitor system performance and user feedback.Identifies improvement opportunities.
  • Conduct operational reviews.Validates that processes are effective.
  • Identify opportunities for enhancements.Maximizes ROI from the solution.
  • Implement continuous improvement initiatives based on feedback and analytics.Keeps the system aligned with evolving needs.
  • Client Success & Support transition.Hands the account to the CSM for ongoing lifecycle management.
§8

Leadership Decks

Customer-facing presentations that pitch our value proposition — the CloudConnect platform and the Migration Assessment Tool that backs our Discovery phase.

Platform & tool demo CloudConnect & MAT Demo CloudConnect's four-module client visibility platform (Discovery, CloudPro, CloudSupport, Optimization) plus a full live walkthrough of the Migration Assessment Tool — automated PBX audit, feature-parity scoring, and cloud-readiness reporting. Download deck (.pptx, 28 MB)
This deck is account-agnostic — good as a leave-behind for prospects. Swap in a customer's own audit data before presenting the MAT sample section.
§8

PM Project Decks

Direct customer-facing presentations a PM builds and delivers for a specific project — kickoffs, migration methodology, governance, training, and support handoff.

Master template PM & Support Presentation — 2026 The full project deck: CloudConnect/MAT recap, migration philosophy (phased waves, no "big bang" cutover), governance & executive checkpoints, the six-phase migration methodology, change control process, site survey deliverables, training plan options, and the CloudSupport SLA matrix. Download deck (.pptx, 57 MB)
Includes a customer-ready version of our methodology (Kick Off → Discovery & Planning → Design & Build → Pilot Migration → Migration & Porting Waves → Decommission & Optimization) — the same phases as §PH-01–06 above, adapted for direct presentation. Also has a hospital-specific migration section (Code Blue, E911, telehealth) — skip that block for non-healthcare accounts.
§9

Templates & Checklists

The starting structure for every project — these are drawn from the Implementation Methodology Playbook. Check the Cloud PM Docs library for the live SharePoint copy.

Kickoff Meeting Agenda

  • Introductions
  • Project overview & goals
  • Roles and responsibilities
  • Implementation timeline & milestones
  • Communication plan & cadence
  • Risk identification
  • Next steps

Technical Discovery Agenda

  • Current state review
  • Network assessment discussion
  • Data & call flow review
  • Integration requirements
  • Compliance & security review
  • Migration planning
  • Next steps & action items

Call Flow Documentation

  • Call entry point
  • IVR menu options
  • Routing rules
  • Queues
  • Overflow & failover handling

UAT Checklist

  • Test inbound calls
  • Test outbound calls
  • Validate call routing rules
  • Test IVR menu navigation
  • Validate CRM integration
  • Confirm reporting accuracy
  • Document issues & resolutions

Go-Live Readiness Checklist

  • Finalized training for all users
  • Validated data migration
  • Confirmed integration functionality
  • Reviewed support escalation plan
  • Communication sent to all stakeholders
§9

Porting Guidelines

Average of 30 business days for completion. Global ports can take longer. Rejected orders restart the porting process at Day 1. Date changes and cancellations must occur more than 48 hours prior to the port date.

Not Supported

  • Expedites
  • Specific times (pre/post business hours)
  • Weekend porting
  • National holiday porting
  • After-hours porting

Requirements

  • Account and phone number(s) accurate, active, and in working condition
  • Customer Service Record (CSR) from the current provider, if available
  • Numbers written correctly and legible on the Letter of Authority (LOA)
  • Latest copy of the losing provider's bill
  • LOA signed by a person authorized with the losing provider
  • Project Business Requirements Document complete and signed

Local porting typically begins between 8–9am PT on the confirmed port date (timing varies by country). Some downtime may be experienced; call forwarding prior to the transfer date can help minimize it. The customer is responsible for testing and verifying all numbers after the port.

§9

Project Escalation Path

Know this before you need it. Escalate up the chain in order — don't skip a level unless the situation truly warrants it.

RoleWhen to escalate here
Sr. Project ManagerFirst point of contact for in-flight project issues.
Director — Gary ConnerIf the Sr. PM cannot resolve the issue within the set timeframe, or it's beyond their authority.
VP, Solutions & Services — Kevin SabonisIf the Director cannot mitigate the risk, or the issue poses a significant threat to the project's success or the business relationship. The VP's decision is final, with clear communication to all stakeholders.
After hours. During a pending project, administrators can leverage Packet Fusion Support for escalations or technical problems outside business hours — Support will handle the issue until the Project Team is back online.