Which product boundaries should be set for identity, appointments, and support?
Cover identity, household or organization accounts, products or services, requests, cases, documents, appointments, orders or invoices as references, preferences, consent, notifications, and support. Treat identity, household or organization accounts, and appointments as one operated product boundary. A credible first release makes support observable and defines how exceptions involving notifications are recovered.
Best for: Teams planning Customer Account and Service Portal that need to agree on identity, appointments, and support before detailed scope.
The first release should connect identity to support and expose a clear recovery path for exceptions involving notifications.
Good fit / poor fit
Test whether identity and appointments require an operated product
This topic is specific enough when identity has durable state, appointments changes that state, and the team can own exceptions around notifications while observing support.
Good fit when
Customer Account and Service Portal needs a durable workflow connecting identity, appointments, and observable evidence for support.
People in the process participant role need a repeatable path from products or services through appointments.
The business operator must govern household or organization accounts and intervene when exceptions involve notifications.
Progress can be observed through support, not merely visits or screen activity.
Choose a narrower model when
An existing tool or simple information surface can already handle identity without owning its lifecycle.
household or organization accounts does not need separate permissions, history, or accountable state.
No operated workflow must connect products or services to appointments.
The team cannot yet name who resolves exceptions around notifications or what evidence is needed for support.
End-to-end workflow
Trace identity through appointments and evidence for support
Use one representative Customer Account and Service Portal journey. Keep household or organization accounts, exceptions around notifications, and manual operator work visible so the release boundary reflects the real product rather than an idealized happy path.
1
Frame Products or services
Process participant
A person in the process participant role enters with products or services and enough context to begin working with identity.
Business operator
The business operator function defines eligibility, ownership, and the initial state for identity.
Boundary question
Who may begin with products or services, and what makes identity ready?
2
Establish Household or organization...
Process participant
A person in the process participant role creates, selects, or confirms household or organization accounts before progressing.
Business operator
The business operator function validates permissions, quality, and lifecycle rules around household or organization accounts.
Boundary question
Which version of household or organization accounts is authoritative, and which changes need history or review?
3
Operate Appointments
Process participant
A person in the process participant role moves through appointments with visible state, next actions, and feedback.
Business operator
The business operator function observes orders or invoices as references, stalled work, and interventions that cannot be safely automated.
Boundary question
Which state changes prove progress through appointments, and where does orders or invoices as references branch?
4
Handle Notifications exceptions
Process participant
A person in the process participant role receives a clear recovery path when an exception involving notifications interrupts the expected journey.
Business operator
The business operator function resolves the exception, records the result, and captures evidence for support.
Boundary question
Who owns exceptions around notifications, and what evidence is needed for support?
First-release boundary
Scope the smallest release that makes support observable
The first release of Customer Account and Service Portal should connect products or services to support before expanding every variant of preferences, integration, automation, or reporting need.
Prove in the first release
Name one primary process participant segment and the exact role of identity in its journey.
Model the minimum state and permissions needed for household or organization accounts and products or services.
Implement one complete path through appointments, including the essential branch around orders or invoices as references.
Give the business operator a practical way to detect, inspect, and recover exceptions involving notifications.
Capture evidence of support so the team can continue, narrow, or revise the product boundary.
Hold until evidence justifies it
Additional audiences, variants, and advanced permissions around identity and household or organization accounts.
Automation, integrations, and optimization for preferences before the core workflow is reliable.
Sophisticated reporting or personalization beyond the evidence needed to verify support.
Decisions that materially change effort
The number of roles and permission boundaries controlling identity and household or organization accounts.
Lifecycle branches, approvals, reversals, and recovery paths across appointments and orders or invoices as references.
Operational exposure when exceptions involving notifications occur repeatedly or at scale.
External systems that create, change, or depend on products or services or preferences.
Audit, accessibility, availability, localization, and support expectations attached to support.
Trust, exceptions, and operations
Assign ownership for appointments, exceptions around notifications, and support
The interface for Customer Account and Service Portal is only the visible layer. The operating model must also govern identity, keep household or organization accounts trustworthy, and make recovery from exceptions involving notifications practical.
Ownership of Identity
The business operator function needs explicit rules for creating, changing, and retiring identity while keeping household or organization accounts consistent.
Who creates or approves identity, and which roles may change it?
What happens when identity and household or organization accounts disagree?
Which changes need history, notification, approval, export, or deletion controls?
Control of Appointments
Every important transition through appointments needs a visible owner, especially where orders or invoices as references changes the normal path.
Which states make progress through appointments visible to each role?
Where can orders or invoices as references be automated safely, and where is review required?
How is duplicated, abandoned, or contradictory work returned to a valid state?
Recovery for Notifications exceptions
A credible release makes exceptions involving notifications visible, gives the business operator a workable response, and preserves evidence for support.
What can the process participant do when an exception involving notifications occurs without contacting support?
Which evidence does the operator need to investigate and resolve exceptions around notifications?
Which signal demonstrates support without relying on vanity metrics?
Useful next steps
Turn the planning boundary into an evidence-backed first release
For Customer Account and Service Portal, use the Custom Web Application guide to verify the wider product model, then choose whether a quick range or a detailed plan is the useful next step. These links are limited to routes that advance this decision.
Plan partner organizations, users, tiers, onboarding, training, certifications, opportunities, deal registration, resources, marketing assets, support, performance, renewals, and partner administration.
Planning basis and review
A complete catalog brief with room for deeper research
This page is generated from the reviewed WebGrid opportunity catalogue and application-type decision model. The baseline was reviewed 17 August 2026; its next scheduled review is 17 February 2027.
This guide defines product responsibilities. Payment, tax, consumer, identity, privacy, and marketplace obligations depend on jurisdiction, provider configuration, contracts, and operating choices; verify them with the relevant specialists.