COMMUNICATIONS | ||||
Issue Key | Summary | Description | Issue Type | Release |
V5-1245 | Ability to create rich push notifications | In-App push notifications enhanced to support images. | Improvement | 5.4.0.0 |
V5-1232 | Create default Automation upon Merchant Registration | Upon Merchant registration, a default, inactive (to be enabled by the Merchant) Automation will be automatically created. The Automation trigger point will be Contact Registration, whereby a push notification will be sent to the Contact, welcoming them and informing them that they must enable and set their spending preferences. | Improvement | 5.4.3.0 |
V5-1167 | Shared Communication Integrations between Service Owner and Business | Service Owner communication integrations (and not Business) will be used only for contact registry auth communications and user creation and email verification resend during business registration | Improvement | 5.3.5.0 |
V5-1147 | Disabled Integrations and communications/automation | When an integration has been enabled and then disabled, do not display it as an option to select in Communications and Automation. | Improvement | 5.3.4.0 |
V5-1115 | New Communication tag #contact.email | New Communication tag contact. email representing a contact’s email address. | Improvement | 5.3.1.1 |
V5-1103 | The ability for contact to unsubscribe from receiving communications (emails/sms) | The ability for contact to unsubscribe from receiving communications (emails/sms) | New Feature | 5.4.0.0 |
V5-1068 | Prevent deletion of a segment that is used by an offer | Prevent deletion of a segment that is used by an offer | Improvement | 5.3.3.0 |
V5-1046 | Communication plan enhancement | The ability for the system to not send the same communication plan to contacts of a segment that have already received it. E.G. If a Communication Plan has been scheduled and posted to Contacts in a segment if the same Communication Plan is rescheduled to be posted, those Contacts who have already received the communication should not receive it again. | Improvement | Candidate Features |
V5-841 | Ability to notify 'fulfilled by' merchant on order creation | Ability to notify ‘fulfilled by’ merchant on order creation through Automation - either email or SMS. | New Feature | 5.3.0.0 |
V5-828 | New contacts.phone_number tag in Communication Plans | New contacts.phone_number tag in Communication Plans | Improvement | 5.2.4.0 |
V5-796 | HTML for Email Communications | Ability to embed HTML in email communications. Applicable for Communication Plans and Automation. Make sure we do not use the word notifications / use only communications. We do not need rich text for in-app. | Improvement | 5.3.0.0 |
V5-791 | New contact.balances tag |
| Improvement | 5.3.2.0 |
V5-734 | Save the Communication plan as a draft without setting scheduler settings | Have the option to save a communication plan as ‘Draft’ without the need to set the scheduler settings. | Improvement | 5.2.3.0 |
V5-733 | Restrict the number of times a contact receives a communication plan message. | Have the option to not send the same email to contacts that have already received this communication plan the last X days | New Feature | Candidate Features |
V5-661 | Ability to ignore opt-in/opt-out settings for all communications | When configuring communication plans and communications with automation, there should be an option to override the contact's opt-in/opt-out settings in order to force communications. | Improvement | 5.2.2.0 |
V5-22 | Event-Based Communications | Ability to define a message with optional tags for personalisation that is sent when an event takes place, such as an award, a spend or a payment. | Story | 5.2.0.0 |
V5-21 | Integrations | Marketing
Analytics
Communications
| Story | 5.1.0.0 |
V5-20 | Communication Templates | Templates are used to define a pre-formatted message (subject and content) that allows a business to quickly and easily create communication plans. The content of a communication template can be dynamically customisable for each recipient by including communication tags that will be replaced by contact-specific information. | Story | 5.1.0.0 |
V5-19 | Tracking a Link (for email only) | Identifies when a link in an email has been visited. | Story | Candidate Features |
V5-18 | Communication Viewed (for email only) | Identifies when an email has been viewed. | Story | Candidate Features |
V5-17 | Communication Tags | Communication Tags allow an organisation to create personalised communications for their contacts quickly and easily. | Story | 5.2.0.0 |
V5-16 | Communication Plans | Communication Plans provide a means for the organisation to re-engage its contacts (e.g. announce new reward offers). They can be scheduled to run once at a set date and time or repeatedly within a date range. The recipients are defined using segments. | Story | 5.1.0.0 |
V5-14 | Create, Update, and View Communications | Create, update and view communication in multiple languages. Available channels are Email, SMS, in-app, and device. | Story | 5.1.0.0 |
V5-2321 | Ability to create communication templates for Orders | Ability to create a communication template for Orders using existing tags. | New Feature | 5.4.5.4 |
V5-2265 | Ability to use editor templates to email documents or print | 1 ) Create communication templates from Settings instead of via a communication plan or an automation communication. 2 ) Communication templates can be used to: a) Email a document (e.g. an Invoice) to a contact's email address 3 ) Ability to update and delete a communications template 4 ) New communication tags. | New Feature | 5.4.5.2 |
V5-2144 | Ability to include Service Requests charges/Order Items table in communications | A new communication tag #service_request.charges_table to allow for Service Request charges to be displayed as they appear on the Service Request screen. | Improvement | 5.4.5.4 |
V5-2841 | A new rich text editor implemented | CKEditor is to be integrated as CRM.COM's rich text editor, replacing the existing editor | Task | 5.4.6.3 |
V5-2596 | Have the ability to set up communication templates for financial transactions. | Provide the ability to configure communication templates for Payments, Refunds, Credit Notes and Payouts that can be used for printout and email actions. | Improvement | 5.5.1.0 |
V5-3003 | Ability to include custom fields in communication templates | Ability to include custom fields in communication templates. The feature includes contact custom fields (the contact of each event) as well as the custom fields of the entity as such (e.g. Orders) | Improvement | 5.5.1.0 |
V5-2595 | Ability to set up communication templates for Service Requests | Provide the ability to configure communication templates for Service Requests that can be used for printout and email actions | Improvement |
|
V5-3621 | Ability to define whether to communicate the contact statement per month or year | Ability to define whether to communicate the contact statement per month or year. In the first case, which remains the default option, the contact receives the statement for the current month. Otherwise, the contact receives the statement for the current year. | Improvement | 5.5.3.2 |
V5-3809 | Include a contact's primary address in communications | Implement #contact.primary_address communication tag to be used when setting up communication templates for an entity (e.g. Orders) and in Automation | Improvement | 5.5.3.4 |
V5-2370 | Communications improvements for Service Requests |
| Improvement | 5.5.3.4 |
V5-733 | Restrict the number of times a contact receives a communication plan message | Have the option to not send the same email to contacts who have already received a specific communication plan during the last X days | New Feature | 5.5.4.1 |
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 reconfigurability 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 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 http://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 http://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 | |