In this guide
Define the reference purposeLeave secrets out of the patternHandle collisions and correctionsUse references in handoversA support reference should identify a case, not provide access to the account. Choose a simple internal scheme that remains unique within the team’s records. Keep the original seller order and transaction references in separate fields so an internal label is not mistaken for a provider-issued identifier.
Define the reference purpose
The case reference connects observations, replies and next actions. The order reference connects a purchase. The payment reference connects a money record. A local profile nickname helps the customer navigate an app. These values can be linked without replacing each other.
| Reference | Purpose |
|---|---|
| Internal case | Coordinate the team’s work |
| Seller order | Identify the purchase |
| Payment transaction | Identify the money record |
| Local profile label | Identify a saved entry to the viewer |
Leave secrets out of the pattern
Do not build an identifier from a password, full connection URL, recovery code or payment-card value. Avoid unnecessary personal details such as a child’s full name or an entire phone number. A neutral sequence can do the job. Use the actual system’s supported access controls; knowing a case reference should not itself grant authority to change an account.
Handle collisions and corrections
Check for an existing case before creating another for the same unresolved request. If two cases must be linked, preserve both references and name the current owner. If a reference was mistyped, record the correction rather than silently redirecting an account action based on a similar-looking value.
Use references in handovers
A concise handover can state the case, relevant order, confirmed state and next action. Keep sensitive evidence in its restricted location. This is an internal record-design example, not a claim that Dream provides a case-number system, API or automatic duplicate detection.
Questions about this guide
Can I put an internal reference in a customer message?
Yes, if the team uses it consistently and explains its purpose. Make clear that it identifies the support case. It should not be presented as a seller-issued order reference or as proof that an account change has completed.