Skip to main content

Built by transit people

We worked in transit customer service before we wrote software for it.

Our story

We worked at public transit agencies. We used the old complaint systems. We called the vendor for changes as small as a new option in a dropdown list. We kept spreadsheets that the whole department came to depend on.

Most customer service software is made for retail stores or IT help desks. Transit is different. It has routes and vehicles, ADA rules, board reports, and riders who call from a bus stop at 11 PM.

So we built Pulse for transit. Your own staff can change it. It handles the calls and complaints that agencies get every day.

  1. We worked at transit agencies

    We used the legacy systems and called the vendor for every small change.

  2. We saw what agencies needed

    Customer service tools built for transit, not generic software with transit added later.

  3. We built Pulse

    Software that your own staff can change, made for routes, riders, and deadlines.

How we work

Made for transit

Each feature must solve a problem that an agency told us about, or that we had ourselves.

Your agency makes the changes

Your staff can change fields, workflows, and routing without us. You should not need to call us for a small change.

Straight answers

If a feature does not exist yet, we say so. For example, RideInfo answers fixed-route questions only. Our FAQ says that.

AI where it saves time

We use AI to answer arrival questions, sort new feedback, and match lost items. We do not add it anywhere just to say we have it.

Let's talk about your agency

Tell us how your agency handles calls and complaints today. We will tell you honestly whether Pulse is a good fit.

Get in Touch