Authentic
AuthenticContact
  • Authentic 101
    • About Authentic
    • Company Background
    • Customer Reviews
    • How Authentic Works
      • Captive Insurance
      • Business Owner's Policy
      • Coverage Options
      • Our Partner Appetite
        • Exclusions
        • Endorsements
  • Embedding Insurance
    • Integration Overview
    • Add Insurance to Your Platform
      • Embed our widget
        • Accessing Event Data through Webhooks
      • Different endpoints & functionality within our widget
        • Instant Estimate (/estimate)
        • Welcome Page (/welcome)
        • Direct to Lead Form (/apply)
        • Policy Hub (/policy)
    • Data Share
      • Data Sharing via Widget
      • Data Sharing via URL
      • Commonly Prefilled Questions
      • SMB Class Codes
      • Data Capture (Easy Webhook Set Up)
      • Sample Webhook Events
    • Authentic User Verification Offering(s)
    • Custom Insurance Domain
    • Tracking Marketing (UTM Params)
  • Go To Market
    • Go To Market for SaaS Partners
      • Create Access Points
      • Buying Triggers
      • Prequote Marketing Emails
        • Authentic-Led Prequote Campaigns
        • Tenant-Led Prequote Campaigns
        • URL Prefill Instructions
    • Brand Assets + Marketing Templates
    • Generating Estimate Links
  • More Reading
    • Learn More about Authentic!
    • Why Authentic?
  • Support
    • FAQs
Powered by GitBook
On this page
Export as PDF
  1. Embedding Insurance
  2. Add Insurance to Your Platform
  3. Different endpoints & functionality within our widget

Policy Hub (/policy)

Direct customers who have already purchased to /policy

PreviousDirect to Lead Form (/apply)NextData Share

Last updated 6 months ago

Our policy hub is where we send Policy Holders to manage their policy post-purchase. In there, they can endorse their policy, add new locations, add new products, file a claim, or cancel their policy.

One note: if you intend to directly send customers to /policy within your platform, we strongly recommend you first begin sharing some sort of customer ID with us (preferably through the URL, which you can ). Without sharing your customer ID, we will not know which policies are owned by which customer, so the UX of the policy hub is not particularly smooth without it.

Even with your customer ID shared, the user will still have to authenticate with a code sent to their email to view/manage their policy(s). However, after initially shipping with just customer ID shared, we are able to integrate with your MFA if there is customer demand.

read about here