LearnGrokUse these prompts to turn scattered case records into a file a specialist can review quickly. They are for support teams preparing disputed-payment cases, not for deciding liability or making the final submission.
Start with the intake prompt. It tells you what is present, what conflicts, and what must be found before anyone writes a case summary. Then build the chronology and inventory. Use the handover summary only when those two documents are stable.
Key point
Build from records, not recollection
Keep each factual statement tied to a dated source document. A neat summary cannot repair a missing or contradictory record.
Work through the case in order
Collect the source records
Gather the order confirmation, transaction record, fulfilment events, delivery record, refund or return activity, customer messages, and internal notes. Paste the material in date order where possible. Keep the original wording of customer messages and event statuses.
Remove information that is not needed for the review, such as unrelated account notes. Do not remove a date, order number, event identifier, or the name of the system that produced a record. Those fields let the reviewer trace a statement back to its source.
If you are using file uploads or platform features to provide records, their availability can vary. Check the relevant setup guidance in the xAI documentation overview before changing your workflow.
Run
Case intake and evidence triageUse the intake output as the control sheet for the case. Check that its
Case identifiersmatch the transaction and order record. If it lists more than one transaction, split the work into separate packs unless your internal process says otherwise.The useful part is usually
Evidence gaps. Turn each gap into an owner and a request. For example, a dispatch event without a delivery event is not proof of delivery. A customer saying an item did not arrive is a statement, not a delivery record. Keep both, and label them correctly.
Watch out
Do not turn system status into a stronger claim
Label created, dispatched, out for delivery, and delivered are different events. Include the exact carrier wording and timestamp.
Make the chronology before writing prose
Run
Evidence chronologyonce the main records are present. Read the rows from top to bottom. This exposes the gaps that a folder of screenshots hides: a refund recorded before a customer contact, a delivery date after an alleged cancellation, or two versions of the same event.Do not force uncertain records into a sequence. Use
not statedfor a missing timezone andlowconfidence for an undated note. A reviewer can work with uncertainty that is labelled. They cannot safely work with uncertainty disguised as fact.Build the inventory and request missing records
Run
Evidence inventory and gap logafter the chronology. This separates documents that support a specific fact from documents that merely provide background. Mark incomplete screenshots and internal notes carefully. They can help the reviewer understand the case, but they may not be suitable for inclusion in the final evidence set.When the pack is blocked, use
Missing evidence requestrather than sending a vague message such as “please send proof”. Ask for the exact event, identifier, date range, or status field. Record a negative response too. “No signature record exists” closes a gap more clearly than an unanswered request.
Note
Keep a source reference in every file name
Use a consistent internal pattern such as order-record_2026-08-04, carrier-event_2026-08-06, or customer-message_2026-08-07. Do not rename a record so its date or origin becomes unclear.
Check the pack before handover
Use the table below to review common failures. Do this before generating the specialist summary.
| If you see this | Treat it as | What to do |
|---|---|---|
| A delivery status with no timestamp | Incomplete delivery evidence | Request the full carrier event history or mark the date as unknown |
| A customer message contradicting a system record | A material conflict | Include both sources and quote the relevant wording |
| A refund mentioned in notes but absent from payment records | Unverified internal claim | Request the payment or refund transaction record |
| Two order numbers in one conversation | Possible mixed case | Confirm which order the dispute concerns and split the pack if needed |
Check
A reviewer should be able to trace every key fact
For each statement about payment, fulfilment, delivery, cancellation, return, or refund, check that the pack names a source document and date. If it cannot, move it to Outstanding evidence.
The output is wrong if it fills a gap with a plausible assumption. Watch for phrases such as “therefore”, “clearly”, “must have”, or “likely” where the source does not establish the point. Also check for silent changes to dates, currencies, order numbers, and customer wording. These errors often appear when material contains duplicate records or copied internal notes.
Prepare the handover
Run Specialist handover summary last. Read the Neutral account of events against the chronology, not against memory. The summary should describe what each record says and identify conflicts. It should not argue the case or make a decision reserved for the specialist or manager.
Attach or retain the source documents named in Evidence included. If the summary refers to “proof of delivery” but the inventory calls it an incomplete delivery screenshot, correct the summary. The document names, dates, and limitations must match across the pack.
When the output does not work
If the output is too general, paste fewer records and start with the chronology or inventory prompt. If facts are mixed between orders, run separate prompts for each order. If a prompt invents a field or overlooks a conflict, add the missing source record and ask it to rebuild only that document.
Do not patch a doubtful summary by rewriting its conclusion. Go back to the intake, chronology, or evidence gap log, fix the source trail, then generate the handover again. If key records remain unavailable or the case includes a material contradiction, route it to the specialist or manager with the gap clearly stated.
