How do I schedule a demo with Mandolin for infusion intake, benefits verification, and prior auth?

If you’re evaluating Mandolin for infusion intake, benefits verification, and prior auth, the fastest way to move from curiosity to real numbers is to see the agents run your workflows. Scheduling that demo is straightforward—and you can be on the calendar in a couple of minutes.

Below is exactly how to schedule a demo, what to expect, and how to prep so you get an operator-grade session (not a generic AI tour).

This guide is written from the perspective of someone who’s run specialty-drug access and rev cycle teams. I’ll call out the specific intake, benefits, and prior auth pain points you should bring to the demo so you can walk away with real throughput and backlog math.

How to Schedule a Demo with Mandolin

Step 1: Go to Mandolin’s website

Open your browser and go to:
https://www.mandolin.com
You’ll see Mandolin positioned as a back office of AI agents for specialty-drug operations—intake, benefits, out-of-pocket estimation, prior auth, and claims.

Step 2: Find the contact / demo form

On the site, look for the primary call-to-action (usually something like “Get Started” or “Talk to Us”). You can also go directly via:

Get Started:
https://www.mandolin.com/ (primary CTA on the homepage)

Click that button to open the secure contact form.

Step 3: Submit the demo request form

In the form, you’ll typically provide:

Name and role
(e.g., Director of Infusion Operations, Revenue Cycle Leader, Access Services Manager)
Organization
(multi-site AIC, hospital outpatient department, specialty pharmacy, or clinic)
Contact information
Work email and best phone number
Focus areas
In the message/notes field, specify that you’re interested in:
- Infusion intake & onboarding (fax-to-EHR, referral normalization)
- Benefits verification (payer portals, eligibility, coverage details)
- Prior authorization (medical policy review, package assembly, submission via portal/fax/phone)

Example message you can drop in:

“We’re looking to see Mandolin specifically for infusion referral intake, benefits investigation, and medical-benefit prior auth. Our biggest issues are fax-to-EHR delays, portal-based benefits work, and variable PA requirements by payer/policy. We’d like to understand impact on minutes per referral, backlog days, and denial rates.”

Step 4: Response time and next steps

Mandolin’s team typically responds within 24 hours.

From there, you can expect:

Initial email follow-up
- Quick confirmation that they received your request
- A scheduling link or proposed times based on your availability
Calendar invite
- Video conference details (e.g., Zoom/Teams link)
- Names/roles of Mandolin participants
- Agenda focused on infusion intake, benefits verification, and prior auth workflows

What to Expect in the Demo (Intake, Benefits, Prior Auth)

You’re not signing up to see a dashboard. You’re signing up to see how AI agents actually do the work your staff does today across fax, portals, and phone.

A typical session for infusion intake + benefits verification + prior auth will cover:

1. Intake & Infusion Onboarding

You’ll see how Mandolin:

Reads and interprets referral forms, lab reports, and clinical notes
– regardless of formatting or source (fax, scanned PDFs, emails).
Extracts the key fields you care about:
- Diagnosis codes, drug/ regimen, dosing
- Supporting labs and imaging
- Ordering provider details
- Site-of-care details
Enters this into your EHR or source-of-truth system
– removing the 10–20 minutes per doc that staff spend rekeying information.

Mandolin’s published outcomes here include:

24x increase in speed:
A team that manually processed ~250 documents/day at ~20 minutes per document moved to ~3 minutes with under-2-hour turnaround.
0-day backlog:
One clinic eliminated a 4-day prescription backlog that previously consumed 2–3 FTEs, moving to real-time processing.

In the demo, ask them to walk you step-by-step from fax/scan → intake → EHR, and to show how every agent action is logged and traceable.

2. Benefits Verification (Medical & Pharmacy)

This is where most “automation” pitches fall apart, because the work lives in portals and phone calls—not clean APIs. In the demo you should see how Mandolin:

Navigates payer portals
- Logs in like a trained back-office specialist
- Pulls eligibility, plan details, and coverage specifics
Makes outbound calls to payers when portal data is incomplete or unclear
Extracts and structures:
- Deductibles, coinsurance, and copays
- Medical vs. pharmacy benefit coverage
- Prior auth and step therapy requirements, if exposed
Compiles a full benefits investigation that your team can trust

Mandolin will show how the agents do this work end-to-end, with each portal step and phone interaction logged and auditable, which matters for compliance and internal QA.

You should also ask to see how benefits data feeds into patient out-of-pocket estimation (if that’s part of your scope), including:

Site-specific fee schedules
Co-pay assistance programs
GPO and 340B pricing
Drug acquisition costs

That’s what allows Mandolin to generate precise out-of-pocket estimates that both finance and clinicians will trust.

3. Prior Authorization for Infusions

For prior auth, the demo will focus on building and submitting authorization packages the way a seasoned access specialist would:

Medical policy review
- Agents check payer medical policies to confirm PA requirements and clinical criteria.
Document gathering
- Pulls required clinical notes, labs, images, and prior treatment history from the referral / EHR.
PA package assembly
- Builds the complete prior auth submission packet according to payer policy.
Submission through the right channel
- Portal-based submission where available
- Fax or phone where the payer requires it

This is all done without relying on perfect integrations or custom APIs—Mandolin operates in the same portals and channels your team does today, but faster and without fatigue.

Ask them to show:

How they handle different rules by payer and plan
How they track status and follow-ups
How agent actions are logged to support audits and appeals later

How to Prepare for Your Demo (So It’s Not Just a “Tour”)

To get real value from a Mandolin demo focused on infusion intake, benefits verification, and prior auth, bring your operations reality into the room.

Here’s what to assemble before the call:

1. Your current baseline metrics

Have rough numbers on:

Intake / referral workload
- New referrals per day or week
- Average minutes per referral to get from fax to EHR
- Current backlog (in days)
Benefits verification workload
- Number of BVs per week (by drug or clinic, if you have it)
- Average time per BV when it lives mostly in portals and phone calls
- Common payers and plans that slow you down
Prior auth workload
- Number of PAs per month
- Average time from referral to PA submission
- Denial rate tied to missing documentation or policy mismatch

This lets the Mandolin team translate the demo into your metrics—minutes saved, backlog days eliminated, and FTE equivalents redeployed.

2. Your top pain workflows

Call out specific problem areas you want to see:

We lose 2–4 days just getting referrals fully into the EHR.
Benefits verification is scattered across 5+ payer portals and constant phone calls.
Prior auth requirements change by payer and policy, and staff spend hours chasing missing pieces.
Our backlog spikes whenever volume or staffing shifts.

Share these in the form or early in the call so they can tailor the walkthrough around those use cases.

3. Stakeholders to invite

To move quickly after the demo, include:

An operations lead (infusion, access, or revenue cycle)
Someone from finance or FP&A who cares about margin, staffing, and 340B/GPO economics
An IT/compliance voice to ask about logging, traceability, and HIPAA/BAA

Mandolin is built to be “workflows, not widgets,” so it helps to have the people who live in those workflows on the call.

Compliance, Logging, and Traceability: What to Ask During the Demo

Because Mandolin’s agents work with PHI and payer-facing actions, you should test for the controls you’d expect from any back-office solution:

Compliance posture
- How do they handle HIPAA and BAAs?
- How are AI agent actions governed and monitored?
Traceable actions
- Can you see a log of each portal interaction, fax, and phone call?
- How are decisions and data extractions recorded for audits or appeals?
Alignment with payer requirements
- How do agents stay aligned with medical policies and documentation requirements?
- How is that kept up to date as payers change rules?

Mandolin’s positioning is “Fully Compliant, Always Transparent,” with every AI action logged and traceable. Ask them to show that in the product, not just describe it.

After the Demo: How Teams Typically Move Forward

Following the session, next steps often look like:

Quantified follow-up
- Mandolin maps what you saw to your volumes:
  e.g., “At your 300 prescriptions/day and 10–12 minutes per Rx, we’d expect similar outcomes to the 0-day backlog case study.”
Pilot or phased rollout discussion
- Decide where to start:
  - Intake only, then layer benefits and PA
  - Or a full referral → benefits → PA workflow for select drugs or sites
Implementation planning
- How Mandolin’s AI agents will work in your current portals, fax lines, and phone-based workflows
- How you’ll access logs and reports for oversight

The goal isn’t just to “see AI”; it’s to understand how you could go from multi-day fax-to-EHR delays and prescription backlogs to real-time intake, faster authorizations, and fewer denials—without adding staff.

Ready to See It in Action?

If you’re dealing with:

Multi-day delays getting referrals into the EHR
Staff spending 20+ minutes per document or 10–12 minutes per prescription
Benefits and prior auth work stuck in payer portals and on the phone
Backlogs that grow every time volume spikes or someone is out

The next step is to watch Mandolin’s agents run those workflows end-to-end.

Get Started