Subscription Additional Processes 2 - R15
B2B Subscriptions
Business-to-Business subscriptions represent the agreement between the service company and another company instead of a physical person. They allow the concurrent usage of the subscribed services in various locations, by multiple users or on multiple devices.
- Maximum Capacity: a number defined upon subscription creation which will always be used by billing
- Actual Capacity: a number provided every time the subscription is billed and is based on the actual number of devices/users that used the subscription
- Number of devices added to the subscription: the number of installed items added to the subscription
The above parameters are set on the subscription at the time of its creation
B2B subscriptions can only be created for accounts associated to companies and not physical persons.
To create a B2B subscription you must use a 'Commercial' subscription type and a billing term scheme which supports concurrent usage.
Offering Subscription packages
- A fixed price for all services included in it
- Common subscription and pricing terms to all customers that select to subscribe to it
- Can be swapped with other packages (Swap Package)
- Can be replaced by other subscription types (Replace Subscription)
- Can be discounted automatically by auto-applied additive discounts or by discounts added by on the fly (ad-hoc discounts (Apply Ad-hoc discount)
- Have additional services swapped
For more information on packages refer to Subscription Type
Communicating subscriptionsÂ
It is possible to automatically create communications on various events that take place with regard to a subscription, such as creating, cancelling activating or deactivating, changing etc. by setting up 'Event Based Communication Definition' accordingly. You can use tags related to wallets (text that is automatically replaced by values specific to selected records) when creating communication templates or communications. Tags are available for selection by typing '#'. It is also possible to manually create communications which include subscription related information through the communications page by adding the subscription number in the 'Referring to Entities'
Refer to the Communications manual for a complete list of service request tags.
Approving subscriptions
Subscriptions can be configured to require approval from a specific user before they are further processed. This is done by setting up Approval Definitions and triggering Workflow Rules. For more information refer to Managing Approval Requests.
Automation on subscriptions
Subscription processes can be automated by using Workflows. For example, you can use alerts to contact users or schedule activities, when a subscription of a specific type is created. For more information refer to Workflows.Â