Portal Hound

Portal Hound for BPO and VA agencies

One gateway per client, named staff, and a log you can hand to the client.

Your clients hand you their portals and expect you to know who touched them. Portal Hound gives each client engagement its own dedicated gateway and address, named access for your staff, and an access log per client. Agencies resell it or run it under their own brand.

The problem

Clients want control and proof. Shared logins give them neither.

Every client questionnaire asks the same things: who on your side can access our systems, from where, and how do you cut them off. Home connections and shared client logins have no good answer, and your best accounts leave over it.

Client security questionnaires

'Who can access our systems, from where, and how do you revoke them' needs a one-paragraph answer.

Shared client logins

One login per client for your whole team is the first thing a client's security team will reject.

Offboarding across clients

A departing agent had access to six clients' portals. Which passwords do you change tonight?

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 bpo and virtual assistant agencies.

Each client's own portalsHelpdesks and CRMsAccounting and payroll platformsMarketplaces and e-commerce adminHealthcare payer portals (with a BAA)Marketing and ad platformsProperty, logistics and insurance systemsClient SSO and admin consoles

What you get

A dedicated gateway per client, named agents, and per-client logs.

  • Each client engagement gets its own gateway, address and sign-in pool; nothing is shared between clients.
  • Your agents use their own users on each client platform; Portal Hound never shares a login.
  • Per-client access logs tie every session to a named agent, ready to show the client.
  • Revoke an agent from one client, or all, in a click. Resell at 15% or white-label under your brand.
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

Each client's contracts and each portal's terms decide whether offshore access is permitted and under what conditions. Confirm with the client before routing anything. Portal Hound is not a way around a portal'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

Your clients' data is governed by your contracts with them, including any regulatory terms they pass through (HIPAA, FCRA, privacy law). Portal Hound supports access control and audit; your obligations under those contracts 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 bpo and virtual assistant agencies

Can we bill clients for it?

Yes. Resell at list price and keep 15%, or white-label it under your own brand. See the partner program.

One gateway for all clients, or one per client?

One per client. Each client's engagement is isolated: its own gateway, address, sign-in and logs. That's what their security teams expect.

Can the client see the logs?

You can export them for the client, and with an Enterprise plan the client can hold the gateway in their own AWS account and see everything directly.

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.