Watson Marketing Ideas
Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Tealeaf, Universal Behavior Exchange, Watson Customer Experience Analytics, Watson Marketing Insights, Watson Content Hub, Web Content Manager and WebSphere Portal solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.
Connect with your peers and IBM experts on the Watson Marketing and Commerce Community
Submit ideas for other Watson Customer Engagement Products:
• Watson Campaign Automation
• Watson Commerce
• Watson Supply Chain
This is a proposal to have a User session storage network (USSN, as compared to LSSN). When a user is replaying a session, they can have a longer term session storage, similar to "Export as TLA". This is where they are able to COPY a session from LSSN over to their LSSN, where they can give it a name, and share it with other users (to make it private or public). Links to this session will NO LONGER EXPIRE as the normal Canister Trim, and can be used for problem tickets, etc, legal and more.
SECURE: As the sessions are still stored in the Tealeaf system, they are still SECURE for authentication. They can even share the same on demand privacy rules by users, for proper data redaction or decryption.
EASY: Much easier than extracting a TLA. It can be stored in a user's storage section, where they can give the sessions names, tags, or other info so they can organize them.
MANAGEABLE: On saving them, they MUST give the sessions an expiration date, so the sessions will be cleaned up. Systems administration can have a report on USSN storage size, trending, and see how old the oldest sessions are and who has them. They can initiate cleanup processes if users have too much stored - or ask those users to clean up their storage.
VALUE: Admins can see how much data those people are storing, and if they are actively being used for replay. If they ARE then easy to use that as a value add metric for people using this in the system.
How will this idea be used?
Almost every user will use this to create a "bank" of these sessions.
|What is your industry?||Banking|
|What is the idea priority?||High|
|Link to original RFE|