Appointments data model
This data source has details of all service appointments and their attributes, such as feedback rating, service, provider, start and end times, etc.
Note
Deleted appointments, segments, turnaways, and waitlisted appointments are not included here.
Example use-cases:
Appointments by booking source
Appointments by status
Guest feedback rating by Center/Employee/Service Category
Appointment rebooking percentage or count by Center/Employee/Service category.
Granularity of data
At the most granular level, we have a unique identifier ‘appointment pk’ for each service for which an appointment is created. To identify the group of appointments that are booked together, we have another unique identifier called ‘appointment group id’. To identify whether the appointment is for a service that has segments, we have a flag 'is segmented'. Below we have an example of a guest named 'Kelly' who booked appointments for three services. All these appointments will have the same 'appointment group id' but different 'appointment pk'. Among the services booked, there is one service called 'Brazilian Blow Dry' which has segments and this can be identified using the column 'is segmented'. To get the details of the segments, the 'Appointments' data source needs to be blended with the 'Appointment Segments' data source on 'appointment pk'.
![]() |
In case of a rebooking, the data is populated as shown here:

In case of a recurring appointment, the data is populated as shown here:

Note
Many fields in this data source are attributes of the center, service, etc. rather than attributes of the appointment. Examples are fields such as zone name, center city, is center franchise, operating center. These details are pulled from master tables and the value in the field always reflects its current status. If these fields are updated in core, all the past data in analytics also gets updated. We do not maintain versions or change tracking here. For example, if Center A was associated to Zone A and is changed such that it is now associated to Zone B. The zone name against Center A will get updated to Zone B even for past data and all the data in Analytics will show Center A's data against Zone B.
Group | Description | Field | Field Description | Example | Data Type |
---|---|---|---|---|---|
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | organization name | The formal name of the organization. | 'Massage Spa Express' is the formal name of an organization. | varchar(512) |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | organization account name | The domain name of the organization in Zenoti. | If you use this URL to log in to Zenoti 'https://massagespa.zenoti.com', then "massagespa" is your account name. The formal name and domain name may be different. | varchar(256) |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center name | The center where the appointment is scheduled to be serviced. | varchar(128) | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | zone name | The zone that the center belongs to. | varchar(800) | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center city | The city where the center is located. | varchar(128) | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center state name | The state where the center is located. | varchar(1024) | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | country name | The country where the center is located. | ||
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center zip | The zipcode of the center's location. | varchar(32) | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center company name | The name with which the center is registered. | Businesses, especially in a franchisee model, may register each center as a different company, such details are tracked in the Centers > General tab. | varchar(200) |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | operating center | A flag that indicates whether the center is operational. - True indicates operational - False indicates not operational | boolean | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | minutes to add | The number of minutes that need to be added to UTC time to get the current time at the center. Timestamps that are generated by Tableau [E.g. if you use filters such as Today, Tomorrow, etc.] are in UTC, hence this field is needed to arrive at the center time. This is not needed for timestamps that are in the data source directly- these are already in the center time zone. | int4 | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center wid | A unique identifier for the center. This is generated in Analytics, it does not exist in the core system. | bigint | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | is center franchise | A flag that indicates if the center is a franchisee. - True indicates a franchisee - False indicates not a franchisee | boolean | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center cst number | The Central Sales Tax (CST) number of the center. | varchar(80) | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center tin number | The Taxpayer’s Identification Number (TIN) number of the center. | ||
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center tot number | The Transient Occupancy Tax (TOT) number of the center. | ||
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center service tax number | The service tax number of the center. | ||
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center vat number | The value added tax identification number (VAT) of the center. | ||
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | center luxary tax number | The luxury tax number (VAT) of the center. | ||
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | etllastupdatedon | Latest timestamp at which the corresponding record was either inserted or updated in this data source. | timestamp without time zone | |
Center, Zone, Organization | An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center where the appointment is scheduled to be serviced. | etllastupdatedby | ETL system admin user who inserted or updated the corresponding record in this data source. | varchar(50) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest first name | First name of the guest. This is a mandatory value and cannot be blank. | varchar(160) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest middle name | Middle name of the guest. This is a non-mandatory value and it can be blank. | varchar(128) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest last name | Last name of the guest. | varchar(256) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | user wid | A unique identifier for the guest. This is generated in Analytics, it does not exist in the core system. | bigint | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | user id | A unique identifier for the guest. This is a non-blank value that is generated in the core system for every guest. | varchar(36) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest code | A unique identifier for the guest. This is a non-mandatory value and it can be blank. This maps to the guest code in a guest's profile in Zenoti. | varchar(128) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest city | The city to which the guest belongs. This is a non-mandatory value and it can be blank. | ||
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest state | The state to which the guest belongs. This is a non-mandatory value and it can be blank. | varchar(4000) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest country name | The country to which the guest belongs. This is a non-mandatory value and it can be blank. | ||
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest zipcode | The zipcode of the guest. This is a non-mandatory value and it can be blank. | varchar(32) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest email | Email ID of the guest. This is a mandatory value and it cannot be blank. | varchar(512) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest mobile phone | Mobile number of the guest. This is a mandatory value and it cannot be blank. | varchar(64) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest phone code | Phone country code of the guest. This is a mandatory value and it cannot be blank. | integer | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest gender | Gender of the guest. This is a non-mandatory value and it can be blank. | Possible values: - Male - Female - Not Applicable | varchar(14) |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest dob | Date of Birth of the guest. This is a non-mandatory value and it can be blank. | timestamp | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | referred by guestid | The user id of the person who referred the guest. | varchar(36) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest anniversary date | Marriage anniversary date of the guest. This is a non-mandatory value and it can be blank. | timestamp | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest type name | An indicator of whether the guest is indeed a guest or an employee. | Possible values: - Guest - Employee - Internal Guest/Virtual Guest: Guests who made their first purchase on Webstore. | varchar(128) |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest tags | The tags associated with the guest. | Tags can be setup for guests in their profile under the 'General' tab. These will be comma separated values if there are multiple tags. | varchar(65535) |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | is guest inactive | A flag indicating if the guest is inactive. A guest is considered inactive if his/her profile has been removed from the system. - True indicates that the guest is inactive. - False indicates that the guest is active. | boolean | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest referral source | The source from where the guest got to know about the organization. | Possible values: - Advertisement - Driving By - Friend - Guest - Instagram - Other - Walkin - Yelp - Youtube | varchar(3200) |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | check in date and time | The date and time when the appointment status was changed to 'Checkin' | This gives us the latest date and time when the appointment status was changed to checkin. | timestamp |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | user creation date | The date on which the profile of the guest was created. | ||
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest member status | DO NOT USE - THIS FIELD IS BEING DEPRECATED. | varchar(100) | |
Guest | These fields detail the attributes of the guest for whom the appointment is booked. | guest base center | Base center of the guest. This is where the guest's profile was created. | varchar(256) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment group id | A unique identifier for each appointment group. Appointment group refers to a set of appointments that are booked together for a guest. | If a guest books three appointments at once in the appointment book, all three will have the same 'appointment group id'. But each appointment will have a different 'appointment pk'. When group bookings are done, bookings made by each guest will have a different 'appointment group id'. If a guest rebooks an appointment, the resulting appointment will have a different 'appointment group id' than the source appointment. If a guest books a recurring appointment, all subsequent appointments will have different 'appointment group id'. | varchar(36) |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment pk | A unique identifier for each appointment. | integer | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment wid | Unique identifier for each appointment. This is generated in analytics, it does not exist in the core system. | bigint | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | factappointmentid | A system-generated unique identifier for each record in the appointment data source. This is generated within Analytics. | integer | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment source | The application from where the appointment was created. For example, through the Employee app, the mobile app, etc. | - MMS: Appointment created through the core system (i.e abc.zenoti.com) - PoS: Appointments created through PoS screen of the core system - Employee App: Appointments created through Employee App - Mobile: Appointments created through the CMA (Customer Mobile App) - Web: Appointments created through the Webstore - Imports: Appointments created through bulk data import - Offline: Appointments created through the offline app - Take5: Appointments created through the 'Take5 mobile app' - MobilePosAndroid: Appointments created through the Therapist Android App - Therapist Android App: Appointments created through the Therapist Android App (This source was renamed as 'MobilePosAndroid') - MobilePosiOS: Appointments created through the Therapist iOS App - Kiosk: Appointment created from the Guest-Kiosk: In-store - KioskCMA: Appointment created from the Guest-Kiosk : CMA - KioskWeb: Appointment created from Guest-Kiosk : Webstore | varchar(128) |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | is surprise | A flag to indicate whether the appointment was created for a walk-in guest. -1 indicates a walk-in guest. -0 indicates that it is not for a walk-in guest. | integer | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment created date | The date on which the appointment was created. | date | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment created date time | The date and time on which the appointment was created. | timestamp | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | actual appointment time | The scheduled start date and time of an appointment at the time of its creation. | If any changes are made to the appointment start date, this column will not change. | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment start date | The date on which the appointment is scheduled to start. | If any changes are made to the appointment start date, this column will have the latest start date of the appointment. | date |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment start date and time | The date and time on which the appointment is scheduled to start. | If any changes are made to the appointment start date and time , this column will have the latest start date and time of the appointment. | timestamp |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment end date | The date on which the appointment is scheduled to end. | If any changes are made to the appointment end date, this column will have the latest end date of the appointment. | date |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment end date and time | The date and time on which the appointment is scheduled to end. | If any changes are made to the appointment end date and time , this column will have the latest end date and time of the appointment. | timestamp |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment actual start date and time | The date and time on which the appointment status was changed to 'Checkin'. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | actual completed date and time | The date and time on which the appointment status was changed to 'Closed'. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment status | The current status of the appointment. Possible values: - Cancel - Checkin - Closed - Confirmed - Noshow - Open | varchar(100) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | is primary appointment | A flag indicating if within the group, the appointment will be the first one to be serviced. Note: The first appointment to be serviced is marked based on the 'appointment start date' and 'appointment group id'. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | service minutes | This is the duration of an appointment in minutes. This is the difference between 'appointment start date and time' and 'appointment end date and time'. Note: 'service minutes' does not include the recovery time. | integer | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | cancelled source | Source from where the appointment was cancelled. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment cancel or no show status | A flag indicating if the appointments with status as 'Cancel' or 'Noshow' have a cancellation or no-show fee associated with them. Below are the possible values: - Cancelled Appointment: Appointment has a cancellation fee. - No Show: Appointment has a no-show fee. - Fulfilled Appointment: Appointment does not have a cancellation fee. | varchar(21) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment category code | The unique code for the appointment category. | Appointment categories can be created when we navigate to Categories > Appointments. | varchar(1024) |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment category name | The name of the appointment category. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | is appointment category active | A flag indicating if the appointment category is active. | An appointment category is said to be inactive if the 'Active' checkbox is not selected when we navigate to Categories > Appointments. | boolean |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment cancel reason | The reason for appointment cancellation. This is a mandatory field that must be filled for every cancelled appointment. | The reasons for appointment cancellation can be configured when we navigate to Admin > Setup > Reasons. | varchar(65535) |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment cancel reason code | The unique code for each cancellation reason. This is a mandatory field that must be filled for every appointment that is cancelled. | varchar(1024) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | action performed date time in center | The latest date and time on which a change was made to the appointment status, the appointment start time, or the appointment end time. | timestamp | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | is rebook service | A flag indicating whether the appointment is the source for a rebooked appointment.Possible values: True - The appointment is the source for a rebooked appointment. False - The appointment is not the source for a rebooked appointment. | varchar(100) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | is rebook target | A flag indicating whether the appointment is a rebooked appointment.Possible values: True - The appointment is a rebooked appointment. False - The appointment is not a rebooked appointment. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | rebooked source group id | The 'appointment group id' of the source appointment which caused the rebooking. This is filled only if the entire appointment group is rebooked. | varchar(36) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | rebooked source appointment pk | The 'appointment pk' of the source appointment which caused the rebooking. This is filled only when few of the appointments within the appointment group are rebooked. | bigint | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | rebooked appointment count | The number of appointments or appointment groups that got rebooked from the source. This is populated only for source appointments. If the entire appointment group is rebooked, this field populates the number of times the appointment group is rebooked. If a few appointments within a group are rebooked, this field populates the number of times the appointment is rebooked. | integer | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | recurrence wid | The unique identifier for group of recurring appointments. This is generated in Analytics and is not available in core. | int8 | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment group | The unique identifier for each appointment. This is similar to 'Appointment pk'. | For all practical purposes- 'Appointment pk' is to be used as the unique identifier. | integer |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment group primarty key | The unique identifier for each appointment. This is similar to 'Appointment pk'. This is same as the 'appointment group'. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | recurrence appointment group primary key | The 'appointment group primary key' of the first appointment in the appointment group which was set to recur. This field can be used to identify the first appointment from where the recurring appointments started. | int4 | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | recurrence appointment pk | The 'appointment pk' of the first appointment in the appointment group which was set to recur. This field can be used to identify the first appointment from where the recurring appointments started. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment recurrence start date time | The start date and time of the first appointment in the appointment group which was set to recur. This field can be used to identify the first appointment from where the recurring appointments started. | timestamp | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment recurrence time period | The frequency of the recurring appointment. Possible values: - Daily - Weekly - Monthly - Yearly | varchar(100) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment recurrence interval | The interval between the recurring appointments. Note: This value should be used along with 'appointment recurrence time period'. If 'appointment recurrence time period' is 'Weekly', then the 'appointment recurrence interval' value is in weeks. If 'appointment recurrence time period' is 'Monthly', then the 'appointment recurrence interval' value is in months. If 'appointment recurrence time period' is 'Daily', then the 'appointment recurrence interval' value is in Days. If 'appointment recurrence time period' is 'Yearly', then the 'appointment recurrence interval' value is in years. | integer | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment recurrence occurences | The maximum number of times the appointment is set to recur. This is the value that was set when the recurring appointment was created and it is not updated if the future appointments are cancelled. Note: This number gets duplicated for all the appointments in a recurring group. | ||
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | invoice id | A unique identifier for the invoice. It is unique within the organization. | varchar(36) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | invoice no | A unique identifier for the invoice. It is unique within the center. | varchar(40) | |
Appointment | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | recurrence appointment invoice no | The 'invoice no' of the first appointment in the appointment group which was set to recur. This field can be used to identify the first appointment from where the recurring appointments started. | ||
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service name | The name of the service. | varchar(1024) | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service category | The category of the service. This is set up as Sub-category in core. | For a 'Brazilian Wax' service, the category could be 'Waxing', and parent category could be 'Hair removal'. | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service parent category | The parent category of the service. This is set up as Category in core. | For a 'Brazilian Wax' service, category could be 'Waxing', and parent category could be 'Hair removal'. | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service has variant | A flag indicating whether the service has a variant. - True indicates that the service has a variant. - False indicates that the service does not have a variant- Not Applicable. | A center has a service called 'Massage' which has two variants - '30 minute massage' and '60 minute massage'. This flag would be True for the service 'Massage; and it would be False for the services '30 minute massage' and '60 minute massage'. | varchar(14) |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service is variant | A flag indicating whether the service is a variant. - True indicates that the service is a variant - False indicates that the service is not a variant- Not Applicable | A center has a service called 'Massage' which has two variants - '30 minute massage' and '60 minute massage'. This flag would be False for the service 'Massage; and it would be True for the services '30 minute massage' and '60minute massage'. | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | is addon primary appointment pk | The 'appointment pk' of the appointment to which the add-on service belongs. | integer | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | is addon | A flag indicating whether the service is an add-on. - True indicates that the service is an add-on - False indicates that the service is not an add-on | boolean | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service businessunit | The business unit to which the service belongs. | varchar(800) | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | is service inactive | A flag indicating whether the service is inactive. A service is considered inactive if it has been removed from the system. - True indicates that the service is inactive - False indicates that the service is active | boolean | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service tags | The tags associated with the service. | Tags can be created for a service in the Organization view. These will be comma separated values if there are multiple tags. | varchar(65535) |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service length | The ideal time taken to complete a service (in minutes), as set up in Zenoti. | integer | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | recovery minutes | The ideal recovery time taken to complete a service (in minutes), as set up in Zenoti. | ||
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service internal cost | The internal cost that a center incurs for a service. | This is the value that is entered as 'Cost to Center' when a service is created in Zenoti. | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | service sold count | This field is filled with '1' in each row. Sum of this column would give us the number of rows in the data source. | ||
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | equipment name | The name of the equipment that is associated with a service. | Hot Stone Warmer, Tanning machine, Blow Dryer, etc | varchar(512) |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | equipment capacity | The capacity of the equipment that is associated with a service. | integer | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | is equipment active | A flag indicating whether the equipment is active. An equipment is considered inactive if it has been removed from the system. - True indicates that the equipment is active - False indicates that the equipment is inactive | boolean | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | resource name | Name of the resource associated with the service. | Therapy room, Chair, etc. | varchar(128) |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | resource code | Unique code of the resource associated with the service. | ||
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | resource type name | Type of the resource associated with the service. | ||
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | resource capacity | The capacity of the resource associated with the service. | integer | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | room category name | The category of room associated with the service. | varchar(800) | |
Service | These fields detail out the service performed in the appointment - such as the resources, equipment used for the service, etc. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted as categories in Analytics correspond to sub-categories in the core system; Parent categories in Analytics correspond to categories in the core system. | is segmented | A flag indicating whether the service has segments. | Possible values: - '1': Service has segments. - '0': Service does not have segments. | integer |
Package | If the appointment is booked for services which are a part of a day package or promo package, these fields that detail out the package get populated. | package name | The name of the package. | varchar(1024) | |
Package | If the appointment is booked for services which are a part of a day package or promo package, these fields that detail out the package get populated. | package type | The type of the package. | Possible values: - Day package: Combination of services that must be consumed in a single day. - Promo Package: Short-term promotional packages that need to be consumed on a single day. - Not Applicable: If the service is not booked as a part of a package. | varchar(14) |
Package | If the appointment is booked for services which are a part of a day package or promo package, these fields that detail out the package get populated. | package category | The category to which the package belongs. | varchar(800) | |
Package | If the appointment is booked for services which are a part of a day package or promo package, these fields that detail out the package get populated. | package businessunit | The business unit to which the package belongs. | ||
Package | If the appointment is booked for services which are a part of a day package or promo package, these fields that detail out the package get populated. | is package inactive | A flag indicating whether the package is inactive. A package is considered inactive if it has been removed from the system. - True indicates that the package is inactive - False indicates that the package is active | boolean | |
Package | If the appointment is booked for services which are a part of a day package or promo package, these fields that detail out the package get populated. | package tags | The tags associated with the package. | Tags can be created for a package in the Organization view. These will be comma separated values if there are multiple tags. | varchar(65535) |
Bundle | If the item sold is a bundle. | BundlePackageID | Helps you identify the bundle package (GUID). In case of multiple bundle packages, then ID remains same. | VARCHAR(36) | |
Bundle | If the item sold is a bundle. | BundlePackageNo | Helps you identify the number of bundle packages in a invoice. | INT | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee - code | Unique code of the employee who created the invoice. This is the code taken from the employee's profile in Zenoti. | varchar(128) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee code | Unique code of the employee who created the invoice. This is the code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'employee code' is usually the same as 'employee - code' unless someone manually changes it in the employee's guest profile. | ||
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee first name | First name of the employee who created the invoice. | varchar(160) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee middle name | Middle name of the employee who created the invoice. | varchar(256) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee last name | Last name of the employee who created the invoice. | ||
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee gender | Gender of the employee who created the invoice. | Possible values: - Male - Female - Not applicable | varchar(14) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee mobile phone | Mobile number of the employee who created the invoice. | varchar(64) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee job name | Job name associated with the employee who created the invoice. | varchar(255) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee job code | Unique code associated with the job of the employee who created the invoice. | varchar(2000) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee tags | Tags associated with the employee who created the invoice. | varchar(65535) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | is createdby employee inactive | A flag indicating whether the employee who created the invoice is inactive. An employee is considered inactive if they have been removed from the system. - True indicates that the employee is inactive False indicates that the employee is active | boolean | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee additional field 1 | The details in 'Additional Field1' for the employee who created the invoice. | Additional Field1' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti. | varchar(8000) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee additional field 2 | The details in 'Additional Field2' for the employee who created the invoice. | Additional Field2' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti. | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | createdby employee last date | The date on which the employee who created the invoice stopped working for the organization. | timestamp | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist first name | First name of the employee who is scheduled to service the guest. | varchar(160) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist middle name | Middle name of the employee who is scheduled to service the guest. | varchar(128) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist last name | Last name of the employee who is scheduled to service the guest. | varchar(256) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist employee - code | Unique code of the employee who is scheduled to service the guest. This is the code taken from the employee's profile in Zenoti. | varchar(128) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist code | Unique code of the employee who is scheduled to service the guest. This is the code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates his guest profile. Note: The 'employee code' is usually the same as 'employee - code' unless someone manually changes it in the employee's guest profile. | ||
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist wid | Unique identifier for each employee who is scheduled to service the guest. This is generated in analytics and it does not exist in core. | bigint | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist gender | Gender of the employee who is scheduled to service the guest. | Possible values: - Male - Female - Not applicable | varchar(14) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist last date | The date on which the employee who is scheduled to service the guest stopped working for the organization. | date | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist job name | Job name associated with the employee who is scheduled to service the guest. | varchar(255) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist request type | The request type made by a guest. | Possible values: - Any - Female - Male - Specific: This is populated when guest requests for a specific employee. | varchar(100) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist additional field 1 | The details in 'Additional Field1' for the employee who is scheduled to provide service for the appointment. | Additional Field1' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti. | varchar(8000) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | therapist additional field 2 | The details in 'Additional Field2' for the employee who is scheduled to provide service for the appointment. | Additional Field2' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti. | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | is therapist inactive | A flag indicating if the employee who is scheduled to provide service is inactive. An employee is considered inactive if they have been removed from the system. True indicates that the employee is inactive False indicates that the employee is active | date | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee - code | Unique code of the employee marked as primary 'Sold by'. This is the code taken from an employee's profile in Zenoti. | varchar(128) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee code | Unique code of the employee marked as primary 'Sold by'. This is the code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'employee code' is usually the same as 'employee - code' unless someone manually changes it in the employee's guest profile. | ||
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee first name | First name of the employee marked as primary 'Sold by' for the corresponding service. | varchar(160) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee middle name | Middle name of the employee marked as primary 'Sold by' for the corresponding service. | varchar(128) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee last name | Last name of the employee marked as primary 'Sold by' for the corresponding service. | varchar(256) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee mobile phone | Mobile number of the employee marked as primary 'Sold by'. | varchar(64) | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee last date | The date on which the employee who is marked as the primary 'Sold by' stopped working for the organization. | date | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee gender | The gender of the employee marked as primary 'Sold by'. | Possible values: Male Female Not applicable | varchar(14) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee job name | Job name associated with the employee marked as primary 'Sold by'. | Therapist, Manager, Aesthetician etc. | varchar(255) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | is employee inactive | A flag indicating if the primary 'Sold by' employee is inactive. An employee is considered inactive if they have been removed from the system. - True indicates that the employee is inactive - False indicates that the employee is active | boolean | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee additional field 1 | The details in 'Additional Field1' for the employee marked as primary 'Sold by'. | Additional Field1' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti. | varchar(8000) |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | employee additional field 2 | The details in 'Additional Field2' for the employee marked as primary 'Sold by'. | Additional Field2' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti. | |
Employee | This group of fields describes the attributes of three types of employees:1. 'Created by' employee: The employee who created the invoice. 2. 'Therapist': The employee who is scheduled to provide the service.3. 'Sold by' employee: The employee who primarily 'sold' the service. | feedback by employee - code | The employee code of the employee who provided the employee's guest profile. | varchar(128) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback by user id | The user id of the person who provided the feedback. This has the user id of the guest if the guest has provided the feedback or the user id of the employee who entered the feedback on behalf of the guest. | user id' is a unique identifier for all the guests. | varchar(36) |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback by user code | The user code of the person who provided the feedback. This has the 'Guest code' of the guest if the guest has provided the feedback or the employee code of the employee who entered the feedback on behalf of the guest. | varchar(128) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback by first name | The first name of the person who provided the feedback. This has the first name of the guest if the guest has provided the feedback or the first name of the employee who entered the feedback on behalf of the guest. | varchar(160) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback by middle name | The middle name of the person who provided the feedback. This has the middle name of the guest if the guest has provided the feedback or the middle name of the employee who entered the feedback on behalf of the guest. | varchar(128) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback by last name | The last name of the person who provided the feedback. This has the last name of the guest if the guest has provided the feedback or the last name of the employee who entered the feedback on behalf of the guest. | varchar(256) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback source | Source from where the feedback was taken. | Possible values: MMS: feedback obtained through the core system (i.e abc.zenoti.com) PoS: feedback obtained through PoS screen of the core system Employee App: feedback obtained through Employee App Mobile: feedback obtained through the CMA (Customer Mobile App) Web: feedback obtained through the Webstore Imports: feedback obtained through bulk data import MobilePosAndroid: feedback obtained through the Therapist Android App MobilePosiOS: feedback obtained through the Therapist iOS App Manager App: feedback obtained through the Manager Mobile App | varchar(125) |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback updated date time | The date and time on which the feedback was provided by the guest. | timestamp | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback version | The version of feedback form used. Possible values: - 1 indicates Guest Feedback V1 - 2 indicates Guest Feedback V2 | int4 | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | is feedback given | A flag indicating whether the feedback was provided. | boolean | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback ambience | The first feedback question configured in the 'V1' feedback form. The answer format for this question is a rating from 1 to 5. | varchar(4096) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback cleanliness | The second feedback question configured in the 'V1' feedback form. The answer format for this question is a rating from 1 to 5. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback service | The third feedback question configured in the 'V1' feedback form. The answer format for this question is a rating from 1 to 5. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback therapist | The fourth feedback question configured in the 'V1' feedback form. The answer format for this question is a rating from 1 to 5. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback question 1 | The first question for which the answer format is 'Yes/ No' in the 'V1' feedback form. | This is usually a question asking guest whether he would recommend the service to someone else. | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback question 2 | The second question for which the answer format is 'Yes/ No' in the 'V1' feedback form. | This is usually a question asking guest whether the organization can share the feedback provided by him. | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | guest feedback question 3 | The question configured for the feedback comment in the 'V1' feedback form. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | ambience feedback | Feedback rating given by guest for question 'guest feedback ambience' in the 'V1' feedback form. | integer | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | cleanliness feedback | Feedback rating given by guest for question 'guest feedback cleanliness' in the 'V1' feedback form. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | service feedback | Feedback rating given by guest for question 'guest feedback service' in the 'V1' feedback form. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | therapist feedback | Feedback rating given by guest for question 'guest feedback therapist' in the 'V1' feedback form. | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | avg feedback | For 'Guest Feedback v1' - This field contains the average of the feedback ratings provided in the fields 'ambience feedback', 'cleanliness feedback', 'service feedback', 'therapist feedback'. For 'Guest Feedback v2' - This field contains the overall feedback rating provided by the guest. | float8 | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | recommended | This indicates whether the guest has selected 'Yes'/'No' for the 'guest feedback question 1' in the 'V1' feedback form. | Possible values: True, False | boolean |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | share feedback | This indicates whether the guest has selected 'Yes'/'No' for the 'guest feedback question 2' in the 'V1' feedback form. | These values are populated for organizations which use 'Guest Feedback v1'. Possible values: 1,0 | integer |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag1 | This field is filled with one of the feedback tags that a guest selects in V2 feedback form. | Note: This field is populated for organizations who use 'Guest Feedback v2' feedback form. For example, If a guest has selected only three tags, all three tags would be populated in the first three feedback tag columns. | varchar(176) |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag2 | Note: This field is populated for organizations who use 'Guest Feedback v2' feedback form. For example, If a guest has selected only 3 tags, all three tags would be populated in the first three feedback tag columns. | varchar(177) | |
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag3 | varchar(178) | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag4 | varchar(179) | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag5 | varchar(180) | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag6 | varchar(181) | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag7 | varchar(182) | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback tag8 | varchar(183) | ||
Feedback | These fields detail out the feedback provided by the guest. Zenoti offers two different versions of feedback forms, Guest Feedback v1 - Guests read questions on different aspects of the service and rate each question separately.Guest Feedback v2 - Guests provide overall rating and indicate aspects of the business that they liked or did not like. Note: Feedback is populated at an 'appointment group id' level and is replicated for all the appointments that belong to the group. | feedback comments | The feedback comments for the appointment. | varchar(32000 | |
appointments | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | appointment id | Unique identifier for an appointment | VARCHAR(36) | |
appointments | These fields detail the attributes of the appointment. Here we refer to three types of appointments:1) Appointment: This is a normal standalone appointment which is neither rebooked nor set to recur. 2) Rebooked appointment: When an appointment or group of appointments are booked again by a guest, the resulting appointment is referred to as the 'rebooked' appointment and the appointment from which the rebooking was done is referred to as the 'source' appointment.3) Recurring appointment: When an appointment is set to repeat a certain number of times, it is called as a recurring appointment | Initial Suggested StartTimeInCenter | Indicates initial suggest time for a service for Queue based business | TIMESTAMP |