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
When scheduling events we need people to respond by a certain time to be able to organize things. How much time is needed depends on the event type - might have to book a room, or just send out an email with a Zoom link - so this should be configurable per event. It could probably be defaulted to the first time option -24h.
For additional motivation, a follow-up enhancement suggestion will be:
Thanks for adding this wonderful option for setting the "respond-by" date for a Newdle! Now that we have it, could Newdle remind participants to fill in the Newdle, say 24h before the respond-by date, for those that didn't respond yet? It would be so much nicer if a computer did it, reliably, instead of me, unreliably!
😄
Thanks for considering!
The text was updated successfully, but these errors were encountered:
Hm, to me it feels like the kind of thing one may want to simple send as extra context instead of making it structured metadata. So I'd rather have a freetext field where you can add a message to be included in the invitation mail...
We have also already run to the situation that having a description / freetext field/area would be welcomed.
The topic becomes quite full if you want or need to pass some information in regards to the newdle dates.
I can understand the respond-by (like some other product has), but more generalized description field would be more useful.
When scheduling events we need people to respond by a certain time to be able to organize things. How much time is needed depends on the event type - might have to book a room, or just send out an email with a Zoom link - so this should be configurable per event. It could probably be defaulted to the first time option -24h.
For additional motivation, a follow-up enhancement suggestion will be:
😄
Thanks for considering!
The text was updated successfully, but these errors were encountered: