A number of our customers use Prognosis to monitor the health of their payment systems. As part of this, they monitor the transactions flowing through the system, to ensure they are completing successfully and the payments service is performing optimally. But the definition of “optimal” can vary, depending on where you sit in the payments ecosystem and who you consider to be your customer.
If you’re in the operations team, “optimal” probably means that the infrastructure is performing well, links are up and no transactions are timing out. And that your primary customer, maybe the merchant services team, is happy. If you’re in the merchant services team, optimal might mean that your top merchants are transacting normally with no issues, and even if there are issues, you know the cause and can respond to any related complaints. If you are in the fraud team, your definition of optimal will be different again. If you are in the management team, on the customer help desk, in dispute resolution or even out at the merchant supporting your stores, you will likely have more unique definitions of optimal.
Even though these stakeholders have different takes on what is considered optimal, they can all benefit from having a real-time view into how the payment system is performing right now, from their point of view. If you’re currently using Prognosis in the operations team to monitor payments health, but haven’t yet shared real-time dashboards and alerts with the rest of your organization, or you have shared a small number of views and want to expand to other departments, there is no time like the present.
It may surprise you to hear that views for each of the use cases mentioned above are in production use at Prognosis sites. If you’d like to learn more about providing different views of optimal transaction performance for other groups in your organization, feel free to reach out to the community, or your account team, to find out how you can start on, or accelerate, this journey.
