Scheduled maintenance

7th July 2024 7am to 9am IST

The deployment is scheduled for 7th July and all the server will be shutdown, rebooted for maintenance.

We will also be doing some DNS changes to add more regional domains, so a downtime of 1-2 hours is expected for DNS propagation.

Here are the list of upcoming changes -

API changes -

We are doing some major upgrade on DaySchedule API to support some advance feature, filtering, sorting capabilities.

All the ids are in changed with numeric format now, for example - resource_id, booking_id, invitee_id etc.

Availability API

The new /availability API has a improved JSON schema { slots: [], time_zone: string, users: []} to support the upcoming needs of user selection in round-robin events and services.

{
    "slots": [
        {
            "date": "2024-06-20",
            "hours": [
                {
                    "time": "2024-06-20T11:00:00+05:30",
                    "available": 10
                }
            ]
        },        
    ],
    "time_zone": "Asia/Calcutta",
    "users": [
        {
            "user_id": 1,
            "name": "Vikash Rathee",
            "avatar": "https://cdn.dayschedule.com/vikash.png",
            "time_zone": "Asia/Kolkata"
        }
    ]
}

Date selection in webinar

The calendar and slot picker is now available in webinar as well to select a time slot from given options -

Conflict check in Group event

The conflict checker has been removed for group booking and webinar to allow booking even when something is marked on your calendar making it busy.

This ensures that more participants can join group bookings and webinars, as scheduling conflicts on personal calendars no longer prevent them from being included.

Location detection

The location detection feature now automatically identifies the city and country of all your invitees when booking. You can view this location information both in the CRM and on the booking page for all your customers.

Round robin priority

Introducing priority feature in round-robin events. You can specify a priority level to prefer booking assignments when more than one user is available for a slot. A lower priority number indicates a higher preference (e.g., Priority = 1 is the highest priority).

This ensures high-priority users are considered first, but over time, all the users receive bookings fairly in round-robin.

For instance, if there are three agents with different priorities, each new booking is assigned to the next agent in line, maintaining the priority order while ensuring no single agent is overloaded.

Bug fixes

Fixed a bug causing group event not added to the Calendar
Fixed a bug causing phone number + 91 added twice in some pages

Upcoming changes - July 2024