Get Started Guide

Set Up Prudens Around the Core Screens Your Team Will Use Every Day.

This guide follows the Prudens section in the left navigation and gives your team a practical rollout path: set up your AMS, configure Virtual Assistance, compare coverage, build proposals, review carrier appetite, and move work into submissions.

Start the Rollout Back to Guides

Recommended rollout order

  1. Prudens AMS Setup
  2. Virtual Assistance
  3. Policy Comparison
  4. Proposal Builder
  5. Carrier Appetite
  6. Submissions
1

Set Up Your AMS

Start with Prudens AMS setup so the rest of the workflow has live account data and a clear operating model.
2

Configure Client Intake

Set up assistants, routing, messaging, and operating rules before you automate downstream work.
3

Produce Service Outputs

Move from intake into comparison, proposal creation, appetite review, and final submissions.

Before you begin

Have one real account, one real producer workflow, and one target line of business ready. Prudens works best when you implement against an actual operating process instead of trying to configure everything at once.

  • Pick one AMS or CRM source of truth for the first rollout.
  • Choose one assistant or service workflow owner.
  • Prepare sample quote packets, proposal inputs, and submission forms.
Step 1

Prudens AMS Setup

View Feature Page

In the Prudens leftnav, this is the foundation screen. Configure Prudens AMS first so account records, documents, and activity data can be used by the other Prudens workflows.

What to configure

  • Set up accounts, policy structure, and user workflows in Prudens AMS.
  • Confirm the objects you need are available: accounts, contacts, policies, activities, and documents.
  • Validate your data flow and ownership before turning on automation so you do not create duplicate updates.

What good looks like

  • Your team can open one account and see current client context without rekeying data.
  • Documents and notes are available for comparisons, proposals, and submissions.
  • Users know which system owns edits for each record type.
Step 2

Virtual Assistance

View Feature Page

Under the Prudens heading, the Virtual Assistance group includes Assistants, Settings, Live Data, and Realtime. This is where you define how Prudens greets, qualifies, routes, and escalates inbound work.

Assistants Settings Live Data Realtime

Start here

  • Create an assistant with a clear name, overview, language, and voice.
  • Define greetings, phone numbers, SMS/Text behavior, email handling, and activity logging.
  • Set escalation rules for calls or requests that should not remain automated.

Operational advice

  • Launch with one call flow first, such as service inquiries or new business intake.
  • Use Live Data and Realtime to monitor how the assistant behaves before broad rollout.
  • Keep the assistant promise narrow at first so the handoff quality stays high.
Step 3

Policy Comparison

View Feature Page

Once your data is connected and intake is stable, move into Policy Comparison. This screen is where your team can collect quote resources, run AI analysis, and produce side-by-side output for review.

  • Create a new comparison record and save it early so generated output stays attached to the account.
  • Load the carrier quote files and supporting resources your producers would normally review manually.
  • Use the AI chat and comparison result views to identify gaps, value differences, and recommended options.
Step 4

Proposal Builder

View Feature Page

After comparison, Proposal Builder turns account resources into client-ready output. The working pattern here is simple: select the account, use AI Chat to shape the draft, review the proposal, then finalize the presentation.

AI Chat Draft JSON
  • Use the account and resource selector first so the proposal draft is grounded in real account data.
  • Generate the draft in AI Chat, then review the structured proposal content before sharing externally.
  • Standardize one proposal format for your first rollout so your team is not debugging content and process at the same time.
Step 5

Carrier Appetite

Open Appetite Library

Carrier appetite is the decision support layer between intake and submissions. It helps your team narrow the market before they build a package or send work downstream.

How it fits into Prudens

  • Use carrier appetite guidance before starting a final submission package.
  • Reference appetite notes alongside Ask Prudens and underwriting guidance when evaluating risk fit.
  • Confirm eligibility and rules with the carrier before quoting or binding.

What to avoid

  • Do not treat appetite notes as binding authority.
  • Do not skip appetite review if the submission package is being generated from intake data.
  • Do not rely on stale carrier knowledge without checking the latest underwriting rule set.
Step 6

Submissions

View FNOL Feature Page

In the Prudens leftnav, submissions show up through the Form Automation and Underwriting flow. Start by defining packages, then open the AI-assisted Submissions workspace to assemble and complete the outbound set.

Packages Submissions AI Select
  • Create packages that map forms, carriers, and requirements before asking AI to assemble a workflow.
  • Use the Submissions tab to review package rows, required documents, and completion status.
  • For FNOL workflows, apply the same pattern: capture complete intake first, then route to the right carrier with supporting documents attached.
Operating model

How to roll this out without creating noise

First 2 weeks

  • One AMS setup workflow.
  • One assistant use case.
  • One comparison and proposal workflow owner.
  • One submission package template for the target line of business.

Metrics to watch

  • Time from intake to first comparison draft.
  • Time from comparison to proposal sent.
  • Submission package completion rate.
  • How often users leave Prudens to finish work manually.

Need help tailoring the rollout to your agency?

We can map Prudens to your current service, sales, and submissions workflows.

Schedule a Working Session