Can each location have different menus and hours if we run a shared central phone number?

Yes, though most multi-location restaurant groups actually run separate phone numbers per location rather than one shared number, since customers generally expect to call the specific restaurant near them, not a central line that then has to ask which location they mean. Voksha supports both models. If you do run separate numbers per location, the more common setup, each number is tied to its own menu, hours, specials, and reservation policy, so a call to your Brooklyn location and a call to your Hoboken location get entirely different, correct answers even though both are managed under the same Voksha account.

If your group does run a single central number, Voksha can be configured to ask which location the caller wants, or use caller ID or area code as a hint, and then apply that location's specific information rather than a generic group-wide answer, similar to how a call center for a restaurant chain would route calls today, except without hold times or the caller having to repeat themselves to a second person after being transferred.

This matters in practice because restaurant menus and hours genuinely diverge location to location, one location might have a patio and different summer hours, another might not serve brunch, a third might have a completely different chef-driven rotating menu. Treating every location as identical would produce wrong answers constantly, so per-location configuration isn't an edge feature for restaurant groups, it's the default expectation.