Communication Features
- Spyroulla Ioakim
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 |
V5-4831 | Support of reward offer communication tags in Automations | Provide the ability to include a reward offer’s information in communications sent on Activating a Reward Offer. | Improvement | 5.6.0.6 |
V5-5139 | Ability to configure the delivery time of a communication sent over SMPP | Ability to configure the delivery time of a communication sent over SMPP | Improvement | 5.6.9.0 |
V5-5191 | Ability to include devices sold/returned through a financial transaction in communications | Two new communication tag has been created that can be included in communications sent to contacts, to list the devices sold or returned through a financial transaction, i.e. an Invoice or a Credit Note respectively.
| Improvement | 5.7.0.0 |
V5-5097 | Enhanced communication tags for financial transactions | Include all total amounts of Invoices and Credit Notes as communication tags e.g. Tax amount. Amounts should include the currency as does the existing Total amount tag.
| Improvement | 5.7.0.0 |
Â