Program Tools (non OSU) Ideas/Suggestions

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.

We need to know if the utilizing FRP MXP Dashboard to do MCI workshop through Eligible MCI lead to upsell.Currently there's no visibility except to know that. PSM ask manually to partner what deal happened, which MCI worshop that comes from the deal. It leads to very long time because There are multiple layer and many team involved ( might ask CSM need to ask AE/ Ask regional alliance manager, need to check in country/account level)The FRP doing the workshop might be different than the one close the deal, potentially not aware Having dashboard showing possibility ofWhich workshop completed by partnerWhich customer completed workshop by tenant ID and if there's license purchase to trackInclude Tenant Purchase align with Completed Workshop list in the PSM Dashboard

Request to Include CSP Revenue to PIIR in PSM Dashboard to measure the partner contribution across CSP deals

Request to Include Customer Sub Segments in all Reports (MPX and others)

[MPX] Request Graph of usage details with timeline per tenant with timeline in one view (like Lynx Usage details view) Background : Tracking of all products usage is difficult to use as it's spread in multiple rows in the tabDifficult to measure the usage impact based on timeline after the CPOR is claimed. ( partner want to know since the cpor is claimed / workshop done, how's the usage impact or gap) Request : Have usage details view similar like in Lynx Microsoft that shown the workload usage in graphs/ one page view instead of separate in rowsAsk: to have it's in the page of the tenant (together with the subscriptions they have)

Request to enhance MPX by including the count of all eligible customer seats as whitespace in Copilot opportunities. This will enable better prioritization based on customer size and improve opportunity targeting. Current Limitation: Whitespace is calculated as Paid MAU - Free Chat MAU, which doesn’t reflect total customer potential.Partner Impact: Partners currently need to manually analyze license data to estimate customer size, which is time-consuming and inconsistent.Currently partner need to understand customer size by analyzing the existing license

Situation: Some customer shows MAU > PAU Request : Add details Needs clarity of reason why? is it data error? is it counting trial license? is it possible technically MAU>PAU . Happen in many customers in various security workloads Add suggestion talking point what to discuss with customer based on the reason. 

Currently in MPX a user is able to filter on MCI by selecting either 'Eligible' or ‘Ineligible’. To allow for better targeting depending on the specific campaign or motion a partner is looking to run, it would be useful if the filtering was more granular. For example, the ability to filter on Copilot eligibility, Data Security etc.

Currently, the Change Columns button in the FPX customer data area allows users to add or remove data fields displayed. However, these settings are not saved, so every time we access FPX, we must reconfigure the columns. While this may seem like a small task, it becomes a repetitive burden over time. If the Change Columns configuration could be retained, it would significantly reduce wasted time in the long run and greatly improve the usability of FPX. As an advanced enhancement, allowing users to save multiple personalized views e.g., My Views would be even more powerful. This would enable instant switching between different perspectives for analysis, making workflows faster and more efficient.