Splynx ISP Framework

All-in-One ISP Billing and Management Management Software

https://splynx.com/

Feature Request: Purchase Orders + Bulk Hardware Import (MAC / Serial)

Summary Add native Purchase Order (PO) management to Splynx, including the ability to import distributor spreadsheets (Excel/CSV) with MAC addresses and serial numbers before items are deployed Problem Statement Currently, Splynx only supports adding hardware after purchase, at the invoice stage. This creates a workflow gap for ISPs/WISPs that need to: Generate Purchase Orders before ordering from distributors Track hardware that is ordered, backordered, or in transit Pre-stage inventory (MACs / serials) received from distributors before deployment Maintain internal approval and reconciliation workflows Requested Features 1. Native Purchase Orders (POs) Ability to: Create Purchase Orders without creating an invoice Assign PO numbers Attach distributor/vendor Email distributor from Splynx Track PO status: Draft Submitted Partially received Fully received Cancelled Convert PO → Invoice when received 2. Bulk Import of Hardware from Distributors Ability to upload an Excel / CSV file from distributors containing optional fields: MAC Address Serial Number Manufacturer Model SKU PO reference Cost per unit This is critical because many distributors (e.g. wireless, networking, CPE vendors) already provide packing slips or order confirmations in spreadsheet form. Why This Matters (Operational Impact) Without PO + bulk import support: Inventory tracking becomes manual Accounting and ops are forced out of Splynx MAC/serial handling is error-prone Larger deployments become inefficient This feature would significantly improve Splynx’s usability for ISPs managing real hardware supply chains.

TRL 7 days ago

💡 Feature Request

Planned

Splynx Field Service APp

Automatically show Team tasks on Dashboard if user is part of the team Automatically show Team tasks on Calendar if user is part of the team. Filter button should only be used to filter if necessary in a whitelist fashion. But default view should be all tasks that user is assigned to (including Team Tasks) Map shows old (Done) tasks by default for some reason? Tasks page shows Done tasks for some reason by default? Done tasks should be hidden by default only to be brought up by whitelist filter. Tasks page should show To Do and In Progress by default, sorted as earliest to latest Tasks page, select Task, info. Customer and customer details should be visible by default, with the name, phone number, and email at the top of the just above the written address. Checklist should be right below description Tasks page, select Task: Play, add worklog (+), and Close task should all be in the same line. Play and + buttons should be the same style as the close task button (larger to press with a finger on mobile, and colored the same)

TRL 29 days ago

1

💡 Feature Request

Capture additional fields when e-signing contracts

We would find it incredibly helpful if we were able to capture additional information at time of e-signature via Splynx. For example, we would like customer to input their preferred payment date. This could be a short text input field above the e-signature input field. We’d like for this to be visible on the e-signed contract in the same way that a placeholder can be inserted. For us, this would eliminate the need to use an external e-signing service and would drastically increase the value that Splynx provides our business. I feel that this feature would be a perfect build upon: https://features.splynx.com/p/esignature-with-audit-trail-and-pdf-integrity-esign-act-eidas

harryrobson About 2 months ago

💡 Feature Request

Fully Automated Ticket Management in Splynx Using n8n and LLMs

I recently built a workflow using n8n that takes helpdesk ticketing in Splynx to the next level. The workflow reads all new tickets, analyzes their content to determine type and group, and automatically assigns them to the right agent. Using a large language model (self-hosted or via OpenAI), the system can also draft replies for tickets automatically. This creates a fully automated ticketing process from intake to categorization, assignment, and suggested responses, reducing manual work and improving response speed. The setup is flexible. You can run everything on your own server or leverage cloud-based LLMs depending on your preference and scale. With this workflow, Splynx becomes a smart, self-managing support system that helps your team focus on the tasks that matter most.

Samad Mohiuddin About 2 months ago

💡 Feature Request

Seamless WhatsApp Integration with Splynx Using WPPConnect

ISPs often want customers to reach support through WhatsApp, with every message automatically appearing as a proper ticket. With WPPConnect, an open-source tool, you can do this without paying for a WhatsApp provider. WPPConnect acts as a bridge: it receives WhatsApp messages from your business number and forwards them to your system. In this case, messages are sent directly to Splynx via its API. Getting started is easy. Install WPPConnect on your server and link it to your WhatsApp Business account by scanning a QR code. From that point, every incoming customer message triggers a webhook. Your automation tool—like n8n—processes the webhook, checks the customer’s phone number in Splynx, and either creates a new helpdesk ticket or updates an existing one. Photos, attachments, and voice notes can all be included. The integration is fully two-way. Agent replies in Splynx are automatically sent back to the customer on WhatsApp through WPPConnect’s sendMessage API. This setup provides a complete, cost-effective WhatsApp helpdesk for small and medium ISPs, keeping full control of the system while minimizing complexity. All you need to manage is WhatsApp login stability and simple routing logic—everything else runs smoothly.

Samad Mohiuddin About 2 months ago

💡 Feature Request