Subscribe to mailing list

Hydra Billing v4.1.3 Released

Dmitry Koplovich, 11 August 2017

 

Today we are releasing Hydra Billing v4.1.3. With it, your employees and customers can save their time. We have done a big job on the system’s stability and performance, and have added a couple of new integrations.

Password Recovery via SMS in the Customer Self-Care Portal

Now, when logging in the Customer Self-Care Portal, customers can recover forgotten passwords on their own. A customer needs now only a couple of minutes to do that, so that your help desk or customer care department will not have to reset passwords or spell them on the phone. With Hydra, your employees will be able to do tasks that really matter.

Even your customers will appreciate the automated password recovery: the problem can be solved without contacting technical support.

Password reset procedure uses a well-known scheme when a verification code is sent to a customer’s mobile phone.

In order to limit telephone numbers for sending codes set a prefix in the Customer Self-Care Portal configuration.

For example, you can set it as +1 to have SMS sent to the U. S. numbers only. For sending a verification code, the Customer Self-Care Portal uses the address which is stored in Hydra and used for notifications. The number specified by a customer should correspond to the one stored in Hydra.

After entering the correct code, the Customer Self-Care Portal will prompt a customer to set a new password.
If a customer has not received the code, he or she can request a new one. To protect your SMS messaging service we have made provision for a timeout for resending, and a limitation for the maximum number of sent messages.

The new functionality will require a minimum setup on your part: in the Customer Self-Care Portal configuration, turn on an automated password recovery and specify the path for the script for SMS sending. Whenever you have questions our technical support is ready to help you.

A New Non-Payment Suspension

In the 4.1.3. version we have rewritten non-payment suspensions. After installing the new version, the services will get locked only automatically, with the help of the new Suspending for non-payment task. It closes expired subscriptions to services too.

If you decide to apply a non-payment suspension to your customer accounts, or to change any of its conditions, then Hydra will need to re-analyze which accounts should be suspended, when, and on which conditions. In this regard, we have created a special parameter, Process customer accounts using new suspension parameters, within the task. Use it after adding changes to suspension parameters.

We have also introduced a new status for documents, Locked, so that now it can be applied not only to customer accounts, but also to service contracts. Hydra automatically transfers a contract into this status when suspending services. As a result, you can easily distinguish between still active and already locked services in a customer profile.

Invoice tagging

Hydra allows setting tags to various entities in the system. Specify a set of tags when creating invoices, so that Hydra will set these tags to all new invoices.

It is much easier to find a set of invoices when they are already tagged.

Integration of Hydra with External Services

We continue developing Hydra REST API , so that the 4.1.3 version comes with a new method for saving custom fields of equipment.

Our clients often use custom fields in order to employ their own extensions or individual integrations. From now on, working with them via API will require even less effort.

The new version also comes with the Customer Self-Care Portal integrated with the MEGOGO video streaming service. Your customers will be able to subscribe to, activate and pay for the services right from the Customer Self-Care Portal.

Re-Executing Commands in Provisioning

In order to manage equipment, Provisioning executes parameterized commands. They are not always successfully executed: either equipment or connection to network may go down, while applying to external services via HTTP may fail due to a number of reasons.

The new version has a task for re-executing commands. You should set the timeout and the maximum number of retries, so that Hydra will then take care of forwarding commands to the addressee.

A Substitute for Current Bank Account in Printable Templates

Sometimes your clients may change their current accounts. Now you needn’t choose operating accounts from several bank accounts and create complex filters. Simply use the current_settlement_account substitute to insert the current operating banking account of your customer.

Commented: 0
COMMENTS

LOG IN AND LEAVE A COMMENT

OR

↑ TO THE TOP