Setting Up Your ISP on ISP-OS

This tutorial walks through the one-time setup that shapes how ISP-OS works for your operation — your brand identity, when invoices go out, how long subscribers have to pay, what notifications they receive, and who on your team can access the dashboard.

Estimated time: ~10 minutes

Prerequisites:

• An ISP-OS account with owner or admin access
• Your ISP logo file (PNG or SVG, at least 200x200px)

---

Step 1: Set your ISP name and branding

Your ISP name and logo appear on invoices, the subscriber payment portal, and email notifications. Set these first so everything downstream looks right.

1. Navigate to Settings → General.
2. Fill in the fields:
   • ISP Name — your business name as subscribers know it, e.g. FiberLink Internet Services
   • Logo — upload your logo. This appears on generated invoice PDFs, the payment portal (/c/{short_id}), and email headers. Use a square or horizontal logo on a transparent background for best results.
   • Brand Color — pick your primary color using the color picker or enter a hex code (e.g. #2563EB). This tints the payment portal header, email accent bars, and the subscriber-facing QR payment page.
   • Support Phone — the number subscribers should call, e.g. 0917-123-4567. Shown on invoice PDFs and suspension notices.
   • Support Email — e.g. support@fiberlink.ph. Used as the reply-to on all outgoing emails.
3. Click Save.

The brand color and logo propagate immediately. Open a subscriber's payment page in a new tab to confirm it looks right.

---

Step 2: Configure billing settings

These settings control when invoices are generated and how long subscribers have to pay before the collections pipeline starts.

1. Navigate to Settings → Billing.
2. Configure the following:
   • Invoice Generation Day — the day of the month when ISP-OS auto-generates invoices for all active postpaid subscribers. Common choices:
     • 1 — invoices go out on the 1st (most common for Philippine ISPs)
     • 25 — invoices go out 5 days before month-end
   • Payment Terms (days) — how many days after generation the invoice is due. Default is 15. If you generate on the 1st with 15-day terms, due date is the 16th.
   • Currency — PHP (Philippine Peso). This is pre-set and affects formatting on invoices and the payment portal.
3. Click Save.

When does invoice generation run?

The GenerateInvoices scheduled job runs daily. It creates invoices for services whose next invoice date is due in the tenant business calendar. If a subscriber was added mid-cycle, their first invoice is prorated automatically using the tenant Proration basis.

---

Step 3: Set up your collection policy

The collection policy defines the timeline from "invoice sent" to "subscriber suspended." This is the most important configuration for your collection rate.

1. Navigate to Settings → Collections.
2. Configure the collection timeline:
   • Remind days before due — how many days before the due date to send the first reminder. Default: 3. Subscribers get an SMS and email saying their bill is due soon.
   • Warn days after due — how many days after the due date to send a warning. Default: 1. The tone is firmer: "Your invoice is overdue. Pay now to avoid disconnection."
   • Suspend days after due — how many days after the due date to auto-suspend. Default: 5. This is also used as the invoice grace period for RADIUS enforcement. After this many days, the subscriber's PPPoE auth is rejected.
   • Suspend schedule time — the time of day (Manila timezone) when auto-suspension runs. Default: 06:00. Set this to early morning so subscribers wake up disconnected and are motivated to pay during business hours, not at 2 AM when your staff can't help.
   • Notification channels — check SMS and/or Email. Both enabled by default. SMS uses iSMS; email uses Resend.
3. Click Save.

Here's what this default policy looks like on a timeline for an invoice generated on April 1 with 15-day payment terms:

Date	Day	What happens
Apr 1	Generation	Invoice created, status: Sent
Apr 13	Due - 3	SMS + email reminder: "Your ₱1,500 bill is due on Apr 16"
Apr 16	Due date	Payment terms expire
Apr 17	Due + 1	SMS + email warning: "Your bill is overdue"
Apr 21	Due + 5	Auto-suspend: PPPoE rejected, active session kicked

Choose suspend timing carefully

Setting suspend days too low (e.g. 1) frustrates subscribers who pay a day late. Setting it too high (e.g. 15) means you're giving 30 days of free internet (15 payment terms + 15 grace). Most Philippine ISPs use 3–7 days after due. Start with 5 and adjust based on your collection rate after the first month.

---

Step 4: Configure notifications

Notifications are how subscribers learn about their bills, overdue status, and suspension. Configure the channels and sender identity here.

1. Navigate to Settings → Notifications.
2. Configure SMS settings:
   • SMS Provider — pre-configured to iSMS (the integrated SMS gateway).
   • Sender ID — the name that appears as the SMS sender on the subscriber's phone, e.g. FiberLink. This is typically your ISP brand name (max 11 characters, alphanumeric). Some carriers may require pre-registration of sender IDs.
   • SMS templates — ISP-OS ships with default templates for each collection stage (reminder, warning, suspension, restoration). You can customize the wording. Available variables:
     • {subscriber_name} — subscriber's full name
     • {amount} — the outstanding or restoration amount
     • {due_date} — invoice due date
     • {payment_link} — the subscriber's payment page URL
3. Configure email settings:
   • From Name — e.g. FiberLink Billing
   • From Email — must be a verified domain on Resend, e.g. billing@fiberlink.ph
   • Email templates — similar to SMS, but with richer formatting. ISP-OS generates HTML emails with your logo, brand color, a fee breakdown table, and a "Pay Now" button linking to the payment portal.
4. Click Save.

After saving, send yourself a test notification to confirm delivery. The SMS should arrive within 5–10 seconds; email within 30 seconds.

Notification dedup

ISP-OS tracks every notification in the dunning_events table. If a reminder SMS was already sent for an invoice within the last 24 hours, it won't send a duplicate — even if the scheduled job runs again. Each channel is tracked independently: if SMS succeeded but email failed, only the email retries.

---

Step 5: Invite your team

If you have staff who handle billing, field operations, or customer support, invite them so they can access the dashboard without sharing your admin credentials.

1. Navigate to Settings → Users.
2. Click Invite.
3. Enter the team member's email address, e.g. tech@fiberlink.ph.
4. Select a role:
   • Admin — full dashboard access for a second operator
   • Staff — billing and subscriber operations without router/network control
   • Technician — router and service operations without billing access
5. Click Send Invite.
6. They'll receive an email with a link to create their account and set a password. The link expires after 48 hours by default.

All invited users join your ISP's tenant with a role. Owners and admins can manage settings and team access. Staff can handle billing and subscriber operations. Technicians can handle router and service work without seeing billing controls. Keep personal credentials personal and invite everyone else explicitly.

---

You're ready to operate

Your ISP is now configured on ISP-OS:

• Branding — your logo and colors on every touchpoint
• Billing schedule — invoices generated automatically on your chosen day
• Collection policy — remind, warn, suspend timeline set
• Notifications — SMS and email configured with your sender identity
• Team access — owner/admin/staff/technician roles without shared passwords

From here, the platform handles the monthly cycle automatically: generate invoices, send reminders, warn overdue subscribers, suspend non-payers, and reconnect them the moment they pay.

Next step

If you're migrating from another system (spreadsheets, UISP, Zal Pro) and have an existing subscriber list, import them in bulk:

Import Subscribers from CSV →

Was this helpful?