Quick answers to the questions that come up most often on CSR and agent calls about the BriteCore Policyholder Portal. For long-form troubleshooting, see the linked articles at the end.
"Is the portal real-time, or is it a copy of BriteCore?"
Real-time. There is no middleware, no nightly sync. What an insured sees in the portal is what you see in BriteCore the same second. A payment posted in the portal shows up in BriteCore immediately; a coverage edit in BriteCore shows up in the portal on the insured's next refresh.
"What's the difference between the portal and the app?"
Same product, different surfaces. The web portal lives at portal.yourcarrier.com. The app is downloaded from the App Store or Google Play and shows your carrier's logo on launch. They share the same configuration, the same data, and the same login. Insureds can switch between them freely.
"An insured can't sign in. Where do I start?"
Ask the diagnostic question first: "Is this your first time, or have you signed in before?"
- First time → see Helping a Policyholder Enroll.
- Signed in before → see Sign-In Issues & Resetting Codes.
90% of cases resolve with the first three checks: right portal, right username, password reset.
"Can I sign in as the insured to see what they see?"
Not directly. Two safer options:
- Use the simulated mobile preview in the admin console (Builds > Details) to walk through the same screens.
- Use the BriteCore co-browse feature — you join the insured's session with their permission and see exactly their screen without signing in as them.
If you absolutely need to reproduce something from the insured's account, ask BriteCore Support for a one-time impersonation session. It's logged in your audit log.
"What's the test bypass code I keep hearing about?"
911911 — but only in the dev / test environment. It bypasses the email verification step during enrollment. It does not work in production and never will. Don't share it with insureds.
"How long does an enrollment code stay valid?"
10 minutes by default. Configurable in Settings > Authentication > Verification code TTL. If your carrier has raised it (some go to 30 minutes), check that section to confirm.
"An insured says they didn't get a notification. Why?"
Three checks in order:
- Did anything happen? — confirm in BriteCore that the event (payment, claim status change, etc.) actually occurred. No event = no notification.
- Channel preference — open the insured's profile in admin and check Notifications. They may have turned off the channel.
- OS-level permissions (push only) — the insured may have denied push permission when they first installed the app. They re-enable it in their phone's Settings app.
"Can two people share an account?"
Each insured gets their own account, but multiple named insureds on the same policy can each enroll separately and both see the same policy. Sharing one set of credentials is technically possible but discouraged — it breaks the audit trail and prevents per-user notification preferences.
"An insured wants to delete their account."
Open a case with BriteCore Support — it's a deliberately manual process for compliance reasons. They'll need:
- The insured's identity verification.
- Confirmation the policy is closed (or that the insured understands they can't access an active policy without an account).
- Confirmation the insured wants the audit history deleted as well (GDPR-style request) or just deactivated.
"Can the insured pay with cash, check, or money order through the portal?"
No. The portal supports ACH, debit/credit cards, and (in the app) Apple Pay / Google Pay. Cash and paper checks go through your normal channels.
"Why does some insureds' dashboard show different cards than others?"
Two reasons:
- Per-product feature toggles — autopay or claims FNOL might be on for personal lines but off for commercial.
- Conditional cards — the renewal countdown card only shows in the 30 days before renewal; the bill card hides if there's no balance.
If a card you expect is missing entirely (not data-conditional), check Settings > Features and Content for that page.
"Why doesn't my carrier-branded app show on my colleague's phone when they search the App Store?"
A few reasons:
- Geographic availability — apps are typically published US-only by default. International searches won't find it.
- Search term — the app indexes by the exact name configured at submission. Searching variations may not surface it. The TestFlight or direct App Store URL is more reliable than search.
- Apple search lag — newly published apps take 24–48h to fully index in App Store search.
"A whole batch of insureds can't sign in. What do I do?"
This is an outage signal, not a user-by-user issue. Check:
- The portal status page (provided to your team during onboarding).
- BriteCore status page for related incidents.
- Open a Severity: High case with BriteCore Support immediately. Don't wait — batch issues need engineering eyes fast.
"Can the insured see their policy when they're offline?"
The mobile app caches the most recent dashboard data and a copy of the most recent declarations PDF. So an insured can view their balance, policy summary, and dec page offline. They can't take any action (pay, file claim, update profile) without a connection.
The web portal is fully online; there's no offline mode in browsers.
"What if our adjuster needs to attach something to a claim that came in through the portal?"
The adjuster works the claim normally in BriteCore. Anything attached in BriteCore appears in the insured's portal claim view. The insured gets a notification (if enabled).
"What happens if the insured updates their email address?"
If they update via the portal:
- The email on the policy is updated in BriteCore.
- Their sign-in username does not automatically change — it stays the email they originally enrolled with. To change the sign-in username, they update it in Profile > Sign-in email (separate field) and confirm via a verification email to the new address.
This dual-handling exists because some insureds use a personal email for sign-in but want statements to go to a different address (e.g., a spouse, an accountant).
"Do agents have a different view than insureds?"
Currently no — there is no separate "agent view" of the policyholder portal. Agents either:
- Look at the policy in BriteCore (their normal workflow).
- Use BriteCore's co-browse to see exactly what the insured sees in the portal.
A dedicated agent surface is on the Policyholder Portal roadmap; ask your BriteCore account team for status.
"What's WCAG AA, and why do I keep hearing about it?"
It's the accessibility standard the portal and apps are built and tested against — covering color contrast, screen-reader compatibility, keyboard navigation, and focus indicators. It matters because:
- Some carriers' state regulators require it.
- It avoids ADA-related complaints.
- It also produces a better experience for older insureds in low-light conditions.
If a CSR call is about an accessibility issue (insured can't read text, screen reader misbehaves), capture details and open a case — these get prioritized.
"Where do I file a feature request?"
Two paths:
- Bring it to your weekly check-in with your BriteCore Implementation Manager — they triage with product.
- Submit through your account team's feedback channel (varies per carrier).
Don't hold onto requests — even small UX papercuts inform the roadmap.