A client asking a question about an active service needs a different response from a client expressing interest in something new. When both messages arrive in the same inbox, your team must identify the service, determine the intent, and find the right owner before work can begin.
A client service catalog gives those situations separate, structured entry points. It also gives clients a current view of what your business offers inside the portal they already use for work.
Define the catalog around the client relationship
A client service catalog is an organized list of services available to clients. In Sydnee, Service Showcase is the catalog module inside the client portal.
Your team maintains shared service categories and offerings, then activates the relevant services for each client account. The full portal catalog can show both:
- Active services: offerings the client currently receives
- Inactive services: other catalog offerings not currently active for that account
This gives the client context without turning the catalog into ecommerce. Service Showcase does not process checkout, subscriptions, proposals, contracts, or billing.
Show useful details for active services
An active service can include account-specific information such as an identifier, date, quantity, amount, or link. The client sees only non-empty values in a read-only Your Info view.
Use these details for information the client may need to reference, not for internal notes. Clients can copy text values or open URL values, but they cannot edit the details from their portal.
The active-services dashboard widget is different from the full catalog. The widget summarizes active services, while the full Services page can also show inactive offerings.
Give inactive services a clear next step
An inactive service can include an optional Learn More link. When the service-request feature is enabled, it can also show Request Service so a client can express interest.
The link and request action serve different jobs:
- Learn More: sends the client to explanatory content your team configured
- Request Service: creates follow-up work in the client account when available
Do not assume visibility produces a sale. A request still needs qualification, scoping, pricing, and a response from your team.
Route active-service tickets separately
When workspace and account settings allow active-service tickets, an active service can show Submit Ticket. This gives the client a structured way to ask for work or help related to a service they already receive.
Both active-service tickets and inactive-service requests use the Service Showcase request workflow. They create a Task in the client account's Service Tasks section rather than a separate lead or help-desk record.
Assignment follows the current fallback order:
- An eligible account-level service assignee override
- An eligible default assignee for the service
- The workspace owner
Access checks can change the final assignee. Do not promise that one configured person always receives every request.
Walk through the two client paths
Consider a firm that offers payroll and advisory services.
An active payroll client needs help
The client opens Services in the portal and selects the active payroll service. They review any available Your Info details and, when active-service tickets are enabled, choose Submit Ticket.
The submission creates a follow-up Task under Service Tasks in that account's default Task board. If Tasks is visible to the client, the success experience can link them to the Task.
The same client is considering advisory
The client sees advisory as an inactive service. They can open the configured Learn More destination or choose Request Service when that action is available.
The request creates follow-up work in the same client account. Your team can then qualify the need and decide whether to create a proposal or another business-specific next step outside Service Showcase.
The paths begin in one catalog but preserve the difference between support for active work and interest in a new service.
Build a useful Service Showcase
Set up the catalog in this order:
- Organize services into clear categories
- Write descriptions in language clients recognize
- Add an optional explanatory URL where an inactive service needs more context
- Configure the default request assignee
- Add account-level assignee overrides only where responsibility differs
- Enter useful client-specific details for active services
- Activate the services each client currently receives
- Configure active-service ticket settings where available
- Use View as Client to review the resulting portal experience
The assisted setup flow can create a starting category, descriptions, and detail fields from a list of related service names. Review and edit that output before presenting it to clients.
Avoid service-catalog mistakes
Treating the catalog as a static PDF
A client-facing catalog should reflect the services available now and give configured offerings an appropriate next step. Review it when your service model changes.
Promising request buttons for every account
Service-request availability depends on current feature, workspace, and account settings. Active-service tickets and inactive-service requests also use different gates.
Mixing internal notes into client details
The Your Info area is client-facing and read-only. Store only information the client should see.
Calling every request a lead
Service Showcase creates follow-up Tasks. It does not create a separate customer relationship management (CRM) lead, sales pipeline, or support-desk object.
Assuming the request completes the sale
The catalog captures intent and routes work. Your team still owns qualification, scope, pricing, and agreement.
Give clients a structured way to ask
A useful service catalog explains what the client receives, presents other relevant offerings, and routes supported requests into owned follow-up work. It reduces ambiguity without pretending that discovery, support, and sales are the same process.
Explore Sydnee Service Showcase to see the client experience. The client engagement lifecycle shows how service discovery can follow completed work without becoming an automatic sales process. If your catalog needs account-specific routing or ticket settings, book a demo to test those paths.
