Sales Accelerator combines worklists with AI-generated recommendations to suggest the next best actions. Representatives receive prioritized activities such as follow-up calls or emails based on engagement signals, allowing them to maintain consistent communication without relying solely on manually designed automation.

The correct action is to select a valid price list on the opportunity and verify that the product has a matching price list item for the selected unit. Dynamics 365 Sales calculates Price Per Unit from the price list item when an existing catalog product is added to an opportunity, quote, order, or invoice. Microsoft states that if an existing product is associated with a price list, the price per unit is calculated from the related price list item; otherwise, it is set to 0.
The failure pattern described in the question is classic missing or mismatched price-list setup.
Price calculation will not occur when no price list is selected, when the selected price list does not contain the product, or when the required price list item is missing. Microsoft also notes that price lists tie the product, unit, and pricing details together. Option A is incomplete because matching currency alone does not create the product/unit price list item. Option B is wrong because User Provided revenue bypasses system calculation. Option D handles discounts only; it does not fix a zero base unit price.

The three default rule-style suggestions are the Record Owner of the initiating record, the Created By user of the initiating record, and the manager assigned on the seller's system user record. Suggested contacts in Dynamics 365 Sales Teams chat are intended to help sellers quickly find coworkers who are relevant to the record they are working on. Microsoft states that administrators can enable suggested contacts when a seller starts a new connected chat, and that rules-based contact suggestions can be configured for supported Dynamics 365 record types.
The rule engine supports relational rules: Microsoft explains that a relational rule suggests a user who has a relationship with the linked record type or one of its related records, and administrators can select a user field directly on the record or through related entities. The record owner and created-by user are direct relational users on the initiating record. The seller's manager is reached through the system user relationship. The business-unit owner is not the default suggestion path for seller collaboration, and "last modified by" or a user who updated a timeline activity are not the default rule answers in this configuration set.

Explanation:
Requirement
Component
Record engagement is pending, completed, or failed
Sales Agent Runs table view
Weekly performance view of the Sales Close Agent in Research mode
Insights and metrics for the Sales Close Agent
For a specific opportunity that stopped receiving automated outreach, use the Sales Agent Runs table view .
Microsoft states that to resolve the engagement status of a specific record, administrators can go to the sales agent run record view and filter the Regarding column by the record of interest. The Status field shows whether the engagement is Active , Failure , or Completed ; Active means pending, Failure means the engagement failed, and Completed means it finished successfully.
For the manager's weekly performance requirement, use Insights and metrics for the Sales Close Agent .
That is the performance reporting surface for the agent, not the per-record run table. The requirement specifically mentions a weekly performance view plus Last refreshed and a time period filter , which maps to the agent's insights dashboard/metrics area. The Sales Agent Runs view is operational monitoring for individual records, while the insights and metrics view is for aggregate performance analysis such as engagement outcomes, response rates, and trend monitoring. Do not select Engage settings because settings configure how the agent behaves; they do not provide performance metrics. Opportunity pipeline view helps sellers manage opportunities, but it is not the agent performance monitoring dashboard.
References/topics: Sales Close Agent monitoring; Sales Agent Runs table; engagement status; Sales Close Agent insights and metrics; Research mode performance reporting.

Explanation:
The correct sequence starts by opening and configuring the predictive scoring settings for lead scoring. The administrator must access the predictive lead scoring configuration page before changing the model.
Microsoft's predictive scoring configuration guidance states that the Predictive lead scoring page is where administrators configure model settings, including model criteria and field behavior.
Next, the administrator should edit model attributes . This is the actual model-tuning step. Microsoft states that Edit model is used to update or add fields that affect the prediction accuracy score, especially when the organization wants the model to consider different fields or a unique business process.
After modifying the attributes, the model must be retrained . Retraining is required when prediction accuracy does not meet expectations or when recent data should be incorporated. Microsoft explains that retraining uses the latest leads in the organization so the model can provide more accurate scores.
Finally, the administrator must verify predictive score accuracy by reviewing the model accuracy and performance. Exporting all lead records is unnecessary, and editing health score grading applies to opportunity health scoring, not predictive lead scoring.
References/topics: Predictive lead scoring; model attributes; model retraining; scoring accuracy; lead prioritization in Dynamics 365 Sales.