Skip to content
The Chat Archive
vicuna-33b Arena Human Preference 55K

act as an english professor and rewrite this text Context To simplify the creation of…

  1. User

    act as an english professor and rewrite this text Context To simplify the creation of "customer Information and repository" pages for new customers the template described below has been created Instructions How, Where and When to create Customer Information and Repository Pages From your regional customer section of the Customer Information Repository, Status and Activity Pages - this is where your page will be created Click the "..." button next to "create" (figure 1.) This opens out the template section of figure 2. choose "Customer Information Page", and select "Next". Add the customer name into the Prefix field (#1) as shown in Figure 3. Note the page names auto-completed and shown as #2; and select "Next" #3 The pages should not be created in the section you began in step 1 above. Edit the title of the new page remove the text "customer information page" leaving only the customer name Note do not edit child page title with customer persona. Add the regional Confluence page label by: Editing the new page and choosing the label icon. In the text box when opened add: emea_csm_status for EMEA customers latam_csm_status ...for LATAM apac_csm_status ...for APAC csm_status ...for NAM **note no region specified Ensure your new customer page roles up to the regional dashboard. Review step 7 if its missing. On creation ensure the page is fully completed including Jira filters and Customer Persona child page Engage with regional CS leads for hints on Jira filters

    When to Review and Update Customer Information and Repository Pages Review - once per week minimum Update - as per review, or update immediately as on change of critical status. Note the usage MRR graph should be updated when an update is released Remove - old information that is no longer relevant, in particular from solution summary and next steps

  2. Assistant

    Title: Creating and Maintaining Customer Information and Repository Pages

    Context: The purpose of this document is to provide a clear and concise guide for creating and managing "Customer Information and Repository" pages for new customers. By following the instructions provided, you will be able to efficiently generate and maintain accurate, up-to-date pages for each customer.

    Instructions:

    1. How to Create Customer Information and Repository Pages a. Access the regional customer section of the Customer Information Repository, Status, and Activity Pages. b. Locate the "..." button next to "create" (figure 1). c. Click the "..." button to open the template section (figure 2). d. Within the template section, select "Customer Information Page" and proceed to the next step.
    2. Adding Customer Details a. Fill in the Prefix field (#1) with the customer name, as shown in Figure 3. b. Observe the auto-generated page names (#2) and select "Next" (#3).
    3. Creating and Naming Pages a. Ensure that the pages are not created within the initial section you started in step 1a. b. Edit the title of the new page, removing the text "customer information page" and retaining only the customer name. c. Note: Do not edit the child page title with the customer persona.
    4. Adding Regional Confluence Page Labels a. Edit the new page and select the label icon. b. In the text box that opens, add the appropriate label for your region:
      • emea_csm_status for EMEA customers
      • latam_csm_status for LATAM customers
      • apac_csm_status for APAC customers
      • csm_status for NAM (no specific region) c. Ensure that your new customer page rolls up to the regional dashboard. Refer to step 7 if it is missing.
    5. Completing Customer Pages a. Upon creation, ensure that the page is fully completed, including Jira filters and Customer Persona child page. b. Collaborate with regional CS leads for guidance on Jira filters.
    6. Reviewing and Updating Customer Information and Repository Pages a. Periodically review customer pages, with a minimum frequency of once per week. b. Update pages as necessary, either during the review process or immediately after a change in critical status. Note that the usage MRR graph should be updated when an update is released. c. Remove outdated or irrelevant information, particularly from the solution summary and next steps.

    By following these guidelines, you will be able to effectively create and maintain customer information and repository pages, ensuring that your team has access to accurate and up-to-date information at all times.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.