Loading
Engagement
Содержание
Выбрать фильтры

          Результаты отсутствуют
          Результаты отсутствуют
          Ниже приведены некоторые советы по поиску.

          Проверьте орфографию ключевых слов.
          Воспользуйтесь более общим поисковым запросом.
          Выберите несколько фильтров для расширения области поиска.

          Выполните поиск по всей справке Salesforce.
          Customize AI Summary on Home Page with Context Service

          Customize AI Summary on Home Page with Context Service

          Use the Context Service integration to create dynamic, insightful summaries and show them on your homepage. For example, a sales rep’s dashboard can highlight top leads and opportunities to help them prioritize high-impact tasks.

          Required Editions

          Available in: Lightning Experience
          Available in: Starter, Professional, Enterprise, and Unlimited Editions for Industries clouds where Context Service is enabled
          Note
          Note This is a sample prompt template, and the user has to verify and test it.
          1. Start by turning on Context Service next create a context definition by using User as the parent object and then select the related entities that you want to include. See Create a Context Definition
          2. Add a mapping of the context definition to the objects. See Add Context Mappings..
          3. Activate the context definition. See Activate Context Definition.
          4. Create prompt template of type User Summary.
          5. Write the prompt instructions and use the Context Service for training data. See Example Prompt Template Library.
            You are an assistant for an account executive, responsible for identifying and prioritizing the opportunities and leads that require immediate attention. This guidance will help the account executive optimize their efforts for the day, ensuring they focus on the most critical tasks and maintain a clear understanding of what needs immediate action. The input data includes detailed information on Opportunities and Leads, and is associated with the account executive for whom you are compiling the summary (including the FirstName and LastName provided in JSON for user).
            
            In the JSON object for Opportunity, you will receive the following fields:OpportunityName, Description,  NextStep, CloseDate, CreatedDate, Amount, AccountName, HasOpenActivity, Stage
            In the JSON object for Opportunity Product, you will receive the following fields: Name, CreatedDate and Description.
            In the JSON for Lead, you will receive the following fields : Company, Description, Name,
            LeadStatus, CreatedDate, LastActivityDate.
            
            
            Instructions: 
            """
            Review the opportunity description and next steps to understand the customer sentiment (Positive, Negative, Mixed), then create a clear summary and suggest next steps to improve the chances of closing the deal. Incorporate relevant details from the Opportunity products, if applicable.
            Opportunities with higher stages are closer to being won; prioritize them accordingly. Opportunity stages are similar to : "Prospecting, Qualification, Needs Analysis, Value Proposition, Decision Makers, Perception Analysis, Proposal/Price Quote, Negotiation/Review" in order of least priority to highest priority.
            Sort opportunities in ascending order of CloseDate. If there are multiple opportunities with the same CloseDate, then the opportunity with the higher stage must come first. If there are multiple opportunities with the same closedate and same stage, then the opportunity with the higher amount should come first.
            For an opportunity, if the opportunity stage is closed, then do not show it in the response.
            Leads with higher leadstatus are closer to being converted; prioritize them accordingly. Leadstatus is similar to : "New, Contacted, Nurturing" in order of least priority to highest priority.
            Sort leads in ascending order of LastActivityDate. If there are multiple leads with same lastactivitydate or no lastactivitydate then the lead with the high priority leadstatus must come first. If the description is empty, do not assume any value.
            For a lead, if the leadstatus is converted, qualified or unqualified, then do not show it in the response.
            When generating the response, must show upto 5 opportunities and must show upto 5 leads based on the instructions mentioned above, listing them in a single line separated by bullet points. If fewer than 5 are available, only list those provided in the data set, without creating or assuming additional data. If data is missing for any points mentioned in the response structure, do not include those points in the response.
            Generate response with markdown components for headers, bullets, and bold for labels.
            If any detail is missing for a lead or opportunity in the input data, then strictly do not show label in the response.
            
            
            Response Email format instructions: 
            
            """
            The response format must strictly follow this structure (this is not an email):
            Hello [First Name of User] (from the input json), here are the top opportunities and leads that you can focus on:
            Opportunities details:
            (bullet list for every opportunity detail)
            Opportunity Name:
            Stage:, Amount: (strictly do not show in the response if the corresponding information is not available)
            Last Activity Date: , Has Open Activity: (strictly do not show in the response if the corresponding information is not available)
            Summary: (strictly always generate summary of opportunity)
            Close Date: (strictly do not show in the response if the corresponding information is not available)
            Lead details:
            Lead Name: (If LeadName is not available for a lead, then strictly do not show this Lead Name label in the response)
            Company: (If company is not available for a lead, then strictly do not show this company label in the response)
            Status: (If leadstatus is not available for a lead, then strictly do not show this status label in the response)
            Last Activity Date: (If lastactivitydate is not available for a lead, then strictly do not show this Last Activity Date label in the response)
            Description: (If description is not available for a lead, then strictly do not show this description label in the response)
            
            Thank you for your attention.
            
          6. From the resource picker, select Salesforce Data Action, Context Service, and then Default Context Data Provider.
          7. On the Default Context Data Provider tab, provide the details.

            Context Definition API Name

            Specify the Developer Name of the Context Definition to fetch the data.

            Context Mapping Name

            Specify the name of the Context Mapping, which is used to map the data in the Context Definition. If not specified, Default Mapping is used.

            Context Record Id

            Specifiy the Record ID of the object defined in Context Object Name, which is used to map the data.

            Context Object API Name

            Specify the name of the object mapped to the root node in the Context Mapping.

            Context Node API Name

            Specify the name of the root node in the context definition. This parameter is required only if the root node's name and the mapped object's name are different in the context mapping.

            Time Period In Weeks

            Specify the retrieval period in weeks from the current date for fetching the data.

            Context Node Data Limit

            Set the upper limit for the total number of records that are shown.

            Context Node Sort Field

            Specify the field on which the fetched data is sorted.

            Context Node Sort In Ascending Order

            Specify the order in which the fetched data is sorted. If true, the data is sorted in ascending order.

            Filter API Name

            Specify the API name of the filter to apply when fetching data. Using a Filter API Name ignores the Time Period, Context Node Data Limit, Context Node Sort Field, and Sort Context Node Ascending/Descending settings. Without a Filter API Name, the system honors at run time filters and defaults to a 20-node limit if none is specified. See Context Filters.

            Default Context Data details
          8. Save and activate the prompt template.
          9. To add the AI Summary component on the home page, use the Lightning App Builder page, add the new prompt template to the page, and click Activate. See Add AI Summary to a Page.
           
          Загрузка
          Salesforce Help | Article