Apricot | ETO Software | Product Blog | Webinar
Apricot | ETO Software | Product Blog | Webinar
Great news: Schedule is now available for both Apricot and ETO!
With Schedule, you can schedule appointments, with the ability to set availability and add video conferencing services, right from within Apricot or ETO. In addition, Schedule integrates seamlessly with the tools you already use today, like Google Calendar, Outlook and Zoom.
Schedule makes it easier to deliver both virtual and in-person services, removing barriers to service and making it easier for people to connect with the help they need.
In the webinar recording below, Fallon Thompson, Product Manager, and Chelsea Edwards, Product Marketing Manager, share how you can work smarter with Schedule. The recording includes a demo of the new feature and answers to common FAQs.
Below the webinar recording, you’ll find the Q&A from the webinar. Check out the release notes to learn more about Apricot & ETO Schedule: (Apricot | ETO).
Schedule is included (at no additional cost!) for the following customers:
We have partnered with a third-party software called Cronofy to implement this capability into our software, so we are able to integrate with the applications that Cronofy will support. To learn more about Cronofy—what they will support for integrations, as well as their security and privacy qualifications—please check out their website.
For calendars, Schedule will integrate with Outlook, iCloud, Gmail, Exchange and Office 365. For video conferencing, Schedule will integrate with Zoom, GoToMeetings and Teams.
We currently do not integrate with RingCentral. However, for RingCentral and other video conferencing services, you can still manually add your account link as the location when adding an appointment.
We currently do not integrate with Microsoft Bookings or other booking software.
When you sync your calendar, you are essentially sharing your existing appointments, as well as your availability, with Apricot or ETO. This means that you will see all of your appointments for your existing calendar account (ex. Outlook) in Apricot or ETO. It’s a two-way sync, so any appointments made in Outlook will automatically transfer and be viewable in Apricot/ETO, and any appointments made in Apricot/ETO will be transferred to Outlook (or whatever calendar provider your organization uses).
You cannot currently choose which appointments will sync – all of them will sync. However, if you set an appointment as private in Outlook (or another calendar provider), then it will show in Apricot/ETO as “Private.” You and other users will not be able to see any details whatsoever for a private appointment.
With Connect Scheduler, they will be able to! Connect Scheduler was released to Apricot 360 on Friday, July 23. We will eventually be implementing this capability into ETO as well.
To learn more about Connect Scheduler, check out our release notes.
In ETO, yes! Schedule is currently available to report on. To learn more, please check out our Knowledge Base Article.
In Apricot, we are currently in the development process of making Schedule available in reporting; Coming very soon!
A common question is being able to report on “no shows” to appointments. Unfortunately, our software has no way of knowing whether or not a participant shows up to an appointment without someone telling it, especially if it was an in-person meeting. “Telling” the software typically looks like filling out a Tier 2 form or a TouchPoint that indicates whether the participant showed up or not. This would definitely be reportable!
Yes! You can see other users’ calendars if they have also synced their calendars with Apricot/ETO. You can even choose to see all of your coworkers’ calendars at once in order to see a “Master Calendar” for your organization and get a high-level view of everyone’s availability.
For ETO specifically, there is an additional setting where you can set up additional permissions for whose calendars you can see in Schedule. This is in addition to existing security settings that your organization already has in place. This setting is under Manage Schedule under Manage Site Administration. This setting allows a site to determine whether they want to be able to “view across site” or simply “view across program” for Schedule. This means that a user can either see all users’ calendars and participants across an entire site or only the users and participants in the program that they are currently in.
Currently, this setting is “all or nothing” – in other words, you can either set Schedule across the entire site or set it to only programs. There is no way to configure which programs can share and which cannot.
NOTE: In Apricot, Tier 1 permissions are still respected when populated in the participant dropdown.
Yes! In Apricot, there is a new tab on the Document Folder called “Appointments.” You will be able to see all upcoming and past appointments for that participant. You will also be able to add an appointment for that participant right from that tab!
In ETO, there is a new link on the Participant Information dashboard part, as well as on the View/Edit Participant page, labeled “View Appointments.” It will take you to a new page where you will see all upcoming and past appointments for that participant. You will also be able to add an appointment for that participant right from that tab.
Yes! In Apricot, you can select multiple participants for an appointment. In ETO, you can do that, but you can also select to add appointments by Family or Collection as well.
From Schedule, they will receive an email or “Appointment Notification,” which will notify them of an appointment being made. It will include all of the information that the staff user entered for the appointment – Participants, Staff Attendees, Appointment Title, Date and Time, Description and Location.
An email will get sent to the email listed under the participant in your database. While there is no way to “turn off” notifications for an appointment for a participant, you can choose not to send the participant an email by listing a fake email address under the participant (fake@fake.com).
That being said, in order to add an appointment with a participant, they will need to have an email address associated with them. Again, if your organization does not collect email addresses for the populations you serve, entering a fake email address will allow you to implement Schedule in your organization.
There are not reminders for appointments, but eventually, we would like to integrate Schedule with capabilities like Rules & Alerts, Workflows & Alerts and even Direct Messages to help even further simplify this workflow.
Your administrator will need to configure Schedule prior to anyone in the organization using Schedule. During this configuration, the administrator will choose what Tier 1 form(s) will populate Schedule as participants in the participant dropdown. They will also choose what secondary identifier is used to search for participants in the dropdown. For more information on this configuration, please see the Knowledge Base Article.
We have had a lot of great feedback on Schedule, but we know there is always room for progress, too. We encourage you to visit our Ideas Portal and enter these ideas (or upvote them if they exist already!). The Product team uses the Ideas Portal to determine what’s next for our software, so upvoting and commenting on an idea is the best way to get a direct say to what we build next! Below are some ideas for enhancements for Schedule that were mentioned during the webinar.
For any other questions or concerns, we encourage you to reach out to our Support team, and they will be more than happy to assist you.
Cookie | Duration | Description |
---|---|---|
_biz_flagsA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_pendingA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_sid | 30 minutes | This cookie is set by Bizible, to store the user's session id. |
ARRAffinity | session | ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user. |
ARRAffinitySameSite | session | This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
BIGipServerab09web-nginx-app_https | session | This cookie is associated with a computer network load balancer by the website host to ensure requests are routed to the correct endpoint and required sessions are managed. |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__atuvc | 1 year 1 month | AddThis sets this cookie to ensure that the updated count is seen when one shares a page and returns to it, before the share count cache is updated. |
__atuvs | 30 minutes | AddThis sets this cookie to ensure that the updated count is seen when one shares a page and returns to it, before the share count cache is updated. |
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
_biz_nA | 1 year | This cookie, set by Bizible, is a sequence number that Bizible includes for all requests, for internal diagnostics purposes. |
_biz_uid | 1 year | This cookie is set by Bizible, to store user id on the current domain. |
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_gaexp | 2 months 10 days 10 hours | Google Analytics installs this cookie to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in. |
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |
Cookie | Duration | Description |
---|---|---|
_BUID | 1 year | This cookie, set by Bizible, is a universal user id to identify the same user across multiple clients’ domains. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_33YSH1JFFW | 2 years | This cookie is installed by Google Analytics. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
_hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
at-rand | never | AddThis sets this cookie to track page visits, sources of traffic and share counts. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
undefined | never | Wistia sets this cookie to collect data on visitor interaction with the website's video-content, to make the website's video-content more relevant for the visitor. |
uvc | 1 year 1 month | Set by addthis.com to determine the usage of addthis.com service. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_mkto_trk | 2 years | This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
loc | 1 year 1 month | AddThis sets this geolocation cookie to help understand the location of users who share the information. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | No description available. |
_clck | 1 year | No description |
_clsk | 1 day | No description |
_dc_gtm_UA-718299-1 | 1 minute | No description |
_hjSession_2602456 | 30 minutes | No description |
_hjSessionUser_2602456 | 1 year | No description |
6suuid | 2 years | No description available. |
AnalyticsSyncHistory | 1 month | No description |
CLID | 1 year | No description |
d-a8e6 | 1 year | No description available. |
dpi_test | 1 day | No description |
dpi_utmOrigVals | 5 months 27 days | No description |
intercom-id-rbb6qelf | 8 months 26 days 1 hour | No description |
intercom-session-rbb6qelf | 7 days | No description |
li_gc | 5 months 27 days | No description |
loglevel | never | No description available. |
referrer | session | No description available. |
s-9da4 | 15 minutes | No description available. |
SM | session | No description available. |
xtc | 1 year 1 month | No description |
We are becoming BonterraTM
|