AI-powered coaching

We have introduced two AI-powered features into the 1:1 coaching experience:

• Previous session summaries

• Suggested topics for discussion

These AI features analyze previous 1:1 sessions to provide actionable context for coaches to incorporate into their planning efforts. Both features are designed to help coaches plan and develop agendas more efficiently, empowering them with information while ultimately keeping them in control of planning and delivery.

Previous session summary

The new Previous Session Summary module includes an AI-generated recap of the coachee's previous coaching session, taking all metrics, notes, and action items into account. Coaches can review the AI-generated summary to identify potential followup topics and effectively plan the next meeting agenda.

When enabled, you will see the Previous Session Summary module near the top of the right column of the coaching page.

Suggested topics

Coaches can now click Help Me Coach near the top of the Agenda field on the coaching page to view AI-generated suggestions for agenda topics.

Suggested topics are based on what our LLMs have learned from analyzing previous sessions with the coachee. These suggestions are meant to guide the planning process rather than control it. For example, a coach may find that several of the suggested topics are useful, while others may not apply to the goals for that session.

To learn more about both of these features, see 1:1 best practices or Create 1:1 sessions.

Coaching and QA enhancements

Coaching UI enhancements

We have enhanced the 1:1 coaching session page with modern styling and intuitive navigation. All of the familiar features are available, with a few new additions to make the coaching experience more convenient and effective.

Some of the new enhancements include:

• New slide-out panels keep important information at hand without cluttering the UI.

• New AI-powered features have been added to guide coaches through session planning.

• Metrics, saved feedback, and saved QA reviews are easily accessible in the right column.

• The main column has been expanded for greater visibility.

To learn more, see 1:1s.

Coaching templates

Coaches can now apply pre-configured templates to the Agenda field rather than creating new notes for each session. This helps to standardize 1:1 sessions by using the same outline and topics for all coachees or using standard outlines for specific scenarios.

To learn how to create and use coaching templates, see 1:1s.

Visual indicator for assignment goal changes

For assignments based on groups or teams, any changes in the group/team membership will automatically change the number of reviews assigned to each reviewer. If a reviewer's assignment goal has changed, a yellow indicator will be displayed near the "Assignments" option in the QA menu for that reviewer.

After loading the Assignments page, the reviewer will see a note on the affected assignment detailing the changes. Hovering over either of the two indicators on this page will reveal what changed and how the change impacted the number of assigned reviews:

Restrict access to editing completed QA reviews

We have added a new optional permission for user roles that allows users to edit QA reviews after they have been completed. Previously, all admins and team leaders could edit completed reviews. Now, you can enable or disable the new permission for any particular role.

For more information about adjusting role permissions, see Data scope and permissions.

User management enhancements

New Last Active filter

You can now filter the Manage Team page by the last date that a user logged in. In the Users tab of the Manage Team page, the new filter can be accessed above the users table.

Deactivate users profiles in bulk

The Bulk Actions menu on the Manage Team page includes a "Deactivate Users" option, which opens the Deactivate Users page. From the Deactivate Users page, you can quickly identify and select multiple user accounts for deactivation.

To learn more, see Deactivate profiles in bulk after release.

API updates

New Last Active response property for GET /v2/employees and GET /v2/employee

To accommodate the new Last Active metric introduced in this release, we have updated the API endpoints that provide user information to add a last_active response property.

Additionally, the GET /v2/employees and GET /v2/employee endpoints are now documented at https://apidocs.stellaconnect.net/.

Enhanced Sequence ID handling in Feedback Data Return API

We have improved the Feedback Data Return API to ensure that users leveraging sequence IDs for efficient polling will consistently receive all new or updated survey responses.

Previously, there was a rare edge case where updates to responses on a previously queried survey could be missed, particularly for users polling frequently (for example, every minute). This enhancement ensures the sequence ID is updated after every new or modified survey response, eliminating the risk of missing updates.

For users storing sequence IDs and polling at regular intervals, this update enables more reliable and efficient data retrieval. If you use date-based polling instead of sequence IDs, this change will not impact your workflow.

Subdomain update in documentation

We have updated our API documentation to reference <subdomain>.api.stellaconnect.net for each endpoint. This replaces the previous instances of api.stellaconnect.net. This change brings our documentation in line with best practices to cover the full range of URLs possible for developers.

Coming soon!

Salesforce managed package update

Version 2 of the Salesforce managed package for Agent Connect will soon be available on the Salesforce App Exchange.

The new Version 2 of the managed packaged enhances the Agent Connect and Salesforce integration in several ways:

• Events are now processed in real-time using Flows, rather than in five-minute intervals. When a survey request is sent from Salesforce to Agent Connect and when completed survey data is returned, events are processed and logged immediately.

• The integration now supports the option for in-channel delivery of surveys. Rather than triggering Agent Connect to send surveys via email, you can specify channels (SMS, whatsapp, etc.) to suppress automatic email surveys, instead choosing to use a link to deliver surveys directly in the specified channel.

• Employee names are now included in Request and Response objects, allowing you to quickly associate employees with interactions.

• New fields for Agent Name and Email/ID have been added to Response objects, allowing you to associate agents with interactions more directly.

• Field mapping for requests, data return, and service recovery interactions have been updated and enhanced. Data return fields can now be edited, and new custom fields can be mapped.

• We have improved the validation of API Key fields in the Agent Connect Lightning Configuration app to ensure that required fields are configured.

• You can now resend multiple requests at once, when needed, directly through the Agent Connect Requests app in Salesforce.

• For those using multiple instances of Agent Connect, you can now map multiple unique field identifiers to a single field in Salesforce.

For complete integration instructions, see the Salesforce integration guide when Version 2 is released.