You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm really curious about the forwarding functionality. Who are users typically forwarding messages to? Are the recipients also users of the system? If not how else can they act on the message they've been forwarded?
I guess what I'm wondering is if the forwarding use case would be better served by some sort of in-app notification (using email) system.
During our discussions for the first phase, it was determined that the forwarding feature was intended to be for notification to a specific worker in the field. It was decided that only singular messages to singular recipients made sense. I can see the case where a singular message has value for multiple people, but then it creates confusion in terms of accountability for dealing with that message.
It's not a technical challenge to add this, but having these sort of assumptions in place help with the more challenging human element for systems like this. We are almost always better off keeping things as simple as possible.
This would also be cool. The ability to forward to email as well would be a big plus.
The text was updated successfully, but these errors were encountered: