𝗜𝘀𝘀𝘂𝗲: Managing Messages Is Unnecessarily Cumbersome and Creates a Risk of Transactions Being Assigned to the Wrong Customer

First, I appreciate CL's continued efforts to improve CitrusPay and the new messaging functionality associated with Payment Links. However, I've encountered a couple of workflow issues that I hope your team will consider addressing.

Unfortunately, this system does not allow me to upload a screen recording to demonstrate what I'm experiencing, so I'll do my best to explain.

𝗜𝗦𝗦𝗨𝗘 #𝟭: Add a "Mark All as Read" Option

Currently, when reviewing messages associated with a customer, I must click on each individual text message to mark it as read.

If a customer has several messages, this becomes unnecessarily tedious.

𝗥𝗲𝗾𝘂𝗲𝘀𝘁𝗲𝗱 𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁: Please add a "Mark All as Read" button next to the customer's name, allowing us to clear all messages associated with that customer in one click.

This would be a simple, time-saving improvement.

𝗜𝗦𝗦𝗨𝗘 #𝟮: Customer Remains Loaded in POS After Reviewing Messages

This issue is more concerning because it creates the potential for sales transactions to be recorded under the wrong customer.

When I finish reviewing and marking a customer's messages as read, 𝘁𝗵𝗮𝘁 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿'𝘀 𝗻𝗮𝗺𝗲 𝗿𝗲𝗺𝗮𝗶𝗻𝘀 𝗹𝗼𝗮𝗱𝗲𝗱 𝗶𝗻 𝘁𝗵𝗲 𝗣𝗢𝗦, as though I'm preparing to complete a sales transaction for them.

This creates two problems:

𝗔. 𝗥𝗶𝘀𝗸 𝗼𝗳 𝗔𝘀𝘀𝗶𝗴𝗻𝗶𝗻𝗴 𝗮 𝗦𝗮𝗹𝗲 𝘁𝗼 𝘁𝗵𝗲 𝗪𝗿𝗼𝗻𝗴 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿

If I forget to manually remove that customer's name, my next sale could inadvertently be recorded under that person rather than "Walk-In Customer" or the actual customer making the purchase.

This is an unnecessary risk to the accuracy of our customer records and transaction history.

𝗕. 𝗧𝗵𝗲 𝗠𝗲𝘀𝘀𝗮𝗴𝗲 𝗜𝗻𝗯𝗼𝘅 𝗗𝗶𝘀𝗮𝗽𝗽𝗲𝗮𝗿𝘀

Once I've finished reviewing a customer's messages, I expect to return to my message list so I can continue clearing my inbox.

Instead, the POS continues displaying the customer I just finished with, and I can no longer see my list of messages.

To get back to my inbox, I must manually delete the customer's name from the POS.

𝗧𝗵𝗶𝘀 𝗶𝘀 𝗰𝗼𝘂𝗻𝘁𝗲𝗿𝗶𝗻𝘁𝘂𝗶𝘁𝗶𝘃𝗲. I'm not processing a sale. I'm managing messages. Why should I have to remove a customer from a sales transaction screen simply to continue reviewing my inbox?

𝗥𝗘𝗤𝗨𝗘𝗦𝗧𝗘𝗗 𝗜𝗠𝗣𝗥𝗢𝗩𝗘𝗠𝗘𝗡𝗧

Please consider separating the messaging workflow from the active POS sales transaction.

When I finish reviewing a customer's messages and return to the message list, the system should:

𝗧𝗛𝗘 𝗕𝗜𝗚𝗚𝗘𝗥 𝗣𝗜𝗖𝗧𝗨𝗥𝗘: 𝗟𝗲𝘁 𝗨𝘀 𝗦𝘁𝗮𝘆 𝗪𝗶𝘁𝗵𝗶𝗻 𝘁𝗵𝗲 𝗧𝗮𝘀𝗸 𝗪𝗲'𝗿𝗲 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗶𝗻𝗴

When I'm working through my message inbox, 𝗜 𝘄𝗮𝗻𝘁 𝘁𝗼 𝘀𝘁𝗮𝘆 𝗶𝗻 𝗺𝘆 𝗺𝗲𝘀𝘀𝗮𝗴𝗲 𝗶𝗻𝗯𝗼𝘅. I shouldn't have to interrupt that process to manage customer information in the sales portion of the POS.

More importantly, reviewing messages should not inadvertently affect which customer is associated with the next sales transaction.

I believe these are relatively straightforward workflow improvements that would make the messaging feature more intuitive, efficient, and safer to use.

𝗠𝘆 𝗿𝗲𝗾𝘂𝗲𝘀𝘁 𝗶𝘀 𝘀𝗶𝗺𝗽𝗹𝗲: Please design the messaging workflow around the task we're actually performing, which is managing customer communications, not initiating sales transactions.

Thank you for considering these suggestions and for continuing to improve the CitrusPay experience for retailers.