PageSignal

PageSignal User Guide

PageSignal is a browser extension that detects tickets in your PSA (ServiceNow, ConnectWise, Jira Cloud) and helps you sync them to HaloPSA.

Getting Started

Install the Unpacked Extension (Chrome and Edge)

Use these steps when running PageSignal locally from source.

For a quick project setup overview, see:

Download Source ZIP

  1. Download the latest source ZIP: PageSignal Source (PageSignal-source.zip)
  2. Extract the ZIP to a local folder.
  3. In the browser steps below, select the extracted folder that contains manifest.json.

Google Chrome

  1. Open Chrome and go to chrome://extensions.
  2. Turn on Developer mode (top-right).
  3. Click Load unpacked.
  4. Select the project folder that contains manifest.json (the PageSignal root folder).
  5. Confirm PageSignal appears in the extensions list and is enabled.
  6. (Optional) Click the pin icon in the toolbar to keep PageSignal visible.

If you update files while developing:

Microsoft Edge

  1. Open Edge and go to edge://extensions.
  2. Turn on Developer mode (left side panel).
  3. Click Load unpacked.
  4. Select the project folder that contains manifest.json (the PageSignal root folder).
  5. Confirm PageSignal appears in the extensions list and is enabled.
  6. (Optional) Use Show in toolbar to keep the extension icon visible.

If you update files while developing:

Troubleshooting Install Issues

  1. Open Chrome and make sure the PageSignal extension is installed and enabled.
  2. Sign in to HaloPSA in the same browser.
  3. Click the PageSignal icon in the toolbar to open the popup.
  4. Confirm the status indicator shows “Connected to HaloPSA”.

Detecting Tickets

PageSignal detects tickets automatically when you open a ticket page.

Supported systems:

When a ticket is detected, it appears in the ticket list and begins time tracking.

Dashboard View (Your Tickets vs. All Engineers)

By default, the dashboard shows only the tickets you synced or detected through your own PageSignal account/extension. This keeps your view focused on the tickets you personally worked on.

Note: PageSignal identifies “your” tickets by the HaloPSA technician you are logged in as. If PageSignal cannot determine the current technician (for example, when you are not signed in to HaloPSA), it falls back to showing all tickets so nothing is hidden unexpectedly.

Ticket List Basics

Each ticket card shows:

Actions

Syncing to HaloPSA

  1. Select a ticket and click Sync.
  2. Fill in the sync form:
    • Organization (required): the Halo client that owns the ticket.
    • Company / Site (optional): free-text name of the company or site referenced in the alert. This is recorded on the HaloPSA ticket details and included in the sync note/time entry.
    • Status (required), NOC Service Type (required), Charge Rate (required, defaults to Partner Work).
    • Escalation Remarks: required when the selected status is an escalation.
    • Notes (optional).
    • Time Taken / Adjust Time (minutes) (required).
    • Entry Date / Time (required): defaults to now in your local time. Change it so the time entry lands on the correct day in HaloPSA. This is important for teams working outside US hours (e.g. IST morning shift) whose entries would otherwise be dated to the US day.
  3. Submit to sync to HaloPSA.

If the ticket is already linked, PageSignal will update it. If not linked, it will create a new HaloPSA ticket (if allowed by configuration).

Choosing the time-entry date/time

Time entries in HaloPSA are dated using the Entry Date / Time field on the sync form. The field is pre-filled with your current local date and time. If you are logging work that was performed earlier (or you are in a timezone that is ahead of the HaloPSA server), set the field to the actual local date/time of the work so it appears on the right day in your timesheet.

Warning/Critical Alerts

If a ticket stays open long enough, it can generate alerts:

Alerts are shown as:

Alerts are filtered to the current technician and clear after a successful sync.

The footer shows:

Client List (Left Sidebar)

The left sidebar shows clients with unresolved webhook tickets. Click a client to open its PSA site.

Linking helps PageSignal route weekly analysis and ticket actions to the right Halo client.

  1. Find the client in the left sidebar.
  2. Right-click the client badge to open the client menu.
  3. Choose Link.
  4. Select the correct Halo client and save.

To remove the link later, open the same menu and choose Unlink.

Common Questions

The extension says “Not connected”

Log in to HaloPSA in a browser tab, then reopen the popup.

A ticket is not detected

Refresh the ticket page and wait a few seconds. If it still does not appear, open the popup and click Refresh.

The Refresh button doesn’t seem to show the latest updates

The Refresh button now force-reloads everything (ticket list, statuses, daily stats, and notifications) instead of using short-lived cached values, and it shows a “Refreshing…” state while it works. The list also auto-refreshes about every 10 seconds. If a ticket you expect is missing, confirm you are viewing the right scope (see Dashboard View — you may be filtered to your own tickets), and that you are connected to HaloPSA.

A ticket was reassigned to another team after I escalated it (for administrators)

PageSignal does not assign tickets to any team. When you sync, it only sets the assignee to you (the current HaloPSA technician) and changes the ticket status. If an escalated ticket is being reassigned (for example, to a “Development Team”), that reassignment is coming from a HaloPSA workflow/automation or status rule tied to the escalation status — not from the extension.

To review it in HaloPSA:

Adjust or disable the relevant rule in HaloPSA if the reassignment is not desired.

A ticket is detected but missing fields

Some fields depend on the page layout. For Jira Cloud, make sure you are on the issue view (not a board card).

Tips

Need Help?

Contact your internal IT/support team or the PageSignal administrator.