Swiftlane sucks. A resident's review of Swiftlane's intercom and access control

More than a year of unreliable doors, unanswered emails, and "no ETA." This is what happened after my Chicago condo building bought Swiftlane's access control system. If it's happening to you too, tell me.

Share your Swiftlane experience

Last updated

Swiftlane problems: what was promised vs. what I got

What was promised

  • Tap a locked phone on any reader to unlock
  • Double-tap the back of the phone to unlock
  • Tap with the Swiftlane app open to unlock
  • A system resilient to internet and power outages
  • A 45-day return policy on hardware and subscription

What I got

  • Phone unlock that works sometimes, slowly, or not at all
  • Phones vibrating in residents' pockets for no reason
  • Intercom reboots in the middle of the day
  • Doors that stop working when the internet goes down
  • A main entrance door that still doesn't work
  • An installation that was missing a required component for months

The timeline: phone unlock not working, outages, and "no ETA"

  1. August 2025

    My building installs Swiftlane intercoms and STid hybrid "no-PIN" readers. Phone unlock, the headline feature, doesn't work reliably from day one.

  2. September 2025

    Within the 45-day return window, I send Swiftlane a formal written notice that the system does not perform as marketed.

  3. October 2025

    Swiftlane acknowledges that Bluetooth tap-to-unlock "only works if the app is running in the background, and even then it can be inconsistent." They say it has been escalated as a P1 with the reader manufacturer, extend the refund window, pause billing, and promise a service credit once it's fixed. Swiftlane's VP of Sales, Jason Petrini, writes to say that supporting me is his "top priority."

  4. October 2025

    I have to chase them for an update. Swiftlane tells me an Apple update, iOS 26.1, "will resolve the behavior." When I ask what happens if it doesn't, the answer is that it's "difficult to outline a definitive course of action."

  5. Late October 2025

    I test the iOS 26.1 betas and release candidate. No improvement: unlocks take so long that it's faster to open the app or use a physical key, some don't happen until the app is opened, and every tap pops up Apple Wallet. A Swiftlane engineer confirms there is "no ETA or clear deadline" for a fix.

  6. November 2025

    After iOS 26.1 ships, residents' phones start vibrating constantly in their pockets. Every neighbor I asked has the same problem. Swiftlane says it hasn't heard of this "from other users apart from users of your building."

  7. December 2025 – January 2026

    I ask for a clear status. The readers are still unpredictable: sometimes they work right away, sometimes after a long wait, sometimes the light changes but the door stays locked, and sometimes the door unlocks with no light change at all. The intercom reboots during the day. A Cloudflare outage knocked the system offline, even though it was sold as resilient to internet outages. Swiftlane's answer after the holidays: the reader problems are "on manufacturer" with no milestone or deadline, and offline operation "depends on the building/hardware setup."

  8. April – May 2026

    While preparing a technician visit, Swiftlane discovers that the Access Control Unit, the component offline operation depends on, was never installed at my building. Swiftlane never sent it to the installer, and the installer never flagged it as missing. Swiftlane ships one and the visit gets rescheduled around delivery.

  9. After the ACU install

    Performance regresses to the same erratic behavior. During an internet outage, keypads beep and light up for phone taps and codes, but the door strikes don't fire. Codes work only at the main unit.

  10. Fall 2026

    A third outage leaves my building's main entrance door not working. After months without a meaningful response, I only get attention by escalating publicly to Swiftlane's founder and CEO, Saurabh Bajaj, on LinkedIn. Swiftlane's proposed fix is a technician visit to check backup power and offline behavior. A correct installation checks both before handoff. And they want a site visit fee on top.

In Swiftlane's own words

"When issues arise, we don't shy away, we take full ownership and work tirelessly to resolve them."

Jason Petrini, VP of Sales, Swiftlane, October 2025

"Our testing shows BLE unlock only works if the app is running in the background, and even then it can be inconsistent."

Swiftlane Account Executive, October 2025

"If the system doesn't work, then it doesn't work, independently on whether it is Apple's fault, partner fault or Swiftlane fault."

Swiftlane engineer, late 2025

"There is no ETA or clear deadline when this can be fixed unfortunately."

Swiftlane engineer, late 2025

"Please note that a site visit fee will apply for the technician dispatch and would need to be covered individually."

Swiftlane technical support, October 2026

Offline mode: missing hardware nobody noticed

Swiftlane was paid in full to supply and install this system. It never sent the installer the Access Control Unit, the component that keeps doors working when the internet is down. Swiftlane itself only discovered this in spring 2026, months after installation.

The installer never stopped to ask why a critical component was missing. And as far as I can tell, nobody ever tested what happens when the internet or the power goes out. That's the most basic check before anyone hands over a door system. Instead, residents found out the hard way, standing at doors that wouldn't open during real outages.

Like the reader manufacturer, the installer was part of the job Swiftlane was paid to deliver. A working installation was Swiftlane's responsibility.

Swiftlane customer service: "It's the manufacturer's problem"

Again and again, Swiftlane pointed the finger elsewhere: the reader problems are "on manufacturer," the fix would come from an Apple update, and their partner is "in talks with Apple."

But my building didn't buy anything from the reader manufacturer. It bought a Swiftlane system, hardware and subscription, under a Swiftlane purchase agreement. Swiftlane chose STid as its reader partner, sold those readers as part of its product, and marketed what they would do. Choosing a supplier is a business decision, and it doesn't hand off responsibility for the product you sell. If a car's brakes fail, the automaker doesn't tell the driver to call the brake supplier.

Even Swiftlane's own engineer agreed: "if the system doesn't work, then it doesn't work, independently on whether it is Apple's fault, partner fault or Swiftlane fault." I just want Swiftlane to act like it.

Swiftlane reviews and complaints from other buildings

I'm not the only one. In March 2026 a property manager posted a warning about Swiftlane on Reddit, and people from other buildings replied with their own experiences. Here are some public, firsthand complaints. Each one is quoted word for word and linked, so you can read the whole thing.

For balance: Swiftlane's average ratings on review sites are high (at the time of writing: Capterra 4.6 from 58 reviews, Trustpilot 4.4 from 111, G2 4.7 from 17), and plenty of people on Reddit say it works well for them. The complaints above are the ones that match what I've lived through.

A note on Swiftlane's online reviews

One Swiftlane resident wrote on Reddit that Swiftlane's support team asked them to comment on a thread. Worth keeping in mind when you read reviews before you buy.

What I'm asking for

Share your Swiftlane experience

Resident, board member, property manager, or installer: if Swiftlane has let you down, I want to hear it. Submissions are reviewed before anything is published, and your email is never published.

Privacy: I store what you type into this form (name, email, role, city, products and your story) so I can review it. Only I see submissions. If a story is published, it shows your role, city and story. It never shows your email, and shows your name only if you ask. Your email is used only to follow up with you. To have a submission deleted, email hello@swiftlanesucks.com from the address you submitted with. The verification check is run by Cloudflare Turnstile, which receives your IP address to tell people from bots. This site does not store your IP.