Hirepad White-Label Portal Launch (Onboarding)

Hirepad White-Label Portal Launch (Onboarding)

1. 01

   Point the white-label branding and custom domain settings at the agency's own domain

   Candidates and clients must never see the vendor's name. Complete this before any user is invited, because portal URLs are baked into every shift alert and booking confirmation Hirepad sends. Vendor guidance puts a full branded launch at 2-3 days, so schedule the DNS change early in the week.

2. 02

   Import the candidate database and map each candidate to role types

   Hirepad matches candidates to openings by role, so a flat CSV import without role tags produces empty shift alerts. The Starter plan caps active candidates at 500 and the Growth plan removes that cap, so confirm which tier the agency sits on before importing a full roster.

3. 03

   Build role-specific compliance certificate rules with auto-expiry reminders

   Set certificate requirements per role rather than globally. Hirepad fires expiry reminders 8 weeks out, which gives the agency time to chase renewals before a candidate becomes ineligible for a booked shift.

4. 04

   Create a test shift requirement and walk a pilot client through the client portal

   Have the client post and approve one booking themselves. This surfaces permission gaps while the agency is still on the call, not on the first live shift. Keep the pilot to a single client until the approval flow is clean.

5. 05

   Configure targeted shift alerts for the pilot candidate pool

   Hirepad's marketing automation sends shift alerts to matched candidates. Send one test alert to the internal team first to confirm sender identity and link routing resolve to the agency's domain, not the vendor's.

6. 06

   Turn on bidirectional post-shift reviews for the pilot client

   Both the client and the candidate submit reviews after a completed shift. Reviews feed the performance analytics the agency uses to justify placements at renewal, so enable them from shift one rather than retrofitting later.

7. 07

   Set the admin user roster and confirm the plan's seat limit

   Starter includes 3 admin users and Growth includes 10. Adding a fourth admin on Starter is a plan change, not a settings toggle, so decide the roster before the client's ops lead asks for access.

8. 08

   Run a monthly shift volume check against the plan ceiling

   Starter covers 0-50 shifts per month and Growth covers 50-300. Track the count in the admin dashboard; crossing the ceiling mid-month forces an upgrade conversation the agency should lead, not the vendor.