Feature Ideas

In large distributed Support/Sales teams, they manage different products/SKUs & customers entirely independent of each other and it would useful to restrict their access to the relevant Products & Customers.

Allow client to collect Analytics usage data client side online and offline Also for the LLS

Like V10 Consumer Registration data - Allow the client push back metadata upon activation

How do we change the key parameters of the insights engine to fit with our models vs the Zengain standard?

With small nos users the UIO works well but when there are millions of them how do you display and use that data to be helpful? how to segment large volumes to be manageable? How to ensure performance with big volumes and easy ways to extarct the data to data warehouse/BI tools vs using the UI

How to send a really intimate email to each user based on their usage patterns, if they used or didnt use a key feature...using existing marketing tools. Is there a webhook or API and a tool to map the flows to allow for mass automations of volumes of emails to users?

So, understanding not just that one particular user is showing more engagement but where that's coming from. Is it just because it's a Monday, and they have time on Monday to test the tool? Or did we send them an email that they attended the webinar a couple of days prior? I think there's an additional level of information of data that customers, like your customers, like tech meet, do have, but that needs to be integrated in here. So, I see this from both a prospecting tool as living part of a marketing automation tool. So, we can differentiate when it goes from MQL to SQL but then from an account management.

show all the user and customer data inside the CRM, ideally with never leaving

How to allow other parties to access their OWN customers i.e. a distributor may have a reseller with end users - how to allow them to review their own data and not the rest of the data in the stack - hierachical access to end user data

How can we add to each customer the MQL/SQL, lead source and other such prospecting data to improve the sale data stack

Allow the customer in the EUP to take a assigned entitlement and split across different departments (eg)

Allow an end user to be linked to multiple entitlements i.e. an Auditor/contractor can be on multiple customers by username (Ill add more later)

Allow a hierarchy of customers, i.e. sub departments, divisions etc. This allows fine grain reporting of multilevel customers

Add reseller functionality, a multilevel hierarchy Reseller Account Management Vendors can create and manage reseller accounts within the licensing platform. Each reseller can have a specific set of permissions and are assigned the License Codes by the level above Resellers can create distributers below them Delegated License Generation Resellers can be allowed to generate licenses for end users(?) or pull licenses they have been assigned. You can restrict license types, quantity, expiry, or features they can assign. License Codes can be assigned to resellers these are only visible to them and the level above Custom Portals for Resellers Resellers may get access to a customized portal where they can issue(?) and track licenses to customers. Branding and access control are configurable per reseller. Activity Tracking and Reporting Full audit logs and reports show which reseller issued which licenses, to whom, when, and have activation history visibility Helps vendors track usage and sales performance per reseller and resellers for the distributers Quota and Entitlement Control Vendors can set quotas (limits) on how many licenses each reseller can issue by assigning License codes to them Integration with E-Commerce or CRM Can be integrated with e-commerce platforms (like FastSpring or cleverbridge) to automate license delivery through resellers. Also integrates with CRM systems (e.g., Salesforce) to manage reseller performance and customer data. 🛠 Use Cases SaaS and desktop software vendors who sell through VARs, OEMs, or regional distributors. Visibility is defined via the hierarchy. Enables channel partners to self-serve while maintaining central control.

This will allow our admin to add user friendly page names for visited url's for display purposes. This will allow us to do this without getting coding changes Also good for legacy applications i.e. that use masterpages