Back to the blog

Agendize Product Updates January 2020

January 17 2020 | Agendize

Modified on 16/03/22 | 2 minutes read

New features & Innovations



Reseller SMS quota

As a reseller, you can define how much credit should be added or reloaded to a customer's account for text-messages :


Please find our documentation here


Birthday search in your CRM

You can search contacts in your CRM based on their birthdate's month and/or day. A good way to send out a marketing email to all your clients having their birthday next month :


Please find our documentation here

Create a custom period from a staff calendar

A new privilege can be granted to your staff to enable them to create custom calendar periods (eg: doing part time for the upcoming week) right from their calendar view :



Warning about upcoming appointments when deleting a staff

A warning about upcoming appointments will be displayed when removing a staff :





API code snippets in PHP and JS

On top of our API documentation, we share code samples in PHP and JavaScript to illustrate some use cases with the API: you can find these snippets here


New parameter to track the origin of a new scheduling appointment

When booking an appointment with the API, you can now define if it was generated from a public widget or operated by a staff from a backoffice. A new parameter source is available for that purpose :

  • dashboard (console)
  • mobile (application mobile)
  • widget (module de prise de rendez-vous public)


Marketing consent update

When synchronizing contact information from a CRM to Agendize, you can now use the API to update the marketing consent in Agendize CRM.

Please find our documentation here


Improvements for the mini-calendar

The last days of the previous month and the first days of the next month are now displayed. Past days are now grayed out to help distinguishing them from future days :



7-days and 14-days reminders

You can now trigger text-messaging and email reminders 7 days and 14 days before an appointment :



Please find our documentation here

This article was written by