August already! We sat down with Kawartha Credit Union to hear how they’re using the data captured in Coconut to make informed decisions that optimize branch operations and improve member experience. Listen here. If you’d like to share your team’s success story, reach out to marketing@coconutsoftware.com.

Also, Coconut is building new and improved learning resources and we’d like your input! Help us create what is most helpful for you and your organization by completing our 3 minute survey. We look forward to your feedback!

Now, read on for what is coming when release is live in production August 23.

Participants in a Connect meeting can now leverage closed captioning during a call. This functionality extends accessibility options for our video appointment-taking staff and their clients or members, while also supporting your organization’s WCAG compliance requirements.

This feature is available to all Connect customers.

Please refer to our Connect section when release is live in production for more details on closed captioning.

Closed captions are now available in Connect meetings

For customers using our B2B APIs, please note that changes are coming to bulk operations. Currently, when calling a bulk API with only one record included, the response will return simply that record.

However, in the future, when calling a bulk API with only one record included, the response will return an array that includes that record. This update is upcoming in the September release so please have your team check that this change won’t impact your integration with Coconut and reach out if you have any questions or concerns.

Coming in the September release, you will be able to get an Open API 3.1 version of our API documentation. This will allow your development team to not only understand how to invoke the Coconut B2B APIs, but also how to quickly generate SDKs to invoke the API from your technology stack.

Once available, to access the Open API spec, simply login to Coconut and navigate to Settings->Integrations & APIs->API. You can then proceed to import the spec URL in your favorite Open API editor (e.g. Swagger) and/or use it with your favorite SDK generator tool.