This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
1. Scope & Usage
Do you want the usage report at individual mailbox level, partner level, or organization level?
Should the report include historical usage (last 3, 6, 12 months) or only current-month data?
Historical data is also detailed, as well as Summary report, similar to how it is showing in epm where sales/support access and share it with clients.
2. Report Content
What specific fields/metrics do you expect in the usage report?
Examples:
Data volume consumed
Number of documents
Mailbox capacity vs. used
File types / protocols involved (AS2, SFTP, VAN, API)
Overages forecast
Should the report highlight threshold breaches or near-capacity warnings?
The similar report which is present in epm, which support used to download and share it with customer based on each mailbox , should be visible in Doc tracker so that customer can download it/view it. epm is having summary and detail report. The similar report should be added to doc tracking.
3. Delivery & User Experience
When you say “download/subscribe,” what options are required?
Download as CSV? : Download as excel,pdf
Email subscription? : yes, so that if user need email every month.
Scheduled subscription (daily/weekly/monthly)? : Monthly
Should the report be available directly in Doc Tracker UI or also via API? : Directly in Doc tracker
4. Existing Pain Points
What issues do users currently face with the monthly usage sent on the 10th? : Some customers need it even before 10th of every month, which is not possible for us to provide. They have to depend on support case for adding additonal users and for historic reports also they need support case.
How many tickets does support typically receive for manual usage-report requests? : In 2025 156 tickets.
5. Business Value
How critical is this for customers from a business perspective—
Avoid overages? : Yes
Compliance? : Yes
Cost control? : Yes
Usage should be visible for every customer in the visibility tool. It increases user experience, prevent overages and better customer satisfaction.
6. Role & Access
Which user roles should be able to view or download the report? : All doc tracker users.
(Admin only, or all Doc Tracker users?)
Once I have this information, I will review it with our architecture and engineering teams and share the next steps, including prioritization and potential timelines.
Hi Abida,
Thank you for submitting this Request for Enhancement regarding “Usage Report for each client based on mailbox within the Doc Tracker application.”
This is a valuable suggestion, especially as customers increasingly want more transparency into their mailbox usage and proactive controls to avoid overages.
I’d like to gather a few more details so we can evaluate the requirement accurately and identify the best experience to deliver. Could you please help clarify the points below?
1. Scope & Usage
Do you want the usage report at individual mailbox level, partner level, or organization level?
Should the report include historical usage (last 3, 6, 12 months) or only current-month data?
2. Report Content
What specific fields/metrics do you expect in the usage report?
Examples:
Data volume consumed
Number of documents
Mailbox capacity vs. used
File types / protocols involved (AS2, SFTP, VAN, API)
Overages forecast
Should the report highlight threshold breaches or near-capacity warnings?
3. Delivery & User Experience
When you say “download/subscribe,” what options are required?
Download as CSV?
Email subscription?
Scheduled subscription (daily/weekly/monthly)?
Should the report be available directly in Doc Tracker UI or also via API?
4. Existing Pain Points
What issues do users currently face with the monthly usage sent on the 10th?
How many tickets does support typically receive for manual usage-report requests?
5. Business Value
How critical is this for customers from a business perspective—
Avoid overages?
Compliance?
Cost control?
6. Role & Access
Which user roles should be able to view or download the report?
(Admin only, or all Doc Tracker users?)
Once I have this information, I will review it with our architecture and engineering teams and share the next steps, including prioritization and potential timelines.
Thanks again for helping us improve the Doc Tracker experience.
Regards,
Manoj Panda
Product Manager – Sterling B2Bi SaaS & VAN