Program Tools (non OSU) Ideas/Suggestions

a {text-decoration: none;color: #464feb;}tr th, tr td {border: 1px solid #e6e6e6;}tr th {background-color: #f5f5f5;}Request: Quarterly Graphical View of Upcoming EA / CSP Tenant Renewals in ASPXImpact: Provide at‑a‑glance visibility of upcoming renewals by quarterSupport early action planning for retention, upsell, and migration conversationsReduce reactively applying filters on the renewals to view the opportunity

Distributors have customers assigned to resellers via CSP licensing and sometimes those customers also have EA agreements. The Copilot Whitespace is based on all licenses to that customer regardless of purchasing vehicle. It is requested that when we filter it based on CSP, that the whitespace totals also adjust. The tier 2 reseller feels that that may not have an opportunity to fill all of the whitespace associated with the customer as they cannot have an effect on the EA licenses. being able to filter the whitespace based on vehicle will give the tier 2 reseller a true view of their opportunity. 

It would be great to be able to filter on the Tier 2 reseller name in the ASPX UI

Its becoming more apparent that in many cases the purview and Copilot conversations are intertwined. Is there a way to identify the tenants that have whitespace opportunities that overlap in those to workloads? Otherwise downloading and running an agent may be the solution??

One of the distributors that is integrating ASPX with the APIs has suggested that along with the Teir 2 reseller name that we should include the Partner ID or the tier 2 reseller MPN ID in the feed. This will help with their integration into their internal tools and marketplaces.

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. 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.

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.

ASPX: Automate Lead creation based on customer signals Configure the system such that when it identifies signals that indicate intervention could be required, it alerts the Partner and creates a Lead for them to follow up Describe the business problem or pain point (why is this feature needed?) Currently Partners manually have to export data or review the content within the tool to understand which Customers to target. By having our tool monitoring for changes, and categorising them and pushing them as Leads, it takes the burden off the Partner who can then focus on proactively reaching out to their customer base.   Describe the expected impact (quantify the impact e.g. improves productivity, reduces manual toil) This would save time. At the moment a Partner could be using a variety of resources to dig into ASPX depending on their role - from Pre sales to CSMs [both ends of the usage spectrum]. It would be another way to streamline and add value to an already great tool   How many partners asked for it? (quantify the ask) This would benefit ALL partners globally.    What is the urgency? High/Medium/Low Given its an enhancement request, its hard to quantify - but given the potential upside, the sooner we provide it, the quicker the benefit is to be had.    How does success look like? (success criteria, measurable outcomes, KPI) Partners could focus on value add conversations rather than administrative tasks with our customers. We could push white space to sales roles, or low usage high PAU to CSM roles. This is a feature that has broad scale impact. 

1. 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)       We would like to request the addition of a "Select All" option to the Change Columns feature in the Customer Detail area of ASPX Views (Copilot Opportunities, E3 Opportunities, E5 Opportunities, and E5 Expansion Opportunities).      2. Describe the business problem or pain point (why is this feature needed?)      Currently, partners must manually check every column before downloading Customer Detail data. This process is time-consuming, repetitive, and prone to errors, especially when all columns are needed for analysis. The lack of a bulk selection option creates unnecessary friction and reduces efficiency.      3. Describe the expected impact (quantify the impact e.g. improves productivity, reduces manual toil)      • Reduce manual processes performed weekly to improve productivity. • Minimize human error in row selection. • Enhance the ASPX experience for partners.      4. How many partners asked for it? (quantify the ask)      At least 2+ partners have raised this need. 5. What is the urgency? High/Medium/Low      High – This is a frequent pain point impacting daily workflows for partners who rely on ASPX Views for opportunity management and reporting.      6. How does success looks like? (success criteria, measurable outcomes, KPI)      Success Criteria:  • “Select All” option is available in Change Columns for all relevant ASPX Views. • Partners can download full Customer Detail data with one click. Measurable Outcomes / KPIs:  • Reduction in time spent preparing downloads. Increase in partner satisfaction scores related to usability.