Summary
Service transitions define which statuses a service can transition to. In this example we are going to add a transition for the “Suspended” service status we created in Service Status Configuration Example. The transition we create will allow the “Suspended”, “Non-Billable” status to transition to an “Active”, “Billable” status.
For additional details on the fields presented on this screen see the Service Transitions guide.
Prerequisites
Service Status Configuration Example needs to be completed before service transitions can be setup.
Service transitions only apply to services that are of the “Fee” type so you need to have a fee set up.
Sample Configuration
Log into your Logisense Billing application
Click on the “Setup” menu then on the “Product Catalog” sub menu
Click on the “Service” button then “Service Transitions” tab at the top
Click the “+” button to add a new service transition
Enter a name then set the “From Status” to “Suspended” and the “To Status” to “Billable” and click Save
Result
When configuring package frequencies you can setup one time charges based on the transitions you create here, for instance applying installation fees, activation fees or re-activation fees as service statuses are changed. We’re going to add an “activation fee” when a service moves from a suspended status to an active status.
Click on the “Setup” menu then the “Product Catalog” menu
Click on the “Packages” button
Click on a package then on one of the package frequencies
On the “Edit Package Frequency” screen click the “Transition” button then the “+” button.
Fill out the info below. This example is showing that when the “5G Data - Unlimited” service uses the “Suspended to Active” transition we are going to charge an activation fee of $3. When you have the fields filled out, click the “Add” button
Click the “Save” button on the “Edit Package Frequency” screen to save the transition
Next Steps
<<documentation team task: link to next configuration article>>
Related Guides
<<documentation team task: link to API guide which covers the same config process>>
<<documentation team task: link to Data Import guide which covers the same config process>>