Skip to Content

Agree Which Record a Shared Case Reference Identifies

A Genesys external-reference update gives clients and providers a reason to agree identifier meaning, association checks and correction ownership.

Table of contents

No titles in the blog post

A client and an outsourcing provider may describe the same piece of work through different systems. Adding a shared reference can help them find the connection. They still need to agree precisely which record the reference identifies, including its source system and how to handle uncertainty.

The Genesys Cloud release notes dated November 16 describe optional external references for cases. Users can create or update a reference and search using either that reference or the preserved Genesys Cloud case reference. The feature is presented as a way to associate a case with a record in another system. Availability remains subject to regional readiness, licensing and release schedule. The announcement does not establish automatic synchronisation or universal uniqueness of external identifiers.

Say which kind of record the number means

The following is our original client–provider operating analysis. The situation is hypothetical and does not describe a tested integration or actual customer records.

Imagine a provider handling enquiries about a client’s event bookings. The client uses one reference for a booking and another for a payment. A customer mentions a number in a message, and a colleague wants to attach it to the service case.

Before doing so, the colleague needs to know what the number represents. A booking reference and a payment reference could both be relevant, but they would connect the case to different records. A shared instruction should identify which one belongs in the agreed field.

Include enough context for the next colleague to understand the reference. A bare value can be hard to interpret when several systems or clients use similar-looking identifiers. The team should agree how that context is retained in its actual workflow.

Check the link against the work

In the invented case, a customer could have two bookings and be asking about only one. Finding a record with a matching-looking number would not, by itself, establish that it is the record needed for the current enquiry.

The client and provider can define what supporting information a colleague should examine before making the association. The appropriate check depends on the service and the information the colleague is authorised to use. It should connect the reference to the request being handled, rather than simply confirm that some record exists.

If the available information leaves the link unclear, identify who can resolve it. Keeping an uncertain case visibly unresolved is more useful than attaching a confident reference that sends later work in the wrong direction.

Give a correction an owner

Suppose the hypothetical team discovers that the reference points to the other booking. Agree who corrects the association and who checks whether any continuing work relied on it. The response should fit what actually happened.

A short note can explain the corrected link and the reason for the change. The next colleague should not have to infer the history from two different values appearing in separate places.

Avoid assuming that an edit in one system has changed another. Ask the people responsible for the actual setup what it does, and distinguish a reference used to find a record from a mechanism that transfers changes between records. Those are different capabilities.

Keep the continuing responsibility clear

Finding the related record does not settle who owns the next business action. In the event-booking example, the provider might answer a question while the client’s booking team decides whether a requested change can be made.

The handover should identify both the relevant record and the action needed from its owner. That helps the receiving team understand why it is being contacted and which question remains open. An identifier without that explanation can turn a handover into another search exercise.

A shared reference is most useful when the client and provider agree its meaning, the basis for attaching it and the route for resolving a mistaken association. Those agreements connect the convenience of finding a record with the practical work of serving the customer.

AI-generated conceptual photograph of a fictional records review; not actual customer records or a Genesys product demonstration.