IntegrationsISP billing systems
ViSP
Connect ViSP so the AI agent knows who’s calling, reads their balance live, takes a payment with the card on file and opens tickets in ViSP.
- Plan
- Telco Ops Bundle (ViSP is part of its Telecom Connector Pack)
- You need
- A ViSP API client ID and secret, and a ViSP username and password
- Where
- Build > Apps > ViSP
Before you start
You need two sets of details from ViSP:
- An API client ID and client secret, issued by ViSP.
- The username and password of a ViSP back-office login that can see your ISP. Crulon reads your ISP from this login, so you never enter an ISP ID.
Connect ViSP
Install the App
In Crulon, open Build > Apps, choose ViSP and select Install ViSP.
Add your ViSP details
Under Connector setup, enter the Client ID, Client secret, Username and Password. Leave GraphQL API endpoint and Token endpoint as they are; every ViSP account uses them, and you’d change them only for ViSP’s beta or sandbox API.
Connect
Select Connect. Crulon checks the connection straight away, and you can check again at any time with Test connection under Connection health.
Check the ISP and where devices come from
Under Connector settings, ViSP ISP shows the ISP your login reaches. If it reaches more than one, choose the one Crulon should read and select Save settings.
Choose Devices before the first sync (see Equipment).
What comes across
Crulon copies your ViSP customers, in every status, every hour by default. Each sync re-reads every customer in full. Change how often under Sync cadence, from every 15 minutes to daily, or select Run sync to sync now.
| In ViSP | In Crulon |
|---|---|
| A customer | A contact, with their name, email, address and every phone number on the account |
| Account details | Account type, services with their price, monthly charge, and the date they’re paid through |
| Status | Active, suspended, inactive or cancelled. Change how ViSP’s statuses map under Status mapping |
| Balance | What they owe |
| Equipment | An asset for each item, with its MAC address, serial number, IP address and model |
Texting consent, open invoices, usage, notes and extra contacts aren’t copied. A customer removed from ViSP is retired in Crulon after two syncs that don’t find them.
Equipment
Devices sets where Crulon reads each customer’s equipment:
| Option | Use it when |
|---|---|
| Inventory list (recommended) | Your ViSP inventory assigns equipment to customers. Right for most ISPs |
| Customer records | Your inventory list is empty, and equipment is recorded on each customer instead |
| Don’t sync devices | Your ViSP doesn’t track equipment |
The two lists don’t share IDs, so changing the option after a sync adds every device again from the new list and retires the old ones. Nothing changes in ViSP.
What the agent can do on a call
Attach these tools to your agent under Business Tools:
- Look up customer finds the account from the number the caller rings from, using the copy in Crulon.
- Check balance and billing reads the account from ViSP as the caller asks: what they owe or have in credit, the next bill date, whether autopay is on, and the cards on file. If ViSP doesn’t answer, the agent gives the last balance Crulon copied and says how old it is, and can’t take a payment until ViSP is back.
- Take a payment charges a card already saved on the account in ViSP.
- Create ticket opens a ticket for the caller’s problem.
Payments
Payments are off until you turn them on in the Payments card: Allow the AI agent to charge cards on file. Before it charges, the agent is told to read back the amount and the card’s last four digits and wait for the caller to say yes, and it can’t charge until it marks that the caller agreed. Crulon never takes a card number over the phone.
Restore service when a payment goes through is on by default once payments are on: ViSP lifts a suspension as soon as the balance is paid.
The agent takes one payment per call, of at least $1 and no more than the balance due. If it can’t confirm whether a payment went through, it tells the caller and opens a high-priority ticket for your team to check before anyone charges again.
Tickets in ViSP
Ticket push is off until you turn it on in the Ticket sync card:
- Create a provider ticket when one is created here creates each ticket in ViSP, as an open ticket of type Other.
- Close the provider’s ticket when this one closes marks it Resolved in ViSP.
- Create a ticket at the end of every call files a Call Summary ticket after each answered call from a ViSP customer, with the summary, the caller and how long it took.
ViSP needs every ticket to belong to a customer, so a ticket for a caller who isn’t linked to a ViSP customer isn’t sent; it shows as excluded. Comments and edits aren’t sent, only new tickets and closures.
Crulon doesn’t change customers, packages or billing settings in ViSP.
Restarting equipment
ViSP brings in each customer’s equipment, but checking a device live or restarting it needs an equipment App: UISP, Cambium cnMaestro, Nokia Corteca or TP-Link TAUC.
If something goes wrong
The connection test shows this for any failure, including a wrong client secret, username or password. Check each detail under Connector setup, then select Test connection again.
Choose the ISP Crulon should read under Connector settings > ViSP ISP, then select Save settings. Syncs wait until you do.
The ViSP login can’t see an ISP. Give it access in ViSP, then connect again.
Crulon reads numbers written without a country code as numbers in your workspace’s country, and skips any it can’t read. Check how the numbers are written in ViSP. If your workspace’s country is wrong, email support@crulon.ai.
Turn off Scheduled sync to stop copying straight away; nothing already copied is deleted. Turn off ticket push in the Ticket sync card too. To remove the App completely, email support@crulon.ai.
Last updated 18 Oct 2026