# Milestone M32 - phone call, minimum start time increment, variables and more

> Milestone M33 brings a new phone call meeting option, bug fixes, UI improvements, and enhanced scheduling features for a smoother booking experience.
- **Authors**: Kirti Gulati
- **Published**: 2025-03-24
- **URL**: https://www.neeto.com/neetocal/blog/milestone-m32-updates
- **Page title**: Milestone M32 - phone call, minimum start time increment, variables and more
- **Meta description**: Milestone M33 brings a new phone call meeting option, bug fixes, UI improvements, and enhanced scheduling features for a smoother booking experience.
- **Keywords**: meeting scheduling, phone call option, workflow enhancements, booking updates, availability fixes, Google Calendar, and scheduling tool

---

Let's go through what we got done in Milestone M32 (Mar 10 - Mar 23).

## New features and enhancements🚀

#### ✅ **Phone call option for meeting mode**

Hosts can now can select [phone call](https://neetocalhelp.neetokb.com/p/a-6fd01185) as one of the options when choosing a meeting place. This makes scheduling more flexible and convenient for those who prefer phone conversations over video or in-person meetings.

#### ✅ **Minimum start time increment set to 3 minutes**

The minimum[start time increment](https://neetocalhelp.neetokb.com/p/a-1ce57ebe) has been updated from its previous value which was 5 to **3 minutes** , giving hosts fine control over their scheduling.

#### ✅ **New variables for booking time in emails**

We’ve introduced new [dynamic variables](https://help.neetocal.com/articles/dynamic-variables) that allow [workflow](https://neetocalhelp.neetokb.com/p/a-eb3768ff) emails to specify the **booking start and end times** in both the client’s and host’s timezones. This ensures better clarity and reduces confusion regarding scheduled times.

## Bug fixes⚒️

#### ✅ **Fixed missing time slots for clients behind UTC**

Clients in timezones behind **UTC** were facing an issue where some time slots for the current day were missing. This has now been resolved, ensuring all available slots are correctly displayed.

#### ✅ **Proper slot ordering in Russian language**

When the page was set to **Russian** , time slots were not appearing in the correct order. This issue has been fixed.

#### ✅ **Disabled workflows execution**

There was a bug where **disabled workflows** were still running. This has been fixed, ensuring that only active workflows execute as expected.

#### ✅ **Thank you page redirection variables fixed**

Previously, variables used in the **Redirection to external link** option on the Thank you page were not working. This has now been corrected, so dynamic variables function properly.

#### ✅ **UI fix for editing availability in Safari**

Host editing their availability on the **Safari browser** were experiencing UI issues. This has been fixed for a smoother experience.

#### ✅ **Meeting hosts can now update booking notes without admin permissions**

Previously meeting hosts without **admin permissions** were unable to update booking notes. This is now a standard permission, allowing hosts to make necessary updates without needing additional access.

#### ✅ **Fix for availability override using external API**

Fixed an issue, where setting an **availability override** as unavailable for a day via the external API wasn’t working correctly. This now functions as expected.

#### ✅ **Google Calendar read-only access selection issue fixed**

Hosts were mistakenly able to select Google Calendars that had **read-only access** to add events. This has been corrected, ensuring only full access calendars can be used for event creation.

#### ✅ **Booking URL variable now available for calendar events**

The **client.booking\_url** dynamic variable was missing when customizing calendar events. This has now been added, making it easier to include booking links in event details.

#### ✅ **Fixed 403 error on intro page creation**

Hosts with permission to manage **intro pages** but not scheduling links were encountering a **403 error** when creating an intro page. This issue has now been resolved.