ISPbox Wiki

Quick start guide for ISPBox: add your first router, package, client, and service in the correct setup order.

The optional extras of an internet package: burst, a different speed at night, a limit on connections per login, and locking a login to one device.

Insert answers you wrote once, merge the ticket that was reported twice, and let customers rate support after a ticket is closed.

Add up to 20 fields of your own to a customer: text, a number or a list of choices.

Move many services to another plan at once: pick the customers on the client list, choose the plan and the timing, read a preview of every service, confirm, and take it back if needed.

Build routine work as a tree of steps: what starts it, what it checks and what it does, with waits, approvals, AI steps, retries, a message limit and results per workflow.

When a customer leaves, archive them: the history stays, running services are switched off for you, and you choose per device whether it is collected, stays at the address or returns to stock.

Create teams such as Office, Field techs or NOC and route tickets, leads and tasks to a team instead of one person. A user can be in several groups; groups never change permissions.

Install an ONT at an address before anyone orders service, let it pass to the next resident when one leaves, check it is alive on the network, and keep the install readings.

A premise is a place you serve or could serve, with or without a customer: its address, equipment, tickets and every customer who was there. Add them one by one, as a numbered range or from a spreadsheet.

Work out what a park, HOA or building owner is owed each month or quarter: a percent of what was invoiced or paid, or a fixed amount per active service, by active days, with tiers and a minimum.

With NetFlow or IPFIX switched on, your routers tell the probe who fills a link: which customers, which remote addresses, which services, and the saturation diagnosis names them.

Every few minutes a probe logs in like a customer: a RADIUS request, a full PPPoE login and a DHCP lease. When that fails you hear about it even though every ping is green.

One score from 0 to 100 per customer per hour, from everything the panel measures, with the reason when it is low, the one thing to do about it, and the access points that are overloaded.

Every MikroTik you manage backed up every night and a few minutes after anyone changes it, every version kept, any two compared line by line, and the change shown next to the fault it caused.