On Boarding Steps (Prime Customer Self-Service Portal)
Go-live essentials for Prime Customer Self-Service Portal. Start with customer deliverables, then four scopes.
Top customer deliverables
Prio | Deliverable | Owner (customer) |
|---|---|---|
1 | Portal access model — customer login / password flow, portal URL, SSO or reset policy | IT / Care |
2 | Billing visibility — which invoices, CDRs, and payment methods customers may see/change | Billing / Legal |
3 | Support workflows — ticket and modem-move request routing | Care / Ops |
4 | Upgrade catalogue — eligible Internet, VoIP, and TV upgrades with prices / rules | Product / Sales |
5 | Branding & owners — portal branding, customer texts, production administrators | Marketing / IT |
Scopes
# | Scope | Goal |
|---|---|---|
1 | Access & enable | Test customer can log in |
2 | Main decisions | Visible data and allowed actions agreed |
3 | Initial wiring | Billing, tickets, products, admin handoff connected |
4 | Acceptance | Customer journey signed off |
1. Access & enable
NMS Prime brings | Customer brings |
|---|---|
CCC package and default portal | Portal domain / certificate, customer login policy |
Standard portal roles | Named admins / SSO groups |
Decide: password reset and customer activation process.
2. Main decisions
NMS Prime brings | Customer brings |
|---|---|
Standard invoice, CDR, address, payment, ticket, move, and upgrade options | Which actions are enabled; legal / consent wording |
Default portal texts | Branding and customer-facing wording |
Decide:
3. Initial wiring
NMS Prime brings | Customer brings |
|---|---|
Integration guidance | Test customers and representative contracts |
Admin handoff | Billing, ticket-routing, and eligible-product owners |
Decide: test customer(s) covering billing, VoIP, TV, and upgrade cases.
4. Acceptance
NMS Prime brings | Customer brings |
|---|---|
Care + billing + product testers |
Decide: which rows block go-live? Recommend login, invoices, address change, and admin handoff; add any enabled optional journeys.