For DMVs, tax offices, colleges and utilities

Multiple data sources. One clear picture.

Meridian connects queue and business data, showing what drives wait times, staffing and service, with every number explained.

Book a demoSee Meridian at work
Queue dataFrom your queue system
Business dataTransactions from your business systems
MeridianOne clear picture
Illustration: a waiting line, a service counter and a records room each send a stream of light up into one large screen showing a single combined chart, while a manager looks up at it.

Your data lives in separate systems.

Your queue system shows who waited and for how long. Your business systems show what each customer came in for and how long the transaction took. Each keeps its own records, so the story of a day is split in two, and neither one tells you what the numbers mean.

Your queue system shows

  • When people arrived and checked in
  • How long they waited
  • Which counter served them
  • Who walked out

Your business systems show

  • Which transactions were completed
  • How long each type of transaction takes
  • What was left unfinished
Illustration: the waiting line and the service counter on separate platforms, each with its own half-picture floating above it. A manager stands alone in the gap between them, unable to see both at once.
TodayTwo systems, two half-pictures.
Illustration: the waiting line and the service counter on one shared floor, with one large screen above them showing a single chart that combines both. The manager looks at it.
With MeridianOne clear picture.

What we do

Your queue and business data, together and explained.

Meridian shows how your offices are running. It connects your queue data with your transaction records, and every chart comes with a plain-language guide: what the number means, whether it's on target and where to look next.

Every chart explains itself.

Each chart is titled as the question a manager asks. Open its guide to see how to read it and what to look for next.

Use it for tomorrow's staffing and for next year's budget request.

A Meridian chart with its How to read guide open, explaining what each line and bar means.
Queue Summary · How to read guide

Four steps, agreed with you before we start.

Connecting two systems is mostly about asking the right questions about how your offices run. That's the part we do.

Our team works alongside your analysts and IT.

  1. 1

    Discover

    We learn your services, your offices and the questions you can't answer today.

  2. 2

    Connect

    We connect to your queue system and get a copy of your transaction records. We only read, we never change anything, and we leave out personal details.

  3. 3

    Build

    We build your charts around the questions you ask.

  4. 4

    Interpret

    We walk your team through what it shows. After that, Meridian explains every number on its own.

Insights

Research and guides on public service wait times.

Organizations can share their records with us, with names removed. We turn them into free research, so every office can see how it compares with others.

All insights
Bar chart of ten customer waits against a 15-minute target: seven helped in time, three waited longer (18, 19 and 33 minutes).

Operations · Analytics · 6 min read

How to Tell If Your Office Is Meeting Its Wait-Time Target

Measure the share of served customers helped within your target, then check what that number hides: how long the late customers waited, who walked out, and which queues let down the most people.

Product · Meridian · 5 min read

Your Dashboard Titles Are the Problem

A clinical chart title tells you what was calculated. A question-based header tells you what to do about it. Here's the small change that cuts the quiet friction keeping good reports unused.

Benchmarks · Coming soon

Where the wait comes from

Our first study of how transaction mix affects wait time, compared across similar offices. Ask us about including yours.

Questions public service teams ask us

What is VelocityNex?

VelocityNex helps public service organizations, such as DMVs, tax offices, colleges and utilities, understand what drives their wait times, staffing and service. Its software, Meridian, connects queue data with business data and explains every number in plain language. The VelocityNex team sets up Meridian with each organization and publishes free research on public service wait times.

How is this different from the analytics in my queue system?

Built-in analytics read the queue system's own data: arrivals, waits, service times. Meridian connects them with your business data, such as which transactions were completed and how long each took, and explains what each number means. Our team sets it up with you.

What business data can you bring in?

Transaction records from the systems behind your counters: the transaction type, start and end times, the outcome and the station. We read them through a read-only connection or a scheduled export, and we leave out personal details like names, plates and addresses.

Does it work with our queue management system?

Meridian is vendor-agnostic and already runs on more than one queue system. Tell us which one you use and we'll tell you how the connection works.

How do you work with our analysts and IT?

Alongside them. We handle the connection and the build, and your analysts get connected data with clear definitions they can work from.

Built for public-sector data.

Your data stays yours. We take only the fields the analysis needs, and our security overview is ready for your IT review.

Request the security overview
  • Isolated per organization. Your data is never mixed with another organization's.
  • Encrypted. AES-256 at rest and in transit, hosted on AWS.
  • Read-only. We never write to your queue system or business applications.
  • Minimal personal data. Personal details stay out. Research uses only anonymized, aggregated data.

Better answers.

Will it work with your systems? Let's find out.

Tell us which systems your offices run. We'll walk you through Meridian.

Book a demo