This system map is part of the call transfer recovery guide. It lists which system holds each record, the identifier that links it, who owns it, and what one fully joined Illustrative case looks like when every key is present.
Four systems, one customer call
A transferred call leaves pieces in at least four places:
- Telephony platform. One contact record per leg, with queue, agent, timestamps and disconnect reason. On Amazon Connect, a contact created by a transfer to queue or transfer to flow block carries a previous contact ID, and all legs share an initial contact ID for the first contact in the chain.
- Speech analytics. A transcript for each leg, keyed to that leg's contact ID. In Amazon Connect, a user with the right permissions can search by contact ID and review the transcript and recording together.
- CRM. The case, its activities, approvals and resolution code. Some CRMs also hold their own voice call records: in Salesforce Service Cloud Voice, a voice call record created for a transfer carries a parentVoiceCallId pointing to the parent call, required when the initiation method is Transfer.
- QA or workforce tool. Scorecards and evaluations on sampled calls, usually keyed to the contact ID.
Amazon Connect
Salesforce Service CloudLinking keys, system by system
| System | Record | Linking key | Owner |
|---|---|---|---|
| Telephony platform | Contact record per leg | Contact ID, with previous contact ID on transferred legs | Telephony administrator |
| Telephony platform | Whole-call chain | Initial contact ID shared by all legs | Telephony administrator |
| Speech analytics | Transcript per leg | Contact ID of that leg | QA or analytics lead |
| CRM | Voice call record | Vendor call key, parent voice call ID on transfers | CRM administrator |
| CRM | Case and its activities | Case number, plus contact ID if the integration writes it | Head of customer operations |
| CRM | Supervisor approval | Case number and approval timestamp | Customer operations, finance for credits |
| CRM | Resolution code and closed date | Case number | Head of customer operations |
| QA tool | Scorecard on a transferred call | Contact ID | QA lead |
The weak row is the case. Whether it carries a contact ID depends on the integration, and cases opened by hand often do not.
One fully joined case (Illustrative)
Illustrative. A fictional 340-person consumer lender runs a service center on a cloud telephony platform with a CRM. A borrower calls collections to say they have lost their job; collections cannot set up a hardship plan and transfers the call to the hardship team. The hardship agent answers without the collections notes.
| Join | Key value in this case | Where it was found | Holds? |
|---|---|---|---|
| Leg 2 to leg 1 | Leg 2 previous contact ID points to leg 1 | Telephony contact records | Yes |
| Both legs to the call | Shared initial contact ID | Telephony contact records | Yes |
| Call to case | Initial contact ID written on the case activity | CRM case | Yes, for calls since the integration upgrade |
| Words to legs | Two transcripts, one per contact ID | Speech analytics | Yes; leg 2 opens with the borrower repeating the story |
| Decision | Hardship plan approved by a team lead, 14 minutes into leg 2 | CRM approval | Yes |
| Outcome | Resolution "hardship plan, transfer context lost"; first payment made on plan | CRM case and payments note | Yes |
Every key holds, so a reviewer can line up the lost context, the recovery, the approval and the outcome without guessing. For calls before the integration upgrade, the call-to-case row would read "no", and those cases could only be matched by phone number and time, which is not reliable.
Where joins break, and what to ask
| Break | Effect | Question for the client |
|---|---|---|
| Case stores only a phone number | Cannot tell which call a case belongs to | Since when does the integration write the contact ID on the case? |
| Consults mixed with transfers | Transfer counts inflated; some chains misread | Does the team separate consults, conferences and transfers? AWS publishes logic for this on its platform |
| Transcripts kept elsewhere, shorter | Words drop out of older cases | How long are transcripts kept compared with contact records? |
| Contact record retention | Older chains disappear | How long does the platform keep call records, and were any streamed out to the company's own storage? |
| Resolution codes revised | Old and new codes mean different things | When did the code list change, and is the old list kept? |
| Time zones differ | Events appear out of order | Do the telephony platform and CRM store times in the same zone? |
None of these questions requires opening a recording or a case. A CCaaS consultant can usually answer half of them from the integration design. The parallel problem in ticket data is covered in support tickets with useful resolution context, and recording-specific rules in contact center migration and call recordings.
Before you introduce the company
Keep discovery at metadata level: which systems, which keys, how many years, who administers each. The worked recovery case shows the same joins in a single call, and the referral brief template has a field for the call-to-case key. Consultants who advise on contact center change can read the CX consultant referral page.
For SourceX, an introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Buyer interest, the rights result, which joins survive and any offer stay unknown until SourceX reviews it.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client's CRM cases carry the call ID and its telephony legs link back to the first contact, register as a partner, check the company against who qualifies and read the program terms before you introduce the head of customer operations.