CONTACTS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1456 | Ability to segment contacts based on name, day/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 the mobile app | Display contacts referral code in the 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 the Contact page | Have the ability to view the 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 a new condition to allow the user to create a 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 the Contact page Core behaviour: the system sends communication in the language of the Contact' preferred language. If not configured, then use the default. | Improvement | 5.3.5.0 |
V5-1114 | Contact enhancements - Backoffice operations & Activity Feed | Enhance the backend system to provide summary screens for financial and reward transactions. Enhance the 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 the Google Places ID field on the Contacts -> Address section. The field is populated when the Google address is selected and 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 is ignored. The Mobile Client should use an image scaling component and upload a single file that can 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 re-configurability on the backend to specify allowed payment methods at the level of business. Add a 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 the app and port’s new feature. | Ability to configure whether the contact can select a preferred merchant for ordering and a preferred merchant for rewards and customer care. | Improvement |
V5-772 | Contact's Country of Agreement | Ability to support multi-regional 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 | The ability for the 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 the option to add more. | New Feature | 5.4.0.0 |
V5-375 | Contacts Financial Actions | Financial actions are available for Contacts. Create a new account - Create a new account for the current contact. | Story | 5.1.0.0 |
V5-325 | Payment Methods and Refund Methods |
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 | 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 contacts that participate in 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, and JCC Medium | y | 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 numbers, email, passcodes) 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 its 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 is set ups 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, and 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 the 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 segment's 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 which contacts will be retrieved; multiple conditions can be specified by the user. | Story | 5.1.0.0 |
V5-69 | Create, Update, and View Segment | Create and maintain one-time password editions. | Story | 5.1.0.0 |
V5-2406 | The ability for a back office user to request and validate one-time-password and sign-up 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 the 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 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” communication to be sent with Service setup integration. SMS communication to remain at the Business level. | Improvement | 5.4.3.1 |
V5-1786 | The ability for a Business to set default spending preferred spending | The ability for Businesses to setup Automatic Spend Preferences for their contacts 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 the maximum allowed number of concurrent sessions for contact and users. | Improvement | 5.4.5.0 |
V5-1393 | Contact Activity Feed enhancements | Improve the activity feed to show the most relevant information on two 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 a 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-1312 | Ability to resend the email for email verification | Resend email for verification purposes. | Improvement | 5.4.0.0Automation |
Contact Approvals for Orders | The 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 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 spending 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 |
V5-4180 | Ability to set up Usage Charge Limits per Contact | Ability to set up Usage Allowance Limits per contact, that override the business's default business rules when it comes to these settings | New Feature | 5.6.0.0 |
V5-4124 | Customer Identification Medium Enhancements | Ability to support case insensitive CIM identification | Improvement | 5.6.0.1 |
V5-2936 | Contact Identities Verification Enhancements | Enhance contact credentials verification process to be part of contact (settings) core behavior and not part of front-end application configuration | Improvement | 5.6.0.1 |
V5-4423 | Enhanced Create Purchase Web API | A member of a community submitting a purchase event must be identified using the contact's identifiers (id, code, wallet etc.) PLUS, the community through which they intend to use their CRM.COM Wallet sharing option. | Improvement | 5.6.0.1 |
V5-3372 | Nameday improvements | A) Summary screen filtering enhancements
B) UI enhancements to offer a better view for long name lists in modals and tables
C) Wrong validation message if name day (day/month) is not specified. Now it says “Please specify month”, it should say “Please specify name day’s Day/Month” D) Mark mandatory fields with a red asterisk | Improvement | 5.6.0.2 |
V5-4368 | Ability to set up the contact authentication to be applied to all applications |
| Improvement | 5.6.0.4 |
V5-4758 | Search for contacts based on their demographics information | Search for contacts based on their detailed information:
| Improvement | 5.6.0.5 |
V5-2369 | Attachments improvements | Ability to upload attachment (links) to contacts, orders, service requests and leads | Improvement | 5.6.0.5 |
V5-4977 | Improved UI/UX when managing a SaaS Subscription |
| Improvement | 5.6.8.0 |
General
Content
Integrations