Feature Ideas

Right now there is no way to push coupons directly to a specific group of users from the backoffice. If we want to reward or target a segment with a coupon offer, we have to work around the system. We need the ability to select one or more existing coupons, assign them to a segment, and optionally trigger a notification — all from the backoffice. On the user side, these coupons should appear in a dedicated "Personal offers" section, kept separate from coupons earned through campaigns, which stay under "Earned coupons". Example Epic Jurgen made: PUT-4238

We’re going to develop the means for end-users to register an account by providing their telephone number on which they will receive a SMS containing a Activation Code that they have to fill in during the registration process.

Why your idea is useful: It allows customer service teams to quickly fact-check a customer's loyalty status (e.g., verifying if a user is in the 'Gold' tier) when they reach out with questions or complaints.Who would benefit: Our clients' customer service departments and our own support/backend team, as it eliminates unnecessary internal support tickets.How should it work? When looking up a specific user account in the backoffice, the current loyalty tier should be clearly visible on their profile overview page.

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.

As the platform expands its Tiering service capabilities, there is an increasing need for a dedicated analytical framework to track performance across different levels. Currently, the lack of tier-specific reporting creates a gap in evaluating the success of these offerings. This suggestion outlines the requirement for integrated analytics to bridge that gap. Suggestion: Introduce a comprehensive suite of analytical tools designed specifically for tiered models. This would allow users to move beyond general data and gain insights into segment-specific behavior, migration patterns, and engagement levels within each tier. Specifications: A summary of the proposed logic, key metrics, and reporting visualizations can be found here: Tier-Related Analytical Framework | Documentation Link Value Proposition Closing Functional Gaps: Addresses a vital "missing feature" for any organization currently launching or managing tiered programs. Actionable Insights: Provides the data necessary to justify tier pricing, identify churn risks within specific levels, and optimize the value proposition of higher tiers. Operational Efficiency: Eliminates the need for manual data workarounds by providing a native, automated reporting solution.

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

Why your idea is useful: Customer service agents frequently deal with scenarios where a customer claims they won or deserved a voucher but didn't receive it. Being able to check and manually resolve this directly saves time and keeps customers happy.Who would benefit: Clients' support teams (more autonomy), end-users (faster resolution), and our own backend developers (fewer ad-hoc data requests).How should it work? On the user profile page in the backoffice, there should be a 'Vouchers' section showing a history of linked vouchers. Additionally, an "Issue Voucher" button should be added to allow agents to select and manually assign a voucher to that specific account.

Dynamic Campaign Eligibility (Block/Unblock) User Introduce a control mechanism in the backoffice that allows merchants to dynamically block or unblock specific users from participating in targeted purchase-to-win campaigns. This directly targets the "return loop" vulnerability where bad actors game the system by buying, winning, returning, and repeating. 📈 Business-Side Advantages (The ROI) Plugs Revenue Leakage: Prevents "negative revenue" scenarios by stopping serial returners from exploiting reward payouts. If a customer returns the qualifying purchases after claiming the prize, they can be immediately restricted from future campaigns. Protects Margin & Inventory: High-value reward inventory is preserved for genuine, loyal customers rather than system exploiters. Automated or Manual Risk Management: Manual: Store managers can flag accounts caught abusing policies. Automated (Future Phase): The system can automatically block users if their return-to-purchase ratio exceeds a specific threshold (e.g., returning 80% of items used to claim a reward). Campaign Flexibility: Gives marketing teams the confidence to run high-value, high-reward campaigns without the fear of massive financial exposure from fraud. 🤝 Client/Customer-Side Advantages (The UX & Trust) Fair Play Ecosystem: Legitimate customers often get frustrated when rewards run out because "coupon-clippers" or exploiters drain the prize pool. This ensures rewards go to the rightful community. Grace Period / "Unblock" for Genuine Cases: Honest customers who had legitimate reasons for returns (e.g., defective items, wrong sizes) aren’t permanently banned. The "Unblock" feature allows customer service to easily restore eligibility once the issue is resolved, preserving the customer relationship. Clear, Transparent Rules: It allows the business to update terms of service clearly (e.g., "Accounts with high return rates may be temporarily paused from promotional rewards"), managing expectations upfront.

The objective is to implement an automated, multi-stage in-app onboarding engine that triggers targeted promotional campaigns based on the user's registration age. This feature aims to increase early-stage user retention, drive mobile app adoption, and incentivize real-world behavior or conversions. Sample Flow: After 7 days, a member can participate in a spin the wheel promotion. This promotion would only be visible to that specific member. After 14 days, the member receives a stamp card challenge. They would have 10 weeks to complete it, after which the promotion would automatically disappear from the app.

As a customer viewing my account history, I want to see a single, consolidated entry for an order refund. So that my transaction history remains clean, clear, and easy to understand without confusion. Currently, when a full order refund is processed, the refund is processed and displayed to the customer in incremental line items instead of a single point credit. This creates an unappealing user experience and can lead to customer confusion or support inquiries regarding why the refund is fragmented.

We need to implement an in-app survey within the application for customers to complete after their shopping experience. The collected data must be linked to the Business Intelligence (BI) platform to visualize the results via an analytical dashboard.

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.

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.