Splynx ISP Framework

All-in-One ISP Billing and Management Management Software

https://splynx.com/

Upgrade tariff: charge price difference and preserve current expiry date for prepaid services

We would like a feature enhancement for subscription/package upgrades for prepaid services. When a client requests an upgrade to a higher service package before their current subscription expires, we would like the system to: Allow the client to top up the difference amount required for the higher package. Allow the ISP/operator to upgrade the client to the new package. Carry forward the remaining subscription days from the current package to the upgraded package. Maintain the existing subscription expiry date after the upgrade. Complete the process without requiring: Credit notes Manual balance adjustments Manual recalculation of subscription periods Example A client is subscribed to a Basic package valid until 31 July. On 15 July, the client requests an upgrade to a Premium package. The client tops up the difference amount required for the higher package. The ISP upgrades the client to the Premium package. The system carries forward the remaining subscription days to the upgraded package, ensuring that the expiry date remains 31 July. The objective is that a client can move to a higher package/service plan during an active subscription period by paying the difference amount, while the remaining validity is preserved and transferred to the upgraded package.

Fred Maina 2 days ago

πŸ’‘ Feature Request

Better reporting on ticketing

We would like to be able to view more information from the ticketing reporting. Reporting similar to other ticket platforms like Zendesk and HALOPSA in terms of graphs and per agent statistics, allowing us to QA agents using these stats. We would also like the ticket reporting to be more customizable on both the ticket dashboard and the and the reports that are able to be pulled from the admin tab. These need to provide details for email responses and Whatsapp responses per ticket, providing First response time, Average response time, Average resolution time which is already part of Splynx reporting but allow additional information such as Opened tickets by category, Opened tickets by types, Opened tickets today, Stale tickets, tickets resolved within # time, tickets in different statuses.

JarrydT 8 days ago

πŸ’‘ Feature Request

Push Customer Tariff Speeds to ONT / CPE Devices

We would like Splynx to support pushing customer tariff upload and download speeds directly to customer access equipment, such as: Fibre ONT / ONU Wireless CPE dish Many ISPs and FNOs use Splynx to manage customer packages, but the actual speed limit often also needs to be applied at the customer access device. This is especially important where the FNO manages the access network and hands traffic over to an ISP for breakout. The requested feature is for Splynx to automatically push the customer’s tariff speed to the linked ONT/ONU or wireless CPE when: A customer is activated A package is upgraded or downgraded A customer is suspended or reactivated A service is changed This could be done through UISP integration or another device/API integration method. Splynx should also allow a user-defined margin above the tariff speed, for example 10%, when pushing the limit to the ONT/CPE. This allows the ONT/CPE to act as a safety limit, while the ISP can still use its main router or optimisation platform for proper QoE shaping such as FQ-CoDel, CAKE, or other shaping methods. Why this is important If speed limits are only applied at the main router, access router, or central traffic shaper, some traffic may already have crossed the last-mile network, wireless sector, PON, repeater link, backhaul, or internal ISP network before being shaped. This can cause: Customer devices uploading or downloading at full port speed before reaching the shaper DDoS attacks or infected devices using the full ONT/CPE upload capacity Congestion on the last mile, PON, wireless sector, repeater link, or backhaul Other customers on the same access network being affected Local/on-net traffic bypassing the central shaper and running at full port speed Customers using more than their package speed when local/on-net traffic and internet traffic are combined For example, a business customer may view live CCTV from home over the same ISP network. This traffic may route internally and never pass through the central shaper. The customer may then receive CCTV traffic at full port speed while still receiving their full internet package speed, resulting in total usage above the package they are paying for. Example If a customer is on a 20Mbps package, Splynx should be able to push a 20Mbps limit to the ONT/CPE, or push 22Mbps if the ISP sets a 10% margin. This would be useful for ISPs/FNOs using Splynx with Ubiquiti fibre and wireless networks, and for any provider that needs customer speeds enforced at the access-device level before traffic reaches the core router or central traffic shaper.

Bsz786 24 days ago

πŸ’‘ Feature Request

Automatic Image Compression for Schedule Attachments

We would like to suggest automatic image compression or resizing for photo uploads in the Schedule section. Currently, staff often upload photos directly from smartphones, which can result in very large image files. This may affect system responsiveness and loading performance when opening schedules or attachments. It would be very helpful if uploaded images could automatically be compressed or resized to below 1 MB per file while maintaining reasonable image quality. Benefits: Faster loading times Reduced storage usage Better responsiveness for staff Improved experience on slower connections Thank you for considering this feature request.

Natthana Thepthong about 1 month ago

1

πŸ’‘ Feature Request

Send Message update to an emailed/SMS communication

Most useful update for communicating with customers would be to be able to update the same group of customers with an update from the Messages/History tab. When we have a network event, we go through the process of selecting the customers affected, but after a while or when the event is cleared, we need to update the same group of customers. The most logical way to ensure that teh same group is messaged would be to simply click a button in the History tab and the system auto select the customer list to resend to them! That way we dont waste time trying to ensure we select the same parameters/filters for the new message - in fact it could include the previous message sabiject possibly marked as *** UPDATE *** or *** RESOLVED *** or something intelligent maybe?

afutter about 1 month ago

πŸ’‘ Feature Request