Welcome to the Ideas Portal for Quria users!
Axiell invites customers to contribute ideas for new features or functions. While we can't develop every suggestion, your input helps shape Quria’s roadmap. You are welcome to add ideas, vote on others’ suggestions, and discuss them. To make this portal more effective, please submit your ideas in English.
Ideas are regularly reviewed by the product manager or local representative. Once reviewed, the ideas are visible for voting and discussion. Popular ideas will be prioritized within our backlog.
Status meanings:
Under investigation: Developers and specialists are discussing if the idea is possible to implement.
Planned: The suggestion will be fulfilled in some way in a foreseeable future
Future consideration: A good idea, without technical obstacles, but it can't be prioritized into the roadmap at the moment.
No action: Technical or other issues prevent development, or an alternative solution exists.
We reserve the right to reject ideas and to close issues after 3 months if we don't receive answers to follow-up questions.
For technical issues, please contact your local support.
Es gibt bei uns häufig den Fall, dass Kunden verschiedene Sperren haben. Bei den Zahlungserinnerungen ist das dann problematisch, da die Mahnstelle hier mit den Kunden schon zu den Versäumnissen persönlich in Kontakt steht. Wenn dann noch automatisierte Zahlungserinnerungen zugestellt werden, sorgt, dass bei den Kunden zu sehr großer Verwirrung. Wir müssen aufgrund dessen leider komplett auf die Funktion der Zahlungserinnerung verzichten.
Es wäre gut, wenn das Personal vorübergehend die „Teilnahme“ eines Kunden an der Zahlungserinnerung aussetzen könnte (zum Beispiel über ein Häkchen im Benutzerkonto) .
We often have the case that customers have different blocks. This is problematic in the case of payment reminders, as the dunning office is already in personal contact with the customers about the defaults. If automated payment reminders are then sent, this causes a great deal of confusion among customers. Because of this, we unfortunately have to completely abandon the payment reminder function.
It would be good if the staff could temporarily suspend a customer's "participation" in the payment reminder (for example, via a tick in the user account).
Conclusion after meeting:
Our suggestion is that you create a special patron category and create rules that prevents this category to get reminders after the first one. Please evaluate this suggestion and come back if you are not satisfied.
Regards
Magdalena
Hi!
I am not sure that I understand the user case, but we can maybe talk about it when I visit you in September?
Best regards
Magdalena