...
CONTACTS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1456 | Ability to segment contacts based on nameday/birthday in exactly x days | Improvement | 5.4.1.0 | |
V5-1412 | Enhance security and validations of Self-Service Contact APIs | Enhance security and validations of Self-Service Contact APIs to not allow arbitrary values such as HTML tags and JavaScript code | Improvement | 5.4.0.0 |
V5-1310 | Contact Phone enhancements - trigger phone verification | Ability to set whether contact phone requires verification in order to trigger phone verification process (send otp) and also display if it has been verified | Improvement | 5.4.0.0 |
V5-1306 | Release App - Display contacts referral code in mobile app | Display contacts referral code in mobile app | Improvement | Pending Release (App) |
V5-1236 | Contact Registration Enhancements | Ability to sign-up/sign-in using email and OTP verification | Improvement | 5.4.0.0 |
V5-1233 | Contact Enhancements - New Webhooks for Create Contact & Update Contact | Create two new webhook triggering points: 1) upon Create Contact & 2) Update Contact | Improvement | 5.4.0.0 |
V5-1160 | View Contact's preferred store on Contact page | Have the ability to view contact's preferred store from the back-end on the contact page. Pending UI | Improvement | Candidate Features |
V5-1159 | Enhancement to segment conditions - contact verification status | Create new condition to allow user to create segment to retrieve contacts based on the verification status | Improvement | Candidate Features |
V5-1123 | Manage Multiple Phone Numbers on Contact | At the moment it is only possible to manage / Display a single Phone number on Contact. UI needs to be improved to allow multiple. Example add + New Phone action to allow another phone number to be added. | Improvement | Candidate Features |
V5-1119 | Preferred Communication Language - enhancements | Addition of Preferred Communication Language as a Contact Registry Attribute Addition of Preferred Language on Contact page Core behaviour: the system sends communication in the language of the Contact' preferred language. If not configured then use default. | Improvement | 5.3.5.0 |
V5-1114 | Contact enhancements - Backoffice operations & Activity Feed | Enhance backend system to provide summary screens for financial and reward transactions. Enhance Contact Activity Feed module with UI / UX improvements | Improvement | 5.4.2.0 |
V5-1085 | Segment Enhancements |
| Improvement | 5.4.1.0 |
V5-1062 | Enhancement to Contacts - Add Google Place ID field | Show Google Places ID field on Contacts -> Address section. Field is populated when address from google is selected and is editable. | Improvement | 5.3.4.0 |
V5-1016 | Allow Upload of Avatar from Self Service. | Images to be used for avatar do not require the overhead of the complex flow required including media_groups and multiple scaling. The signature will allow a single file upload with any server to server communication if using cloudinary ignored. The Mobile Client should use a image scaling component and upload a single file that can the update the contact table with a single URL. | Improvement | 5.3.2.0 |
V5-949 | Consumer - Ability to sign-up with Google | Ability to sign-up with Google | Improvement | |
V5-859 | Cash as a payment method is optional | Ability to disable cash as a payment method / Investigate to do with no config Add configurability on backend to specify allowed payment methods at level of business. Add section under finance configuration and call it Payment settings. For now specify only allowed payment methods Amend core behaviour of list payment methods to return the specific cards or accounts of contact plus the option of cash if cash is enabled Amend app and portal to display cash only if returned in list payment | Improvement | 5.3.0.0 |
V5-847 | Preferred Merchant new feature | Ability to configure whether contact can select a preferred merchant for ordering and a preferred merchant for rewards and customer care. | Improvement | 5.3.0.0 |
V5-772 | Contact's Country of Agreement | Ability to support multiregional contact registry, where contacts can register against a country | New Feature | 5.3.0.0 |
V5-727 | Ability to search by Contact Email Address | Include Email address in search criteria for a Contact | Improvement | 5.3.0.0 |
V5-716 | Contact Enhancements | Ability to display (UI) whether contact email has been verified | Improvement | 5.2.4.0 |
V5-697 | Enhance Payment methods to have JCC as an option for refunds | Ability for cardholder to provide a card for card linked rewards that is hashed and can be refunded | Improvement | 5.3.0.0 |
V5-694 | Terminate account enhancement | Ability to merge accounts and the wallet balance | Improvement | 5.2.3.0 |
V5-552 | Import industries and industry sectors | Ability to import pre-defined industries and industry sectors. | Story | Candidate Features |
V5-551 | Ability to activate pre-defined name days | Ability to load default name days of the system with option to add more. | New Feature | 5.4.0.0 |
V5-375 | Contacts Financial Actions | Financial actions available for Contacts. Create new account - Create a new account for the current contact. | Story | 5.1.0.0 |
V5-325 | Payment Methods and Refund Methods | A payment method represents the way a contact can credit their account or wallet. Payment methods are defined at the level of the Contact and it is mandatory to define at least one payment method per contact. A pre-defined list of payment methods is supported which includes: A contact can have multiple payment methods registered in CRM.COM. A ‘primary’ payment method can exist and an optional ‘backup’ payment method can also be specified. The primary payment method is used by default in online (automatic) payments and if the payment fails, then the backup method is used. Payment methods can be added, updated and removed at any time. Primary payment method Opt-in for purchases and subscriptions | Story | Candidate Features |
V5-109 | Contact Identification based on Loyalty Card Enhancement | Loyalty identifiers provide the ability to external systems (e.g. POS) to identify contact that participate on a business reward scheme in usually a face to face (over the counter) manner | Story | 5.2.0.0 |
V5-81 | Payment Methods for Contacts | Ability to define payment methods for contacts and process payment with PCI compliance via payment gateways such as Stripe, PayEasy, PayPal, JCC. | Story | 5.2.2.0 |
V5-10 | One Time Password (OTP) | Generate and send OTPs to contacts via SMS and email in order to authenticate a contact. | Story | 5.1.0.0 |
V5-9 | Customer Identification medium (CIM) | A customer identification medium is a set of fingerprints (card numbers, mobile phone number, email, pass code) that enable applications (i.e. external systems) to submit transactions for contacts using the contact CIM as a contact identifier. A customer identification medium should not be confused with an authentication service, as it's sole purpose is to provide an alternative means of identifying a customer from an already established (authorised) external system. | Story | 5.1.0.0 |
V5-8 | Categorisation | Categorise contacts into generic groups based on specific similar attributes that they share. | Story | 5.1.0.0 |
V5-7 | Managing and controlling data protection regulations including GDPR. | As part of data protection the following actions and processes are available: Contact Consent, Anonymizing Contacts and Deleting Contacts. | Story | 5.1.0.0 |
V5-6 | Marketing Authorisations | Contact authorisation settings are used to define how to manage contact in relation to internal or external activities of the company. More specifically, each contact has the ability to specify (opt in) whether he/she wants to receive emails or sms. | Story | 5.1.0.0 |
V5-2 | Create/Update/View Contact | Create, update and view contacts and their details. Create and update a contact following the rules setup for mandatory data to be captured. | Story | 5.1.0.0 |
V5-77 | Pre-configured Segments | A list of pre-defined segments ready for use. These include segments for Rewards, Subscriptions, Contact Accounts. | Story | Candidate Features |
V5-76 | Segmentation Integrations | Integration to Mixpanel - an analytics software that tracks user interactions with web and mobile apps. | Story | 5.1.0.0 |
V5-75 | Export the Results of a Segment to Mailchimp | Export the results of a segment to Mailchimp marketing platform. | Story | 5.1.0.0 |
V5-74 | Import Contacts for a Segment | The user can add contacts to a segment using the import process as opposed to defining conditions. The imported contacts are considered the result of the segment. | Story | 5.1.0.0 |
V5-73 | Preview a Segment | Preview a segment to see the results, i.e. the list of contacts meeting the segments conditions. | Story | 5.1.0.0 |
V5-72 | Refresh a Segment | A time interval can be set whereby each segment will be refreshed automatically therefore recreating the segment. However, it's also possible to refresh a segment manually. | Story | 5.1.0.0 |
V5-71 | Segment Groups | A segment's conditions can be separated into groups and can be combined or not using the AND/OR operators. | Story | 5.1.0.0 |
V5-70 | Segment Conditions | A segment's conditions determine how and which contacts will be retrieved, multiple conditions can be specified by the user. | Story | 5.1.0.0 |
V5-69 | Create, Update, View Segment | Create and maintain a segment and it's conditions. | Story | 5.1.0.0 |
V5-2406 | Ability for a back office user to request and validate one-time-password and sign up a contact to a business | Ability to request a one-time-password for a specific contact. The request sends an OTP to the contact’s email address or primary phone number that can be used to verify the contact. | New Feature | 5.4.5.4 |
V5-2227 | Add an existing person contact for People section | Ability to select an existing person contact for the People section for a company contact. | Improvement | 5.4.5.2 |
V5-2205 | Enhance segment to be able to segment based on Account classification | Account classification filter for segmentation. | Improvement | 5.4.4.2 |
V5-1990 | Enhancement to inputting and storing phones in front-end systems and back-end | Backend enhancements Release app enhancements | Improvement | 5.4.4.0 |
V5-1908 | Ability to create and update payment methods for contacts with a back office API | Ability to add/update a payment method for a contact (person or business) with a back office API | New Feature | 5.4.5.0 |
V5-1792 | Communications and Integrations core behaviour | Refer a friend email communication to be sent with Service Owner integration. SMS communication to remain at Business level. | Improvement | 5.4.3.1 |
V5-1786 | Ability for a Business to set default spend preferences | Ability for a Businesses to setup Automatic Spend Preferences for their contacts, these will be enabled by default upon registering, and also set default values for automatic spend. | New Feature | 5.4.4.0 |
V5-1418 | Concurrent Session Policy | Ability to configure maximum allowed number of concurrent sessions for contact and users. | Improvement | 5.4.5.0 |
V5-1393 | Contact Activity Feed enhancements | Improve activity feed to show the most relevant information on 2 lines without the need to expand/collapse rows. | Improvement | 5.4.3.1 |
V5-1125 | Ability to register a Contact with a gift card and no KYC | Ability to register a Contact with a gift card and no KYC | Improvement | 5.4.5.0 |
V5-867 | Ability to delete primary payment method |
a. If there is a back-up payment method then that automatically becomes the primary payment method | Improvement | 5.4.3.1 |
V5-325 | Payment Methods and Payouts | A payment method represents the way a contact can credit their account or wallet. Payment methods are defined at the level of the Contact and it is mandatory to define at least one payment method per contact. A pre-defined list of payment methods is supported which includes: A contact can have multiple payment methods registered in CRM.COM. A 'primary' payment method can exist and an optional 'back-up' payment method can also be specified. The primary payment method is used by default in online (automatic) payments and if the payment fails, then the backup method is used. Payment methods can be added, updated and removed at any time. Primary payment method Opt-in for purchases and subscriptions | Story | 5.4.5.0 |
V5-1312 | Ability to resend email for email verification | Resend email for verification purposees. | Improvement | 5.4.0.0 |
V5-2105 | Contact Approvals for Orders | Ability for a contact to approve/reject an order's progression using default communication sent via CRM.COM Approval on Order Status Change automation | Improvement | 5.4.6.2 |
V5-1922 | Anonymise Contact and Delete Contact | Ability to perform admin and operational actions, such as delete contact (and all data) and anonymise contact | Improvement | 5.4.6.2 |
V5-2899 | Ability to upload attachments for Contacts | Ability to upload attachments for Contacts. Documents to be uploaded using back-office and self-service Web APIs | Improvement | 5.4.6.4 |
V5-3095 | Ability to send a contact's statement through a Communication Plan | Communication plans can be configured to send contact statements
A new dedicated communication tag is used to implement the above behaviour. | Improvement | 5.5.1.0 |
V5-2902 | Contacts Enhancements | Ability to search for a contact using their account number (as a search value) | Improvement | 5.5.1.0 |
V5-3050 | Devices Usability Enhancements | Ability to register a device for a contact and update a contact's device characteristics from the back-end | Improvement | 5.5.2.0 |
V5-2435 | Include Spend cancellation entry in Contact Activity Feed | When cancelling a purchase transaction that had a spend, a purchase cancellation is logged. Include an entry for cancellation of spend under both the 'Activity Feed' and 'Financial Events'. | Improvement | 5.5.2.2 |
V5-3455 | Ability to segment subscribers based on their services' quantities | Ability to segment subscribers based on their services' quantities - Include each service's quantity in contact profiles and modify it on quantity change | Improvement | 5.5.3.0 |
V5-3380 | Ability to search for a contact using the full phone number | Ability to search for a contact using the full phone number, i.e. combining the country code and the phone number (e.g. 35799778866). | Improvement | 5.5.3.2 |
V5-3206 | Active Contacts Metric | Implement Active Contacts metric for Contacts Dashboard | Task | 5.5.3.3 |
V5-4179 | Communities CRM.COM Wallet & Usage Consumption Enhancements | Ability to set up Communities where members have access to consuming usage and use CRM.COM wallet | New Feature | 5.6.0.0 |
CUSTOMER EVENTS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1496 | Ability to support self-submit purchases | Ability to support self-service purchase for reward purposes | New Feature | 5.4.2.0 |
V5-1343 | Aggregate same product SKU with same unit price in multiple lines in same purchase event | Aggregate same product on multiple lines in same purchase event as one line with aggregated quantity | Improvement | |
V5-422 | Consumer Self-Service Purchase Customer Events | Ability to identify and process purchase customer events through consumer self-service process | Story | 5.2.2.0 |
V5-118 | Enhancement of TAP to support IP Address | Ability to set IP Address on organisation TAPs to handle ESC/POS integrations | Story | 5.2.2.0 |
V5-111 | Customer Event Classifications | Ability to categorise customer events (e.g. purchase) based on similar characteristics using customer event classifications | Story | 5.2.0.0 |
V5-38 | Referral Customer Event | Referral events are created when an existing customer introduces a friend to the business, resulting in new customers signing-up to one of the available reward schemes. | Story | 5.2.0.0 |
V5-2392 | Customer Events Engine | Processes customer events from external systems in their native format and creates CRM.COM customer events (purchase event and achievement event) | New Feature | 5.4.6.0 |
V5-1644 | Ability to create purchase event from the backend | Ability for back-end users to create purchase customer events in order to perform correction actions on customers purchase activity | New Feature | 5.4.6.1 |
V5-3213 | Customer Events Reclaim Enhancements | Ability to reclaim a purchase customer event using a human readable code | Improvement | 5.5.2.0 |
V5-3912 | Purchase Quantity Enhancements | Ability to support decimal based quantities on purchase events | Improvement | 5.5.4.1 |
...
ORDERS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1449 | Include operational details in Order fulfilment Web API | Include operational details of an organisation's opening hours in Order fulfilment Web API | Improvement | |
V5-1448 | Include creatives in Get Order Web API | Include product creatives in Get Order Web API for the ordered items | Improvement | |
V5-1434 | Ability to specify different payment methods for each supply method | Improvement | 5.4.1.0 | |
V5-1401 | Coverage with map coordinates | Ability to define delivery coverage via coordinates on a map (define map area) | New Feature | 5.4.3.0 |
V5-1388 | Ability to retrieve product dependencies during ordering | Ability to retrieve product dependencies on purchasing a termed service. Any required services or physical goods are provided so as to also be included in the order prior checkout | Improvement | 5.4.0.0 |
V5-1384 | Exclude expense and usage services from orders | Usage and Expense services must be excluded from the ordering process since they cannot be purchased. Expenses are applied based on business rules, whereas Usage service is consumed through one-time/termed services | Improvement | 5.4.0.0 |
V5-1334 | Filter Promotions based on organisations | Filter Promotions based on organisations | Improvement | 5.4.0.0 |
V5-1305 | Ability to specify the amount to be used from wallet funds | Ability to specify the amount to be used from wallet funds | Improvement | 5.4.0.0 |
V5-1304 | Enhance Order details report to support multiple payment methods | Order details report should be enhanced to support multiple payment methods when multiple payment methods are applied on an order purchase | Improvement | 5.4.3.0 |
V5-1295 | Products / Orders |
| Improvement | 5.3.5.0 |
V5-1285 | Ability to re-print order ticket | Orders will be marked as printed if printing was successful. icon in summary screens will show which orders were printed | Improvement | 5.3.5.0 |
V5-1268 | Enhance /estimates/orders Self-Service and Back-Office APIs according to spec | Enhance /estimates/orders Self-Service and Back-Office APIs according to spec | Improvement | 5.4.1.0 |
V5-1254 | Orders display mode configuration | User should have the ability to set display mode on the orders page once and each time user visits the page to have the mode of their preference. | Improvement | Candidate Features |
V5-1228 | Ability to auto refresh Orders summary page | Ability to auto refresh Orders summary page | Improvement | 5.4.0.0 |
V5-1221 | Enhance /estimates/orders apis to consider selected payment method for promotions | Enhance /estimates/orders APIs to consider selected payment method to apply promotions | Improvement | 5.3.4.0 |
V5-1204 | Enhance Self-Service POST /orders API to re-calculate estimated delivery/pick-up time | Enhance Self-Service POST /orders API to re-calculate estimated delivery/pick-up time. | Improvement | 5.3.4.0 |
V5-1117 | Ability to accept contact's current location (address, coordinates) and display in Orders | Enhancement to Self-Service /estimates/orders and /orders/\{id} APIs | Improvement | 5.3.4.0 |
V5-1021 | Enhancements on order taking to handle product characteristics | Handle API and UI. Characteristics are billing period, trial period, termed period | Improvement | 5.4.1.0 |
V5-826 | Fulfilment Policy Enhancements - Expiration of Orders | Improvement | Candidate Features | |
V5-778 | Improved UI for Orders | Enhancements to backend UI for Orders | Improvement | 5.3.0.0 |
V5-760 | Automatically update Orders to Complete status | Ability to configure to automatically set order status to Completed when X time (minutes, hours, days) has passed after Ordering average completion time. | Improvement | 5.2.4.0 |
V5-713 | Ability to set preferred venue/merchant for order delivery |
| Improvement | 5.2.3.0 |
V5-673 | Enhancements to the Order screen |
| Improvement | 5.2.1.2 |
V5-672 | Add Notes to the bottom of the printed Order ticket | Add Notes to the bottom of the printed Order ticket under Total Items. | Improvement | 5.2.1.2 |
V5-481 | Activities for Orders | Activities that need to be scheduled to complete an order (e.g. installation). | Story | |
V5-480 | Clone an Order | Orders can be cloned, i.e. used as a template for creating additional orders with similar items for a different contact. | Story | Candidate Features |
V5-476 | Setup your Order Milestones | Setup multiple milestones based on payments which are expected to be made to pay off an order in instalments based on the fulfilment policy. When a milestone due date is reached the billing process will generate an invoice for the necessary payment and identify the milestone as paid when the payment has been received. Point of no return Prior to reaching the Point of no Return (date), all items, including those that may have already been delivered can be returned to the company, the contact will not be billed, and the order will be cancelled. On the other hand, if the Point of no Return has been reached, then any items that have been delivered cannot be returned - they will be billed and paid for, while any undelivered items will not be delivered nor billed and the remaining order will be cancelled. The Point of no return applies while the order is in progress, i.e. once delivery of items begins. | Story | 5.4.5.0 |
V5-475 | Orders Fulfilment Policies | A fulfilment policy is set up for an organisation and is by default inherited by all of the organisation's members (merchants, subsidiaries, venues etc.) unless a separate policy is set up for a specific member. A separate fulfilment policy can be setup for delivery, pick-up and on-site (dine-in). Users can set the minimum cost for an order to be accepted, define how and when orders can be fulfilled as well as which products can be ordered based on their availability. Charges per supply method can also be defined (e.g. a delivery charge). Completion Rules Venues Operational Hours | Story | 5.2.2.0 |
V5-474 | Create and Amend Orders | Orders can be placed by contacts (using an app) or by users of the system. In either case an order progresses through the various life cycle states until it is either Completed or Cancelled. An estimated completion date/time is calculated for each order and the payment is processed according to the customer's payment method. Any overdue orders can also be identified by the system. If an order is amended prior to reaching the completed or cancelled states, then the total amount will be recalculated. | Story | 5.2.0.0 |
V5-359 | Product Catalogue for Subscriptions | Product Catalogue includes service products that can be purchased by subscribers, as well as expenses which are applied to subscribers in the form of penalties or fees. Product catalogue includes business rules that define how these products should be purchased: Dependencies between products.
Tiering of products
Services Pricing
| Story | 5.4.1.0 |
V5-2084 | Ability to dispatch items for an order | Order items are dispatched against an order and result in a stockout transaction. | Improvement | 5.4.5.0 |
V5-2365 | Display Total before discount on order ticket. | Enhance Order ticket to include: | Improvement | 5.4.5.3 |
V5-2268 | Backend Ordering enhancement, display modifiers section AFTER a variant product is selected | Display modifiers section AFTER a variant product is selected and based on modifiers of selected variant product | Improvement | 5.4.5.2 |
V5-2086 | New view options for Orders summary screen | Updates required to Orders list view/Kanban view. New Kanban view linked to queue types. New detailed order summary page. | Improvement | 5.4.5.0 |
V5-2085 | Ad hoc discounting | Ad hoc discounts for Service Requests and Orders. | Improvement | 5.4.5.3 |
V5-2083 | Point of No return | Implement the point of no return for orders. | Improvement | 5.4.5.0 |
V5-2082 | Updates to Orders | Ability to change certain details of an order once an order is created and change order statuses. | Improvement | 5.4.5.0 |
V5-1986 | Include conditions in Order Fulfilment policy expenses | Provide the ability to set up conditions on when an expense will be applied during ordering. Currently the supply method is already a condition. The order's amount should be added (order amount before the discount) | Improvement | 5.4.4.1 |
V5-1981 | Include Product Notes in Order ticket | Notes for orders | Improvement | 5.4.4.1 |
V5-1797 | Enhancement to provide detailed promotion information in invoicing | Include promotion information when invoicing | Improvement | 5.4.3.2 |
V5-1701 | Enhance Self-Service Order fulfilment response with estimated delivery/pickup time | Enhance Self-Service Order fulfilment response with estimated delivery/pickup time so that order fulfilment checks can be removed from order estimates. Required for mobile app ordering flow | Improvement | 5.4.3.1 |
V5-1685 | Ability to create default fulfilment policy upon new Business sign-up. New Direct Sale supply method | A default fulfilment policy will be created when a new Business signs-up. | Improvement | 5.4.4.2 |
V5-1602 | Enhance order to include whether order paid in full or partially with wallet funds | Order enhancement to include amount partially paid using wallet funds and amount partially paid using another payment method | Improvement | 5.4.3.1 |
V5-479 | Ability to have Separate Queues for your Orders | Ability to setup different order queues with each queue having its own workflow of states. Setup the business characteristics of orders to be fulfilled by each queue, for example B2B orders assigned to 'Wholesale' queue, and B2C orders assigned to 'Retail' queue. | Story | 5.4.5.0 |
V5-477 | Orders Quotation | A Quotation provides a formal estimation of an order's cost that includes all physical goods, expenses and services that the contact is interested in buying. In other words, the quotation is a preliminary form of the order's invoice | Story | 5.4.5.0 |
V5-476 | Orders milestone and progress based invoicing | Support for invoicing based on preset milestones or based on progress of delivered services and products. | Story | 5.4.5.0 |
V5-2274 | Ability to define on front-end systems whether to allow purchases only if requested spend amount is fully covered with available wallet balance | Ability to define on front-end systems whether to allow purchases only if requested spend amount is fully covered from the available wallet balance.
| Improvement | 5.4.5.2 |
V5-1405 | Purchases & Business Network | Posting purchase against an organisation should allow only purchases of organisations within the business network | Improvement | 5.4.0.0 |
V5-2633 | Using Wallet funds on ordering improvement |
| Improvement | 5.4.6.2 |
V5-2632 | Improved use of account funds on placing the order | Improved use of account/wallet funds on placing an order
| Improvement | 5.4.6.2 |
V5-2105 | Contact and User approvals for orders | Ability for a contact and/or user to approve/reject an order's progression via CRM.COM Approval Request automations | Improvement | 5.4.6.3 |
V5-2903 | Ability to set up automations on order stage change | Ability to set up automations which are triggered upon changing the stage of an order | Improvement | 5.4.6.4 |
V5-3056 | Orders & milestones enhancement | Display Order milestones (whether invoiced or not) on Order screen | Improvement | 5.5.0.0 |
V5-2438 | Order Attachments | Ability to add attachments on an order | Improvement | 5.5.1.0 |
V5-480 | Clone an Order | Orders can be cloned, i.e. used as a template for creating additional orders with similar items for the same or a different contact. | Story | 5.5.2.1 |
V5-480 | Clone an Order | Orders can be cloned, i.e. used as a template for creating additional orders with similar items for the same or a different contact. | Story | 5.5.2.2 |
V5-3622 | Search for orders based on their address | Ability to search for an order using its delivery address. New 'Address' filter option added | Improvement | 5.5.3.2 |
V5-3416 | Ability to change an Order's Delivery address | Ability to change an Order's Delivery address before its completion. Changing the delivery address is allowed only if no items have been sent out to the contact. Order fulfilment estimation should be triggered again to ensure that the order can still be fulfilled at the new delivery address | Improvement | 5.5.3.2 |
V5-3606 | Improved Orders management | Ability to amend order items and milestones, provided a point of no return is not reached | Improvement | 5.5.3.2 |
V5-4295 | Ability to set up and use Event-based Charges for Orders | Ability to set up and use Event-based Charges for Orders. In addition, introduce the ability to charge an extra expense on a delivery Order based on the distance | New Feature | 5.6.0.0 |
V5-4287 | Product Ordering & Commerce Spend Restrictions | Ability to support (per product) the max wallet commerce amount that can be spent during ordering | Improvement | 5.6.0.0 |
PASSES | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1453 | Create a filter in automations to differentiate between Top-up and Gift passes | Ability to create automations based on pass type (Gift or Top-up). At the moment the filtering options in Automations don't allow this. | Improvement | 5.4.2.0 |
V5-1409 | Encryption of pass codes | Generated pass codes should not be visible from the back end, they should be encrypted throughout their life cycle. | Improvement | Candidate Features |
V5-884 | Passes Enhancements | Changes to the way passes are configured and generated. | Improvement | 5.4.0.0 |
V5-172 | Redeem a Pass | Redeeming a pass is the process whereby a contact uses their pass either to get a discount at the time of purchase, or to top-up their wallet with the value of the pass. Only passes in 'Active' state can be redeemed. If OTP validation is required the user can instantly generate an OTP for verification. | Story | 5.2.0.0 |
V5-171 | Managing Passes | It's possible to manage a whole pass plan or just an individual pass. Activate generated passes Pass cancellation Change pass expiration | Story | 5.2.0.0 |
V5-170 | View a Pass Lot | Viewing a lot displays all passes generated by the specific lot, their current state, recipient details, usage and expiry information, and method of communication. | Story | 5.2.0.0 |
V5-169 | Create a Pass Plan | The only way to generate one or more passes is to create a pass plan for a specific pass type. Setup includes:
| Story | 5.2.0.0 |
V5-168 | Pass Product Conditions (for Gift & Top-up Passes) | A list of product SKUs or product families that the value of the pass can be consumed on. | Story | 5.3.0.0 |
V5-167 | Passes / Top-up Pass | A top-up pass is used to top-up an existing contact’s wallet with an additional amount of money. Validity: Generic settings:
Passes format: | Story | 5.3.0.0 |
V5-166 | Passes / Gift Pass | A gift pass provides an amount of money to the contact either to be redeemed for their own benefit, therefore crediting their own wallet (for registered contact), or for use as a gift card loaded with funds (for non-registered contacts). Validity Generic settings:
Passes format: | Story | 5.3.0.0 |
V5-165 | Create and Maintain Pass Types and Passes | Create a pass type of a specific classification, choose from PROMOTION, GIFT and TOP-UP. Passes once created can have one of four life cycle states: | Story | 5.3.0.0 |
V5-110 | Passes / Promotion Pass | As the name implies, these passes are issued as part of a promotion campaign or rewards offer and target (in the form of criteria) products, services and contact segments. Validity: Generic settings:
Pass codes format: For Promotion passes, the value (amount/percentage) that the contact will benefit from is specified in the promotion or rewards offer a definition. | Story | 5.2.0.0 |
V5-2413 | Ability to re-use same pass plan prefix | Allow a configuration of a second pass plan using the same pass code prefix as another pass plan definition. | Improvement | 5.4.5.4 |
V5-2088 | Hashing of Passes |
| Improvement | 5.4.4.1 |
V5-1955 | Enhancements to Passes to handle lost Gift pass scenario | Changes to Passes to accommodate the case of a lost Gift pass for a registered Contact (i.e. with identification details). | Improvement | 5.4.4.1 |
V5-2800 | Ability to specify custom fields for Passes |
| New Feature | 5.4.6.3 |
...
PRODUCT CATALOGUE | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1452 | Products as Controllable Entity Enhancement | Support the ability for a business to allow its products to be used across business network (as controllable entity) | Improvement | 5.4.1.0 |
V5-1396 | Ability to filter Product Categories on the organisation that owns the products | Ability to filter Product Categories on the organisation that owns the products | Improvement | 5.4.0.0 |
V5-1381 | Ability to retrieve product tier rules | Ability to retrieve product tier rules when a contact requests for an upgrade or a downgrade of the subscribed services | Improvement | 5.4.0.0 |
V5-1331 | Ability to restrict products for ordering based on organization that owns the product | Ability to restrict products for ordering based on organization that owns the product | Improvement | 5.3.5.0 |
V5-1330 | List Product enhancement - Restrict products that are modifiers from product/order catalogue | List Product enhancement - Restrict products that are components from being selected for ordering | Improvement | Pending Release (Backend) |
V5-1299 | Ability to define more than one product family on products | Ability to define more than one product family on products | Improvement | Candidate Features |
V5-1294 | Enhance Product catalogues to handle collections and supply role | Ability to group products into order catalogues and the organisations that have access to those order catalogues | Improvement | 5.4.1.0 |
V5-1273 | Ability to differ a price by merchant / venue | Improvement | Candidate Features | |
V5-1187 | Ability to search products using product family filter | Ability to search products using product family filter | Improvement | Candidate Features |
V5-910 | Check product pricing and taxes | Improvements on tax exclusive or inclusive and applying tax on a contact | Improvement | 5.3.1.0 |
V5-897 | Product Promotions | Ability to configure Promotions to enable Products / Services to be discounted. | Improvement | 5.3.1.0 |
V5-861 | Enhancements to Product Synchronisation settings modal | Enhancements to Product Synchronisation settings modal. | Improvement | |
V5-857 | Product type 'classification' to be returned by self-service and back-office APIs | Amendment to self-service and back-office APIs to return the product classification. | Improvement | |
V5-793 | Ranking for Product Components & Variants, define default variant | Ability to rank order of components, order of component options, order of variant attributes | New Feature | 5.4.1.0 |
V5-471 | Product Type Enhancements | Ability to provision products Defines if products of a type are used for provisioning purposes by third party providers which are integrated with CRM.COM Software. Available for:
| Story | Candidate Features |
V5-470 | Product Tags | Define tags for products and promotions and use them to group products/promotions based on similar characteristics that enable tracking, managing and promoting the products/promotions (e.g. food, drinks, Base TV service). | Story | Candidate Features |
V5-469 | Product Promotions old | Promotions define discounts that can be automatically applied on product sales or during billing, given that a set of conditions are met. Promotions can be auto-applied if the conditions are met or presented to contacts or agents as (selectable) offers during a purchase or placing an order. | Story | 5.3.0.0 |
V5-468 | Product Synchronisation | This process is responsible for synchronising (creating and updating) products between a third-party system and CRM.COM.. The process automatically s syncs products from the master system (third-party system, i.e. POS) to the destination system (CRM.COM). | Story | 5.2.0.0 |
V5-467 | Product Pricing | Pricing determines how a product will be priced based on the various parameters that can affect the price. Multiple prices can be configured for products, based on the rate model (flat, tiered, volume), the tax model (tax inclusive or exclusive), whether the product is sold individually or as part of a bundle, the currency, the supply method (delivery, pick up, on-site/dine-in, the countries in which the price will be applied (based on the contact's billing location). | Story | 5.1.0.0 |
V5-466 | Create and Maintain Products | Define the products that a business can sell or deliver to its contacts. Products can be sold individually, awarded through reward offers, sold as part of a subscription, or consumed as part of a subscription. A product has a unique SKU, name and validity period. Product Types Composition method & Variants Product Classifications Up Sell & Cross Sell Products | Story | 5.1.0.0 |
V5-2533 | Ability to use 'hours' as billing period when creating products of type 'one time service' | Ability to use 'hours' as billing period when creating products of type 'one time service' | Improvement | 5.4.5.8 |
V5-2089 | Ability to define a Display Name for Product Categories, Families, Types & Component Sets | Ability to configure a display name for
If no display name is provided then the name is set as the display name | Improvement | 5.4.4.1 |
V5-2001 | Ability to configure the modifiers of variant products | A Variant product can have different modifiers compared to its composite product | Improvement | 5.4.4.0 |
V5-1983 | Ability to edit the Product Type of a Product | Ability to amend the Product Type of a Product to a Product Type of the same classification. | Improvement | 5.4.4.1 |
V5-1693 | Enhanced Promotions conditions and offerings | Enhanced Promotions basket conditions and offerings
| Improvement | 5.4.4.0 |
V5-1683 | New 'Component Sets' for products | New feature Component Sets will allow for products to be easily grouped together and used as add-on components to products. | New Feature | 5.4.3.1 |
V5-1583 | Ability to include services and physical goods within a bundle | Ability to include services and physical goods within a service bundle (fixed or flexible) | New Feature | 5.4.4.2 |
V5-1330 | List Product enhancement - Restrict products that are modifiers from product/order catalogue | Restrict products that are modifiers from being selected for ordering | Improvement | 5.4.4.0 |
V5-1000 | Products list enhancements |
| Improvement | 5.3.3.0 |
V5-2679 | Ability to keep track of applied promotions per contact | Ability to keep track of applied promotions per contact. A promotion is applied for a contact:
In the case of applying a promotion for a termed service, then the applied promotion (per contact and per service) will be utilised by the billing run process to ensure that the contact receives the discount for the correct period of time, enhancing thus the billing run's performance since promotions will not be re-evaluated in each run. | Improvement | 5.4.6.2 |
V5-2542 | Enhanced Subscription Promotions |
Advanced Subscription Promotions
| Improvement | 5.4.6.2 |
V5-1848 | New Price rate models: Tiered, Volume, Stairstep | New Price models: Tiered, Volume, Stairstep | Improvement | 5.4.6.2 |
V5-2679 | Ability to keep track of applied promotions per contact | Ability to keep track of applied promotions per contact. A promotion is applied for a contact either:
In the case of applying a promotion for a termed service, then the applied promotion per contact and per service) will be utilised by the billing run process to ensure that the contact receives the discount for the correct period of time, enhancing thus the billing run's performance since promotions will not be re-evaluated in each run. | Improvement | |
V5-1848 | New Price rate models: Tiered, Volume, Stairstep | New Price models: Tiered, Volume, Stairstep | Improvement | 5.4.6.3 |
V5-2877 | External reference codes for products | Product catalogue setup includes an external reference code for products. | Improvement | 5.4.6.4 |
V5-3115 | Search products based on categories and their sub-categories | Provide the ability to search for a product using either a category or a sub-category. | Improvement | 5.5.1.0 |
V5-3066 | Enhancements in setting up and and applying a Dependency rule | Multiple Dependency rules can be configured per Product/Product Type instead of a single one. When multiple rules are configured, then all of them must be met. Within a rule, operator All/Any determine how the specified dependencies will be evaluated (all required product exists or at least one of the specified) | Improvement | 5.5.1.0 |
V5-3169 | Product Ownership Enhancements | Ability to support duplicate products (SKU based) across the business network, but maintaining uniqueness on the organisation level (different product with same SKU per business/merchant) - configurable on the business level. The customer events engine should identify a product and it's owner, based on the related 'fulfilled by' organisation and if such a product does not exist (neither on merchant organisation, nor on business level), then it should be created automatically with the 'fulfilled' by organisation as the owner. | Improvement | 5.5.2.0 |
V5-2859 | Product Sync | Have the ability to define the TAP for the product sync API as a request with core behaviour to create such product with merchant as owner.
| Improvement | 5.5.2.0 |
V5-3428 | Ability to keep a label per product price | Ability to keep a label per product price to improve usability in cases where a business has multiple prices with various conditions. A price's label is also available through the Ordering flow (when placing a new order, viewing or amending an existing one) | Improvement | 5.5.3.0 |
V5-2718 | Enhanced Product Catalogue usability | Various enhancements required when setting up the product catalogue: 1) Products
2) Prices
| Improvement | 5.5.3.0 |
V5-3568 | Ability to apply promotions based on already subscribed services | Provide the ability to set up a promotion that gives a discount to a basket service based on services that the contact has already subscribed to. The contact can benefit from this promotion for the newly ordered service as long as they are still subscribed to the specified service(s) | Improvement | 5.5.3.3 |
V5-3330 | Pricing support for B2B models | Support for B2B models including:
| New Feature | 5.5.3.3 |
V5-3527 | Stock Balance Enhancements | Ability to support products (non-traceable but stockable or traceable) with zero or no balance, and metrics for reserved, dispatched, rented, ownership, available for sale/rent, on stock balance summary page and report | Improvement | 5.5.3.3 |
V5-4206 | Ability to set up custom fields for Products | Ability to set up custom fields for Products | Improvement | 5.5.4.5 |
V5-3285 | Enhanced Product Catalogue | Product Catalogue enhancements
| Improvement | 5.5.4.5 |
REWARDS CORE
Issue Key
Summary
Description
Issue Type
Release
V5-1436
Ability to upload images for reward tiers
V5-3285 | Enhanced Product Catalogue | Product Catalogue enhancements
| Improvement | 5.6.0.0 |
REWARDS CORE | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1436 | Ability to upload images for reward tiers | Business users should be able to upload one marketing image for each reward tier | Improvement | 5.4.1.0 |
V5-1392 | Rewards events back office feature | Ability to view all rewards events (purchase, referral, signup, achievement, just money, lottery, profile completion) and how each event performed and processed (its awards, any spends, any cancellations. | New Feature | 5.4.2.0 |
V5-1391 | New APIs for rewards events | New reward events APIs to be used by back office roles and functions to reconcile and audit reward activity. | New Feature | 5.4.2.0 |
V5-1286 | Default configuration for enabling reward tiers | Enable Reward tiering by default upon creation of a new business | Improvement | 5.4.3.0 |
V5-1188 | Ability to have additional recurring options on reward achievement offer types | Ability to have additional recurring options on reward achievement offer types i.e. run every 1 hour | Improvement | Candidate Features |
V5-1105 | Default Automatic Spend Conditions | Ability to configure (per Business) default contact automatic spend conditions and set to each newly registered contacts | New Feature | Candidate Features |
V5-1056 | Back-End Reduction on default payment method | Ability for back-end reduction to refund first on payment method of the purchase, otherwise on the primary payment method (if allows refund) | Improvement | 5.3.1.1 |
V5-1047 | Wallet Fee Core Behaviour Enhancements | Wallet fees should be applied prior spend calculation (reward offer resolution), where fees are applied before spend; and spend is applied for award amount or wallet balance, whatever is less | Improvement | 5.3.2.0 |
V5-975 | Spending Preferences Enhancements | Ability to set and retrieve additional auto spend preferences that will enhance the contact's experience via applications | Improvement | 5.3.5.0 |
V5-958 | Reward Offer Evaluation Enhancements | Rewards core behaviour should be enhanced to exclude performance offers from best offer restrictions. In addition (based on user setup), the reward offer evaluation should be enhanced to support no awarding events that contacts used commerce wallet balance (excluding instant discounts) | Improvement | 5.3.1.0 |
V5-954 | Auto Reward Schemes Sign Up Enhancement | Ability to sign up existing contacts to new auto sign up reward schemes via a back-end process | Improvement | Candidate Features |
V5-887 | Ability to award and spend at time of ordering | Contacts will have the ability to use their wallet credit (open and commerce) plus a payment method for remaining amount (cash or card) during ordering, and at the same time (via automations) to be awarded and spent (automatic/instant) via back-end reduction. | Improvement | 5.3.0.0 |
V5-808 | Ability to retrieve organisation tags from reward offers APIs | New organisation tag(s) attribute on list reward offers APIs | Improvement | 5.3.0.0 |
V5-664 | Back-End Reduction & Refunds | Ability to refund contacts for back-end spends | New Feature | 5.3.0.0 |
V5-660 | Ability to generate purchase events from a financial transaction and award them | Ability via automations to post a purchase event when an invoice is posted and post a credit note when a purchase customer event is voided | Story | 5.3.0.0 |
V5-45 | Rewards Tiers | A tiering system can be configured whereby contacts can be classified based on their purchase behaviour. During a tier review, a contact can advance to the next level, remain at the same level or revert to the previous tier level based on their purchases within the specified period. | Story | 5.1.0.0 |
V5-44 | Reward Resolution | Reward resolution allows a business to configure how it's contacts will be awarded in cases where they may be eligible to be awarded from more than one offer. Available options are - to award the contact from: All matched offers The best offer The best offer from each scheme | Story | 5.1.0.0 |
V5-43 | Spend Reduction Method | Reduction Method defines how the amount requested to be spent by the contact during a purchase event will be deducted from the total amount to be paid. There are two reduction methods: Front-end Reduction is done by a front-end system (e.g. POS) by instantly applying the reduction to the total amount to be paid by the contact, hence the customer pays the reduced amount. Back-end Reduction is done is by a back-end system (e.g. PayPal) where the contact pays the full amount and they are credited through a payment gateway system or by generating a refund voucher. In the context of Rewards (single merchant and multi-merchant environment), the reduction method may vary per merchant depending on the integration and the API used to post purchase customer events. | Story | 5.2.0.0 |
V5-42 | Rewards Settlement | Ability to define merchant agreements and perform a reward settlement process
Merchant agreements allow the business to define the schemes its merchants can participate and their corresponding contributions. In addition the business can define whether settlement takes place for its merchants on award or on spend. The settlement process charges participating organisations (typically merchants) the cost of awards. Settlement creates financial transactions either real time or in set frequencies, such as daily. | Story | 5.3.2.0 |
V5-41 | Rewards Merchant Commercial Terms | Merchant commercial terms are the agreements between the business and the individual merchants who will be participating in the reward schemes. Terms include the agreed commercial terms for the merchant: a) The reward schemes that the merchant will contribute towards for contact's awards or spends. b) The contribution fee that the merchant will be debited for on an award/spend (calculated based on a percentage of the award/spend, defaults to 100%). c) The management fee that the merchant will be debited for, for use of service (calculated based on a percentage of the awarded amount, defaults to 0%). d) The date that the agreement was made and it's termination date (if any). Blocking a merchant denotes that the merchant can no longer award contacts nor can contacts redeem their awards at that merchant. | Story | |
V5-40 | Financial KPI Customer Event | Financial KPI events are used to measure a contact's monthly financial status and performance against the business' KPIs. | Story | Candidate Features |
V5-39 | Achievement Customer Event | Achievement events indicate a contact's accomplishment (e.g. a Facebook like or completing their personal information). | Story | 5.4.3.0 |
V5-33 | Purchase Customer Event | A purchase event represents a sale (e.g. via a POS) of purchased items. CRM.COM behaves solely as a target system, calculating only the total net, tax and gross amounts for the purchased items. In the context of Subscription & Billing, posting an Invoice (financial transaction) can trigger the creation of a purchase customer event having as purchased items the subscribed products. | Story | 5.1.0.0 |
V5-32 | Customer Events | Customer events capture financial and marketing transactions for analytical and reward purposes. The classification of the event determines how CRM.COM will process and award the event. | Story | 5.1.0.0 |
V5-31 | Reward Schemes | A business can have one or more schemes to market and differentiate their marketing loyalty activities. Each scheme has one of the following three sign up options for contacts to register to Open loop schemes
Closed loop schemes
| Story | 5.1.0.0 |
V5-2212 | Settlement Enhancements | Ability to settle all spends made against any wallet allocation and apply a settlement fee on award/spend transaction | Improvement | 5.4.5.0 |
V5-1698 | Purchase Event Estimates | Ability to get an estimate of awards / spends of a purchase event prior to submitting it as a purchase event Ability to submit the purchase event with an estimate id (recalculation will take place) | New Feature | 5.4.4.0 |
V5-1588 | Customer Identification Medium entity to store the first 6 and last 4 digits of the card on CIM (if type = card) | Ability to keep on CIM (of type card), the first 6 and last 4 digits of the card | Improvement | 5.4.3.1 |
V5-3139 | Payout on Redeem Enhancements | Ability to define a minimum (payout) amount that should be supported on automatic redeem payouts | Improvement | 5.5.0.0 |
V5-3052 | Payout on Redeem | Ability to perform a payout on auto-redeem against the contact's preferred payment method, or to a specific payment gateway (provided that it supports payouts) | New Feature | |
V5-3002 | Rewards Free Product | Ability to award contacts a free product (sku, family, type, brand) and on redemption the amount of such purchased product (or the cheapest one) to be credited to contact's open balance | Improvement | 5.5.0.0 |
V5-2956 | Redeem Enhancement | Ability for a business to enable manual redeem. In this mode, redeem is not automatic but is performed only if a spend is requested. | Improvement | 5.5.0.0 |
V5-2842 | Rewards Lottery Enhancements | Ability to draw a winner based on number of entries for specific contact events | Improvement | 5.5.0.0 |
V5-3557 | Ability to support front end reduction at Transaction Processor level | If a Transaction Processor submits purchase events with a spend request then
| New Feature | 5.5.3.2 |
REWARD OFFERS
Issue Key
Summary
Description
Issue Type
Release
V5- |
Enhancements to Spend Condition representation - validity and expiration
Improvement
Candidate Features
V5-1433
Enhance cumulative option on offer (stamp completion)
Enhance achievement option on offer to track achievement (for example 6 purchases) without a time frame
Improvement
4289 | Delegate Offers | Ability for a B2B Merchant to setup a delegate (proxy) offer
| Improvement | 5.6.0.0 |
V5-4265 | Ability to sign up to reward schemes using codes | Ability to sign up to reward schemes using codes | New Feature | 5.6.0.0 |
V5-4116 | B2B Connect | Ability for a business (the peer) to be a B2B merchant of another business (the scheme owner). The two businesses have a mutual agreement, whereby they will apply promotions, and rewards to contacts registered on the scheme owner business. The agreement as such, defines the common identification method that will be used between the two businesses, to identify the contact on the (scheme owner) business, who purchased from the (peer) business. | New Feature | 5..6.0.0 |
REWARD OFFERS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1465 | Enhancements to Spend Condition representation - validity and expiration | Improvement | Candidate Features | |
V5-1433 | Enhance cumulative option on offer (stamp completion) | Enhance achievement option on offer to track achievement (for example 6 purchases) without a time frame | Improvement | 5.4.2.0 |
V5-1302 | Enhancing Profile completion offer with Gender option | Ability to setup target conditions for Profile Completeness offer type on providing gender | Improvement | Candidate Features |
V5-1298 | Reward Offer Award Product Conditions Enhancement | Product Discount offer type should be able to provide an award percentage based on specific product families, types or brands | Improvement | 5.4.2.0 |
V5-1283 | Enhance time based offers to be evaluated daily | Enhance time based offers (Lottery and Thank You Gift) to be evaluated daily at a specific time | Improvement | 5.3.5.0 |
V5-1235 | Enhanced Profile Completeness Options | Ability to setup target conditions for Profile Completeness offer type on providing gender and verifying phone number | Improvement | 5.4.0.0 |
V5-1109 | Ad-Hoc Return Enhancements | Ability to list ad hoc returns in customer applications and allow negative wallet balance if the ad hoc return is applied on a purchase that award is already spent | Improvement | 5.3.5.0 |
V5-1074 | Approval of Offers | Ability for Business user to approve offers created by a merchant | New Feature | Candidate Features |
V5-960 | Spend Rule Enhancements | When creating a spend rule condition, back-end users should be able to select the business as a spend rule condition. Applicable for business and merchants users | Improvement | Candidate Features |
V5-878 | Create template offers on sign-up of a new business | When a new business signs-up, automatically create a rewards scheme and 4 standard offers in 'inactive' state at the level of the service owner. | Improvement | 5.3.0.0 |
V5-825 | Reward Offer Performance | Ability to award contact based on performance offers (eg buy X products and get an award) | New Feature | 5.3.0.0 |
V5-774 | Reward Offer Target Conditions Enhancement | Ability to target country based locations for incoming purchase transactions | Improvement | 5.3.0.0 |
V5-719 | Happy Hour Offer Amendments | Minor changes related to the Happy Hour offer.
| Improvement | |
V5-63 | Reward Offer Tags | Reward offer tags are used to group reward offers based on similar characteristics (e.g. valentines day offer) | Story | Candidate Features |
V5-62 | Offer Goal - Increase Visits / Xth Transaction Wins | Xth Transaction Wins - award the Xth transaction in a row within a time frame. | Story | Candidate Features |
V5-61 | Offer Goal - Increase Visits / Number of Visits | Number of Visits - award contacts based on the number of purchase transactions that they have performed at a specific location. | Story | Candidate Features |
V5-60 | Offer Goal - Improve Membership / Application Download | Application Download - award contacts for downloading the mobile app. | Story | Candidate Features |
V5-59 | Offer Goal - Improve Membership / Referral | Referral - award existing customers for introducing a new contact. | Story | 5.2.0.0 |
V5-58 | Offer Goal - Reward Achievement / KPI Performance | KPI Performance - award contacts for accomplishing a KPI. | Story | Candidate Features |
V5-57 | Offer Goal - Reward Achievement / Subscription Maturity | Subscription Maturity - award contacts for uninterrupted subscriptions (based on subscription activation date). | Story | Candidate Features |
V5-56 | Offer Goal - Reward Achievement / Reach a Tier | Reach a Tier - award contacts for advancing to the next tier level. | Story | Candidate Features |
V5-55 | Offer Goal - Reward Achievement / Social Media | Social Media - award contacts for their social media interaction (e.g. liking/sharing a FB post). | Story | Candidate Features |
V5-54 | Spend Conditions | During a purchase transaction a contact can spend (redeem) an awarded amount from their 'Commerce' wallet balance. Spending an awarded amount can be classified as conditional (e.g. can be spent only on specific products, locations or times), or unconditional (no spend conditions apply). Spend rules Spend rules can be created on-the-fly and can combine time, location and product restrictions. | Story | 5.1.0.0 |
V5-53 | Award Conditions | The award (cashback) for achieving the offer goal can be in the form of an amount or a percentage depending on the offer type, and will credit the contact's 'Commerce' wallet balance of the primary account. Award conditions include limiting the number of contacts who can receive the offer, and setting the maximum amount to be awarded per transaction for percentage based awards. | Story | 5.1.0.0 |
V5-52 | Reward Offer Target Conditions | Every offer type has its own target conditions that affect how and when an award will be provided. Customers Location Time Products Transactions Profile Completion | Story | 5.1.0.0 |
V5-51 | Offer Availability | The date range within which the offer is valid to award contacts. The reward offer will have an 'active' state so long as the validity period has not passed, thereafter the state will be set to 'expired'. The reward offer can be activated again when a new availability period is provided. | Story | 5.1.0.0 |
V5-50 | Offer Goal - Increase Visits | Focuses on awarding contacts based on the day and/or time of their purchases. Happy Hour - award contact purchases based on a specific location/time/product. | Story | 5.1.0.0 |
V5-49 | Offer Goal - Improve Membership | Award contacts for joining or referring friends Sign-ups - award contacts for signing up to a reward scheme. Profile Completion - award contacts for completing their personal data. | Story | 5.1.0.0 |
V5-48 | Offer Goal - Increase Spend | Focuses on awarding contacts based on their overall purchase value. Monetary Discount - award contacts on the total value of their purchase (e.g. 1% cashback, 20% birthday discount). Products Discount - award contacts for purchasing a product bundle (can target a specific location). | Story | 5.1.0.0 |
V5-47 | Offer Goal - Reward Achievement | Contacts are awarded for accomplishing a goal. Lottery - award a single contact by picking a lottery winner. | Story | 5.1.0.0 |
V5-46 | Create, Update, View Reward Offers | Create and maintain the reward offers. Choose from any of the four offer goals to create an offer: Reward achievement, Increase spend, Improve membership, Increase visits. Each offer belongs to a single reward scheme. | Story | 5.1.0.0 |
V5-2441 | Self-Service List Rewards Enhancement | Self-Service list rewards should also take into consideration the town/city of venues/service points of business and merchants/service providers | Improvement | 5.4.5.9 |
V5-2113 | Enhance Reward Achievement to handle amount of top-up | Addition of 'Achievement Amount' as award condition in Achievement Reward Offer | Improvement | 5.4.4.1 |
V5-1949 | Profile Completeness Usability Issue | Profile Completeness offer should not have a limit on how many times to provide award. Should be by default once | Improvement | 5.4.4.0 |
V5-3072 | Reward Offer Award Improvement | Usability enhancement to provide a (percentage) award only for the matched target products that were purchased | Improvement | 5.5.2.0 |
V5-57 | New Offer Goal - Reward Achievement / Subscription Maturity | New offer 'Subscription Maturity' - awards customers for uninterrupted subscriptions (based on subscription activation date). | Story | 5.5.3.3 |
V5-4222 | Ability to award contacts on transferring wallet funds | Community owners awarded on accepting to transfer their CRM.COM Wallet funds to one of their community's members.
| Improvement | 5.56.30.30 |
SECURITY AND USERS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1480 | Security (2FA) Improvements | Ability to enable 2 factor authentication on business level, using SMS OTP or external authentication application | New Feature | Pending Release (Backend) |
V5-1468 | Security (Password Policy) Improvements | Ability to configure password policy (expiration), apply common password strength and user account lockout practices | Improvement | 5.4.1.0 |
V5-1332 | Enhancement to My Profile functionality | Enhance user role permissions to handle My Profile update flow | Improvement | 5.4.0.0 |
V5-830 | Ability to sign up and sign in with Facebook | Ability to register and authenticate contacts via Facebook | Improvement | |
V5-829 | User Roles to restrict access to back-end application | User Role settings to enable/disable user access to various sections in the backend | Improvement | |
V5-3034 | Contact Strong Password Policy | Ability to configure whether contact strong password policy will be applied for a service owner or business organisation | Improvement | 5.4.6.4 |
V5-1480 | Security (2FA) | Ability to enable 2 factor authentication at the business level, using SMS OTP or external authentication application | New Feature | 5.4.6.4 |
V5-3370 | Enhanced User Information | Extra information to be kept for back-end users:
| Improvement | 5.5.2.2 |
...
SUBSCRIPTIONS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1399 | Subscription Self Service Web APIs | Subscription Self Service Web APIs | Improvement | 5.4.1.0 |
V5-1271 | Subscription & Billing Settings UI Enhancements | Subscription & Billing Settings UI Enhancements | Improvement | 5.4.0.0 |
V5-1267 | Product Catalogue Process enhancements | Enhancements required in setting up and using the product catalogue for termed and one-time services | Improvement | 5.4.0.0 |
V5-1266 | Product Catalogue UI enhancements | Product Catalogue enhancements related to service products sold as part of a subscription. Enhancements include changes in configuring the setting of the product catalogue (e.g. tier paths) as well as setting up the catalogue as such | Improvement | 5.4.0.0 |
V5-371 | Change Ownership | Ability to change the owner of subscription services by:
| Story | Candidate Features |
V5-370 | Provisioning of Subscription Services | Provisioning of Subscription Services
| Story | Candidate Features |
V5-369 | Apply Grace Period | Ability to provide a grace period to subscribers to pay off their outstanding billing debts | Story | Candidate Features |
V5-366 | Service Delivery | Service Delivery is the process responsible for managing subscriptions throughout their life cycle by combining the subscriptions and billing business rules with a customer's service purchases and requests for changes. In summary, the process is responsible
| Story | 5.4.1.0 |
V5-365 | Billing Behaviour | Billing Behaviour
| Story | 5.4.3.0 |
V5-364 | Trial Periods | Trial Periods allow contacts to try out a service for a short period of time with no billing or contract obligations before turning the service into a paid one. The trial period of a service is defined in its pricing terms. Automated communications are sent to contacts prior their trial ends through Communication Plans Segments of contacts in trial can also facilitate running marketing campaigns to minimise cancellations. | Story | 5.4.3.0 |
V5-361 | Manage Subscription Services | Provide the ability to purchase termed and one-time services through a product catalogue and manage their core behaviour throughout their life cycle though various subscription actions:
| Story | 5.4.0.0 |
V5-360 | Manage Subscriptions | Create a Subscription that groups together services of the same billing period. Subscription is created only when a termed service is purchased through an Order. Manage the subscription throughout its life cycle though various subscription actions which are performed per service:
| Story | |
V5-1973 | Promotions for Subscriptions | Improvements in Promotions so as to be applied on selling subscription services | Improvement | 5.4.5.0 |
V5-2218 | Improved Subscriptions Self-service Web APIs | Product pricing for self-service in order to implement ordering of services on Release app. | Improvement | 5.4.5.2 |
V5-2126 | Ability to specify the Wallet as the funding source of a subscription | Wallet is used as the method of paying off subscription services | Improvement | 5.4.4.1 |
V5-1598 | Subscription services webhooks: On activate and on deactivate | New webhooks: | Improvement | 5.4.4.0 |
V5-367 | Subscription Devices | Ability to utilise Devices that will provision (i.e. deliver) a number of subscription services to subscribers
| Story | 5.4.4.0 |
V5-2346 | Enhanced billing and disconnection of wallet funded services | Differentiation of billing behaviour between account and wallet funded services. | Improvement | 5.4.5.3 |
V5-2055 | Ability to send provisioning commands to a group of devices | Ability to send provisioning commands to a group of devices:
| Improvement | 5.4.4.1 |
V5-368 | Usage Based Billing | Ability to order termed or one-time services that allow usage consumption | Story | 5.4.6.0 |
V5-1959 | Payment-driven subscriptions | Payment-driven subscriptions | Improvement | 5.4.6.0 |
V5-2353 | Ability to support WIFI platforms for subscriptions and billing | Core APIs created Support the device MAC address as contact authentication Enhance the organisation UI to provide usage analytics for WIFI | New Feature | 5.4.6.0 |
V5-2433 | Ability for an organisation to purchase one-time/termed services | Ability for an organisation to purchase one-time/termed services
| Improvement | 5.4.6.0 |
V5-2433 | Ability for an organisation to purchase one-time/termed services | Ability for an organisation to purchase one-time/termed services
| Improvement | 5.4.6.1 |
V5-1959 | Payment-driven subscriptions | Implementation of payment-driven subscriptions | Improvement | 5.4.6.1 |
V5-368 | Usage Based Billing | Ability to order termed or one-time services that allow usage consumption | Story | 5.4.6.1 |
V5-2616 | Improved Provisioning Provider Filtering | Available filters:
Content views to be included also | Improvement | 5.4.6.2 |
V5-2542 | Enhanced Subscription Promotions | 1 ) Ability to apply the discount
3 ) Advanced Subscription Promotions
| Improvement | 5.4.6.3 |
V5-2846 | Ability to call Provisioning Provider Integration Web APIs for services | Ability to call Provisioning Provider Integration Web APIs for services | Improvement | 5.4.6.3 |
V5-2797 | Ability to group one-time services in a subscription | Ability to group one-time services in a subscription
| Improvement | 5.4.6.3 |
V5-2764 | Ability to deactivate/reactivate services based on an amount threshold | Introduction of a new Subscription business rule called Activation rule. The rule determines whether a service can remain in Effective state or can move into the Effective state as long as the account's outstanding amount meets an activation threshold. A service is a candidate for deactivation when its account has an outstanding amount (unsettled and overdue) and this amount is greater than the threshold amount. The threshold defaults to 0 amount (set in the business's base currency) | Improvement | 5.4.6.3 |
V5-2760 | Ability to view a service's allowed and remaining usage allowance | Ability to view a service's allowance, i.e. how much usage a contact is allowed to consume in general based on what the product catalogue specifies, as well as the remaining of this usage per transaction, day and billing cycle In addition, present the recorded usage records of a subscription | Improvement | 5.4.6.3 |
V5-1964 | Implementation of service bundles | Implementation of service bundles | Task | 5.4.6.3 |
V5-2797 | Grouping of one-time services in a subscription | Ability to group one-time services in a subscription
| Improvement | 5.4.6.4 |
V5-2779 | Ability to set up business rules for Pausing a service | Ability to set up and apply business rules for Pausing a service
| Improvement | 5.4.6.4 |
V5-2834 | Enhanced usage consumption based on the usage being consumed | Enhanced usage consumption based on the usage being consumed
| Improvement | 5.5.0.0 |
V5-2811 | Event-based Recurring Charges | Event-based recurring charges is a set of policies triggered on various subscription events that identify if and which Expenses will be applied on a subscription and will be charged on a recurring basis, i.e. per subscriber billing cycle. Recurring charges policies include two major events - the event that will add the recurring expense on the subscription, and the event that will remove it. | New Feature | 5.5.0.0 |
V5-2773 | Enhanced Event-based Conditional Expenses | Enhanced Event-based Conditional Expenses
| Improvement | 5.5.0.0 |
V5-1838 | Enhancements in Pause Services action | Enhancements in Pause Services action
| Task | 5.5.0.0 |
V5-2717 | Enhanced service change process | A service change can be classified as an upgrade or a downgrade. What classifies the service change is either:
| Improvement | 5.5.1.0 |
V5-3253 | Ability to manage devices for a Company | Ability to create a subscription (through an Order) for a contact of type 'Company' and be able to view and modify the DEVICES. Flow should be the same as for contact of type 'Person' | Improvement | 5.5.1.0 |
V5-3224 | Include service locations in Invoice communications | On sending a communication for an Invoice that bills termed services, provide the ability to also display the services' locations | Improvement | 5.5.1.0 |
V5-3084 | Automation to automatically activate a service when settled |
| Improvement | 5.5.1.0 |
V5-2778 | Communication Tags and Subscriptions Segmentation & Automations Enhancements | Ability to segment contacts based on subscription services conditions and trigger automations based on new subscription events | Improvement | 5.5.1.0 |
V5-3110 | Ability to bill upcoming billing cycles in advance | Ability to bill upcoming billing cycles in advance
| New Feature | 5.5.2.0 |
V5-3084 | Automation to automatically activate a service when settled |
| Improvement | 5.5.2.0 |
V5-3423 | Ability to send service commands to a Provisioning Provider through the front-end | Ability to send service commands to a Provisioning Provider through the front-end. New Self-service Web APIs allow consumers to send provisioning commands for their services to the provisioning provider | Improvement | 5.5.2.3 |
V5-3427 | Billing engine to issue a single financial transaction according to the total billed amount | Billing engine to issue a single financial transaction according to the total billed amount | Improvement | 5.5.3.0 |
V5-3335 | Product Dependencies to be applied across all contact services, not per subscription | Product Dependencies to be applied across all contact services, not per subscription | Improvement | 5.5.3.0 |
V5-3287 | Ability to hide Churned subscriptions in Contacts screen | Ability to filter the subscriptions based on their state | Improvement | 5.5.3.0 |
V5-3161 | Enhanced listing of subscription actions to present additional information | Enhanced listing of subscription actions to present additional information
| Improvement | 5.5.3.0 |
V5-369 | Apply Grace Period | Ability to provide a grace period to subscribers to pay off their outstanding billing debts
| Story | 5.5.3.0 |
V5-2713 | Ability to regret a service | Provide the ability to regret a subscription service
| New Feature | 5.5.3.2 |
V5-3495 | Ability to set up billable and non-creditable states per service | Ability to set up additional billable and/or non-creditable states for specific services | Improvement | 5.5.3.3 |
V5-2729 | Enhanced Trial Management | Trial Management rules define whether a contact gets a Trial service once (amongst all subscription services), upon subscribing to the first service that includes a Trial period in its price terms, or a trial period for each service to which they subscribe to. | Improvement | 5.5.3.3 |
V5-3687 | Improvements in resetting a Subscription's Billing Day | Business rules included in Subscription Settings define when the Billing day is reset on a Subscription | Improvement | 5.5.3.4 |
V5-3838 | Ability to view and manage future Subscriptions | Contacts are able to order services and schedule their first activation on a future date. Provide the ability to view and manage these services prior their activation
| Improvement | 5.5.3.5 |
V5-4027 | Ability to add multiple services within the UI | Ability to add multiple services from the back-end
Supported for both adding a service to the contact and to a subscription. | Improvement | 5.5.4.1 |
V5-4247 | Ability to communicate a subscriber's upcoming bill | Introduce a new communication tag that returns a contact's upcoming bill. The tag will be used in communication plans templates. Communication plan runs on a daily basis and notifies contacts whose upcoming bill is due in an X number of days. | Improvement | |
V5-4180 | Ability to set up Usage Charge Limits and Usage Allowance settings per Contact | Ability to set up Usage Allowance Limits and Usage Charge Limits per contact, that override the business's default business rules when it comes to these settings | New Feature | 5.6.0.0 |
V5-3854 | Ability to extend a service's trial period | Ability to extend a service's trial period | New Feature | 5.6.0.0 |
USER EXPERIENCE AND TECHNICAL | ||||
Issue Type | Summary | Description | Issue Type | Release |
V5-886 | Default configuration on business creation | There are a number of configurations which should be set by default (across CRM5) when a new business is created: API keys, reward scheme, reward offers, financial transaction types, reward commercial terms and admin user role | Improvement | |
V5-807 | Get Started Usability Enhancements | Amendments to the 'Get Started' screen, regarding info messages and labels | Improvement | 5.3.4.0 |
V5-951 | Uploading Images Flow Enhancement | Ability to support a more intuitive user flow when uploading images that will provide a visual que that images have been uploaded or queued to be uploaded | Improvement | Candidate Features |
V5-1751 | JCC Merchant Integration Enhancement | Usability enhancement on importing outlets during JCC Merchant integration setup | Improvement | 5.4.3.2.1 |
V5-1163 | Ability to perform an advanced search using filters in summary screens | Ability to performed an advanced search using filters in summary screens | Improvement | 5.4.0.0 |
V5-2648 | Summary page filtering enhancements | Add Predefined Filters on the summary screen for:
| Improvement | 5.5.2.0 |
V5-3395 | Ability to keep last filters in summaries | Summary screens remember the last filter applied by a user and re-apply it when the same screen is revisited. | Improvement | 5.5.2.3 |
V5-3363 | Financial/Reward Events Summary screens - ability to navigate to the related entity (if it exists) | Financial/Reward Events Summary screens - ability to navigate to the related entity (if it exists) by clicking on the transaction number | Improvement | 5.5.3.0 |
V5-2648 | Summary page filtering enhancements | Added Predefined Filters on the following summary screens:
| Improvement | |
V5-3777 | Automatically set queue stages colours | When setting up a queue's stages, the stage's colour should be automatically set (randomly) instead of being manually set by the user (currently when adding a new stage the colour defaults to grey). Applicable for all entities that have stages (Leads, Service Requests and Orders) | Improvement | 5.5.3.4 |
...
UTILITIES | ||||||
Issue Type | Summary | Description | Issue Type | Release | ||
V5-3722 | Ability to update Payment information through automations | Payment automations to be enhanced so as to support:
| Improvement | 5.5.3.4 | ||
V5-3710 | Assignable Entities Enhancements | Enhancements on assignable entities to support accessibility coverage across users of the same team | Improvement | 5.5.3.4 | ||
V5-2680 | Automations Enhancement | Ability to support synchronous automation events, where external (webhook) validations/customization may apply prior creating/updating contacts or contact phones | Automations Enhancement | Ability to support synchronous automation events, where external (webhook) validations/customization may apply prior creating/updating contacts or contact phones | Improvement | 5.5.3.4 |
V5-4316 | Ability to create custom forms for merchants/venues |
| Improvement | 5.56.30.40 |
WALLET | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-2209 | Move the expiration functionality to the condition group | Ability to define a new condition group outside a reward offer | Improvement | 5.4.5.0 |
V5-291 | Top-ups and Transfers to have Spend Conditions for Products | Ability to transfer money to another wallet with conditions (assign a spend condition group). | Story | 5.4.5.0 |
V5-291 | Top-ups and Transfers to have Spend Conditions for Products | Ability to transfer money to another wallet with conditions (assign a spend condition group). | Story | Candidate Features |
V5-286 | Global Wallet Fees | Wallet fees are executed either to charge the contact a fee per transaction, or a fee over a period of time (i.e. for maintenance purposes). The fee can either be a fixed amount or a percentage on the transaction. Multiple rules can be set up for global wallet fees.
| Story | 5.3.0.0 |
V5-106 | Virtual Currency Wallet | In the case that the system is enabled to support virtual/alternative currency (e.g. points system) then a second wallet with a virtual currency is setup against the primary account. | Story | Candidate Features |
V5-105 | Wallet Limits | Global wallet limit rules can be defined by the business in order to restrict the number of transactions, or maximum total amount allowed for transactions within a given time frame. Back-office users can override the global wallet limits by specifying separate (lower) limits for individual contacts . | Story | 5.3.1.0 |
V5-104 | Wallet Top-up Rules | A contact can define the minimum acceptable wallet balance to be maintained. An automatic process is responsible for checking if a wallet balance is less than the balance threshold, and if so it creates an auto top-up transaction to transfer funds from one of the contacts payment methods. | Story | 5.3.2.0 |
V5-103 | Wallet Balance Expiration Process | Awards can be subject to expiry conditions, i.e. if they are not consumed by a specified date then they are voided. This process identifies any awarded amounts of the 'commerce' wallet which have expired and debits the wallet balance accordingly. | Story | 5.1.0.0 |
V5-102 | Spend Wallet Amount | This is the process whereby a contact consumes part or all of their 'commerce' wallet balance during a purchase transaction, and may or may not be subject to spend conditions. | Story | 5.1.0.0 |
V5-101 | Wallet Spend Conditions | Wallet spend conditions are the restrictions on how the wallet's 'commerce' balance can be consumed (can be viewed via the balance breakdown). The restrictions are set based on award conditions and can apply to products, places and times that the amount can be consumed. Spend conditions apply solely to the commerce balance, the open balance never has conditions. | Story | 5.1.0.0 |
V5-100 | Transfer Money to/from a Wallet | A money transfer can be performed between two accounts, two wallets or an account and a wallet. The transfer debits one entity and credits the other, the result of which is recorded as a wallet and/or account journal entry. | Story | 5.1.0.0 |
V5-99 | Top-up a Wallet | Topping-up a wallet is the process of adding money to a wallet through external means (e.g. cash, credit card, direct debit, PayPal etc.). | Story | 5.1.0.0 |
V5-98 | Activate Wallet | Activate a terminated wallet so that it can be used once again, both 'open and 'commerce' balances will commence at zero. | Story | 5.1.0.0 |
V5-97 | Terminate Wallet | A wallet can be terminated therefore halting it's use. The 'open' balance will be transferred back to the account of the contact and the 'commerce' balance will be set to zero (i.e. any awarded unspent amounts will be lost). | Story | 5.1.0.0 |
V5-96 | Wallet Balance Breakdown | View the breakdown of the wallet's balance and more specifically view the 'commerce' balance with conditions in regards to:
| Story | 5.1.0.0 |
V5-95 | Wallet Commerce Balance | The commerce balance is added to the wallet through a rewards process (e.g. awards, voucher use etc.) and may or may not be conditional. This balance is the aggregation of the non-expired awards and can only be spent as part of a purchase event. When a contact is awarded by an offer, the wallet of the primary account is always credited. | Story | 5.1.0.0 |
V5-94 | Wallet Open Balance | The open balance is the result of a top-up or a transfer from an internal or external "fresh money" Account and has no spend conditions. This balance can be used to transfer money to a bank account, or pay an external debit, or spend at merchants. | Story | 5.1.0.0 |
V5-93 | Wallet Balance | Wallet balance is the aggregated amount of posted debits and credits allocated against the wallet as of a specific date. The wallet balance is the total of the 'open' balance and the 'commerce' balance. | Story | 5.1.0.0 |
V5-92 | Wallet Periods | Wallet periods are calendar month based and maintained through an automatic process performed on the 5th of each month. Once a period is closed its balance and spend conditions are carried forward to the new open period and no other wallet transactions can be executed against the closed period. | Story | 5.1.0.0 |
V5-2700 | Ability for a contact to transfer money from one wallet to another | Ability for a contact to transfer money through a mobile app/portal.
| Improvement | 5.4.6.2 |
V5-2665 | Introduce Wallet automatic top-up when it's being used as a payment method | Automatically top-up the CRM wallet when using it as a payment method. Use the contact's primary card to retrieve funds to pay off the purchase. Automatic top-up in such cases is performed only if the feature is enabled in Wallet settings | Improvement | 5.4.6.2 |
V5-2589 | Enhanced Wallet and CRM Wallet payment method types | Introducing CRM Wallet as a new Payment method type, whereas Wallet can be used for payment methods represented as Wallet such as PayPal Solution overview:
| Improvemen | 5.4.6.2 |
V5-2520 | New Generation Wallet |
a. Top ups
| New Feature | 5.5.0.0 |
V5-3737 | Spend request should not be accepted if consumer asks for more funds than the available wallet funds | Spend request should not be accepted if consumer asks for more funds than the available wallet funds Web API (self-service POST /contacts/{id}/tokens) to return an error code if the requested amount is more than the available amount. | Improvement | 5.5.3.3 |
V5-3153 | Ability to award contacts on their wallet creation and not on registration | Ability to award contacts on their wallet creation and not on registration | Task | 5.5.3.3 |
V5-3708 | Ability to display expiry dates on journals of Wallet Analysis | Display expiration details on Wallet journals (self-service) | Improvement | 5.5.3.6 |
V5-3905 | Settlement Fees Enhancements | A spend settlement fee should be created when contacts request a front-end spend or payout due to redeem | Improvement | 5.5.3.6 |
V5-3904 | Rewards Payout Enhancements | Auto-payout due to reward redeem should take into consideration the purchase amount as well, and payout the minimum amount between the available wallet balance (including redeem) and purchase amount | Improvement | 5.5.3.6 |
V5-3903 | Wallet Payout Enhancements | Auto-payout due to redeem should not be performed when an eligible payment method is not in place | Improvement | 5.5.3.6 |
V5-2521 | B2B Spend | Ability for businesses to enable the CRM.COM Wallet (gateway), therefore, providing the possibility for their contacts to spend their wallet money at other businesses, which have also enabled such a gateway | New Feature | 5.6.0.0 |
V5-4046 | Promote & Join | Promote & Join' model provides the ability for businesses registered with CRM.COM to collaborate by promoting commerce pools, while others can join and award their contacts' purchases with such commerce money. Any awards provided against such pools, can be spent on the promoted business | New Feature | 5.6.0.0 |
V5-4045 | CRM.COM Wallet Enhancements | Introduce CRM.COM Wallet (integration) across business organisations with financial and rewards support | New Feature | WALLET |