Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: Support colleagues hand over a case folder beside shared records.
A customer reports a missing shipment. Support can see an order, fulfillment has information about dispatch, and a carrier check may still be needed. If every person starts a separate conversation, the customer can receive conflicting answers while nobody owns the next update.
NetSuite cases provide a record for the issue, assignment and communication. The product supports replies, escalation and closure, but those actions still need a clear operational meaning. Changing a status does not prove that someone accepted the handoff or that the customer agrees the problem is solved.
This lesson follows a fictional missing-shipment case. It focuses on keeping the original issue, business records, customer-facing replies and internal investigation connected.
Write the reported problem in language another representative can understand. Include what the customer expected, what they observed and which order or service is involved.
“Customer asks where order SO-EXAMPLE is; the expected delivery date has passed” is more useful than “Shipping issue.” The example identifier is invented. In your account, use the actual identifier through the approved internal process and avoid unnecessary personal data in summaries.
Separate reported facts from assumptions. “Customer says no parcel arrived” is evidence about the customer’s report. “The carrier lost the parcel” is a conclusion that requires further evidence.
Also identify what the customer needs next. They may want a delivery update, clarification of a partial shipment or a replacement decision. Those requests can involve different owners and approvals.
Cases can be created through several configured routes, including a representative’s entry, online forms and support email. The route affects how information arrives, so confirm the account’s case-management setup before assuming every email automatically becomes a correctly linked case.
Use the case to preserve the relationship to the business event rather than retyping an entire order into a note.
NetSuite supports linking cases to supported transaction types, including sales orders and invoices. On the case’s Related Records subtab, the Transactions area includes an Attach option for linking an existing transaction. Use the existing record when it is the record you need to investigate; creating a new transaction is a different action.
A link helps reviewers reach the authoritative order or invoice within their permissions. It does not automatically give everyone access to every linked record. The support process should respect the boundaries of each person’s role.
For a missing shipment, read the sales-order status lesson before treating ordered, fulfilled and billed as equivalent states. The order’s accounting or billing status may answer a different question from the customer’s delivery concern.
Keep any carrier evidence clearly attributed and dated. A copied tracking statement is a point-in-time observation, not an unlimited promise about delivery.
Cases can be assigned to a person or group, either manually or through configured rules and territories. The Assigned To field represents the current assignment.
A group assignment can support a shared queue, but a queue still needs an operating rule for who picks up work and who notices unattended cases. “It belongs to support” is too vague when a customer is waiting for an answer.
NetSuite provides a Grab action for eligible group-assigned or unassigned cases. Grabbing a case assigns it to the representative. A case already assigned to another representative does not present the same opportunity.
The team should agree how the named owner changes and how an absence is covered. This is a process decision around the product’s assignment mechanism, not a reason to share credentials or silently work under another person’s identity.
Before saving a response, inspect who will receive it and which visibility options apply.
The case Reply field can be used with Send to Customer to email the response when the case is saved. The Email(s) field can include additional recipients, so check every address rather than assuming only the main customer contact will receive it.
Internal Only controls a different audience. Under the documented case behavior, an internal-only reply is visible to employees and is not emailed to the customer; employee copies follow the relevant copy settings.
These controls make a simple habit important: draft the message, check the audience and visibility, then save or send through the approved process. Saving a case can have communication effects. It should not be treated as harmless note storage when customer-send settings are selected.
Use customer-facing language for confirmed facts, agreed next steps and approved commitments. Keep internal diagnostic speculation and unrelated commercial information out of that response. Marking a previously sent message internal later cannot make the recipient unread the email already received.
For training, use a test case with safe addresses and verified notification settings. Do not practice sending on a live customer case.
This is an important NetSuite distinction: escalating a case sends an assistance message and changes its status to Escalated. It does not change the Assigned To owner or automatically raise priority.
The escalation message is private from the customer and is logged on the case. The escalation email includes case information and the customer’s message. Choose recipients authorized to receive that information, especially if the process permits escalation to an external partner or supplier.
If the business intends to transfer ownership, manage the assignment explicitly and confirm the new owner’s responsibility. If it intends only to request specialist help, keep the existing response owner responsible for following up and communicating with the customer.
A useful escalation question is bounded: “Please confirm whether this fulfillment was handed to the carrier and provide the available dispatch evidence.” That is better than “Please investigate,” which leaves the specialist to reconstruct the purpose.
The escalation should explain what is known, what has been checked, what remains uncertain and when the response owner needs the result. Do not invent a promised deadline; use one agreed under the team’s service policy.
In this fictional case, the customer reports that an expected order has not arrived. The representative verifies the customer and order, attaches the existing sales order and records the customer’s report without concluding that the shipment is lost.
The representative inspects the permitted order and fulfillment information. They find a fulfillment reference but still need confirmation of dispatch and tracking evidence. They ask the fulfillment team a specific question through the approved escalation route.
The support representative remains Assigned To while fulfillment supplies the requested evidence. If the team decides that another representative should own the case, it changes assignment deliberately. Escalation alone does not accomplish that transfer.
Fulfillment then confirms that the order was split into two shipments and provides the relevant records. One shipment has delivery evidence; the other is still in transit. The representative checks which items the customer says are missing before replying.
The customer-facing update can now explain the verified split and the confirmed status of the outstanding items. It should avoid claiming a delivery date that has not been confirmed or promising a refund or replacement without approval.
If a replacement, credit or refund becomes appropriate, it requires the relevant business process in addition to the case conversation. The returns and refunds lesson explains why authorization, receipt, credit and refund are different stages.
Before closing, record what resolved the issue and how it was checked. The evidence might be a clarified shipment split, a verified correction or an answer to the customer’s question.
The case status should reflect the team’s closure policy. A representative sending an answer does not necessarily establish that the customer has received or accepted it. Be clear about what is known and what remains conditional.
Closed cases remain in the system even though the default case list may filter them out. When an apparently missing case needs review, inspect the list filters before creating a duplicate.
In the documented email route, a customer reply to a closed-case message can reopen the case and assign it to the last representative who replied. A fresh online case submission can create a new case instead. Closed-case lockout settings can further restrict reopening and updates, so do not promise that every reply follows one universal behavior.
Agree a clear route for a customer whose issue continues. Test that route with the actual configuration and keep the response owner aware of reopened or newly related cases.
If a case is unattended, check assignment, queue ownership and the rules that routed it. An Escalated status is not proof that ownership changed.
If a reply seems missing, inspect the original case, its messages and configured email routing before starting a separate record. Confirm which support address and conversation route were used.
If the case keeps reopening, review whether the recorded resolution actually addressed the reported problem. A repeated closure cycle may indicate an incomplete answer, an unresolved dependency or a route that creates duplicate cases.
If a record changed unexpectedly, the System Notes lesson can help the administrator investigate supported change evidence without guessing who caused the problem. Use the access review guide if representatives cannot reach the records needed for their authorized work.
For exercises that connect case fields with real service responsibilities, explore CuriousRubik NetSuite training and adoption. The best test is whether another authorized representative can continue the case without asking the customer to tell the whole story again.