Portal Hound

Portal Hound for insurance agencies and TPAs

Carrier portals for your offshore service team, under their own names.

Policy service, endorsements, certificates and claims follow-up happen in dozens of carrier portals. Portal Hound lets your offshore CSRs work in them as named users from one agency-owned U.S. address, with a log of who touched which carrier and when.

The problem

Twenty carrier portals, each with its own idea of a suspicious login.

Carrier portals, comparative raters and agency management systems each react differently to overseas logins. The result is locked producer codes, repeated identity checks, and the temptation to hand the team one shared login per carrier.

Locked producer logins

A carrier portal that sees the agency's user signing in from three countries locks it, and the account manager's day stops.

Shared carrier logins

One login per carrier for the whole offshore team is against most carrier agreements and leaves no trail.

E&O exposure

When a certificate or endorsement goes wrong, you need to know who issued it. Shared logins can't tell you.

How it works

One button for workers. Full control for you.

You approve the portals

Add each platform your team works in. Portal Hound suggests the domains it needs, and nothing is reachable until you approve it.

Workers press Connect

They install a small app for Windows or Mac, sign in with their work email, and connect. There's nothing to configure.

Only approved portals go through

Those platforms are reached through your company's U.S. gateway, tied to that person and logged. Email, banking and everything else use the worker's own connection.

Platforms

The portals these teams approve first.

Any web platform can be approved. These are typical for insurance agencies and tpas.

Carrier portals and producer sitesApplied Epic and Vertafore AMS360EZLynx and Applied RaterIvans and Transact NowClaims systemsHawkSoft and NowCertsCertificate platformsPremium finance portals

What you get

Named users, one agency address, an audit trail for E&O.

  • Every CSR has their own carrier portal user where the carrier allows it; Portal Hound never shares a login.
  • Carrier logins come from your agency's one U.S. address, so identity checks settle down.
  • Access logs tie every carrier session to a person, which is what your E&O carrier wants to see.
  • Revoke a departing CSR in one click without changing a single carrier password.
Portal Hound admin console

Requirements

Portal Hound is for teams already allowed to work offshore.

It controls and records how your team reaches portals. It doesn't change who is allowed to use them, or where from.

Your agreements must permit offshore access

Carrier producer agreements and portal terms differ. Some restrict offshore access to policyholder data or require the carrier's consent. Check each carrier before routing it. Portal Hound is not a way around a carrier's location rules.

Every person uses their own login

Your team members sign in to each platform with accounts issued to them, in the role they need. Portal Hound never shares, stores or fills in a login, and it isn't for working as somebody else.

Regulated data stays your responsibility

Policyholder information is covered by state insurance privacy law and, for health lines, HIPAA. Your agency's safeguards and training still apply.

Tell your team access is logged

The access log records which person reached which platform and when. Tell them, and follow the privacy and employment rules where they work.

Portal Hound doesn't guarantee access to any portal. The companies that run them decide who may use their systems. Full requirements.

Questions from insurance agencies and tpas

Our carriers issue one login per agency. Does that work?

Route it through Portal Hound only if the carrier permits that login to be used by your offshore staff. Where the carrier issues individual users, use those; where it doesn't, ask them. Portal Hound doesn't change the carrier's rules.

Can we see what was done in a carrier portal?

Portal Hound logs which person reached which carrier and when. It doesn't record page contents, so the detail of what was changed stays in the carrier's own audit trail.

Does it work with our AMS?

Any web-based AMS can be approved as a portal. Desktop-installed systems aren't affected either way; Portal Hound routes browser traffic to approved sites.

See Portal Hound with your own portals.

We'll show you the worker app and admin console, and talk through setting up a gateway for your team.