Set up the landing pages that were supplied with legacy workspace or create landing pages starting with an empty page to show agents the issues that need to be resolved.

Landing pages are the pages that agents see when they open their workspace. The pages typically include:
  • Performance Analytics and Reporting (PAR) visualizations and widgets, for example, the number of open issues
  • Lists of records, for example, all records that are assigned to the agent
Figure 1. Landing page
Landing page
Every workspace should have at least one landing page. You can either:
  • Use the supplied landing pages or modify them.
  • Create a landing page starting from an empty page using the legacy User Interface Builder (UI Builder). The legacy UI Builder enables you to build a landing page. The new UI Builder enables you to build a Configurable Workspace, and is only only compatible with CSM. For more information on the new UI Builder, see UI Builder.

Domain Separation for landing pages

Domain Separation enables the following functionality for landing pages.
  • Create a landing page: You can create landing pages that are domain separated. Domain separation enables landing pages to override settings for a specific domain.
    Note: Macroponents are not domain separated. Changes made to macroponents affect all landing pages that use the value stored in this reference field.
  • Editing a landing page in a sub-domain: To make a change in a sub-domain, you must create a copy in the domain you want to edit and edit the new landing page.

    You can edit landing pages in sub-domains that are set to Global. Editing landing pages in sub-domains enables you to change the name or element within a component. The changes are saved to the Global landing page. The definition of the landing page is changed and the domain is unaffected.