Program Tools (non OSU) Ideas/Suggestions

Describe the scenario briefly (what is the feature? how will it work as a partner i can do X so that i can achieve Y)  This feature adds an “At Risk” column to ASPX – Copilot Opportunities. Partners can quickly identify tenants with very low paid Copilot usage so that they can take proactive actions (engagement, enablement, adoption support) to prevent Copilot license churn. The experience is similar to the existing “At Risk Tenants” column in ASPX – Secure Productivity.   Describe the business problem or pain point (why is this feature needed?) Partners currently lack visibility into Copilot adoption risk within Copilot Opportunities. Low usage tenants are often discovered too late, after churn discussions have already started. Without an at‑risk signal, partners must rely on manual analysis or assumptions, which delays intervention and reduces retention.   Describe the expected impact (quantify the impact e.g. improves productivity, reduces manual toil) Enables earlier intervention for low‑usage Copilot tenants Reduces Copilot paid license churn Improves partner productivity by eliminating manual analysis   How many partners asked for it? (quantify the ask) This idea was proposed by one partner, but it affects all partners involved in the Copilot business.   What is the urgency? High/Medium/Low High, Copilot adoption and retention are critical business priorities, and churn risk increases rapidly in the first 3–6 months after license purchase.   How does success looks like? (success criteria, measurable outcomes, KPI) “At Risk” column available in ASPX – Copilot Opportunities Partners actively using the column in adoption reviews Measurable reduction in Copilot churn rate for flagged tenants Increased Copilot MAU and usage for tenants previously marked as at risk

Currently Partners are only able to view opportunity details in ASPX for customers they have registered CPOR on. This is great where relationships exist already, however there are many times when account teams present new customers with no link to the Partner.  It would be beneficial for Partners to have a holistic picture of the customer landscape in those initial conversations to help shape an outcome that will have a higher chance of resonating with the customer and therefore landing successfully. This also reduces the amount of time expended given a Partner would likely have to engage the account team and or customer direct to get the required information.  Ultimately this would reduce lead conversion times significantly, reducing effort across the board, and likely see greater satisfaction for all involved.  While it was raised by 1 Partner, this would benefit all Partners globally. Given the potential positive impact, releasing this capability sooner rather than later would be highly beneficial.   

When we include the Teir 2 reseller name into the ASPX data feeds, is there a way to include the Teir 2 resellers MPNID along with the name. It can prove to be a good validation point for the Distributors to connect the tenant usage data.

Describe the scenario briefly (what is the feature? How will it work as a partner I can do X so that I can achieve Y) Adding more metrics to ASPX that are from the FRP dashboard so parters can have more overall historical usage data and account details for better data share and analysis. As the FRP dashboard deprecates, partners will still need the overall metrics that are not captured in ASPX. Describe the business problem or pain point (why is this feature needed?)Partner Compugen suggested adding features from FRP Dashboard that they commonly use for MAU YTD reporting. These reports help the partner consult with their AM, check overall YTD usage and track Specialization metrics. The ASPX are missing the following features from the FRP Dashboard. Performance OverviewAll up Tenants; Usage Visualization and MetricsSpecific month(s)/Year(s) MAU information.Performance by UsageFTA name associated with the customerTPID informationMonthly Users deltaCurrent associated partner nameDescribe the expected impact (quantify the impact e.g. improves productivity, reduces manual toil)Adding the FRP metrics to ASPX will help partners/PSM track historical and overall usage to understand the impact of campaigns, motions and quicker data share. How many partners asked for it? (quantify the ask)Currently 1 but others will benefit from the change. What is the urgency? High/Medium/LowMedium, depending on the date the FRP Dashboard is no longer supported/updated. How does success look like? (success criteria, measurable outcomes, KPI)Adding the data features from the FRP dashboard to another tab in ASPX.