Difference between revisions of "ReleaseNotes"

From Emersion
Jump to: navigation, search
(→‎3.55.00 - 3 February 2014)
(→‎New Events)
Line 161: Line 161:
  
 
===New Events===
 
===New Events===
 +
'''''<u><i>Fees may apply to have these activated and maintained</i></u>'''''
  
 +
If you are interested in the following enhancements, please contact our Sales Team at sales@emersion.com.au
 +
 +
 +
'''SMS Gateway Module'''
 +
 +
Emersion offers an SMS Gateway Module than can be enabled to allow you to send Message Events as SMS as well as Email. Most Events now support SMS and/ or Email as delivery options.
 +
A Monthly Access Fee and Per Transaction SMS Fees apply (Tiered pricing with volume).
 +
 +
 +
'''New Product Purchase Event'''
 +
 +
Added a new Event to notify when a product purchase has been made to trigger fulfilment.
 +
 +
 +
'''TCP Events'''
 +
* Emersion now provides Telecommunications Consumer Protection Act (TCP) compliant reporting 50%, 85% and 100% and X% via email and SMS
 +
* These Events have been extended to support
 +
-Included Usage Caps
 +
-Bolt Ons – for e.g Mobile Data Bolt Ons
 +
-Data Allowances -  for Data Plans
 +
* Further Reporting has been added around these Events also
 +
 +
 +
'''Invoice Overdue Event – TIO Queue Support'''
 +
 +
Those with TIO Queue in the ticketing System can now have prevent accounts flagged as TIO from receiving invoice overdue events. (Once off Configuration Charge applies)
 +
 +
 +
'''Calls to high risk locations Event'''
 +
 +
A New event has been developed to send an alert to report on calls to high risk locations (e.g. > $1 Flag fall or >$1 price minute)
 +
 +
 +
'''Semi Manual Provisioning Client Notification Event'''
 +
 +
Added support to have events fire to send communication to child account on provisioning status changes in Semi manual provisioning
 +
 +
 +
'''Order Halted Event'''
 +
 +
Added a trigger and Event when a provisioning request has been marked as halted to notify the respective provider for action
 +
 +
 +
'''New Service Custom Price (Access Fee override) Event'''
 +
 +
Added support for access fee overrides, with events to notify upstream to check their pricing upon creation
 +
 +
 +
'''Migrate Service Custom Price (Access Fee override) Event'''
 +
 +
Added support for access fee overrides, with events to notify upstream to check their pricing upon change
 +
 +
 +
'''Product Installment Purchased Paid off Event'''
 +
 +
Added support for events to notify when Product Purchase Installment Paid off
 +
 +
 +
'''Notify Service Configuration Complete to Service Provider'''
 +
 +
Added support events to notify upstream once Service Configuration is complete (predominantly for Semi Manual Orders), to allow progression of provisioning.
  
 
===Service Type Framework===
 
===Service Type Framework===

Revision as of 10:45, 31 July 2014

The following topics are available:

3.56.00 - 31 July 2014

Action

ACTION REQUIRED FROM THIS RELEASE:

Emersion is enhancing the Permission System and will be applying by default Base Powers to all existing Org Units during this release. Module based Permissions turn on and of access to certain functions in its entirety. Powers are much more granular and can control access to sections or fields on a page.

You may wish to review Powers granted and Module based Permissions for each or your Org units.

HOW:

  • Admin > Org Units & Roles > Roles Click in the Role.
  • Module Based Permissions are set in the top sections.
  • Powers are set in the lower section.

Both are Hierarchical and if you click to add or remove permission the lower permissions will also be altered.

New Features

Fees may apply to have these activated and maintained

If you are interested in the following enhancements, please contact our Sales Team at sales@emersion.com.au


First Period Invoice Module

By default, when a customer creates a service and package, the access fees that are generated will be created and will appear on the following invoice.

The 'Invoice First Period' allow customers to override this setting and have the system create an immediate invoice. Further, they can also override the trading terms (due days) for this (and only this) particular invoice. The invoice can collect any pending cardlines or stand as an isolated invoice.


Wholesale Ticketing module

Emersion provide a Ticketing System to provide the ability to generate tasks and notes and allocate and reassign duties to specific team members for follow up. The following specific functionality will be included:

  • A new “ticket” to be generated from the Service Provider Portal.
  • All updates to the ticket to be stamped with time and user ID.
  • Ability to assign a ticket to a Queue with Category and Sub Category.
  • Tickets able to be assigned to Staff User.

The System to allow for escalation to other Staff Users.

  • Escalation details and complaints are to be recorded against the same incident. Separate sets of details are to be recorded per incident, unless the continued interaction with the customer is as a result of a previous or existing incident.
  • Ability to record Time against a ticket.
  • Ability to attach documents to the ticket.

A Queue for each of Sales, Support and Accounts will be provided by default with additional queues available.

We also added support for wholesale <-> retail account communication via tickets including support of child account ticket escalation if the Retail Ticketing System is used also.

Ticketing Module Extension – Inbound Email

Added functionality to deal with retrieving emails from customers from a mailbox and inserting into a ticket queue for processing (and customer identification by email or search) Emersion provides the following Email Functionality:

  • Collect from a defined Email Box tickets / responses.
  • Auto-Acknowledgement - Immediately confirm receipt of email inquiry and set to the appropriate Que. Then auto respond via an Event response time expectations for customer.

Account Groups

Added 'Account Groups' functionality which allows agents and other groups of staff / external companies to have limited access to your customer base, and the ability for you to define and manage distribution groups for marketing campaigns. The concept is to create account groups - and these groups can be shared amongst certain OUs. This may also be used for Marketing and other access restrictions at a later stage. An organisational unit will be flagged as one that has account access restrictions, or in other words, they have to have opt-in (deny all, allow some) or opt-out (allow all, deny some) - and as such they will have to be validated against a pool to see what they can access. The following items have been enhanced to support this functionality:

  • Finance - invoice list
  • Finance - take payment
  • Services - list all
  • /customer/account/list
  • /service/service/list
  • /customer/account/search
  • /service/service/search
  • /service/order/list
  • /service/migrate/list
  • /service/provisioning/list
  • /service/order/new - customer selection panel

If a user attempts to bring up an account that they do not have access to, the system does not allow the user to see it, but also tells the user why they were not permitted.

Management interfaces include

  • View Account Visibility by Group List
  • Management of accounts in group
  • Management of the group itself

National Collections Management Ltd. Collections Interaction

  • Thorn Financial Services and other use NCML as their collections agent.
  • Clients (Debtors) that exceed X Days payment terms are able to be referred to NCML.
  • This Transfer requires a passing of Files to NCML.
  • NCML will use their own services to chase with SMS, email and other methods to appropriate the outstanding monies (Debt).
  • The log of this activity will be tracked in the NCML systems and are required to be transferred to Emersion to have a log of the activities against the Client Account.
  • This transfer requires a file to be collected by Emersion and processed into the system as Notes against the Account.
  • NCML Staff will have limited access to be able to take Payments from Debtors and to get information required to defend disputed invoices (using the Account Groups and Permission Functionality)
  • After Y Days (X+Y Days from Initial Debt falling overdue) NCML will stop pursuing the debt, and the account will be removed automatically form the NCML Account Group.

Use Case: SP needs to manage customers that do not pay their bills by isolating them in an account Group and Account profile. Once a customer gets to a certain point in their overdue invoices, they are marked as NCML debt collection clients to chase the underlying debt. Firstly, we have the account profile system, which will manage all the underlying events and alerts that are sent to the end-users. Secondly, leveraging off the new ACCOUNT_GROUP functionality is the ability to restrict pools of customers that can be accessed by ORG_UNITs that have been setup with restrictions. On certain conditions the system will be able to move end user accounts in and out of these profiles and group sets to make them available to special parties when required. Actions:

  • Add the Account to the “NCML Collections” Account Group when we send the file to NCML.
  • Add the Account to the “NCML Collections” Profile to prevent certain Notifications when we send the file to NCML.
  • Remove the Account form the NCML Collections Account Group automatically after 60 Days of first being sent to NCML, and no longer send to NCML.
  • Remove the Account form the NCML Collections Profile and return to its previous profile automatically after 60 Days of first being sent to NCML, and no longer send to NCML.

Late Payment Fees (V2)

  • Emersion has created a second Late Payment Fee structure to be triggered when the Invoice is Overdue (once), rather than the V1 Fee that is triggered on Invoice Payment.

E.g. Charge $x at y days overdue and note 'Late Payment fee for Invoice XXXXXX due DD/MM/YYYY'

  • Use Case: a $100 invoice is due on 1st Feb and remains unpaid after y days.

On the day Due date plus y days a Pending Cardline for 'Late Payment fee for Invoice XXXXXX due DD/MM/YYYY' for $x is created. This will be swept up on the next invoice and presented to the client as a penalty (although it still remains unpaid). This fee is created only once per invoice. When the next Invoice is generated it will contain the Late Fee. If this also is not paid by Due date plus y days then this will also trigger a late fee of $x. When it is paid no action will be taken (V2 is mutually exclusive from the V1 Late payment fee system and they can co-exist).

This functionality comprises an Event Trigger - Late Payment Fee Trigger on X Days Overdue that has 3 actions:

  • Action - Create Pending Cardline
  • Email Message

Variables: Account ID, Export Ref, Account Name, Invoice Number, Invoice Issue Date, Invoice Due Date, Days Overdue, Late Payment Fee $ (Ex Tax), Late Payment Fee (Inc Tax)

  • SMS (if Optional SMS subscription optional in use)

Variables: Invoice Number, Invoice Issue Date, Invoice Due Date, Days Overdue, Late Payment Fee $ (Ex Tax), Late Payment Fee (Inc Tax)

Unbilled Credit Alert – Telstra 3G Mobile (Retail Service Providers)

Emersion now provides a place to store Unbilled Credit Alert limits. This is linked to a number of Events and Reports that can be activated to notify you that an account has exceeded their unbilled credit for Telstra 3G Usage to prevent billshock on mobile services.

Further this can also be integrated to Automatically Bar the Service once the unbilled credit Alert Limit has been reached and unbar it once the account is below the Unbilled Credit Limit (including Credits / Payment on the account)

Use Case: Customer has unbilled credit alert limit for $250 and used excess calls and data. In the processing of CDR’s the Event is triggered. The client in barred. The end user then goes to the End User portal and makes a payment of $100 to bring their account below the $250 limit, the system will automatically unbar them until the account balance plus unbilled usage is again above $250

Xero Accounting Integration – Stage 1

Emersion is Committed to integration to Xero. We have implemented our Stage 1 integration to support Payments and Invoices. Cumulus allows a small subset of integration with the Xero Billing Platform found at www.xero.com. Stage 2 will look at account integration. Integration supports in stage 1:

  • Accounts must be present in both Xero and Emersion
  • A new invoice is generated in Emersion under an account active for Xero – this invoice is then generated in Xero and we take the id from Xero and store it locally for use later on. The new invoice in Xero is generated with no cardlines and just a description to hold it in place, it is generated in DRAFT status.
  • Normal processes occur in Emersion with the invoice gaining cardlines and charges as usual.
  • Once the invoice in Emersion is marked as APPROVED, all of the cardlines will be sent to the appropriate Xero invoice as line items, and marked as APPROVED in Xero. Then if there are any payments allocated against the invoice in Emersion, they will be transferred to the invoice in Xero via the API.
  • As any payments after this fact are allocated against the invoice in Emersion, so too will they be transferred via the API to Xero for the same value against the right invoice. The payment locally will be updated with the Xero payment ID, so we don’t end up doubling up the payment.
  • If any payments are made in Xero against the invoice, and these payments don’t exist in Emersion, and the payment is against an invoice that we know about in Emersion (i.e. the invoice ORIGINIATED in Emersion) then we will pull over the details and assign a payment against the invoice in Emersion.

All of the above assumes a number of things:

  • Emersion is setup for each Emersion Service Provider Account to have a one to one relationship with one company in Xero. This is done via the Private API in Xero. Keys are generated locally and configured here, then uploaded to the API account for the relevant Xero account.
  • Emersion knows of ONE bank account that payments, when sent to Xero, go into. The Emersion API is not going to be designed to handle payment submission to a choice of bank accounts or more than one account in Xero marked as ‘receive payment allowed’
  • Emersion will only pull over payments to Emersion from Xero in the API, under the following rules:

-The payment does not exist in Emersion already i.e. the payment unique ID is not found in the Payments table -The invoice that the payment is done against in Xero exists in the Emersion system as a label against an Emersion invoice -Any overpayments (that in Xero, generate an unrelated new invoice and a credit) will not be pulled over as we have no knowledge of the invoice that is generated by an overpayment (Split payment) in Xero.

Bulk Bar / Unbar for Retail Service Suspension - Telstra 3G Service Type

Added a bulk suspend / unsuspend system - specifically for Telstra Mobile 3G at this stage.

  • Bulk upload page added
  • new screen within customer details section called service restriction to see what the system has done
  • Reporting on Baring Status
  • Report on Clients to bar

Access Fee Override

Added support for access fee overrides, with events to notify upstream to check their pricing upon change


New Events

Fees may apply to have these activated and maintained

If you are interested in the following enhancements, please contact our Sales Team at sales@emersion.com.au


SMS Gateway Module

Emersion offers an SMS Gateway Module than can be enabled to allow you to send Message Events as SMS as well as Email. Most Events now support SMS and/ or Email as delivery options. A Monthly Access Fee and Per Transaction SMS Fees apply (Tiered pricing with volume).


New Product Purchase Event

Added a new Event to notify when a product purchase has been made to trigger fulfilment.


TCP Events

  • Emersion now provides Telecommunications Consumer Protection Act (TCP) compliant reporting 50%, 85% and 100% and X% via email and SMS
  • These Events have been extended to support

-Included Usage Caps -Bolt Ons – for e.g Mobile Data Bolt Ons -Data Allowances - for Data Plans

  • Further Reporting has been added around these Events also


Invoice Overdue Event – TIO Queue Support

Those with TIO Queue in the ticketing System can now have prevent accounts flagged as TIO from receiving invoice overdue events. (Once off Configuration Charge applies)


Calls to high risk locations Event

A New event has been developed to send an alert to report on calls to high risk locations (e.g. > $1 Flag fall or >$1 price minute)


Semi Manual Provisioning Client Notification Event

Added support to have events fire to send communication to child account on provisioning status changes in Semi manual provisioning


Order Halted Event

Added a trigger and Event when a provisioning request has been marked as halted to notify the respective provider for action


New Service Custom Price (Access Fee override) Event

Added support for access fee overrides, with events to notify upstream to check their pricing upon creation


Migrate Service Custom Price (Access Fee override) Event

Added support for access fee overrides, with events to notify upstream to check their pricing upon change


Product Installment Purchased Paid off Event

Added support for events to notify when Product Purchase Installment Paid off


Notify Service Configuration Complete to Service Provider

Added support events to notify upstream once Service Configuration is complete (predominantly for Semi Manual Orders), to allow progression of provisioning.

Service Type Framework

New Service Types

New Service Types

Enhancements – Optional Modules

Enhancements – General

Bug Fixes

Application Programming Interface (API)

3.55.00 - 3 February 2014

New Features

Fees may apply to have these activated.

If you are interested in the following enhancements, please contact our Sales Team at sales@emersion.com.au


Ordering & Provisioning

Support for Financed Products

  • Emersion has enhanced our integration with Dunn & Bradstreet and Decision Intellect to include requirements for finance approval from Thorn (the parent company of Radio Rentals).
  • We can now support the ability to fully integrate as above with Thorn as a lending provider for the purposes of financing products, such as handsets. This is then integrated into the ordering process. If you require services of these types, we can coordinate and make introductions to the appropriate vendors.

These are client-specific implementations and require scoping and will be managed as an implementation project.

100-point Identity Checks

  • The order process now has the ability to optionally force a customer to submit to a 100-point identity check with the information stored in Emersion.

Terms and Conditions Contract Presentation Module

  • Added new terms and conditions types for ordering products with the services order and additional terms for the secondary credit check with Thorn.
  • Added the ability to store terms and conditions which can be shown during the ordering process for payment details that are mandatory.

Packages, plans and services

  • Telstra 3G mobile services can now have optional credit limit barring and associated notifications.
  • Prior to version 3.55.00 caps, discounts and other similar features could be set at a service plan level, or, in the case of a group cap, at a package plan level. Emersion as introduced Account Discount features that can now apply to Account level, over multiple service types and have their own anniversary dates.

End User Portal

  • A ‘forgotten password’ send new password via SMS feature now exists for the End User Portal.

The Automatic password re-set facility is currently only available for Emersion clients who have subscribed to the SMS feature – a once off set up fee applies to configure the End User Portal. Ongoing charges apply for SMS.

Reports, Events, Alerts

  • Emersion now provides TCP compliant reporting 50%, 85% and 100% via email and SMS for mobile customers.

Additional Payment Methods Options

  • Austpost BillPay is now supported via file upload.
  • SecurePay IVR and CommBiz BPAY are now supported via file upload.
  • ABA and Commbiz files can now be exported for upload to the bank.
  • ABA and Commbiz payment gateways now providing feedback on screen when the payment is processed.


Enhancements

End User Portal

  • The End User Portal now shows usage data in format in accordance with TCP guidelines showing the total amount used in the current period. Usage for Bolt-ons now displayed on a separate tab.

Product Management

  • Additional information for each item in the Products module can be stored including manufacturer, colour, model and an image. This is a precursor to our enhanced shopping cart functionality coming soon.

Invoicing

  • Repeated re-rendering of invoices will no longer occur if any invoices are queued for sending.
  • Minor change to the standard invoice template to make refunds clearer.
  • Where a single payment is made against multiple invoices, a single payment transaction will be recorded. This payment record will show on the invoice during the period whereas previously payment transaction was broken up by the amount of invoices it was paid against.

Reports

  • Two new reports have been provided to all clients:
  • A new Detailed Invoice Trending Report shows value of latest invoices vs average of last 3 invoices and percentage deviation.
  • A new Pre Invoice Trending Report shows value of current pending invoices vs average of last 3 months and percentage deviation.

Ticketing module

  • When a ticket is generated by the system, as opposed to by a user, it is closed automatically.
  • Tickets now default to private.
  • Readability improvements on the View Usage pages within the Service Subscription area and within the End User Portal for normal usage and bolt on usage.


Bug Fixes

  • Fixed an issue where duplicate payment records were being created within the Ezidebit payment gateway.
  • Removed additional tax calculation from percentage based payment surcharge.
  • Improved loading speed for packages selection during ordering process when large package catalogues exist.
  • Data in the some lists CSV downloads was incorrectly formatted. This has been reviewed and updated where identified.
Retrieved from "https://mediawiki.emersion.com.au/wiki/index.php?title=ReleaseNotes&oldid=377"