tags vs flags vs info icons

[Paul-Eraman-CoopCycle]

Theoretical basis for visualization of information about a task on the dashboard:

Current Situation

We have tags that can be any color, are customized 100% by a dispatcher/admin, can be used to identify tasks uploaded in the admin panel or the deliveries page, and can be assigned directly to stores. Tasks with a tag are identified on the map with the entire icon changing color, and in the task list with a small colored circle, and on the map if you click on a task the popup window shows a tag name with its corresponding color.

If you assign multiple tags to a task, in the map for a rider and dispatch, the task will appear in the color of the most recently assigned tag color in the map, and in the list will show a few different circles with colors identifying tags. You cannot identify shops (restaurants) with tags, but posteriorly to an order being created, you can add tags to a task in the admin panel.

Current Use Cases

• Use them to filter by time as a substitute for functional routes or groups (Mensakas) so that riders can visually identify what is a morning task, an afternoon task, and an evening task.
• Identify non-urgent tasks (we have a hundred magazines to deliver in 3 days), and so if riders are busy they use the filter in the app to not see tasks with those tags, and if they are "free" they untick the filter so they can see them
• Mark special deliveries or special customers (look, its red! be careful!)
• Make a tag for each client with their color so that the 100 local commerce points we have on the map (all with their various characteristics) so that a dispatcher can better understand what they have on the map to create various routes for today, or the next day.

Proposal for the Future

Flags
A new feature that works the same as tags, except that there are only 4 of them, with colors that cannot be used by tags, and only one flag can be assigned to a task. The current proposal is for the following flags:

1. VIP - special client who we want to prioritize for some reason
2. WeFuckedUp - a client who had a bad experience previously, who we want the make sure the food is correct and arrives on time
3. Asshole - a client who we don´t like, and maybe don´t want to send a certain messenger, or we want to cancel
4. ReviewInfo - a task that we want a rider to make sure they double check the information such as comments

Flags would change the color of the pin in the map and would be visually marked on the task list in some way (another vertical bar? a rectangular bar with VIP instead of a dot?). Flags cannot be filtered away, and are associated both with USERS and SHOPS and STORES

Tags
Eliminate the possibility to use EXACTLY the same colors as the four tags above. Nothing else changes, but we add a filter that is like the filter for messengers on the admin dashboard to facilitate their use as an organizational tool.

❌

✅

Info Icons
Currently the camera icon tells a dispatcher or administrator that a task has a proof of delivery. This small, black icon is functional for administrators who are specialized and know where to look. There may be the need for more of these icons as time goes on, with the implementation of incident reporting (an icon for "not at home" for example) that would be shown to a dispatcher and administrator. However, we do not currently know what these icons might be.

[0bi0ne1312]

It could be a much needed help for flagging special delivery !
For example, to notice the courier some infos about the package in itself : keep it cold / fragile / ...
it is a different level of information than the label that are for us more general infos on the type of clients.

[fortyoneandahalf]

We currently use tags only to identify the client a delivery comes from. As such, we probably have limited use for flagging clients: if there's a client we particularly need to take care about, we have to communicate that to our riders directly because exactly what we need to particularly take care about will change depending on circumstance.

Couple of questions:

• I don't see anything about the rider app. Would flags be displayed in there in the same way tags currently are?
• Still on the app: could we display a bar of the tag/flag colour in the rider's task list in the app in the same way as we do in the dispatcher's view?

Couple of random thoughts:

• WeFuckedUp flag kinda sounds like a special case of VIP? And just generally, would it not be more flexible to allow co-ops to customise what the different flags mean?
• More info icons could be good, e.g. it could be useful to us to have an icon which displays if a courier has added any textual delivery notes, not just if they've added a photo.

[rayon9coop]

>>>FRENCH<<< (English below)

Tags
Quel est notre use case? Nous utilisons les tags pour :

1. identifier les clients (par leur nom). Sur la carte du dashboard, cela permet aux dispatch de rapidement identifier par la couleur le type de livraisons d'une journée.
2. identifier le type de marchandise transportée (Exemple : fragile, alimentaire, express, alimentaire frais, électroménager, etc.). Ce tag n'est en général pas visible sur le dashboard et sert pour des questions statistiques (quelle proportion de tels colis avons nous transporté l'an passé?)

Du coup, chaque tâche porte en général au moins 2 tags.

Sur la question de la limitation des couleurs, nous avons des propositions:

• associer (définitivement) une couleur à un tag : une fois qu’une couleur a été utilisé elle ne peut plus l’être pour un autre tag.
• associer une gamme de couleurs disponibles pour les tags et une autre gamme pour les flags. Par exemple, les flags utilisent la gamme complète de rouges. Les tags ne peuvent donc plus utiliser les rouges.

Flags
Le principe nous semble utile pour mettre en évidence des remarques et/ou des commentaires. Quelques propositions complémentaires:

• Personnaliser les flags: Peut-être serait-il possible d’avoir ces 4 drapeaux de base et de pouvoir en personnaliser d'autres ? Par exemple: "personne à mobilité réduite" ou "a besoin d’aide pour monter sa commande".
• visibilité des flags: il nous semble important qu'ils soient très visibles aussi bien sur le dashboard que sur l’application. Peu importe le moyen mais ça doit accrocher l'œil.

Icons
A nouveau, principe très utile car il permet de remonter une information pertinente.
Use cases typiques chez nous:

1. un.e coursier.ière doit nous transmettre un message important concernant une livraison dont il/elle a la charge
   Par exemple : adresse incorrecte, client a déménagé, changement de numéro de téléphone,...
2. Le dispatch doit attirer l'attention du/de la coursier.ière sur une livraison. Par exemple, sur une livraison assignée, un.e client.e appelle le matin pour signaler un changement d’horaire, d’adresse, une absence temporaire durant la journée, etc.

Dans les deux cas, ces informations doivent sauter aux yeux du dispatch sur le dashboard et du/de la coursier.ière sur l'app car elles déterminent la qualité du suivi de la livraison.

Pour le reste, nous rejoignons @fortyoneandahalf sur ses questions et avis

ENGLISH<<<<

Tags
Our use case
we use tags to :

1. identify customers (by name). On the dashboard map, this allows dispatchers to quickly identify the type of deliveries on a given day by color.
2. identify the type of goods transported (e.g. fragile, food, express, fresh food, household appliances, etc.). This tag is not usually visible on the dashboard, but is used for statistical purposes (what proportion of this type of parcel did we transport last year?).

As a result, each task generally has at least 2 tags.

On the question of limiting colors, we have some proposals:

• associate (definitively) a color with a tag: once a color has been used, it can no longer be used for another tag.
• associate a range of colors available for tags and another range for flags. For example, flags use the full range of reds. Tags can no longer use reds.

Flags
We find the principle useful for highlighting remarks and/or comments. Here are a few additional suggestions:

• Personalize the flags: Perhaps it would be possible to have these 4 basic flags and be able to personalize others? For example: "person with reduced mobility" or "needs help to to carry his parcels".
• visibility of flags: we feel it's important to make them highly visible, both on the dashboard and on the app. It doesn't matter how it's done, but it's got to be very eye-catching.

Icons
Once again, this is a very useful principle, as it allows you to bring up relevant information.
Typical use cases for us:

1. a courier needs to pass on an important message concerning a delivery for which he/she is responsible.
   For example: incorrect address, customer has moved, change of telephone number, etc.
2. The dispatcher needs to draw the courier's attention to a delivery. For example, on an assigned delivery, the customer calls in the morning to report a change of schedule, address, temporary absence during the day, etc.

In both cases, this information must be obvious to the dispatcher on the dashboard and to the courier on the app, as it determines the quality of the delivery follow-up.

As for the rest, we agree with @fortyoneandahalf 's questions and thoughts.

[Paul-Eraman-CoopCycle]

The only thing i would change in this is that we very much do NOT want all the things (flags, tags etc) to get mixed up. They need to be different things with specific uses.

So for example, i would rather limit flags to 4 flags (for example) and no more, but continue to have as many tags as people like. For example, a few of the things you have mentioned for me should be a comment in the task, and the problem we have is that you don't realise there is a comment until too late

[0bi0ne1312]

Very good idea to not make so much of it, like 4 or 5 is quite a good number. If we can customized these to really make these useful and adapted to every needs.

[0bi0ne1312]

Hello !
When the idea came to first discussion, I wasn't really fond of the idea, as it was presented as an add for food delivery and we are not in that branch (for now ahah).
But after many discussion, it could be a real need for adding important and direct information to tasks that can be clearly identified by the dispatch but also and firstly by the courier !

For example, in our use (because we all have different uses of the same software :) ), we could identified express deliveries, or fragile ones, or cold ones (for ice cream for example, or food in general, or drugs for pharmacy) !
The idea is, as Mex proposed, not to have to much of these, like the tags that can be infinite, but having four or five of these, customisable (for the name) and with plain colours and simple colors.

In order to have a direct example, it could be (again, for us) :

EXPRESS (in red) : when courier have to make it with a certain priority
COLD (in blue) : when it needs special bags
FRAGILE (in green) : when the courier needs to be careful in the loading and the travel
RETURN (in orange) : when the courier need to take back an invoice / receipt / other stuffs)
These flags could be directly noted on the task (like a "fragile" stamp ?) and could be configured by the dispatch on the admin panel (or directly by the client but not sure...)

What do you think of it ?

[rayon9coop]

@0bi0ne1312 Perhaps we need to define what a tag is and what a flag is. I understood that the flag could be something that qualifies the client (= recipient) but your last proposal leaves us in doubt