I want my clients to book sessions that can be delivered either online or in-person. Reading the other public posts it seems that I can set Zoom as a "Location". While I "could" do this, Amelia seems to lack the logic to interpret that "Location" selection as a cue to create a Zoom meeting.
If I enable Zoom for the service, Amelia creates a Zoom meeting regardless of the Location setting; if Location is a physical address instead, Amelia still creates a Zoom meeting.
This same problem shows up in notifications too. There seems to be no logic that allows the address to be added to the notification, and OMIT the Zoom-join-url. The opposite should be true too, but isn't (If they choose Zoom as the location, they should get the Zoom-join-url and NOT the physical address in the notification.
Practically now, I am having to manually cancel the Zoom appointments of my in-person clients (Zoom then notifies them of the cancellation), So I have to then manually email them to confirm the meeting is still going ahead, only the Zoom element has been cancelled. They get confused as they didn't ask for Zoom anyway, and we start our relationship on the wrong foot. This plugin has, so far, tripled my workload and ruined user XP.
This was sold as the most powerful booking plugin on WP with great support. Come on team...
Thank you for reaching out and sharing the details of the issue you're facing.
The workaround for this scenario would be to create separate services for Zoom and in-person sessions. By setting up distinct services for each type, you can ensure that the location and notification logic behaves as expected. Zoom sessions will generate the Zoom meeting link, while in-person sessions will provide the physical address. This should help to prevent the confusion and reduce the need for manual cancellations or follow-up emails.
I hope this helps! Let me know if you need any further assistance.
I want my clients to book sessions that can be delivered either online or in-person. Reading the other public posts it seems that I can set Zoom as a "Location". While I "could" do this, Amelia seems to lack the logic to interpret that "Location" selection as a cue to create a Zoom meeting.
If I enable Zoom for the service, Amelia creates a Zoom meeting regardless of the Location setting; if Location is a physical address instead, Amelia still creates a Zoom meeting.
This same problem shows up in notifications too. There seems to be no logic that allows the address to be added to the notification, and OMIT the Zoom-join-url. The opposite should be true too, but isn't (If they choose Zoom as the location, they should get the Zoom-join-url and NOT the physical address in the notification.
Practically now, I am having to manually cancel the Zoom appointments of my in-person clients (Zoom then notifies them of the cancellation), So I have to then manually email them to confirm the meeting is still going ahead, only the Zoom element has been cancelled. They get confused as they didn't ask for Zoom anyway, and we start our relationship on the wrong foot. This plugin has, so far, tripled my workload and ruined user XP.
This was sold as the most powerful booking plugin on WP with great support. Come on team...
Hello Trevor,
Thank you for reaching out and sharing the details of the issue you're facing.
The workaround for this scenario would be to create separate services for Zoom and in-person sessions. By setting up distinct services for each type, you can ensure that the location and notification logic behaves as expected. Zoom sessions will generate the Zoom meeting link, while in-person sessions will provide the physical address. This should help to prevent the confusion and reduce the need for manual cancellations or follow-up emails.
I hope this helps! Let me know if you need any further assistance.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables