Reports Offered by Rentlz

Created by Moveinsync Help, Modified on Thu, 13 Aug at 1:51 AM by Moveinsync Help

Overview

This document gives a simple overview of the reports available in the Rentlz module of MoveInSync. It helps users understand what reports are available and what kind of information each report provides.

Reports Available

The following reports are offered by Rentlz.

Report Name	Description	Key Details Included
Rentlz Booking Report	Provides a comprehensive overview of all bookings within the system.	Rider info, trip details, and current booking status.
Rentlz Billing Report	Focuses on financial data for completed trips.	Billing details, fare breakdown, and reconciliation data.
Vendor Acceptance / Rejection Report	Monitors vendor interactions with assigned bookings.	Acceptance/rejection status and precise timestamps.
Rentlz Employee Communication Report	Tracks outgoing communications sent to staff members.	SMS body, delivery status, and relevant transmission metadata.

Inorder to Enable any Report mentioned above into any new server Please create an SE Ticket.

Refer - ( https://moveinsync.atlassian.net/browse/SE-56213 )

Rentlz Booking Report

The Rentlz Booking Report provides complete details of all bookings created in the system. It captures information related to the booking creation, rider details, trip planning, vendor assignment, and current booking status.

This report is mainly used to:

Track booking details
Identify rider and trip details
Monitor vendor and cab allocation
Analyze booking status and issues

Columns Available in the Booking Report along with its description.

Column Name	Description
TRIP_DATE	Date on which the trip is planned be performed / The date which was requested by the rider for the trip .
TRIP_TIME	The time which was requested by the rider for the trip as the pickup time.
BOOKING_ID	Unique identifier for the booking which was created by an rider for an trip. Booking id is always unique.
TRIP_ID	Unique identifier for the trip - For every booking id when an vendor accepts and assigns an vehicle an unique trip id will get generated. the same can be used to track the status of the booking, vehicle tracking etc.
MASTER_BOOKING_ID	Whenever grouped / multi bookings were created for an rider at a time those all bookings will be comes under one parent booking id which is also called as Master booking id. By which we can track all the subsidiary booking id-s.
BOOKER_ID	EmployeeID / User Id of the person who has created the booking
BOOKER_NAME	Name of the person who created that particular booking
BOOKER_PHONE_NUMBER	Contact number of the person who created that particular booking
REQUESTER_ID	EmployeeID / User Id of the person who has requested the booking.
REQUESTER_NAME	Name of the person who requested that particular booking
REQUESTER_PHONE_NUMBER	Contact number of the person who requested that particular booking
BOOKING_CREATION_DATE	Date on which the booking has been created
BOOKING_CREATION_TIME	Time on which the booking has been created
CUTOFF_PASSED	Indicates if cab allocation cutoff has been passed or not. Basically it shows yes/ no.
RIDER_ID	Employee ID/ User id of the rider who’s involved in that trip , if the rider is guest this will be empty.
RIDER_NAME	Name of the rider who’s travelling in that particular trip.
RIDER_EMAIL	Email ID of the rider who’s travelling in that particular trip.
RIDER_GENDER	Gender of the rider who’s travelling in that particular trip.
COUNTRY_CODE	Country code of rider’s mobile number
RIDER_MOBILE_NUMBER	Contact number of rider who’s travelling in that particular trip.
RIDER_JOB_TITLE	Designation of the rider who’s travelling in that particular trip.
RIDER_OFFICE	Office location of rider who’s travelling in that particular trip.
GUEST_SIGN_IN_TIME	Time when actually guest signed into the trip. This will be captured by the otp entered time by driver in the driver device.
RIDER_COST_CENTER	Cost center mapped/ selected to the rider in the booking.
BILLING_TYPE	Billing type should be selected in the booking creation itself whether the trip is being paid by Bill to user / Billing to company. Bill to user means here the rider will pay. If company means organization of rider will be paying. Hence whatever selected in the booking creation will come here.
APPROVAL_REQUESTED_TO	The reporting manager of the rider will be coming here. Whenever an booking is created the reporting manager should approve the booking . He’s considered as the L1 manager and the same name of him will be coming here.
APPROVAL_REQUESTED_TO_L2	When an rider has selected an different cost centre/ entity code while booking creation that booking will go for two level manager approval for both reporting manager and the cost centre selected manager. Hence this 2nd manager is considered as the L2 manager . And L2 manager name will be coming over here.
ACTION_BY	Reporting manager of the rider name will come here.
ACTION_BY_L2	L2 Manager name will be coming here. / The person name for whom the booking has went for 2nd level approval will come here.
APPROVAL_STATUS	Manager approval Status of the booking created will be visible over here whether the booking has been Approved/Rejected/Pending by the manager.
BOOKING_TYPE	The type of booking which has been selected in the booking creation will be visible here. Booking types for eg - 4hr 40 booking , outstation , Airport pickup , Cab on standby etc
CITY	City which was selected by user for the pickup in that particular trip.
DESTINATION_CITY	Destination city is something which will be coming for mostly outstation trips. For eg - if you want to go from Bengaluru to chennai you need to create an outstation booking type where your pickup city will be Bengaluru and destination city will be chennai. And whatever destination city is selected will come here.
REASON_FOR_CAB_CHANGE	Whenever an cab change occurred for any booking an mandatory comment is required by the person who’s changing the same. The same comment will be visible over here.
FLIGHT_DETAILS	Whenever an airport drop / airport pickup is selected as the booking type an field will popup called as fligh details the flight number in which the rider is travelling should be filled over here. This details will be shared to the driver and this wil be helpful driver inorder to reach the airport based on the flight arrival/ departure time exactly. And whatever details was filled in the booking creation will be visible over here.
GUARD_REQUIRED	Indicates if marshal is required or not for that particular trip. And based on the selection if yes/no the same will be visible in this particular field.
CAB_TYPE	Cab type should be selected in the process of booking creation itself. Whatever selected will be visible over here. For eg - SUV/ SEDAN etc.
PURPOSE_FOR_TRAVEL	This will be filled in the booking creation itself. Its generally for what reason the rider is actually travelling in this trip. For eg- Persponal/ Official / Business meeting etc.
ACTUAL_VEHICLE_TYPE	Actual vehicle type which has been deployed in that particular trip. For eg- Suv was requested but due to unavailability Sedan has been sent for that trip. Here sedan will be considered as the Actual vehicle type.
VENDOR	Name of vendor who has been assigned for that particular booking. ( For eg- Orix , Eco )
CAB_REGISTRATION_NUMBER	The vehicle registration number of the vehicle which has been assigned for that particular trip. ( for eg- KA45TH786)
DRIVER_NAME	Name of driver who has been assigned to perform thatparticular trip.
DRIVER_MOBILE_NUMBER	Driver contact number who has been assigned to perform that particular trip
DRIVER_REPORTING_TIME	Time in which when the driver has actually reached the pickup location of the rider.For eg- if the pickup time is at 6:00 am and the driver has reached the location at 6:10 am then the driver reporting time is 6:10 am.
PLANNED_START_TRIP	Planned trip start is actually the pickup time which was selected in the booking creation. If an booking is with 7:00 am pickup time then the planned start trip is 7:00 am.
PLANNED_START_ADDRESS	Pickup location which has been selected in that particular booking/ The location where rider wanted to be picked for that particular trip.
PLANNED_END_ADDRESS	Drop location which has been selected in that particular booking/ The location where rider wanted to be dropped for that particular trip.
CAB_MODIFIED_BY	If anyone who has changed / removed/ added the cab for that particular trip. That person’s name will be visible over here.
VENDOR_MODIFIED_BY	If anyone who has changed / removed/ added the vendor for that particular trip. That person’s name will be visible over here.
BOOKING_CANCEL_DATE	Date where the booking has been cancelled. If an booking has cancelled on 7th april then 7th april is the booking cancellation date.
BOOKING_CANCEL_TIME	Time where the booking has been cancelled. If an booking has cancelled on 7th april 7:30 am then 7:30 am is the booking cancellation time.
BOOKING_CANCEL_USER_EMAIL	User who has actually cancelled that particular booking. That user’s email will be captured and visible over here.
CANCELLATION_REASON	Whenever an booking is being cancelled an mandatory reason should be filled then only system allows for cancellation. Whatever reason has been provided will be captured over here.
CUSTOMER	Company name of the booker will be present over here . For eg - Amazon
OFFICE	Office of the booker will be present over here.
NUMBER_OF_RIDERS	Total number of riders who are actually involved in that particular booking / trip.
BOOKING_STATUS	Current booking status of that particular booking. For eg- if the trip is completed it will show as Trip completed. If the booking has been cancelled it will show as Trip cancelled. If the booking has been accepted by an vendor but not allocated any vehicle then it will show as Cab allocation pending etc.
DURATION_OF_TRIP_BY_USER	Total time taken for the entire trip. Starting from the pickup location and ending in the drop location.
TRIP_STATUS	Status of that particular trip. For eg- Trip ongoing, Trip completed, Trip cancelled etc.
LOCATION_TO_BE_BILLED	Pickup location city of the trip.
PAYER_RIDER_NAME	If it is bill to user whoever the payer is his/her name will be present over here.
PAYER_RIDER_EMAIL	If it is bill to user whoever the payer is his/her email will be present over here.
START_LANDMARK	Landmark details whichever are provided for the pickup location by the booker. For eg- if the booking pickup location is moveinsync office but landmark mentioned is oben electric showroom then the start landmark will be oben electric showroom.
END_LANDMARK	Landmark details whichever are provided for the drop location by the booker. For eg- if the booking drop location is moveinsync office but landmark mentioned is oben electric showroom then the End landmark will be oben electric showroom.
MERGE_REFERENCE	When two bookings were merged an comment is mandatory inorder to merge the same. Whatever comment provided while merging will be present over here.
BOOKING_NUMBER	Unique identifier for the booking which was created by an rider for an trip. Booking id is always unique.

Rentlz Billing Report

The Rentlz Billing Report provides complete financial and operational details of trips. It includes fare related, taxes, vendor details, trip execution data, and invoice/payment status.

This report is mainly used to:

Track trip-wise billing
Verify fare calculations
Monitor vendor invoices
Handle approvals and payments
Perform reconciliation

Columns Available in the Billing Report along with its Description

Column Name	Description
BOOKING_ID	Unique identifier for the booking which was created by an rider for an trip. Booking id is always unique.
BOOKING_TYPE	The type of booking which has been selected in the booking creation will be visible here. Booking types for eg - 4hr 40 booking , outstation , Airport pickup , Cab on standby etc
TRIP_ID	Unique identifier for the trip - For every booking id when an vendor accepts and assigns an vehicle an unique trip id will get generated for the same booking id which can be used to track the status of the booking, vehicle tracking etc.
MASTER_BOOKING_ID	Whenever grouped / multi bookings were created for an rider at a time those all bookings will be comes under one parent booking id which is also called as Master booking id. By which we can track all the subsidiary booking id-s.
CHARGE_CODE	Cost center used for the billing purposes on that particular booking.
CITY	City which was selected by user for the pickup in that particular trip.
OFFICE_NAME	Office which was associated to the rider who’s involved in that particular trip.
INVOICE_NO	Invoice number which was generated for that particular trip while billing. This will be always unique for every trip.
REFERENCE_KM	Estimated distance ( km ) for the trip between both pickup and drop locations.
BOOKING_STATUS	Current booking status of that particular booking. For eg- if the trip is completed it should show as Trip completed. If the booking has been cancelled it should show as Trip cancelled. If the booking has been accepted by an vendor but not allocated any vehicle then it should show as Cab allocation pending etc.
CONSIDER_FOR_BILLING	Indicates if that particular trip is considered for billing or not.
AUDIT_DONE_BY	The source where the audit for that particular booking has been done. It usually shows system/ client name etc.
P2P_KM	The actual distance between the start location and end location of the trip.
PLANNED_START_LOCATION	Pickup location which has been selected in that particular booking/ The location where rider wanted to be picked for that particular trip.
PLANNED_END_DESTINATION	Drop location which has been selected in that particular booking/ The location where rider wanted to be dropped for that particular trip.
START_GARAGE_KM	Distance from the vendor garage location to the pickup location of that particular trip.
GARAGE_TOTAL_KM	Total garage distance which means it includes both from start garage location to the pickup location of that particular trip and from end location of that trip to the garage location .
ACTUAL_START_PLACE	Actual pickup location where the rider has actually picked up in that particular trip. For eg For an rider pickup location is Hsr bus stop but he has been picked up 200m before the pickup location given. Then the location where he has been picked up will be the Actual start place.
ACTUAL_END_PLACE	Actual drop location where the rider where the rider has actually dropped in that particular trip. For eg For an rider drop location is Hsr bus stop but he has been dropped 200m before the drop location given. Then the location where he has been dropped will be the Actual end place.
PLANNED_START_TIME	The time which was requested by the rider for the trip as the pickup time.
PLANNED_END_TIME	The time which was requested by the rider for the trip as the drop time.
REQUESTED_END_TIME	If any drop time has been selected in the booking for the drop location that is considered as the requested end time.
DRIVER_REPORT_TIME	Time in which when the driver has actually reached the pickup location of the rider.For eg- if the pickup time is at 6:00 am and the driver has reached the location at 6:10 am then the driver reporting time is 6:10 am.
TRIP_START_TIME	The time in which the trip has actually started. For eg if an driver reached the rider’s pickup location at 9:30 am and rider has given signin otp at 9:32 am then the actual trip start time will be 9:32 am.
TRIP_END_TIME	The time in which the trip has actually ended. For eg if an driver reached the rider’s drop location at 9:30 am then the actual trip end time will be 9:30 am.
DELAYED	Indicates if that particular trip was delayed or not.
DELAY_CAUSED_BY	This field will show the reason behind the delay of that particular trip. For eg- Delayed by driver / delayed by rider etc.
P2P_HOURS	The actual time ( in hrs ) between the start location and end location of the trip.
TRIP_WAITING_TIME	The time between the driver reporting and the start of the trip
START_GARAGE_TIME	Time on which the vehicle has actually left from the garage to the pickup location of the rider
END_GARAGE_TIME	Time on which the vehicle has actually reached to the garage from the end location of the rider.
TOTAL_GARAGE_TIME	This includes the total travel time taken for the vehicle including both start garage to pickup location of the rider and from drop location of the rider to the end garage location.
VENDOR	Name of the vendor who has been assigned to that particular booking.
CAB_REGISTRATION_NO	The vehicle registration number of the vehicle which has been assigned for that particular trip. ( for eg- KA45TH786)
PLANNED_VEHICLE_TYPE	The vehicle type in which actually selected in the booking creation itself. For eg- if an suv selected as an cab type in the booking. Suv will become the Planned vehicle type.
ACTUAL_VEHICLE_TYPE	The actual vehicle type which has been assigned in that particular trip. For eg- An booking was created by an employee and the requested vehicle/cab type is Suv. But due to unavailability vendor has sent an Sedan. Hence sedan will be the Actual Vehicle type assigned over here.
BILLING_CONTRACT_NAME	Contract applied in that particular trip
TRIP_COST	The total cost incurred in that trip excluding the Parking and toll charges along with Gst
EXTRA_KM	Extra distance travelled excluding the package km. So for eg 8hr/80km is the package but distance travelled is 100km. Then extra km will be 20 which are excluding the package.
EXTRA_KM_COST	Cost for extra km whichever travellled excluding the package. So if package is 8hr/80 km and travelled is 100km for extra 20km whatever the cost applicable will be shown here.
EXTRA_HOURS	Extra time beyond the package in which the trip has covered. In an 8hr/80 booking if total trip time is 9 hrs extra is 1hr which is excluding the package selected.
EXTRA_HOUR_COST	Extra time beyond the package in which the trip has covered. In an 8hr/80 booking if total trip time is 9 hrs extra is 1hr which is excluding the package selected. For the extra 1 hr whatever cost applicable will be visible over here.
DAY_BATA	Driver allowance for the trip if the trip is performed in the day time.
NIGHT_BATA	Driver allowance for the trip which is performed on the night
OUTSTATION_NIGHT_BATA	Allowance for outstation trips for the driver.
PARKING	Parking charges whichever has been paid by the driver in that particular trip.
TOLL	Toll charges whichever has been paid by that driver for that trip .
TOTAL	Total cost for the trip including all expenses like parking and toll before tax
CGST_PERCENT	CGST percentage applicable in that particular booking.
CGST_AMOUNT	CGST amount which was incurred in that particular trip.
SGST_PERCENT	SGST percentage applicable in that particular booking.
SGST_AMOUNT	SGST amount which was incurred in that particular trip.
IGST_PERCENT	IGST percentage applicable in that particular booking.
IGST_AMOUNT	IGST amount which was incurred in that particular trip.
TOTAL_AMOUNT_WITH_GST	Final billed amount including all the expenses and gsts included.
REMARKS	Whatever remarks added in the booking creation time will be present over here.
RIDER_NAME	Name of the rider who has been involved in that particular trip.
RIDER_GENDER	Gender of rider who has been involved in that particular trip.
DRIVER_NAME	Name of driver who has been involved in that particular trip.
LOCATION_TO_BE_BILLED	Pickup location city of the trip.
GST_NUMBER	GST number which was incurred in billing that particular trip.
LAST_ACTION_TAKEN_BY	Last user who has taken any action for the booking . Name of that particular action taker will be coming over here. ( Action like - booking update / booking cancel etc )
LAST_ACTION_TIME	Time of last action whenever the last action has been taken on that particular booking. ( Action like - booking update / booking cancel etc )
VENDOR_BOOKING_ID	This comes for external vendors. Where the unique id in their system will be different. For eg - the booking id in moveinsync is B245-TY-4567 and in the external vendor system it is D2ER678YUI9 then this D2ER678YUI9 will visible in this particular column.
DUTY_DATE	Date on which the trip should be started.
GUEST_NAME	Name of guest who’s actually travelling in that particular trip.
USER_EMAIL_ID	Email of the rider in that particular trip.
COST_CENTER	Cost center which was selected in that particular booking while booking creation.
ENTITY	Entity name which has been selected in that particular booking.
USAGE_LOCATION	Pickup location city of the trip.
DUTY_TYPE	Booking type of that particular trip For eg- Outstation/ Airport pickup etc.
NO_OF_DAYS	Number of days the trip has been taken inorder to complete from the start date.
PACKAGE_HOURS	Hours whichever are included in that particular booking. For eg - in 8hr/80 booking type package hours is 8 hours.
PACKAGE_KMS	Km’s whichever are included in that particular booking. For eg - in 8hr/80km booking type package km’s is 80 kms.
PACKAGE_NET_AMOUNT	Base package cost which will be coming based on the contract mapped for that booking combination in the system.
EXTRA_KM_RATE	Rate included for the extra KM travelled in that trip excluding the package km rate.
EXTRA_HRS_RATE	Rate included per extra hour travelled in that trip. Excluding the package hrs.
TOTAL_HOURS	Total hours taken inorder to complete that particular trip. Hours between both start trip and the end trip.
TOTAL_KMS	Total km’s travelled in the entire trip.
DRIVER_ALLOWANCE	Total driver allowance which has been incurred in that particular trip.
GRAND_TOTAL	Final total amount incurred for the trip. Which includes all the base cost , expenses like parking and toll along with the GST amount.
APPROVAL_STATUS	This column shows whether that particular invoice has been approved or rejected.
AUDIT_COMMENTS	Reason added for the change of status of invoice.
BOOKING_CREATION_DATETIME	Date and time on which the booking has been created for an trip.
CAB_ASSIGNMENT_TIME	Time on which the booking has been assigned with an vehicle.
CAB_CHANGE_REASON	Reason for cab change in that particular trip if changed. For eg- Changing the existing cab to new because the cab is went for service etc.
FLIGHT_DETAILS	Flight number / Flight details especially for Airport transfer booking types. These will be useful for the driver inorder to reach the airport based on the flight arrival/departure time.
PURPOSE_OF_TRAVEL	This also should be filled in the booking creation itself. Its generally for what reason the rider is actually travelling in this trip. For eg- Persponal/ Official / Business meeting etc.
BILLING_NAME	Name added while creating the booking if it is an bill to user. Booking.
BILLING_ADDRESS	Rider’s pickup location on that parfticular trip.
PAYER_RIDER_NAME	If it is bill to user whoever the payer is his/her name will be present over here.
PAYER_RIDER_EMAIL	If it is bill to user whoever the payer is his/her email will be present over here.
START_LOCATION	Pickup location which has been selected in that particular booking/ The location where rider wanted to be picked for that particular trip.
END_LOCATION	Drop location which has been selected in that particular booking/ The location where rider wanted to be dropped for that particular trip.
START_LANDMARK	Landmark details whichever are provided for the pickup location by the booker. For eg- if the booking pickup location is moveinsync office but landmark mentioned is oben electric showroom then the start landmark will be oben electric showroom.
END_LANDMARK	Landmark details whichever are provided for the drop location by the booker. For eg- if the booking drop location is moveinsync office but landmark mentioned is oben electric showroom then the End landmark will be oben electric showroom.
TRIP_KMS	Total km’s travelled in the entire trip.
TRIP_HOURS	Total hours taken inorder to complete that particular trip. Hours between both start trip and the end trip.
MISC_EXPENSE	Additional expenses which are incurred in that particularv trip excluding the parking and toll charges.
INVOICE_DATE	The Date on which invoice was generated.
MERGE_REFERENCE	When two bookings were merged an comment is mandatory inorder to merge the same. Whatever comment provided while merging will be present over here.
DRIVER_MOBILE_NUMBER	Driver contact number who has been assigned to perform that particular trip
BOOKING_NUMBER	Unique identifier for the booking which was created by an rider for an trip. Booking id is always unique.

Vendor Acceptance / Rejection Report

The Vendor Acceptance / Rejection Report provides details on how vendors respond to booking requests. It captures whether a vendor has accepted or rejected a trip, along with the response time and reasons (if rejected).

This report is mainly used to:

Track vendor responsiveness
Identify rejected bookings
Analyze vendor performance
Take action on delayed or failed allocations

Columns Available in the Vendor Acceptance / Rejection Report along with its Description

Column Name	Description
TRIP_DATE	Date on which the trip should be performed / The date which was requested by the rider for the trip .
TRIP_TIME	The time which was requested by the rider for the trip as the pickup time.
BOOKING_ID	Unique identifier for the booking which was created by an rider for an trip. Booking id is always unique.
TRIP_ID	Unique identifier for the trip - For every booking id when an vendor accepts and assigns an vehicle an unique trip id will get generated for the same booking id which can be used to track the status of the booking, vehicle tracking etc.
BOOKER_ID	EmployeeID / User Id of the person who has created the booking
BOOKER_NAME	Name of the person who created that particular booking
REQUESTER_ID	EmployeeID / User Id of the person who has requested the booking.
REQUESTER_NAME	Name of the person who requested that particular booking
RIDER_NAME	Name of the rider who’s travelling in that particular trip.
RIDER_EMAIL	Email ID of the rider who’s travelling in that particular trip.
BOOKING_TYPE	The type of booking which has been selected in the booking creation will be visible here. Booking types for eg - 4hr 40 booking , outstation , Airport pickup , Cab on standby etc
BOOKING_CITY	City which was selected by user for the pickup in that particular trip.
VENDOR_NAME	Name of vendor who has been assigned for that particular booking. ( For eg- Orix , Eco )
VENDOR_STATUS	Status of vendor response in that particular booking whether the booking has been Accepted/Rejected/Pending.
VENDOR_ACTION	Action taken by vendor for eg- Accepted that booking / Assigned an vehicle etc.
ASSIGNED_BY	User/system who has assigned the vendor in that particular booking.
ASSIGNED_TIME	Time when the vendor was assigned in that particular booking.
ACCEPTED_BY	User/vendor who accepted the booking. The name of person who has taken this action will be present over here.
ACCEPTED_TIME	Time when the booking was accepted by the vendor.
REJECTED_BY	User/vendor who has rejected the booking. The name of person who has taken this action will be present over here.
REJECTED_DATE	Date of rejection when that booking has been denied.
REJECTED_TIME	Time of rejection / denial of that particular booking by the vendor.
REJECTED_REASON	Reason provided for rejection/ denial of the booking when it was assigned to that particular vendor.
LAST_UPDATED_DATE	Last update date of vendor action in that particular booking.

Rentlz Employee Communication Report

The Rentlz Employee Communication Report provides details of all communications sent to employees related to their trips. This includes notifications such as booking confirmations, driver details, trip updates, and alerts.

This report is mainly used by operations and support teams to:

Track communication sent to employees
Verify if sms’s were triggered correctly
Troubleshoot communication-related issues
Ensure employees receive timely trip updates

Columns Available in the Employee communication report along with its Description

Column Name	Description
REQUEST_TIME	Time when the sms communication was triggered
EMPLOYEE_ID	Unique ID of the employee who’s involved in that trip.
EMPLOYEE_NAME	Name of the employee/ rider who’s involved in that trip.
PHONE_NUMBER	Contact number of the employee/ rider who’s actually involved in that trip.
COMMUNICATION_TYPE	Type of communication which is triggered. For eg- Creation sms/ Cab updated sms/ Cancellation sms etc.
COMMUNICATION_CHANNEL	SMS
STATUS	Status of communication whether it is Sent/Failed/Pending
STATUS_UPDATE_TIME	The time when communication status changes from pending to sms successful .
TRIP_ID	Unique identifier for the trip - For every booking id when an vendor accepts and assigns an vehicle an unique trip id will get generated for the same booking id which can be used to track the status of the booking, vehicle tracking etc.
BOOKING_ID	Unique identifier for the booking which was created by an rider for an trip. Booking id is always unique.
SHIFT	Type of the shift during which trip happened. ( For eg- Day shift / Night shift )
OFFICE	Office location of employee/ rider whichever is configured in that particular employee’s profile section.
ORGANIZATION	Organization or company name of the rider involved in that particular booking.
MESSAGE_TEXT	Content of the message sent ( varies for every event. Events like Booking creation event, Cab updation event etc )
MESSAGE_LENGTH	Length of the message sent ( varies for every event. Events like Booking creation event, Cab updation event etc )
MESSAGE_UNITS	Length of the total message. It will be present in numbers.