YES! Wanted to chime in with my support of this idea. Having some transmission statistics would be most helpful. Like number of messages transmitted by month -- just to gauge how frequently the system is being used. Also number of rejected messages (like a message that gets returned because it has an unsupported attachment type) and similar statistics would be greatly helpful. If the sender and subject line info is a sticking point, at least numerical statistics and number of items in the queue would be very helpful in managing the success of my Presto installation.
Categories: HP Printing Mailbox Presto Service
The "Status" info that is presented on the Account home page is much too limited. It merely shows the time of the last connection, and what the paper and ink statuses were at that time (it is not even clear if the paper status would show "emplty" or "jammed", if that were the case).
It would be really helpful to see how many messages were sent, as this would provide some indication of a SUCCESSFUL session.
It would be even better if we could see the message headers, so now we know WHAT has been delivered. This concept has some similarities with the View The Queue thread, and I believe both ideas have merit, and should be implemented. I especially agree with the comment that the Account Manager role includes an implied "power of attorney" over the data in the queue, much in the same way that a Corporate eMail SysAdmin can view headers of all items in the mailboxes.
We have a long list of enhancements to the Presto Service along the lines of what you are both suggesting above. We absolutely capture all of the input we get, and have placed many of the ideas on our product roadmap for future implementation. What always helps is to get a sense of what is most important to Presto users so we can prioritize our efforts.
Presto Insider: Peter Radsliff
CEO, Presto Services Inc.
Peter R. said: We have a long list of enhancements to the Presto Service along the lines of what you are both suggesting above. We absolutely capture all of the input we get, and have placed many of the ideas on our product roadmap for future implementation. What always helps is to get a sense of what is most important to Presto users so we can prioritize our efforts.I am glad to hear that -- can you let us have a peak at your strategic roadmap? It would be nice to know where you are heading, and if we have a chance to influence your choices by "voting" on our preferences, we can help set the priorities. (I sort of feel like we are your Beta testers; it would be good to know how you are using our input.)
RSS