Genesys Cloud - Main

Well, I am sure most of you are tired of hearing my diatribes about the New Features that are API-only.  I have a few questions for you and would appreciate your feedback.  @Becky Powell, I hope this will help you in better communication.  I am really fed up with the idea that API-only releases are listed in the New Feature list. 

What would you prefer?

1. Include them as they are now in normal Release Notes, but have better descriptions to indicate that API-only releases are not in the UI yet.  
2. Include and API Release section in the Release Notes that stipulate new features that are only API features and not UI.
3. Only announce API releases on the Developer Site in their own Release Notes section.
4. Have a separate section in Release Notes like we have for FedRAMP in Release Notes.
5. Something Else - explain.

The idea here is to let Genesys know that when the release a feature, the expectation is that the feature is released in the UI and after exhaustive testing and searching - only to learn that there is no UI - only yet another API.  

Please let me know your thoughts and I'll discuss with Product Management so we can improve the release notes in the future.

#Roadmap/NewFeatures

Personally I would prefer any of option 1 or 2, since I rather get all release notes in one place without having to look separately on the Developer site.

Just putting API-only or similar in the title would be sufficient information, for example

Historical execution data for Architect bot flows and digital bot flows (API-only)

------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB
------------------------------

I think they should stay in the main release notes, but have an "API-only" disclaimer, or explicit notes stating that this is "API-only and UI elements are scheduled for later release".  But adding "this is released and ready to use" for an API-only release is basically just lies, at this point, and I can totally echo your frustration with Genesys doing that multiple times recently.

------------------------------
Paul McGurn
Manager, Telecom & DevOps
GoTo
------------------------------

I echo support for options 1 & 2.

I think it should be included in the main release notes, since then we don't have to check multiple sources of truth for the current state of affairs, however not clearly marking those items that are API only, is misleading - especially for less experienced or technical customers who may not (yet) have dived into the world of APIs.

------------------------------
Paul Simpson
Views expressed are my own and do not necessarily reflect those of my employer.
------------------------------

Definitely options 1 or 2, having yet another release notes section or page would be annoying since we have like 10 already. I don't mind the API only releases - I <3 Postman and will happily play around with things while waiting for a UI, but first we have to *know* that the release is API only.

------------------------------
Brad Murlin
Zillow, Inc.
------------------------------

You asked... we're delivering! Henceforth we will preface our API-first release notes with "API for [insert feature name here]".

We will monitor for the next few months to ensure that improving our release note titles helps to reduce customer angst. 

Cheers!

------------------------------
Becky Powell
Director, Product Management
Genesys - Employees
------------------------------

I believed that will work.  Thank you AS ALWAYS for listening to your users.