Versions Compared
Version | Old Version 27 | New Version 28 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Generic Settings
Info |
---|
Configure system platform settings applicable across the software. The options differ according to the organisation level at which the system user is signed in, i.e., Settings differ for Cloud Operator users, Service Owner users and Business users. |
This manual covers the generic platform settings from the Cloud Operator level down to the Business level, which are not included in the configuration of other manuals. Each setting is clearly marked with the organisation level to which it applies.
Refer to the Reference Material section below for configuring additional platform settings that fall under other system areas and are not covered in detail below.
To configure generic platform system settings - select Settings > Platform.
Time Zone
Status | ||||
---|---|---|---|---|
|
Select the time zone of your Business. All date/time-related actions (e.g. registration date/time, communication scheduled date/time etc.) will be as per the selected time zone.
CRM.COM time zone is UTC based
The supported time zones are based on ISO 8601
Currently, Contact’s time zones are not handled by the system; this should be taken into consideration when scheduling communications to be sent to Contacts in a different time zone than your Business’s
Anchor | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Each Business has a base currency that operates as its operations' default currency. This is assigned to the Business upon registration, based on its locale, but can be changed before any transactions occur.
To enable multi-currency operations for a Business, thus allowing processing transactions in other currencies too - add additional currencies with an exchange rate against the base currency.
The base currency cannot be changed if products, transactions, or payment gateway requests are associated with it
The supported currencies are based on ISO 4217
Exchange rates are manually maintained
Anchor | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
The default language of the software is English. However, additional languages can be defined for selection as the preferred language of communication with Contacts, as well as for customer-facing apps (e.g. mobile app, portal).
The Contact language is automatically set upon contact registration based on the Contact’s locale but can be changed at any point in time either by the Contact themselves via the app/portal or from the backend by a system user (Demographics area).
The available languages that are supported are based on ISO 639-3
The backend UI is available only in English, but the app and portal are currently available in English and Greek
If the contact registry is enabled at the Service Owner level, all Businesses belonging to the Service Owner will adopt the same language settings as the Service Owner.
Anchor | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
If your Organisation operates on a multi-regional level, you can configure the supported countries of agreement for your Contacts to register under. This will allow you to differentiate the prices of products and services offered for ordering based on the Contact’s country.
The Base Country is the default country.
A Contact can select their country during the registration process either using the app or portal
A system user can change a Contact’s country of agreement via the backend from the Contact screen (Demographics area)
Anchor | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Tags are a way of adding keywords or additional information to entities in the system so that they can be easily searched for and located. Tags can be used as a filtering option on summary screens to return only the required records.
Create Tags using terms relevant to your Business for the following entities:
Contacts
Service Requests
Leads
Activities
Products
Organisations
Once a Tag has been created, it needs to be activated to be used. Edit the Tag and change the State to Active.
To add a Tag to an entity - locate and select the record in question (e.g. Contact), edit the Tag placeholder and choose one or more Tags from the available list, or start typing the Tag name to perform a quick search.
Since Tags are entity-specific, you can only choose from those Tags configured for the entity you are currently editing, i.e. Tags created for entity Contacts won’t be selectable when editing Service Requests.
Organisation Tags
Tags can be defined in order to group Organisations based on their business activities and can be created in one of two ways:
By system users via Settings
Using Google Place Types when creating/updating an Organisation. In the event that the address lookup (of an Organisation) is performed using Google Places, any Google Place Types retrieved for the Organisation will automatically populate the tags, the user can amend these tags before saving. Once saved, any undefined tags will automatically be created at the Service Owner level and can also be assigned to other Businesses of that Service Owner. Users cannot delete tags saved in this way.
Business users can create their own organisation tags; however, Merchant/Service Provider users cannot access the configuration page but can search for and select tags when creating/updating their venues.
Mobile app users can use organisation tags to filter locations according to their business type, therefore viewing only those locations of particular interest to them.
Test Data / Live Data
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
CRM.COM software supports two environment modes - Test Data and Live Data.
When you sign in to your newly created business on CRM.COM, you will automatically be switched to the Test Data environment. This is an environment where you can experience CRM.COM firsthand. You can create contacts, set up reward schemes and offers, create physical products and subscription plans, test your billing configurations, and generally get acquainted with the software without affecting your actual Live data.
A back-end system user can switch between Test Data and Live Data as needed by switching the toggle at the bottom of the sidebar menu. The bar at the top of the screen reminds you that you are in Test Data mode.
Test Data and Live Data behave in exactly the same way. They have , with the same features and processes, but they do not hold contain the same data. So it’s It's important to note that data created when in Test Data are never mode is not available when switching into to Live Data mode.
Note |
---|
IMPORTANT It should be noted that only selected system configurations set up in Test Data mode will be copied to the Live environment when you switch over, e.g. . For example, any Contacts, Reward Schemes, Reward Offers, Products, Promotions, etc. created in Test Data mode will need to be re-created recreated in Live Data mode. |
Only the following system configurations set up in Test Data mode will be copied over to Live Data mode:
Business Network
Organisations - Service Owners, Businesses, Merchants, Venues (note that Service Owners, Businesses and Merchants can also switch between Test and Live data too)
TAPS (of Business, Merchant, Venue organisations)
Organisation Groups
Organisation Tags
Security
User Roles
Users
Teams
Platform
Countries of Agreement
Currencies
Industry
Industry Sectors
Languages
Time Zone
Custom Fields
When a back-end system user switches to Live Data mode for the first time, any configurations created in the specified areas are copied to Live Data mode. Subsequently, if the user switches back to Test Data mode and creates new configurations in any of these areas, then switches back to Live Data mode again, then the new configurations created will also be copied to Live Data mode.
White Label
Status | ||||
---|---|---|---|---|
|
White Labelling allows the Service Owner to rebrand the software using their own logo and user policies. The configuration is trickled down to the Businesses registered with the Service Owner. If White Labelling is not configured, then the default CRM.COM branding is used.
White labelling supports a logo which is visible on the registration and sign-in page, as well as the sidebar menu, along with the other relevant user policy URLs appearing on the registration screen.
Sign-in screen
Registration screen
Sidebar menu
Copyright Notice
Status | ||
---|---|---|
|
The Copyright Notice displayed at the bottom of the screen throughout the software is configurable only by the Cloud Operator.
Anchor | ||||
---|---|---|---|---|
|
You may also find it useful to refer to the following manuals for further configuration of Platform Settings.
Applications
Status | ||||
---|---|---|---|---|
|
Mobile Pass Cards
Status | ||||
---|---|---|---|---|
|
Landing Pages
Status | ||||
---|---|---|---|---|
|
Custom Extensibility
Status | ||||
---|---|---|---|---|
|
Custom Fields & Custom Forms Custom Extensibility
Bulk Data Operations
Status | ||||
---|---|---|---|---|
|
Import Contacts & Devices Bulk Data Operations
Business Network
Status | ||||
---|---|---|---|---|
|
Partners https://crmdevelopment.atlassian.net/wiki/pages/resumedraft.action?draftId=610697345
TABLE OF CONTENTS
Table of Contents |
---|