All-in-One ISP Billing and Management Management Software
Splynx ISP Framework
List views - select only this page (visible rows) vs. select all
In the past, I added a request to improve list view operations by supporting “shift+click” partial range selections, but that was rejected. I’m still not really sure why as it would vastly improve UX, although I’m not sure how much code would be involved (though in other products I have seen, it hasn’t been a lot). As of v6.0, there is no way to “select all on the current page” in a List view in Splynx. Clicking the header-row checkbox in the upper left selects all rows across all of the pages in the list view. There is no way to only select the “visible” items on the current page, other than manually clicking every single row/checkbox one at a time. This is very tedious and frustrating. Obviously we can change the number of rows displayed in the list from 10 or 25 up to 100, but the problem is that manually clicking a bunch of boxes is mistake-prone and annoying. Proposal: change the behavior of the header-row checkbox to only select the items on the currently visible page. Above the header-row, Splynx already displays an informational alert about how many rows are selected along with a “reset selection” button that unchecks everything. Add a second button or link to that alert that says “click here to select all rows on all pages” (or something similar). It would also be helpful to explicitly show the count of rows included in “All” - “All (90) rows are selected” in the first image below would be better than just saying “All”. Second option: if changing the info alert section isn’t viable, add a new button somewhere in the upper left for “all rows all pages” and switch the current header-row select-all to “just this page”. Third option, if the developers really want to maintain the existing behavior of the header-row checkbox: add a button in the info alert next to “reset selection” that says “only select visible rows on current page” or something similar. I would like to see this available on most if not all of the major List view sections, like Customers → List, Scheduling → Tasks (list view), Inventory → Items, etc (so it should be generic code across the UI rather than multiple section-specific implementations). I understand that changes like these are not “flashy,” but making your product easier to use is something that helps retain and delight customers and makes them wonder “how did I ever live without this?” These examples are from Scheduling → Tasks, but basically all List views in Splynx would benefit from this improvement.
Tasks List - Add Filter for "Started at" and "End at"
As of v6.0, the Scheduling → Tasks “list view” has a Filter section and a property called “Period” that can be used for filtering. However, “Period” filters on the date the Task was created. We generally don’t care much when the task was created, what matters much more for our needs is when the task was scheduled to start (and sometimes end). We often create a task a week or more before it is actually scheduled. I propose changing “Period” to “Task Created Date,” and then adding two new filters for “Task Scheduled Start Date” and “Task Scheduled End Date” that use the same UI (date-range picker interface). Currently, there is no way to filter the List view by the scheduled date, unless you add the “Started at” column and then do a search for a specific YYYY-MM-DD (which is inefficient and hard to work with).
Technician on the way
It would be cool if a dispatcher or technician could send a SMS/notification on customers app that their technician is on the way to their home/business.
PayAdvantage Payment Gateway Integration
We would like Splynx to support PayAdvantage integration for Australian businesses. This would allow customers to make payments using credit/debit cards, PayID, PayTo, Direct Debit and BPAY. Automatic payment updates and matching payments to the correct customer invoices would help reduce manual work and improve payment reconciliation. Please consider adding this integration to Splynx.
Automatic Percentage based fees based on payment method used along with customer notification of fees when submitting payment info.
A feature is needed to apply a surcharge for credit card payments. It would recognize the payment method of the customer and if they decide to use a credit card/debit card the system would automatically add a percentage based fee on top of the charge. If they use a preferred payment method such as ACH there would be no fee applied. The fee should show up on invoices as well as in the customer portal when they are initially adding payment info or if updating payment info it notifies them.
Translation of whatsapp messages
Enable WhatsApp support to automatically detect the customer’s language, translate their messages into English, and translate our responses back into their preferred language for a smooth, seamless conversation.
Feature Request: Customisable Ticket Status Widget Order
Allow users to manually rearrange the status widgets on the Tickets Dashboard. Currently, widgets appear in the order the ticket statuses were created, with no option to change their order. Expected behaviour: Users should be able to customise the order of the status widgets to suit their workflow and preferences.
USPS API addon for malformed addressing
We would like to make it impossible for a non valid address to be able to create a customer, task, or the like. Booyakasha!
Billing Dates
Allow customers to choose a billing date of either the 1st or the 15th of each month during the onboarding process, as these are the two available options for our customers.
Ezidebit integration Australia
Recurring Payments & Direct Debit for Australian Businesses https://www.ezidebit.com/en-au
Allow multiple & custom Contact Book types
Currently, a contact can only be assigned one type in the Contact Book. When the same person is both the primary and billing contact, we have to create that person twice: once as the Primary contact and again as the Billing contact. Please add either a combined Primary and Billing type or allow multiple types to be selected for one contact. It would also be helpful if administrators could create additional custom contact types, such as: Technical Accounts Site contact Owner After-hours contact
Notifications for unassigned WhatsApp conversations
Currently, administrators only receive notifications about new WhatsApp conversations once the conversation has been assigned to them. If automatic assignment is disabled, new unassigned WhatsApp messages can remain unnoticed - no email notifications are sent. Please add an option to notify selected administrators or administrator groups whenever a new unassigned WhatsApp message is received. The notification method should be configurable as: Email Support ticket Email and support ticket The WhatsApp conversation should remain unassigned so that any available team member can claim it. Ideally, notifications should stop once the conversation has been assigned or answered.
Finance debtors enhancement
Splynx Finance Dashboard – Debtors Age Analysis Currently, the Splynx Finance Dashboard reflects the full value of unpaid or partially paid invoices, rather than the actual outstanding debtor balances. For example, where a customer has partially paid an invoice, the dashboard continues to reflect the full invoice amount as outstanding, rather than the remaining unpaid balance. Consequently, the dashboard does not provide an accurate representation of the debtors book. Requested Enhancement: A dedicated Debtors section within the Finance Dashboard that: Reflects the actual outstanding balance per customer, taking into account partial payments and credit allocations. Provides a debtors age analysis, categorised into Current, 30, 60, 90 and 120+ days. Displays the total outstanding debtors book, with the ability to drill down into individual customer balances and the underlying invoices. Allows the debtors report to be viewed as at a selected date and exported to Excel. Objective: To provide an accurate, real-time view of the debtors book for financial reporting, credit control and collections management.
Sign-Up Flow - API integration for coverage maps
On the South African market, many FNO’s do not provide KML files to upload into Splynx and rather host their own coverage platform and provide API integration. Without this, this sign-up flow will be useless to most ISP’s in South Africa.
Sign up flow pro-rated
Good Day Customers are being charged the full service amount upon sign-up however there is confusion when they have to pay again the balance due to being pro-rated when they sign up. Can we please as a matter of urgency be able to set it so that it can calculate the a prorated amount rounded of course ,so that the customer on the first bill sent just pays the total service amount. Thanks
splynx CommsApp
Please add a feature to the Splynx CommsApp that displays the customer’s Finance and Information pages alongside their messages, so staff can see the customer’s details while handling the conversation.
Ticket Automation per Ticket Group
Current automation applies to all tickets, regardless of configure ticket groups (e.g. Support, Finance, Sales, etc.). It would be very helpful to apply configurations, as in the below example: Support ticket, unattended for an hour: Send a canned response. Finance ticket, when received: Send banking details. Sales ticket, when closed: Change ticket group to Support.
Feature Enhancement Request - Expanded AI Summary for NOC Operations
Good day Splynx Team, We would like to request an enhancement to the existing AI Summary functionality within Splynx Tickets. Ideally, the AI should analyse the complete ticket, including the ticket body and communication history, and provide a concise NOC-oriented summary. We would like the AI summary to include the following information: 1. Communication / Response Times The AI should analyse the communication history and provide: Number of customer responses Number of NOC/agent responses Average response time between communications Longest response interval Who is currently waiting for a response — customer or NOC This would help the NOC quickly identify tickets where communication may be delayed. 3. Issue Identified The AI should analyse the ticket conversation and clearly identify: What issue the customer originally reported Symptoms described by the customer Any troubleshooting already performed Any confirmed technical findings Any information that is still missing or needs to be obtained from the customer For example: Issue: Customer reports intermittent internet connectivity. Troubleshooting completed: Customer has rebooted the router. Outstanding information: Connection logs/ONT signal levels still need to be checked. 4. NOC Recommendation / Next Action This would be particularly valuable. Based on the information contained in the ticket, the AI should provide a recommended next action for the NOC engineer. For example: ... Recommended NOC Action: Check the customer's ONT optical levels and review the last 24-hour connection history for LOS/LOF events. If optical levels are normal, check for repeated PPPoE/session drops before considering escalation. The recommendation should be based only on the information available in the ticket and should clearly distinguish between confirmed information and recommendations. 5. Suggested Customer Response It would also be useful if the AI could generate a suggested response to the customer based on the current ticket status. For example: ... Proposed AI Summary Format Ideally, the information could be presented in a simple format such as: NOC Quick View Issue: Intermittent internet connectivity Ticket Age: 2h 07m Average Response Time: 18 minutes Current Status: Investigating Waiting On: NOC Troubleshooting Completed: Router rebooted NOC Action Required: Check ONT/optical levels and connection history Escalation Required: Not currently Recommended Next Step: Review connection/LOS history The objective is to make the AI summary more than just a summary of the conversation. We would like it to function as a NOC assistant, allowing an engineer to open a ticket and quickly understand: What is the problem → What has already been done → What is the current status → Who is waiting → What should I do next? We believe this could significantly improve NOC efficiency, reduce the time required to read thro
Custom SSO support
We have our own OIDC / LDAP service and would like to be able to link Splynx to that to assist in SSO login into Splynx. The Azure SSO support shows Splynx is ready for such type of adoption, a custom OIDC / LDAP would be perfect. Thank you!
Multiple Sites Under a Single Customer Profile
Enable the system to create multiple sites with different addresses under a single customer profile, eliminating the need to create a separate profile for each site.