IP Allowlists in Helpdesk Tools: How to Give Remote Agents a Fixed Address

A helpdesk holds names, emails, order histories and sometimes payment details, so many admins turn on IP restrictions sooner or later. In an office with one static address this takes ten minutes. With agents working from home it often turns into a stream of internal tickets: someone's router restarted overnight, their ISP handed out a new address, and the helpdesk now refuses to let them sign in.

This guide covers what the main helpdesk tools actually check, three ways to give remote agents an address the allowlist accepts, and where each of them stops working.

What helpdesk IP restrictions check

The feature looks similar across products, but the details differ in ways that matter for remote teams.

Zendesk. IP restrictions live in Admin Center under Account, then Security, then Advanced. You can enter single addresses, ranges with an asterisk wildcard such as 192.168.., or CIDR blocks. Outside the allowed addresses, sign-ins, page access and API calls fail across all Zendesk products, including the mobile apps. Customers can be allowed to bypass the restriction, agents and admins can't. Zendesk also warns that turning the feature on can break third-party integrations unless their IPs are on the list. It's available on all Suite plans and on Support Team, Professional and Enterprise.

Freshdesk. The IP Allow/Block list is part of the Enterprise plan, under Admin, then Security. You choose whether it applies only to the agent portal or to every channel, including the customer portal, chat widget and mobile SDK. Up to 900 entries fit under the fair usage limit. Changes apply immediately, and configured admins get an email each time the settings change. Editing the list requires an admin role with the "Play God with Super Admin controls" permission, and Freshdesk stops you from blocking your own address by mistake.

Jira Service Management. IP allowlists need a Premium or Enterprise plan and are managed by an organization admin in Atlassian Administration, under Security, then Device security. Each app accepts up to 500 addresses, CIDR blocks or countries across all active policies. The allowlist covers both the agent and customer portals on the same site, and API access from other addresses is refused. Atlassian Administration itself stays reachable from outside the list, which helps if you lock yourself out.

Two things follow from this. Integrations count as users, so a reporting tool or a bot calling the API from a changing cloud address will start failing too. And only a small group of people can edit the list, which makes every changed home IP a request to a super admin.

Three ways to give remote agents an accepted address

1. Add each agent's home IP

This works for a small team with stable connections. Many home broadband lines keep the same address for weeks, but there's no promise of that, and mobile hotspots change constantly. Each change locks one agent out until an admin updates the list. If the team also uses a CRM, a billing admin or a status page tool with their own allowlists, every change has to be repeated in each of them.

2. A company VPN or zero-trust access with a fixed exit address

If you have someone to run it, this is the standard answer. All agent traffic leaves through addresses you control, and most products in this category also check device posture and tie into single sign-on. It protects more than the helpdesk. The cost is a client on every device, per-user licences or a server to maintain, and support work when the client misbehaves.

3. A dedicated proxy IP for helpdesk traffic only

A lighter option is to send only the helpdesk domains through a proxy with a fixed address and leave everything else on the agent's normal connection. The helpdesk allowlist then holds one or two entries that stay the same when agents' home addresses change.

The catch is that the proxy needs its own access control, otherwise anyone could use it to pass your allowlist. With FineProxy, access is always tied to the source IP: agents' current addresses go on the proxy's allowlist, and you can add a login and password on top. So the list of home addresses doesn't disappear, it moves to one place. That still helps in practice:

  • one list serves every tool that allowlists the proxy IP, instead of one list per tool;
  • the account supports team access with separate user roles, so a support lead can update it without super admin rights in the helpdesk;
  • an entry can be removed in one click when a contractor leaves, and the API lets a script update entries;
  • connection limits can be split between allowlisted addresses, so one agent's misbehaving browser extension doesn't use up the whole quota.

Use a dedicated IP for this, not a package one. Package proxies are shared by up to five customers, and a shared address on your helpdesk allowlist would let other customers of that IP pass the check. Dedicated IPs start at $2 per IP a month, five allowlist entries are included, and each extra entry costs $1. For a team of 12 agents on one dedicated IP, that means seven paid entries on top of the $2 address (prices as of November 2026).

Setting up the proxy option

  1. Buy two dedicated IPs in the country where most agents work. Targeting is by country. The second address is a fallback, and both go on the helpdesk allowlist.
  2. Add agents' current public IPs to the proxy allowlist. An agent can find theirs on any "what is my IP" page.
  3. Add the proxy IPs to the helpdesk allowlist before you switch the restriction on. Keep your own office or admin address on it while testing. Freshdesk has a sandbox for trying IP rules, and in Jira Service Management you can still reach Atlassian Administration if something goes wrong.
  4. Route only the helpdesk through the proxy with a PAC file. For Zendesk it can be as short as this:

function FindProxyForURL(url, host) {

  if (dnsDomainIs(host, ".zendesk.com") || dnsDomainIs(host, ".zdassets.com")) {

    return "PROXY 203.0.113.10:8085; PROXY 203.0.113.11:8085";

  }

  return "DIRECT";

}

Port 8085 is FineProxy's HTTP port for allowlist access, so the browser doesn't ask for a password. Set the PAC file in the system proxy settings or push it through your browser management policy. The second proxy in the line is used if the first doesn't respond.

  1. Decide what to do with integrations. Servers with fixed addresses can go straight onto the helpdesk allowlist. Scripts on changing cloud addresses can send their API calls through the proxy, but their source address then has to be on the proxy allowlist, so this suits a few fixed servers better than serverless functions.
  2. Test both directions. Sign in as an agent through the proxy, then remove a test address from the proxy allowlist and confirm that the sign-in fails.

Where the proxy option doesn't fit

  • Mobile apps. Zendesk applies IP restrictions to its mobile apps, and phones rarely use a PAC file. Agents who answer from their phones need a VPN or a separate policy.
  • Security beyond the IP. If you need device checks, conditional access or protection for every internal app, a VPN or zero-trust product does that and a proxy doesn't.
  • Changing home addresses. The proxy allowlist still has to follow them. The difference is that you edit one list, or let a script do it.
  • Another party in the path. Helpdesk pages load over HTTPS, so the browser builds an encrypted tunnel through the proxy and ticket contents stay encrypted between the browser and the helpdesk. The proxy provider still sees which hosts are contacted and when, so check that this fits your data processing agreements.
  • One layer of several. An IP allowlist doesn't replace single sign-on or two-factor authentication. Keep both on.

Before you switch it on

  • List every tool with its own allowlist and who can edit each one.
  • Collect the fixed addresses of every integration that calls the helpdesk API.
  • Agree who updates the proxy allowlist when an agent's address changes, and how fast.
  • Test with one agent for a day before applying the restriction to the whole team.
  • Write down how to undo it: who can reach the admin panel from outside the list, and where.