Nimbus Coworking runs three properties — Ahmedabad, Vadodara, and Surat — roughly 1,400 desks combined. Ahmedabad came first, a single floor near SG Highway that filled up faster than founder Rohit Bhatia expected; Vadodara and Surat followed within a couple of years once the model proved out. Each location has one community manager who runs the space day to day: member support, walk-in day passes, events, and, until recently, every phone call and web inquiry from someone who wanted to see the place before joining.
Illustrative example. Nimbus Coworking is a composite scenario built to show how AIVA works for this kind of business — not a verified customer account.
The problem with three phone lines
Tours are how Nimbus converts prospective members, and tour requests came in constantly — about 150 a month across all three locations. Unlike a lot of small businesses, coworking is a genuine comparison-shopping category: someone deciding between Nimbus and another space in the same city is weighing price, vibe, and location, and the tour is usually the moment that decides it. That made getting the tour right — the right time, the right location, an actual person expecting you — more important than it might sound.
The trouble was matching requests to the right person at the right time. A call to the Ahmedabad number about the Vadodara space wasn't unusual. Neither was a tour getting agreed to verbally and then forgotten because the community manager was mid-onboarding with someone else when it came in. Before AIVA, tour scheduling ran on a shared spreadsheet and whatever coordination happened over a WhatsApp group between the three community managers — which worked fine at low volume and started dropping things as soon as more than one location got busy at once. Founder Rohit Bhatia estimated Nimbus was fully losing or mishandling something like one in five tour requests — never confirmed, never followed up, gone.
Rohit remembered one week clearly: a prospective member called about touring the Surat location, got verbally booked against the Ahmedabad calendar by mistake, showed up in Surat anyway because that was the location near their office, and left without a tour because nobody there was expecting them. They didn't call back. A separate mix-up cost them a tour a different way: a community manager double-booked a tour against her own onboarding session for a new member, realized twenty minutes before it was meant to start, and had to scramble to find someone else on site to cover it.
Even the tours that did get booked had a no-show problem: confirmation was whatever the community manager remembered to send, which meant sometimes a text, sometimes nothing. No-show rate ran close to 35% — high enough that community managers started half-expecting empty slots, which made the whole thing feel less worth planning around carefully.
One system, three locations
We set up a single AIVA deployment — voice and the web widget — covering all three properties. It identifies which location a caller means, asking directly if it's not obvious ("which location works best for you — Ahmedabad, Vadodara, or Surat?"), checks that location's real tour calendar, and books directly. Every booking gets an SMS confirmation and a reminder about 90 minutes ahead of time, with the address and the community manager's name attached, so it still feels like a person is expecting you — because one is.
We connected each location's real calendar separately rather than treating all three as one generic grid — Ahmedabad's meeting-room-heavy floor plan means tours run differently there than at the more open Surat space, and AIVA's booking reflects what a visitor actually sees at each property. One deployment, three calendars, all running on the same pay-as-you-go pricing regardless of how many properties it covers.
Rolling out across three cities surfaced one thing we hadn't anticipated: locals in Ahmedabad often refer to the property by its street rather than its official name — "the SG Highway space" — and the first version of AIVA didn't reliably connect that phrase to the right location. We caught it within the first week reviewing call transcripts, added local landmark names as recognized aliases for each property, and it hasn't come up as a problem since, in any of the three cities.
AIVA also fields the routine questions that used to eat into the tour itself — plan pricing, day-pass rates, meeting room availability — so a community manager giving an actual tour can spend that time on the space and the fit, instead of re-explaining a price sheet a prospect could have gotten over the phone.
Beyond tours: meeting rooms and day passes
Tours aren't the only thing that rings Nimbus's phones. A member's guest wanting a day pass, a startup needing a meeting room for a client pitch on short notice, a member calling to book the phone booth for a call in twenty minutes — all of these are the same underlying problem as a tour booking: something to check against a real calendar and confirm, not something that needs a community manager to stop what they're doing and think about it. AIVA handles both categories through the same deployment, checking day-pass capacity and meeting-room calendars alongside each property's tour calendar.
The two request types don't behave the same way, though, and treating them identically was an early mistake we corrected inside the first couple of weeks. A tour request has slack — someone hoping to visit Thursday is usually fine with Wednesday instead if Thursday's full. A meeting-room request from an existing member almost never has that slack, because it's built around an external client's schedule, not the member's own. AIVA now treats meeting-room and day-pass requests as fixed-time bookings that either have a real opening or don't, rather than offering the same flexible back-and-forth it uses for tour scheduling — which matches how a member actually thinks about a room they need in forty minutes for a call with someone else, not a property they're casually comparison-shopping.
That distinction mattered more once Vadodara and Surat came online, since meeting-room demand scales with member headcount in a way tour demand doesn't — a fuller building means more of these short-notice, fixed-time requests stacking up on a given afternoon, not more flexibility to work with.
The results
Two months after rollout:
- Tour requests successfully booked (vs. lost or mishandled): ~80% → near 100%
- Tour no-show rate: 35% → 14%
- Cross-location mix-ups: effectively gone
- Tour-to-membership conversion: up modestly — more tours are actually happening, at times the community manager is genuinely free to make them count
Community managers now get tours handed to them as a clean, confirmed slot on their calendar instead of an unplanned interruption in the middle of something else.
Running three locations used to mean three front desks, three phones, three chances for a lead to fall through. Now it's one system that happens to know the difference between our buildings.
What Rohit tells other coworking operators
Connect each location's calendar on its own terms — don't treat a multi-site business as one generic grid, because the floor plans and what a tour actually shows a visitor are genuinely different property to property. Build in the local nicknames people actually use for your locations, not just the official names on your website. And match the reminder timing to real travel time in your city — 90 minutes ahead works for Nimbus because that's roughly how much notice someone needs to actually leave for a coworking tour, not just glance at a calendar.
Rohit's read on it now: growing to a fourth or fifth location doesn't mean hiring a fourth or fifth person to answer the phone. It means adding a calendar. He can also see tour-to-member conversion broken out by location in one dashboard now, instead of stitching it together from three community managers' memories at the end of the month. If you're running a multi-location business, our guide on multi-location franchises covers the same rollout sequencing, our coworking-specific guide goes deeper on this vertical, or you can just try it against your own properties.
There's a quieter change Rohit mentioned almost in passing: the three community managers talk to each other differently now. The WhatsApp group that used to be full of "did anyone confirm the 3pm Vadodara tour" messages is mostly just used for actual community questions these days — the coordination overhead that used to eat into their day simply isn't there to coordinate anymore. It's the kind of change that's easy to miss in a results summary built around numbers, but it's the one Rohit mentioned first when we asked what actually felt different, three months in.