TEMP Migrating from v1
This information is made available for our launch partners and early customers that are currently using the v1 divergent Cloud.
If you signed up to divergent Cloud yourself or were migrated from a previous Cedita solution, this document is not relevant to you in any way.
This document will be removed once all customers have been migrated successfully.
Introduction
We will have been in touch with you about the new version of the divergent Cloud already as well as most of the changes that are upcoming.
This document serves to provide you information on what's changing with regard to terminology, product availability, and more.
A Workspace is now a Billing Profile
We've simplified the way that customers are managed whilst giving you much more flexibility.
Currently, you have a Workspace which is the root of your interaction with the divergent Cloud. Each Workspace could hold 1 instance of each application, and billing was within 1 subscription with many items.
A Billing Profile is a new concept within the v2 platform which:
- Can have multiple instances of the same application underneath it. For instance, if you have multiple brands under the same company, you could create 2 branded instances of Reserve or Identity underneath a single Billing Profile.
- You will now have a subscription per product, which are billed separately, giving you more control of payment methods or departments within your business.
Your Logo / Branding is no longer global
Branding is now set up on a per product instance basis, meaning you can have a different logo between two different instances of Reserve, for example.
As alluded to above, your Workspace previously had "a logo" and "an icon". Billing Profiles do not have this concept, rather, each application (which has a corresponding public interface) has its own branding settings.
Transact is being removed
We're offering more payment services and removing any instance of "Transact" from your system.
Transact was our initial idea for payments within the platform. A global way for you to manage all payments through a single, centralised system.
When we've spoken to partners, particularly those with multiple operations, we have determined that this is not a workable solution long term.
Instead of Transact, each product like Reserve will have its own implementation of payments.
At the same time, we're introducing more configuration and more payment methods (such as PayPal and Square) that you can add in to certain products.
Interface Changes
We're making the interface of each product more focused to your requirements.
Currently, all products that you use are available in a single navigation bar.
An example of this navigation bar from a customer is below:
In v2, you access each product separately. An example of a customer within Reserve will now see the following navigation bar:
This change focuses on improving usability of the platform, whilst at the same time removing the burden on you for managing individual products. Even though Reserve for example still uses Connect, Identity, centralised People, and a variant of Transact, you are no longer aware of this implementation.
Billing Changes
When you use one of our products, you are billed from that one product rather than multiple.
Following on from above and no longer being aware of multiple underlying products being used, even if you use SMS from Reserve you will not be billed from Connect unless you explicitly use this product separately.
For example, invoicing for your subscription may have previously referenced:
Connect - Per SMS
X @ 2.75p
Connect - Per Email
X @ 0.01p
Identity - Per User
X @ 0.1p
Reserve - Per Booking
X @ 3p
Reserve - Per Digital Event Ticket
X @ 3p
Your invoice for Reserve will now be:
Per Booking
X @ 3p
Per Digital Event Ticket
X @ 3p
Per SMS
X @ 2.75p
You may notice there are no longer any per user or per email fees. Upon a review of our pricing strategy, we have determined that these costs are expected to be included and are now bundled within the Per Booking Fee.