# Splynx

Splynx is a billing / CRM / RADIUS platform for ISPs and WISPs. Connecting it gives Voice Logica a synced copy of your Splynx subscribers, indexed on phone, plus live lookups during a call. The agent can identify the caller by phone, login or name, read their balance and invoices, see which services are active or stopped, check whether their line has a live session right now, open a support ticket, and - after you confirm - reactivate a line that was suspended for non-payment. Because Splynx knows whether a line is technically up or administratively blocked, the agent can explain a "no internet" call instead of just logging it.

Open **Integrations - Catalogue - Splynx - Connect**. One connection is shared by the whole company.

  <ShotPlaceholder
    src="/assets/integrations/splynx.png"
    name="splynx-connect"
    alt="Connect Splynx dialog with Splynx URL, API key and API secret"
    capture="Connect Splynx dialog."
  />

> **Note:** Splynx is enabled per account - if the card is not in your Catalogue, ask Voice Logica to turn it on. Once connected, the **Splynx** card appears under the agent's **Tools & Workflows**, where you pick which lookups and actions the agent may use during a call.
## What you need before you start

- Your Splynx address (Splynx SaaS, for example `https://mycompany.splynx.app`, or your own server). Enter the root URL without a trailing slash and without the API path.
- An API key and secret created in Splynx under **Config - API keys**, with the permissions the AI needs. The secret is shown only once, so copy it when you create the key.
- For a self-hosted Splynx server with a private-CA certificate, you can allow a self-signed TLS certificate in the advanced settings.

## What you enter

- **Splynx URL** (required) — Your Splynx root URL, for example `https://mycompany.splynx.app`. No trailing slash, and do not include the API path.
- **API key** (required) — The public part of the Splynx API key. It travels in the authorization header.
- **API secret** (required) — The secret for that key. It is used only to sign requests and is never transmitted; it is stored encrypted.

Under **Advanced settings**, both optional:

- **Default country code** — `30` — Calling code prepended to local numbers when building the phone index (Greece = 30).
- **Allow self-signed TLS certificate** — Turn on only for an on-prem Splynx server with a private-CA certificate.

## First setup

1. **In Splynx**, open **Config - API keys** and add a key with the permissions the AI needs. Copy the key and its secret - the secret is shown only once.

2. **Integrations - Catalogue - Splynx - Connect**

   Enter your Splynx URL, the API key and the API secret.

3. **Connect**

   Voice Logica verifies the credentials, saves the connection and runs the first sync of subscribers and balances. After that, subscribers are polled daily and balances refresh nightly around 03:00 UTC.

4. **Agent - Tools & Workflows - Splynx**

   Pick which lookups and actions the agent may run on a call. Leave write actions (open a ticket, set subscriber status) off unless you want the agent to use them.

5. **Prove it**

   Call the agent and give a subscriber's phone number or name. The agent should read back the matching subscriber, their balance and service status.

## What the connection can do

| Job | What is available |
|---|---|
| Identify the caller | Look up a subscriber by phone, by login, or by name; link a caller's phone number to a subscriber after they confirm |
| Account | Outstanding balance (sum of unpaid invoices); recent invoices with paid / not-paid status |
| Service health | List services with live status (active / stopped / disabled); check whether the line has a live RADIUS session right now - together these explain a down line |
| Support actions | Open a Splynx support ticket for the caller; set a subscriber's status to reactivate a line after payment or to suspend it (write actions - only after the caller confirms) |
| Follow-up | Build an outbound campaign that calls every subscriber who owes money, with name and balance passed to the agent |

Reads use the local synced cache for a fast answer; service status, invoices and online status are checked live against Splynx. The write actions (ticket, status change) only run after the caller confirms.

## Troubleshooting

**Splynx rejected the credentials**

The API key or secret is wrong, or the key lacks permissions. Create a fresh key in Splynx under **Config - API keys**, copy the secret while it is shown, and paste both again. Make sure the key has the permissions the AI needs.

**Can't reach Splynx / connection error**

Check the **Splynx URL**: use the root address you open Splynx with, with no trailing slash and no API path. For a self-hosted server with its own certificate, turn on **Allow self-signed TLS certificate**.

**The balance-reminder campaign finds nobody**

Balances refresh nightly around 03:00 UTC. Right after connecting, run a balance sync (or wait for the nightly refresh) so outstanding amounts are populated before you build the campaign.

## Next Steps

[Get an integration working](https://docs.voicelogica.ai/integrations/) - company connection, then the agent tool.  
[Odoo ERP](https://docs.voicelogica.ai/integrations/erp/odoo/) · [Soft1](https://docs.voicelogica.ai/integrations/erp/soft1/) - other ERP connections.