Feature Ideas

We would like to have Time-based One-Time Passwords (TOTP) via authenticator apps (e.g., Google Authenticator) for all backoffice logins. This adds a dynamic security layer that requires users to provide a time-sensitive, 6-digit code in addition to their standard credentials.

Can we change/customize the error message when guests have made 3 incorrect login attempts? Now they get a message that incorrect data has been entered, but they don't know that the account has been temporarily blocked. Changing it to something like this: ' Your account has been temporarily blocked, please try again in 30 minutes’' (The Dutch translation is: ' Uw account is tijdelijk geblokkeerd probeer het over 30 minuten nogmaals. ’) The current "incorrect data" message is vague. By specifying that the account is temporarily blocked, you provide the guest with a clear reason why their subsequent attempts (and potentially correct ones) are failing. This eliminates the "But I know my password is right!" confusion. Thank you in advance

When a relevant event occurs during my customer journey (a campaign, a coupon, a tier upgrade, a loyalty transaction), I want to have it captured and accessible in a personal inbox, So I can revisit it at my own pace without relying on a push or email to still be accessible.

I want to suggest to automatically remove or expire active campaign instances from a previous segment when a user is moved to a new segment (tier upgrade), so that users only see the campaigns relevant to their current status and to prevent reward stacking. Description: Currently, when a user transitions to a new segment—specifically during tier upgrades—the campaign instances associated with their previous segment remain active. This causes potential confusion and conflicts in campaign eligibility. Proposed Logic: Trigger: User segment assignment update (e.g., moving from Silver to Gold). Action: System identifies active campaign instances linked to the previous segment. Outcome: Automatically revoke/archive the old campaign instances and surface the new segment-specific campaigns to the user. We need to handle concurrent segment campaigns during tier changes. When a user is reassigned to a new segment, the current behavior retains the previous segment's campaign instances. This is critical for tiered loyalty campaigns where segment exclusivity is mandatory.

A proposal for a UI/UX enhancement for the Feedback Form management section in the Backoffice to improve organization and reduce operational clutter. Currently, there is no mechanism to remove or hide feedback forms once they have been configured in the backoffice. This presents a challenge for clients who: Test Configurations: Often create multiple test forms that become permanent fixtures in the overview. Manage Lifecycle: Have deprecated forms that are no longer in use but remain visible, creating an increasingly cluttered and unclear dashboard. Proposed Solution Add an "Actions" menu or dedicated buttons to the Feedback Form overview list, providing two options: Archive: Hides the form from the active list while maintaining historical data for reporting purposes. Delete: Permanently removes the form (this should ideally have a confirmation modal to prevent accidental deletion of active forms). Or can only remove feedback pages not in used. Expected Benefits Improved Interface Clarity: Allows clients to maintain a clean, relevant list of active forms. Reduced Human Error: Minimizes the risk of configuring or linking an incorrect/old test form by mistake. Streamlined Workflow: Simplifies form management, making it easier for clients to navigate and audit their existing feedback collection setup.

Currently, campaign configuration is a "one-way" process. When clients set up complex, state-dependent campaigns—such as an Advent Calendar—for testing purposes, they are unable to reset the campaign state once testing is complete (e.g., once "boxes" are opened). As a result, if a client needs to perform a clean test run or re-run a campaign, they are forced to manually delete or reconstruct the entire campaign configuration from scratch. This is time-consuming, prone to manual errors, and creates a significant barrier to effective quality assurance. Proposed Solution Implement a "Duplicate/Clone" button within the campaign overview. This functionality would allow a user to create an exact copy of an existing campaign’s configuration, rules, and settings, but with a "clean slate." Key requirement: The duplicated campaign should carry over all structural configurations (dates, reward triggers, UI elements) but exclude all historical test data, user interaction logs, and state-specific variables (e.g., "opened" box states). Expected Benefits Increased Efficiency: Drastically reduces the time required for clients to set up testing cycles or launch repeat campaigns. Error Reduction: Eliminates the risk of misconfiguration that comes with manually rebuilding complex campaigns from memory. Improved UX: Encourages clients to thoroughly test their configurations, knowing they can easily spin up a fresh environment without starting over.

Issue Overview We need to optimize the prize distribution mechanism to prevent "Prize Bottlenecking." Currently, the system evaluates winslots sequentially. If a high-volume prize (e.g., Prize 1 with 4,000 slots) has "Opened" but unclaimed slots, the system stays "stuck" on that prize until all its open slots are exhausted. This results in a poor user experience where participants only receive the first prize in the list, even if other prize slots are technically available. Current Logic and Implementation (Standard Prize Distribution) Sequential Checking: The system checks Prize 1, then Prize 2, etc. The "First-In, First-Out" Problem: If Prize 1 generates a new open slot every 4 minutes and the participation rate is lower than that frequency, the system never moves to Prize 2 or the subsequent prizes. Current workaround: Reorder Prizes (Priority-based): Rearrange the prizes from Low to High based on the number of winslots. This prevents a high-volume prize from blocking others. Time Variation: Consider varying the start/end dates or adding "time exemptions" to specific winslots to create gaps.Batching: Divide your prizes into two distinct batches, using a "No Prize" slot as a buffer/divider between them. This should ensure a much more balanced reward experience for their users. But we need to have a feature that would randomly select a slot whenever there are multiple OPENED slots from different winslot-connected-prizes. Proposal Resolution - Weighted Random Selection We propose a shift from sequential checking to a pool-based randomization model. New Logic Requirements: Availability Scan: The system should identify all currently "OPENED" winslots across all prizes connected to the campaign. Randomized Selection: If multiple prizes have at least one open winslot, the system must randomly select a prize from that available pool rather than defaulting to the first one in the list. Frequency Balance: This ensures that even with low participation turnout, users have a fair chance of winning different prizes (e.g., Prize 3 or Prize 5) rather than being stuck on Prize 1 until exhaustion. Business Value: Improved UX: Provides users with reward variety, increasing engagement. Brand Integrity: Ensures that high-value or "rare" prizes are distributed naturally throughout the campaign period rather than being blocked by high-volume/low-value prizes. Reduced Manual Overhead: Eliminates the need for manual prize reordering and complex "time exemption" scheduling by the implementation team.

A UI/UX improvement for the voucher overview section to enhance usability for our end users. Problem Statement Currently, all vouchers—active, expired, and redeemed—are displayed in a single, unified list. As users accumulate more vouchers, this view becomes cluttered, making it difficult to quickly identify which vouchers are currently available for use. Proposed Solution Introduce a tabbed navigation system within the voucher overview to separate vouchers based on their status: Active Vouchers: A tab showing only currently valid and redeemable vouchers. Voucher History: A separate tab containing expired and already-redeemed vouchers. Expected Benefits Reduced Cognitive Load: Users can focus on relevant, active vouchers without distraction. Improved Efficiency: Faster navigation and less time spent scrolling through inactive items. UX Alignment: This aligns with standard practices for loyalty and wallet applications, providing a cleaner, more intuitive interface. Could we review the feasibility of this implementation? Please let me know if you need any additional context. Thanks!

Possibility to gamify a login streak in the app. For example, if you open the app every week for 3 consecutive weeks, you receive reward X; for 4 consecutive weeks, reward Y, and so on. But if you miss a week and don’t open the app, the streak resets back to 0. This would encourage customers to use the app more often and participate in any ongoing campaigns.

Due to strict gaming regulations, it requires the ability to collect and validate a user's (DOB) during the onboarding process to ensure campaign compliance. Request Details: Field Addition: Can we investigate adding a "Date of Birth" field to the platform's standard user schema? Flow Integration: We need to identify the most effective placement for this validation (e.g., during initial registration or as a gate during login). Goals: Confirm the technical feasibility of adding DOB as a mandatory/validated field. Determine where in the registration/login flow this can be seamlessly integrated.

From within the NeoDay Backoffice, it is currently not possible to manually distribute things such as ‘coupons’, ‘customer cards’, ‘survey (reservation)'. In order to do this, we now have to contact a developer to perform such an action. The reason for this ticket is the following use-case (as it happened with Pathé and La Place (NDD-301)). USE CASE (top-down priority) A. Individually reward a coupon to a user via the BackOffice User Lookup tile. B. As a Backoffice User, I would like to distribute Coupon-A to a set of users (segments) that have completed a campaign, So that I can directly give them a coupon with a code on it

Currently, NeoDay supports the IfCompletedManual trigger, which fires only upon full completion. We are requesting the introduction of an IfHalfwayManual trigger (or a "Partial Completion" trigger) to engage users before they reach the end of a manual or guide. Waiting until the end of a manual to trigger an action (like a review request) can lead to missed opportunities. For example, if a user has read 10 pages of a manual, they are already deeply engaged—this is an ideal moment to ask for a review or trigger a milestone reward while the content is top-of-mind. Proposed Functionality Custom Thresholds: Ideally, the "page number" or "progress percentage" should be configurable when adding the trigger to a campaign (e.g., trigger after page 5, or at 50% completion). Simplified Version (Alternative): If dynamic input is too complex for the initial release, a fixed "mid-way" point (50% progress) would still provide significant value over the current all-or-nothing approach. Use Cases Feedback/Reviews: Asking for a rating once the user has demonstrated clear intent and engagement. Gamification: Awarding partial points for reaching milestones within longer educational or onboarding content. Nudge Notifications: Encouraging users who have started but haven't yet finished a manual to complete the remaining sections.