// Legal Insights Repository (legal-insights-repository) v1 — Prisma seed // Synthetic sample data, CC0-1.0. Generated deterministically; re-running the // generator with the same spec and seed reproduces this file exactly. // // Delegates are named after the tables (prisma.legal_topics), which assumes models // mapped to those table names. Rename the delegates if your models differ. import { PrismaClient } from '@prisma/client'; const prisma = new PrismaClient(); async function main() { await prisma.legal_topics.createMany({ data: [ { id: 1, title: "arbitration", description: "The team asked for a change and the invoice was closed. No response from the reviewer, so the document was approved. The supplier reported a duplicate issue; the account was completed. No response from the supplier, so the order was cancelled.", popularity: 708 }, { id: 2, title: "liability arbitration", description: "An unusual follow-up: the invoice was approved. A standard follow-up: the account was replaced. Flagged as incomplete. The customer delayed the shipment.", popularity: 382 }, { id: 3, title: "regulation damages", description: "The appointment was reopened following an incomplete review. An operator reported a minor issue; the session was rejected. The record was processed after a manual check. Support reported a partial issue; the payment was replaced.", popularity: 582 }, { id: 4, title: "fraud", description: "The account owner reported a routine issue; the appointment was processed. No response from the courier, so the shipment was replaced. The booking was refunded following a duplicate review. No response from the team, so the record was approved.", popularity: 478 }, { id: 5, title: "dispute damages", description: "An urgent ticket was rejected the same day. No response from support, so the item was processed.", popularity: 373 }, { id: 6, title: "damages", description: "No response from the team, so the session was processed. The team confirmed the details and the report was rejected.", popularity: 286 }, { id: 7, title: "rights", description: "Flagged as unusual. The account owner rescheduled the order. The team reported a minor issue; the delivery was rescheduled. A repeat follow-up: the ticket was rejected.", popularity: 455 }, { id: 8, title: "regulation employment damages", description: "The supplier confirmed the details and the booking was reviewed. The account owner reported a partial issue; the session was approved. The delivery was closed following a repeat review.", popularity: 423 }, { id: 9, title: "dispute damages regulation", description: "No response from the courier, so the record was reopened. The invoice was rejected — routine case, no further action. The record was reviewed — manual case, no further action.", popularity: 596 }, { id: 10, title: "dispute", description: "The supplier confirmed the details and the report was escalated. The customer asked for a change and the payment was approved. The session was delayed — late case, no further action. Flagged as standard. Support confirmed the refund.", popularity: 614 }, { id: 11, title: "rights", description: "The supplier reported a minor issue; the item was approved. A late follow-up: the appointment was rescheduled. The claim was cancelled — minor case, no further action. No response from support, so the payment was rescheduled.", popularity: null }, { id: 12, title: "litigation fraud", description: "The shipment was refunded following an automatic review. The reviewer confirmed the details and the transfer was rejected. No response from the courier, so the record was replaced.", popularity: 635 }, { id: 13, title: "intellectual rights liability", description: "An automatic claim was escalated the same day. Flagged as late. The reviewer cancelled the ticket. The document was confirmed following an incomplete review. No response from the supplier, so the payment was rejected.", popularity: 631 }, { id: 14, title: "rights regulation compliance", description: "No response from an operator, so the appointment was replaced. The reviewer asked for a change and the booking was delayed. The account owner confirmed the details and the delivery was approved.", popularity: 474 }, { id: 15, title: "employment dispute", description: "The courier reported an automatic issue; the refund was closed. Support confirmed the details and the delivery was cancelled. The delivery was reviewed — minor case, no further action.", popularity: 599 }, { id: 16, title: "employment settlement damages", description: "No response from the team, so the refund was confirmed. An automatic follow-up: the session was processed. An operator asked for a change and the report was closed.", popularity: null }, { id: 17, title: "misrepresentation", description: "The claim was completed after a repeat check. The customer asked for a change and the refund was cancelled. The report was delayed after a late check. No response from the courier, so the ticket was rescheduled.", popularity: 453 }, { id: 18, title: "misrepresentation negligence property", description: "The document was processed after an automatic check. A partial follow-up: the order was reopened. An operator confirmed the details and the report was completed.", popularity: 525 }, { id: 19, title: "compliance arbitration", description: "The supplier asked for a change and the session was closed. The order was resolved following an unusual review. Flagged as routine. The reviewer cancelled the order. The booking was confirmed after an unusual check.", popularity: 196 }, { id: 20, title: "settlement", description: "The courier confirmed the details and the report was completed. An automatic booking was refunded the same day. The payment was refunded — unusual case, no further action. The team confirmed the details and the account was processed.", popularity: 313 }, { id: 21, title: "dispute intellectual", description: "The shipment was refunded following a partial review. The request was replaced — late case, no further action.", popularity: 567 }, { id: 22, title: "negligence privacy compliance", description: "The courier confirmed the details and the order was delayed. Support confirmed the details and the account was completed. The claim was approved — late case, no further action.", popularity: 437 }, { id: 23, title: "arbitration property", description: "The booking was processed after an unusual check. The supplier confirmed the details and the document was refunded.", popularity: 411 }, { id: 24, title: "damages", description: null, popularity: 440 }, { id: 25, title: "contract", description: "The courier confirmed the details and the request was reviewed. The item was delayed following a repeat review. A late follow-up: the booking was rejected.", popularity: 427 }, { id: 26, title: "damages dispute", description: "The session was refunded after a routine check. The shipment was approved — late case, no further action. No response from the courier, so the claim was escalated.", popularity: 327 }, { id: 27, title: "rights", description: "An unusual follow-up: the delivery was reviewed. A duplicate order was processed the same day. No response from the customer, so the delivery was updated. No response from the supplier, so the invoice was escalated.", popularity: 466 }, { id: 28, title: "litigation liability property", description: "The account was escalated — automatic case, no further action. The document was completed — automatic case, no further action.", popularity: 286 }, { id: 29, title: "intellectual privacy", description: null, popularity: 516 }, { id: 30, title: "discrimination", description: "The payment was rejected following a duplicate review. The customer confirmed the details and the record was updated.", popularity: 252 }, { id: 31, title: "contract", description: "The account owner reported a late issue; the shipment was reviewed. The account owner confirmed the details and the claim was reopened. The claim was confirmed — partial case, no further action. An incomplete follow-up: the request was cancelled.", popularity: 448 }, { id: 32, title: "fraud negligence", description: "An automatic session was reviewed the same day. Flagged as manual. The customer updated the account. Flagged as unusual. The team resolved the order. Flagged as minor. The team closed the request.", popularity: 282 }, { id: 33, title: "arbitration compliance tort", description: "The courier asked for a change and the item was replaced. A standard record was replaced the same day. An unusual payment was closed the same day.", popularity: null }, { id: 34, title: "tort employment", description: "The invoice was closed — incomplete case, no further action. Flagged as urgent. The supplier cancelled the invoice. A repeat transfer was escalated the same day. No response from the courier, so the payment was escalated.", popularity: 285 }, { id: 35, title: "regulation contract intellectual", description: "Flagged as duplicate. The account owner reviewed the document. An incomplete follow-up: the transfer was resolved. Flagged as incomplete. The courier escalated the account. The item was reviewed — unusual case, no further action.", popularity: 601 }, { id: 36, title: "rights", description: "An operator reported an incomplete issue; the report was rejected. The customer reported an incomplete issue; the booking was escalated.", popularity: 197 }, { id: 37, title: "liability tort", description: "Flagged as standard. An operator replaced the refund. The account owner reported a repeat issue; the shipment was replaced.", popularity: 541 }, { id: 38, title: "negligence", description: "A partial shipment was reviewed the same day. Support reported a late issue; the invoice was resolved. A manual record was escalated the same day.", popularity: 209 }, { id: 39, title: "compliance", description: "The reviewer confirmed the details and the payment was processed. The report was resolved following a repeat review. The courier confirmed the details and the record was cancelled. Support confirmed the details and the claim was replaced.", popularity: 703 }, { id: 40, title: "breach", description: null, popularity: 356 }, { id: 41, title: "employment fraud litigation", description: "Support confirmed the details and the request was reviewed. The delivery was delayed after an unusual check.", popularity: 316 }, { id: 42, title: "regulation", description: "Flagged as duplicate. The courier closed the item. The account owner asked for a change and the document was confirmed. No response from an operator, so the request was closed.", popularity: 331 }, { id: 43, title: "compliance misrepresentation property", description: "The reviewer reported an urgent issue; the refund was cancelled. Support confirmed the details and the request was refunded. The supplier reported a routine issue; the transfer was closed.", popularity: 615 }, { id: 44, title: "intellectual settlement", description: "The report was completed after an automatic check. The refund was replaced following a partial review. A routine appointment was completed the same day.", popularity: 301 }, { id: 45, title: "misrepresentation", description: "A manual follow-up: the session was cancelled. The shipment was reviewed — repeat case, no further action.", popularity: 199 }, { id: 46, title: "regulation", description: "The item was confirmed after a routine check. The transfer was confirmed — incomplete case, no further action. The refund was approved following an unusual review.", popularity: 433 }, { id: 47, title: "employment", description: "The session was delayed following a partial review. No response from the courier, so the request was rescheduled. The account was delayed after an incomplete check.", popularity: 476 }, { id: 48, title: "negligence dispute property", description: "The record was processed after a manual check. The team reported an urgent issue; the report was replaced. The appointment was escalated after an automatic check.", popularity: 353 }, { id: 49, title: "litigation", description: "Flagged as standard. The supplier confirmed the refund. The ticket was updated following a routine review. The booking was completed — incomplete case, no further action.", popularity: 597 }, { id: 50, title: "fraud discrimination settlement", description: "A routine ticket was refunded the same day. The appointment was updated following a minor review. Flagged as automatic. The account owner approved the payment.", popularity: 491 }, { id: 51, title: "tort", description: "An operator reported a minor issue; the appointment was approved. The transfer was approved following an incomplete review. An urgent document was escalated the same day. Flagged as urgent. The account owner rejected the shipment.", popularity: 386 }, { id: 52, title: "compliance liability dispute", description: "An unusual follow-up: the document was escalated. The customer asked for a change and the ticket was cancelled. Flagged as late. The team updated the document.", popularity: 634 }, { id: 53, title: "discrimination dispute", description: "An operator reported a duplicate issue; the item was processed. No response from support, so the session was approved.", popularity: 364 }, { id: 54, title: "property misrepresentation litigation", description: "The reviewer asked for a change and the claim was rejected. An urgent account was completed the same day.", popularity: 612 }, { id: 55, title: "negligence privacy contract", description: "The booking was reopened — unusual case, no further action. The delivery was refunded following a routine review.", popularity: 528 }, { id: 56, title: "tort", description: null, popularity: 801 }, { id: 57, title: "contract liability", description: null, popularity: 662 }, { id: 58, title: "dispute property settlement", description: "The session was reopened — incomplete case, no further action. Flagged as standard. The courier approved the delivery. The delivery was refunded — unusual case, no further action. The customer confirmed the details and the item was reviewed.", popularity: 455 }, { id: 59, title: "tort settlement", description: "The transfer was escalated — partial case, no further action. The request was escalated — repeat case, no further action.", popularity: 285 }, { id: 60, title: "rights tort", description: "The account was closed following an unusual review. The refund was rejected after a late check. Flagged as partial. An operator processed the claim. An unusual follow-up: the account was refunded.", popularity: 636 }, { id: 61, title: "dispute privacy damages", description: "The item was replaced — repeat case, no further action. No response from the customer, so the item was completed.", popularity: 586 }, { id: 62, title: "compliance negligence", description: "A standard item was updated the same day. The courier reported a duplicate issue; the document was refunded. The reviewer reported a minor issue; the appointment was processed.", popularity: 391 }, { id: 63, title: "arbitration contract regulation", description: "No response from the supplier, so the session was refunded. The reviewer confirmed the details and the claim was refunded. The team reported a duplicate issue; the order was replaced.", popularity: 507 }, { id: 64, title: "fraud misrepresentation breach", description: "No response from the customer, so the delivery was completed. A routine follow-up: the session was reviewed. The delivery was confirmed following a duplicate review.", popularity: 545 }, { id: 65, title: "breach", description: "Flagged as urgent. The team refunded the ticket. The supplier reported a standard issue; the booking was delayed.", popularity: 319 }, { id: 66, title: "contract liability property", description: "The transfer was rescheduled after a manual check. The account owner asked for a change and the refund was cancelled. A minor report was approved the same day.", popularity: 478 }, { id: 67, title: "misrepresentation", description: "The account was refunded after an automatic check. No response from the customer, so the account was resolved. The ticket was delayed following a partial review.", popularity: 602 }, { id: 68, title: "property fraud", description: "An incomplete follow-up: the invoice was confirmed. The reviewer asked for a change and the delivery was cancelled. An urgent shipment was rejected the same day.", popularity: 719 }, { id: 69, title: "breach tort privacy", description: "A repeat booking was delayed the same day. An automatic report was resolved the same day. An unusual item was completed the same day.", popularity: 515 }, { id: 70, title: "discrimination rights", description: "The request was processed following a minor review. Flagged as unusual. The reviewer rejected the appointment.", popularity: null }, { id: 71, title: "discrimination liability", description: "A repeat claim was confirmed the same day. The supplier asked for a change and the delivery was rescheduled. The customer confirmed the details and the shipment was processed. A duplicate follow-up: the record was cancelled.", popularity: 608 }, { id: 72, title: "damages privacy", description: "The refund was confirmed following a manual review. The payment was completed following a partial review. No response from the account owner, so the refund was confirmed. Support reported a routine issue; the order was replaced.", popularity: 219 }, { id: 73, title: "intellectual", description: "The supplier asked for a change and the transfer was escalated. A minor follow-up: the claim was rejected. The team confirmed the details and the document was completed. Support confirmed the details and the document was delayed.", popularity: 321 }, { id: 74, title: "settlement privacy", description: "A routine transfer was resolved the same day. The item was reopened — automatic case, no further action. A repeat claim was replaced the same day. Flagged as repeat. The team rescheduled the order.", popularity: 421 }, { id: 75, title: "fraud", description: "No response from an operator, so the report was reopened. A partial follow-up: the account was reopened.", popularity: null }, { id: 76, title: "employment damages liability", description: "A manual transfer was completed the same day. The account owner reported an automatic issue; the shipment was processed.", popularity: 322 }, { id: 77, title: "privacy misrepresentation", description: "Flagged as routine. The courier reopened the shipment. The reviewer asked for a change and the booking was completed. The payment was rescheduled following an urgent review.", popularity: 425 }, { id: 78, title: "tort employment property", description: "The reviewer confirmed the details and the appointment was reviewed. A routine follow-up: the shipment was rescheduled.", popularity: 394 }, { id: 79, title: "property privacy", description: "The claim was resolved after a routine check. A standard report was refunded the same day. A late request was closed the same day. The payment was closed following a routine review.", popularity: 410 }, { id: 80, title: "negligence", description: "An operator reported a partial issue; the order was replaced. The report was closed — late case, no further action. The team reported a minor issue; the transfer was delayed. The ticket was replaced after a standard check.", popularity: 689 }, { id: 81, title: "compliance intellectual", description: "The account was processed — standard case, no further action. The team confirmed the details and the report was approved. The appointment was rejected — manual case, no further action. Flagged as manual. The account owner refunded the order.", popularity: 646 }, { id: 82, title: "damages", description: "A routine follow-up: the order was delayed. The item was closed — routine case, no further action. The shipment was completed following an automatic review. Flagged as partial. The courier rejected the session.", popularity: 520 }, { id: 83, title: "arbitration", description: "A late session was closed the same day. An unusual follow-up: the appointment was resolved. The refund was delayed after a partial check. No response from the courier, so the record was reopened.", popularity: 392 }, { id: 84, title: "arbitration breach regulation", description: "The appointment was closed following a repeat review. Flagged as manual. The reviewer reviewed the record. The reviewer confirmed the details and the ticket was replaced.", popularity: 598 }, { id: 85, title: "negligence regulation compliance", description: "The refund was confirmed after a routine check. The shipment was delayed following a duplicate review. The supplier confirmed the details and the session was delayed. No response from the account owner, so the appointment was refunded.", popularity: 416 }, { id: 86, title: "dispute", description: "The supplier asked for a change and the document was confirmed. The courier confirmed the details and the payment was processed. The supplier confirmed the details and the session was processed. A late follow-up: the transfer was replaced.", popularity: 724 }, { id: 87, title: "privacy employment settlement", description: "The report was reopened — minor case, no further action. The courier reported an unusual issue; the record was reopened.", popularity: null }, { id: 88, title: "discrimination", description: null, popularity: 614 }, { id: 89, title: "privacy rights contract", description: "A standard booking was processed the same day. The item was updated after a standard check. The refund was updated after an urgent check.", popularity: 583 }, { id: 90, title: "negligence tort", description: "The request was refunded — standard case, no further action. An operator asked for a change and the invoice was rescheduled.", popularity: 446 }, { id: 91, title: "breach", description: "An incomplete appointment was replaced the same day. The item was confirmed after a standard check. The customer confirmed the details and the ticket was resolved. The ticket was processed — urgent case, no further action.", popularity: 482 }, { id: 92, title: "damages employment breach", description: "A minor invoice was rejected the same day. Flagged as late. The reviewer approved the shipment.", popularity: 530 }, { id: 93, title: "intellectual property", description: "An automatic booking was processed the same day. A repeat follow-up: the invoice was reviewed. The report was replaced after an unusual check.", popularity: 719 }, { id: 94, title: "misrepresentation liability regulation", description: "Support asked for a change and the transfer was resolved. A late appointment was updated the same day. The refund was rejected — urgent case, no further action. The account was reviewed following an incomplete review.", popularity: 385 }, { id: 95, title: "tort liability litigation", description: "An unusual ticket was rejected the same day. The document was replaced — automatic case, no further action.", popularity: 715 }, { id: 96, title: "damages employment", description: "An unusual report was resolved the same day. A repeat document was delayed the same day. The transfer was rescheduled — standard case, no further action.", popularity: 616 }, { id: 97, title: "rights", description: "Flagged as manual. The courier cancelled the booking. The record was confirmed — standard case, no further action. The ticket was resolved — incomplete case, no further action. A manual order was processed the same day.", popularity: 508 }, { id: 98, title: "intellectual negligence", description: "The record was refunded following a manual review. The appointment was refunded — urgent case, no further action. The request was reviewed after a duplicate check.", popularity: 909 }, { id: 99, title: "discrimination contract negligence", description: "Flagged as manual. The team refunded the order. A standard follow-up: the delivery was processed.", popularity: 659 }, { id: 100, title: "rights", description: null, popularity: 367 }, { id: 101, title: "regulation contract compliance", description: "The courier asked for a change and the booking was escalated. The ticket was approved following a late review. The account owner asked for a change and the invoice was completed. A repeat account was reopened the same day.", popularity: 629 }, { id: 102, title: "intellectual contract", description: null, popularity: 276 }, { id: 103, title: "dispute negligence", description: "A partial document was resolved the same day. The transfer was approved — automatic case, no further action.", popularity: 514 }, { id: 104, title: "property negligence liability", description: "A routine ticket was replaced the same day. No response from the account owner, so the transfer was reviewed.", popularity: 315 }, { id: 105, title: "breach", description: "The item was resolved after a partial check. No response from support, so the delivery was cancelled.", popularity: 434 }, { id: 106, title: "litigation compliance", description: "A routine booking was approved the same day. Support asked for a change and the report was approved. The account was closed following a standard review.", popularity: 493 }, { id: 107, title: "rights intellectual", description: "The payment was replaced — minor case, no further action. The refund was cancelled — automatic case, no further action.", popularity: 387 }, { id: 108, title: "contract privacy", description: "The record was delayed following a minor review. Flagged as partial. Support closed the session.", popularity: 530 }, { id: 109, title: "negligence misrepresentation privacy", description: "The invoice was processed — automatic case, no further action. The order was delayed after a repeat check. The ticket was closed following a late review. The record was refunded following a partial review.", popularity: 433 }, { id: 110, title: "employment litigation rights", description: "The customer asked for a change and the booking was closed. The supplier asked for a change and the transfer was completed. A minor follow-up: the shipment was reopened. The account owner confirmed the details and the request was updated.", popularity: 510 }, { id: 111, title: "intellectual rights tort", description: "Support reported a repeat issue; the item was updated. Flagged as minor. An operator updated the transfer.", popularity: 530 }, { id: 112, title: "property regulation", description: "The document was approved following a manual review. The courier reported a partial issue; the payment was resolved.", popularity: 521 }, { id: 113, title: "compliance negligence", description: "No response from the courier, so the payment was delayed. The refund was escalated — repeat case, no further action. The courier asked for a change and the record was escalated.", popularity: 621 }, { id: 114, title: "negligence", description: "A repeat invoice was processed the same day. The customer asked for a change and the record was rejected. The record was refunded after a routine check. The courier confirmed the details and the order was cancelled.", popularity: 336 }, { id: 115, title: "damages", description: null, popularity: 611 }, { id: 116, title: "rights", description: null, popularity: 577 }, { id: 117, title: "property", description: "The transfer was confirmed following a repeat review. The courier reported an automatic issue; the ticket was refunded. Support reported a duplicate issue; the refund was rejected.", popularity: 655 }, { id: 118, title: "employment breach fraud", description: "No response from an operator, so the request was resolved. A routine ticket was confirmed the same day. An operator confirmed the details and the claim was rejected.", popularity: 481 }, { id: 119, title: "damages", description: "The record was updated — incomplete case, no further action. No response from an operator, so the order was updated. The record was cancelled — repeat case, no further action.", popularity: 531 }, { id: 120, title: "arbitration compliance tort", description: "The customer asked for a change and the claim was rescheduled. No response from the team, so the record was confirmed. The team asked for a change and the refund was rejected. The team confirmed the details and the account was completed.", popularity: 458 }, { id: 121, title: "fraud", description: "The team reported a minor issue; the account was updated. No response from the customer, so the delivery was confirmed. Flagged as automatic. Support processed the refund.", popularity: 442 }, { id: 122, title: "intellectual privacy", description: "Flagged as duplicate. The courier delayed the appointment. No response from the team, so the report was reopened. A duplicate account was processed the same day. The shipment was delayed following a minor review.", popularity: 540 }, { id: 123, title: "fraud", description: "No response from the team, so the shipment was processed. The courier asked for a change and the session was closed.", popularity: null }, { id: 124, title: "settlement discrimination privacy", description: "The supplier reported a repeat issue; the record was refunded. A partial account was updated the same day. The transfer was rejected following a repeat review.", popularity: 298 }, { id: 125, title: "contract", description: "A routine delivery was delayed the same day. No response from support, so the claim was rescheduled.", popularity: null }, { id: 126, title: "discrimination regulation damages", description: "No response from the account owner, so the shipment was processed. The refund was rejected after a manual check. The courier confirmed the details and the shipment was reopened.", popularity: 532 }, { id: 127, title: "settlement negligence tort", description: "A manual booking was refunded the same day. The refund was completed — routine case, no further action. The session was rejected — duplicate case, no further action.", popularity: 327 }, { id: 128, title: "dispute damages discrimination", description: "The team reported a duplicate issue; the account was updated. No response from the customer, so the request was reopened.", popularity: 600 }, { id: 129, title: "misrepresentation regulation", description: "The team asked for a change and the booking was rejected. The supplier confirmed the details and the refund was escalated. The item was rejected — automatic case, no further action.", popularity: 323 }, { id: 130, title: "privacy", description: null, popularity: 355 }, { id: 131, title: "property fraud regulation", description: "An operator confirmed the details and the item was rescheduled. No response from the team, so the delivery was reopened. The payment was replaced after a duplicate check. A routine follow-up: the appointment was updated.", popularity: 430 }, { id: 132, title: "compliance dispute employment", description: "The courier asked for a change and the transfer was reviewed. Flagged as routine. The courier processed the appointment.", popularity: 685 }, { id: 133, title: "regulation employment damages", description: "No response from the reviewer, so the item was escalated. The supplier confirmed the details and the report was escalated. The courier confirmed the details and the refund was rescheduled.", popularity: 218 }, { id: 134, title: "litigation damages", description: "No response from the team, so the transfer was cancelled. Flagged as late. The account owner replaced the ticket.", popularity: null }, { id: 135, title: "rights", description: "Flagged as manual. The account owner confirmed the request. Flagged as routine. The customer completed the claim. Flagged as standard. The customer delayed the ticket.", popularity: 487 }, { id: 136, title: "employment negligence", description: "The refund was closed — manual case, no further action. The supplier asked for a change and the report was delayed.", popularity: 494 }, { id: 137, title: "compliance tort damages", description: "The courier asked for a change and the booking was cancelled. No response from support, so the claim was cancelled. An incomplete follow-up: the order was completed.", popularity: 500 }, { id: 138, title: "intellectual arbitration", description: "A routine follow-up: the delivery was cancelled. A late shipment was processed the same day. A standard order was escalated the same day. The supplier confirmed the details and the ticket was reopened.", popularity: 564 }, { id: 139, title: "arbitration intellectual", description: "No response from the supplier, so the session was rescheduled. Support reported an unusual issue; the shipment was resolved. No response from the account owner, so the delivery was rescheduled. An operator asked for a change and the request was cancelled.", popularity: 742 }, { id: 140, title: "negligence discrimination settlement", description: "A late follow-up: the item was refunded. The appointment was refunded — manual case, no further action. The customer confirmed the details and the payment was closed.", popularity: 530 }, { id: 141, title: "breach", description: "Support reported an incomplete issue; the claim was closed. The courier reported an automatic issue; the booking was approved.", popularity: 279 }, { id: 142, title: "liability intellectual", description: "Flagged as unusual. The team resolved the invoice. No response from the team, so the transfer was reviewed. No response from the account owner, so the order was replaced.", popularity: null }, { id: 143, title: "rights breach", description: "The supplier confirmed the details and the ticket was escalated. An operator reported an unusual issue; the report was reviewed. An operator confirmed the details and the order was delayed. The supplier reported an automatic issue; the transfer was delayed.", popularity: 509 }, { id: 144, title: "liability", description: "A standard payment was resolved the same day. The item was rescheduled — standard case, no further action.", popularity: 576 }, { id: 145, title: "tort intellectual dispute", description: "No response from the account owner, so the payment was updated. The claim was cancelled following an automatic review. No response from the supplier, so the refund was replaced.", popularity: 553 }, { id: 146, title: "arbitration", description: "The shipment was updated — manual case, no further action. An operator confirmed the details and the appointment was approved. The reviewer confirmed the details and the refund was refunded. Flagged as minor. The customer rescheduled the payment.", popularity: 507 }, { id: 147, title: "dispute negligence damages", description: "Support confirmed the details and the item was confirmed. The appointment was reopened — automatic case, no further action. Flagged as standard. The account owner reviewed the item.", popularity: 589 }, { id: 148, title: "damages", description: "Flagged as unusual. The customer resolved the report. The claim was confirmed — manual case, no further action. The delivery was processed after a partial check.", popularity: 122 }, { id: 149, title: "arbitration", description: "An automatic follow-up: the delivery was processed. The reviewer reported an automatic issue; the transfer was refunded. No response from the account owner, so the payment was reviewed.", popularity: 272 }, { id: 150, title: "employment settlement", description: "Support asked for a change and the shipment was rescheduled. The ticket was replaced after an automatic check. The request was rejected following a duplicate review.", popularity: 499 }, { id: 151, title: "property fraud litigation", description: "An automatic order was updated the same day. No response from the courier, so the record was updated. The order was rescheduled — minor case, no further action.", popularity: 565 }, { id: 152, title: "compliance contract", description: "An operator asked for a change and the payment was confirmed. An unusual document was confirmed the same day. The supplier asked for a change and the claim was reopened.", popularity: 552 }, { id: 153, title: "damages", description: "Flagged as late. An operator confirmed the delivery. No response from the customer, so the item was resolved. The customer reported a manual issue; the transfer was approved. A manual account was updated the same day.", popularity: 318 }, { id: 154, title: "tort", description: "Flagged as duplicate. The customer refunded the appointment. The courier asked for a change and the record was escalated.", popularity: 415 }, { id: 155, title: "property contract liability", description: "The customer asked for a change and the request was confirmed. An incomplete order was reviewed the same day.", popularity: 513 }, { id: 156, title: "employment breach property", description: "Support reported an unusual issue; the claim was refunded. An incomplete follow-up: the order was cancelled.", popularity: null }, { id: 157, title: "breach discrimination", description: "An incomplete item was reviewed the same day. The order was delayed after a standard check. Flagged as urgent. The account owner resolved the request.", popularity: 668 }, { id: 158, title: "litigation arbitration negligence", description: "No response from the reviewer, so the account was approved. Support reported an automatic issue; the request was processed. The customer confirmed the details and the payment was rescheduled. The courier reported an incomplete issue; the document was escalated.", popularity: 541 }, { id: 159, title: "misrepresentation intellectual negligence", description: "The record was confirmed — standard case, no further action. No response from support, so the account was closed. A routine follow-up: the delivery was confirmed. The delivery was completed — duplicate case, no further action.", popularity: 278 }, { id: 160, title: "property intellectual damages", description: "The order was updated after an incomplete check. The invoice was updated — late case, no further action. Flagged as routine. The courier confirmed the booking.", popularity: 561 }, { id: 161, title: "employment property fraud", description: null, popularity: 395 }, { id: 162, title: "tort settlement discrimination", description: "The session was rescheduled — unusual case, no further action. The claim was updated following a late review. The booking was rejected after an automatic check.", popularity: 602 }, { id: 163, title: "breach regulation", description: "The session was delayed after a manual check. No response from the customer, so the ticket was replaced. The report was confirmed following an unusual review.", popularity: 777 }, { id: 164, title: "rights arbitration", description: "An operator confirmed the details and the session was delayed. No response from the team, so the item was processed. Support reported an automatic issue; the invoice was processed.", popularity: null }, { id: 165, title: "tort", description: "The invoice was rejected — repeat case, no further action. The claim was rescheduled after an incomplete check. The item was rescheduled following a routine review.", popularity: 411 }, { id: 166, title: "arbitration dispute", description: "Flagged as incomplete. The account owner resolved the delivery. The supplier asked for a change and the item was completed. Support asked for a change and the invoice was processed.", popularity: 545 }, { id: 167, title: "arbitration", description: "Flagged as duplicate. The reviewer confirmed the booking. No response from support, so the shipment was resolved.", popularity: 539 }, { id: 168, title: "litigation compliance", description: "Flagged as incomplete. The account owner resolved the session. The supplier asked for a change and the payment was completed.", popularity: null }, { id: 169, title: "privacy regulation misrepresentation", description: "The refund was cancelled — automatic case, no further action. The ticket was closed — minor case, no further action.", popularity: 545 }, { id: 170, title: "tort liability", description: null, popularity: 342 }, { id: 171, title: "privacy", description: "A routine follow-up: the request was replaced. An operator confirmed the details and the request was updated. An incomplete follow-up: the claim was replaced. The ticket was resolved — unusual case, no further action.", popularity: 377 }, { id: 172, title: "tort compliance", description: "The report was refunded following an incomplete review. Flagged as duplicate. The team escalated the refund.", popularity: 809 }, { id: 173, title: "litigation", description: "The supplier asked for a change and the order was resolved. The payment was cancelled following a repeat review.", popularity: 406 }, { id: 174, title: "fraud", description: "The courier reported a repeat issue; the session was updated. The transfer was replaced following a manual review.", popularity: 490 }, { id: 175, title: "litigation breach", description: "Flagged as repeat. The supplier completed the record. The ticket was replaced following a repeat review. The shipment was replaced after an incomplete check. The booking was approved following a minor review.", popularity: null }, { id: 176, title: "property dispute tort", description: "An unusual booking was confirmed the same day. The order was reopened after a minor check. An operator confirmed the details and the shipment was rescheduled. The payment was refunded following an urgent review.", popularity: 746 }, { id: 177, title: "negligence", description: "The courier confirmed the details and the delivery was refunded. The refund was replaced after an urgent check. Support asked for a change and the payment was resolved. The delivery was refunded after a late check.", popularity: 426 }, { id: 178, title: "tort negligence employment", description: "The session was closed after a duplicate check. The customer reported an incomplete issue; the document was processed. No response from the supplier, so the document was reviewed. The booking was refunded after a late check.", popularity: 602 }, { id: 179, title: "breach compliance", description: "The reviewer reported an incomplete issue; the invoice was escalated. No response from support, so the order was replaced. The item was reviewed after a manual check. The invoice was processed — manual case, no further action.", popularity: 391 }, { id: 180, title: "employment liability", description: "The report was rejected after a duplicate check. The request was refunded after a routine check. The report was rejected — duplicate case, no further action. A routine refund was delayed the same day.", popularity: 554 }, { id: 181, title: "rights", description: "Flagged as repeat. The account owner delayed the request. A late follow-up: the record was updated. Flagged as incomplete. The customer confirmed the payment. A late follow-up: the claim was replaced.", popularity: 718 }, { id: 182, title: "liability", description: "The account owner reported an unusual issue; the booking was delayed. The claim was confirmed following a late review. The shipment was approved after an urgent check. A standard follow-up: the order was replaced.", popularity: 387 }, { id: 183, title: "arbitration regulation", description: "The shipment was rescheduled — minor case, no further action. Flagged as late. The courier resolved the delivery.", popularity: 602 }, { id: 184, title: "rights discrimination misrepresentation", description: "Flagged as standard. The supplier updated the claim. The team confirmed the details and the appointment was cancelled. The report was closed after an automatic check.", popularity: null }, { id: 185, title: "regulation discrimination", description: "The transfer was rescheduled after a routine check. The supplier asked for a change and the request was approved.", popularity: 228 }, { id: 186, title: "rights damages contract", description: "An urgent document was confirmed the same day. A repeat account was closed the same day. The document was completed — routine case, no further action.", popularity: 230 }, { id: 187, title: "tort employment compliance", description: "The supplier asked for a change and the item was refunded. The account owner confirmed the details and the booking was approved. An automatic booking was replaced the same day.", popularity: 287 }, { id: 188, title: "property", description: "The courier asked for a change and the item was rescheduled. The refund was escalated after a partial check.", popularity: 589 }, { id: 189, title: "litigation employment regulation", description: "An automatic follow-up: the item was rescheduled. A manual follow-up: the invoice was processed.", popularity: 401 }, { id: 190, title: "tort employment privacy", description: "A standard follow-up: the report was reopened. A minor follow-up: the delivery was refunded. The session was cancelled after a duplicate check. The claim was rescheduled following a routine review.", popularity: 449 }, { id: 191, title: "regulation", description: "The courier confirmed the details and the invoice was refunded. The record was completed following a duplicate review. The courier reported a standard issue; the record was confirmed. No response from the courier, so the item was replaced.", popularity: 713 }, { id: 192, title: "intellectual employment discrimination", description: "A duplicate refund was refunded the same day. The account owner asked for a change and the booking was reviewed. An incomplete claim was confirmed the same day. Flagged as automatic. The reviewer completed the document.", popularity: 564 }, { id: 193, title: "privacy misrepresentation", description: "An urgent follow-up: the order was closed. The team confirmed the details and the account was replaced. An operator asked for a change and the report was reviewed. Support confirmed the details and the invoice was updated.", popularity: 647 }, { id: 194, title: "damages", description: "An automatic follow-up: the request was delayed. An operator asked for a change and the booking was cancelled. The session was reviewed following a minor review. The refund was refunded after an incomplete check.", popularity: 474 }, { id: 195, title: "discrimination", description: "The team asked for a change and the ticket was reopened. Flagged as repeat. An operator reviewed the order.", popularity: 524 }, { id: 196, title: "negligence", description: "A duplicate appointment was replaced the same day. Flagged as partial. The customer cancelled the item. A repeat follow-up: the invoice was confirmed.", popularity: 521 }, { id: 197, title: "breach", description: "The customer reported a routine issue; the shipment was reopened. Flagged as urgent. The customer rejected the order. The appointment was closed following a routine review. The appointment was closed — incomplete case, no further action.", popularity: 552 }, { id: 198, title: "intellectual regulation", description: "The account was approved following an automatic review. An urgent follow-up: the request was replaced.", popularity: 379 }, { id: 199, title: "compliance dispute rights", description: null, popularity: 625 }, { id: 200, title: "discrimination", description: "The report was rejected — late case, no further action. An urgent item was refunded the same day. Flagged as repeat. An operator approved the refund.", popularity: 511 }, { id: 201, title: "dispute damages", description: null, popularity: 369 }, { id: 202, title: "settlement", description: "A manual transfer was updated the same day. The claim was approved following a standard review.", popularity: 723 }, { id: 203, title: "damages property liability", description: null, popularity: 395 }, { id: 204, title: "compliance", description: "A late follow-up: the record was rescheduled. The account was reopened following an automatic review. A manual follow-up: the account was updated.", popularity: 368 }, { id: 205, title: "regulation", description: "No response from the team, so the account was rejected. The account owner asked for a change and the order was escalated. The order was replaced — manual case, no further action. The request was escalated after a minor check.", popularity: 415 }, { id: 206, title: "tort privacy regulation", description: "The team confirmed the details and the invoice was replaced. An operator reported a late issue; the record was updated. The ticket was refunded — standard case, no further action. The courier reported an unusual issue; the invoice was updated.", popularity: 354 }, { id: 207, title: "liability", description: "The payment was replaced following a routine review. The account was closed after a late check.", popularity: 457 }, { id: 208, title: "contract compliance", description: "The team asked for a change and the item was cancelled. The claim was confirmed after a minor check. An urgent follow-up: the request was completed.", popularity: 467 }, { id: 209, title: "regulation contract", description: "The account was confirmed after a late check. The delivery was reviewed after a repeat check.", popularity: null }, { id: 210, title: "negligence misrepresentation breach", description: "Flagged as manual. The customer confirmed the record. The ticket was completed — urgent case, no further action.", popularity: 568 }, { id: 211, title: "negligence property breach", description: "An urgent shipment was resolved the same day. The reviewer confirmed the details and the refund was reviewed.", popularity: 397 }, { id: 212, title: "misrepresentation", description: null, popularity: null }, { id: 213, title: "intellectual", description: "A duplicate session was refunded the same day. The booking was escalated — partial case, no further action. The item was rejected — minor case, no further action. The booking was cancelled following a repeat review.", popularity: 773 }, { id: 214, title: "litigation", description: "Flagged as partial. The supplier closed the record. Support confirmed the details and the booking was replaced.", popularity: 508 }, { id: 215, title: "property employment damages", description: null, popularity: 335 }, { id: 216, title: "intellectual rights", description: "The customer reported an incomplete issue; the session was cancelled. The shipment was escalated following a manual review. The account owner asked for a change and the booking was refunded.", popularity: 384 }, { id: 217, title: "tort dispute", description: "The payment was closed — automatic case, no further action. An operator asked for a change and the order was processed. No response from the customer, so the invoice was delayed. Support reported a manual issue; the report was delayed.", popularity: null }, { id: 218, title: "contract arbitration", description: "The record was resolved after an urgent check. A standard record was processed the same day.", popularity: 511 }, { id: 219, title: "fraud", description: "The payment was escalated — minor case, no further action. No response from an operator, so the refund was rejected. Flagged as partial. The supplier cancelled the transfer. Flagged as urgent. An operator confirmed the appointment.", popularity: 486 }, { id: 220, title: "settlement", description: "A minor follow-up: the claim was updated. The item was reviewed after a late check. The reviewer reported a late issue; the session was approved. The supplier reported an urgent issue; the record was updated.", popularity: 565 }, { id: 221, title: "intellectual fraud negligence", description: "The item was completed following a late review. The item was refunded after a duplicate check.", popularity: null }, { id: 222, title: "negligence property contract", description: "An automatic ticket was delayed the same day. The account was rejected — duplicate case, no further action. No response from the customer, so the ticket was reviewed. The reviewer reported an urgent issue; the delivery was updated.", popularity: 695 }, { id: 223, title: "discrimination contract", description: "Flagged as standard. The team resolved the order. No response from the reviewer, so the refund was confirmed. The reviewer confirmed the details and the claim was cancelled. A duplicate account was escalated the same day.", popularity: 668 }, { id: 224, title: "contract regulation settlement", description: null, popularity: 350 }, { id: 225, title: "regulation rights tort", description: "A manual follow-up: the booking was rescheduled. The ticket was delayed after a routine check.", popularity: 576 }, { id: 226, title: "tort arbitration discrimination", description: "Flagged as duplicate. Support closed the delivery. The reviewer reported an incomplete issue; the request was resolved. The report was rescheduled — manual case, no further action. The item was resolved after an urgent check.", popularity: 473 }, { id: 227, title: "dispute", description: "The item was escalated — unusual case, no further action. Flagged as partial. The courier delayed the delivery. The appointment was confirmed following a partial review.", popularity: 635 }, { id: 228, title: "tort settlement", description: "The customer asked for a change and the transfer was delayed. The order was confirmed after a minor check. Support reported a routine issue; the record was refunded. The team asked for a change and the transfer was processed.", popularity: 578 }, { id: 229, title: "property damages", description: "The claim was escalated after an urgent check. The supplier reported a manual issue; the transfer was closed. Flagged as standard. The customer processed the document.", popularity: 373 }, { id: 230, title: "misrepresentation regulation", description: "The order was delayed following an unusual review. A repeat ticket was completed the same day. An operator reported an unusual issue; the record was closed. The customer confirmed the details and the account was reopened.", popularity: 609 }, { id: 231, title: "breach arbitration compliance", description: "Flagged as urgent. Support replaced the booking. The record was replaced after an unusual check. The customer confirmed the details and the session was escalated.", popularity: 347 }, { id: 232, title: "property arbitration damages", description: "The request was cancelled following a partial review. The courier asked for a change and the shipment was confirmed. The request was approved after a repeat check. The document was reopened following an automatic review.", popularity: 669 }, { id: 233, title: "fraud property", description: "The reviewer reported a manual issue; the request was cancelled. The report was closed — minor case, no further action. The supplier reported an automatic issue; the transfer was reviewed. The supplier reported an incomplete issue; the record was approved.", popularity: 631 }, { id: 234, title: "fraud litigation breach", description: "The courier asked for a change and the payment was confirmed. A repeat follow-up: the invoice was closed. Flagged as standard. The account owner confirmed the request.", popularity: 314 }, { id: 235, title: "discrimination", description: "A late follow-up: the report was delayed. The team reported a repeat issue; the record was confirmed.", popularity: 420 }, { id: 236, title: "rights", description: "Support confirmed the details and the order was confirmed. The invoice was reviewed after an incomplete check.", popularity: 461 }, { id: 237, title: "negligence dispute property", description: "The customer reported an urgent issue; the item was approved. Flagged as manual. The team reviewed the delivery.", popularity: 639 }, { id: 238, title: "settlement dispute compliance", description: "Flagged as unusual. The account owner resolved the claim. No response from the reviewer, so the account was completed.", popularity: 573 }, { id: 239, title: "damages", description: "The account owner asked for a change and the refund was rescheduled. The claim was refunded following a duplicate review. The account was rejected following an incomplete review.", popularity: 531 }, { id: 240, title: "liability misrepresentation fraud", description: "The item was replaced — urgent case, no further action. The team asked for a change and the order was updated. An operator reported a standard issue; the invoice was completed. The account owner confirmed the details and the record was updated.", popularity: 409 }, { id: 241, title: "property contract", description: "The supplier asked for a change and the payment was rescheduled. A routine refund was replaced the same day.", popularity: 550 }, { id: 242, title: "litigation rights tort", description: "The appointment was rejected — minor case, no further action. The reviewer reported a standard issue; the payment was updated. The reviewer asked for a change and the invoice was updated. No response from the account owner, so the order was processed.", popularity: 227 }, { id: 243, title: "liability employment arbitration", description: "The account owner asked for a change and the invoice was rejected. No response from the courier, so the invoice was updated. The order was completed following an automatic review.", popularity: 536 }, { id: 244, title: "fraud misrepresentation", description: "The account owner confirmed the details and the appointment was delayed. The claim was refunded after a repeat check. The reviewer reported a repeat issue; the transfer was replaced.", popularity: 548 }, { id: 245, title: "property", description: "Flagged as urgent. An operator approved the booking. The ticket was cancelled — duplicate case, no further action. The record was updated following a duplicate review. A late appointment was rescheduled the same day.", popularity: 270 }, { id: 246, title: "dispute regulation property", description: "The appointment was reopened following a late review. A standard item was reopened the same day.", popularity: 500 }, { id: 247, title: "damages employment privacy", description: "A partial shipment was rejected the same day. The report was reviewed following a manual review. The account was reviewed — manual case, no further action. The record was confirmed after an automatic check.", popularity: 629 }, { id: 248, title: "discrimination", description: "A minor follow-up: the document was updated. The delivery was updated after an urgent check.", popularity: 407 }, { id: 249, title: "compliance", description: "An operator asked for a change and the record was resolved. Flagged as duplicate. An operator cancelled the appointment. The transfer was refunded — late case, no further action.", popularity: 651 }, { id: 250, title: "privacy", description: "The delivery was cancelled — routine case, no further action. The account owner confirmed the details and the delivery was refunded. Flagged as unusual. The account owner approved the shipment.", popularity: 478 }, { id: 251, title: "dispute contract tort", description: "The supplier confirmed the details and the shipment was resolved. A partial follow-up: the item was resolved. The order was rescheduled following an automatic review.", popularity: 354 }, { id: 252, title: "litigation damages fraud", description: "A routine follow-up: the invoice was completed. An incomplete follow-up: the document was closed. A partial follow-up: the item was approved.", popularity: 611 }, { id: 253, title: "damages negligence contract", description: "A minor follow-up: the claim was refunded. The supplier reported a partial issue; the session was replaced. The appointment was replaced following a repeat review. The transfer was processed after a late check.", popularity: 707 }, { id: 254, title: "dispute intellectual", description: "The refund was cancelled after a manual check. The session was rescheduled following a late review.", popularity: 404 }, { id: 255, title: "damages dispute discrimination", description: "Flagged as duplicate. The courier confirmed the appointment. Support reported a repeat issue; the report was replaced. The claim was closed following a partial review.", popularity: 385 }, { id: 256, title: "damages breach", description: "A repeat report was resolved the same day. The order was reviewed after a duplicate check. The invoice was confirmed — incomplete case, no further action.", popularity: 339 }, { id: 257, title: "fraud discrimination", description: null, popularity: 620 }, { id: 258, title: "arbitration intellectual employment", description: "The item was processed after a late check. No response from the team, so the transfer was resolved.", popularity: 518 }, { id: 259, title: "negligence compliance dispute", description: "The team asked for a change and the record was replaced. The shipment was escalated after an automatic check. The team reported a minor issue; the account was escalated. The refund was escalated — late case, no further action.", popularity: 489 }, { id: 260, title: "regulation rights misrepresentation", description: "The session was processed following a minor review. No response from an operator, so the payment was replaced. A routine record was cancelled the same day. A standard follow-up: the invoice was reopened.", popularity: 298 }, { id: 261, title: "dispute privacy litigation", description: "The appointment was approved after a repeat check. The account owner reported a repeat issue; the record was rejected. The account owner confirmed the details and the record was cancelled. An automatic shipment was closed the same day.", popularity: 775 }, { id: 262, title: "arbitration regulation negligence", description: "The account was cancelled — unusual case, no further action. The claim was closed after a routine check.", popularity: null }, { id: 263, title: "liability", description: "The courier reported an unusual issue; the ticket was completed. A minor refund was refunded the same day. An urgent follow-up: the transfer was approved.", popularity: 705 }, { id: 264, title: "damages rights", description: "The order was delayed — late case, no further action. An operator asked for a change and the refund was confirmed. No response from the team, so the document was closed. A late report was closed the same day.", popularity: 724 }, { id: 265, title: "privacy breach", description: "The document was resolved — standard case, no further action. An unusual follow-up: the report was rescheduled. Flagged as late. An operator confirmed the shipment.", popularity: 588 }, { id: 266, title: "settlement breach dispute", description: "The team reported a late issue; the refund was resolved. An automatic follow-up: the appointment was delayed. A manual follow-up: the shipment was confirmed.", popularity: null }, { id: 267, title: "tort liability", description: "The courier reported a late issue; the claim was processed. Flagged as incomplete. The courier rejected the report. An operator asked for a change and the item was closed.", popularity: 181 }, { id: 268, title: "regulation dispute", description: "The customer asked for a change and the account was escalated. A minor booking was replaced the same day.", popularity: null }, { id: 269, title: "misrepresentation contract compliance", description: "A minor follow-up: the session was confirmed. No response from the reviewer, so the delivery was reopened.", popularity: 318 }, { id: 270, title: "arbitration settlement intellectual", description: "An incomplete follow-up: the transfer was closed. The reviewer asked for a change and the booking was cancelled.", popularity: 570 }, { id: 271, title: "contract tort discrimination", description: "The customer confirmed the details and the order was refunded. No response from the reviewer, so the shipment was rescheduled.", popularity: 445 }, { id: 272, title: "property liability misrepresentation", description: "The supplier reported a repeat issue; the shipment was processed. The account was replaced after an urgent check.", popularity: 563 }, { id: 273, title: "regulation", description: "The item was delayed — late case, no further action. An incomplete ticket was approved the same day. Flagged as automatic. An operator delayed the booking.", popularity: 569 }, { id: 274, title: "intellectual litigation breach", description: "A minor follow-up: the invoice was reviewed. Support asked for a change and the refund was updated. The transfer was replaced after a minor check. Support asked for a change and the ticket was escalated.", popularity: 667 }, { id: 275, title: "intellectual property", description: "The payment was cancelled following a standard review. No response from support, so the session was refunded.", popularity: 500 }, { id: 276, title: "arbitration property breach", description: "An operator asked for a change and the claim was refunded. The refund was refunded following a manual review. The shipment was escalated after a partial check. The team confirmed the details and the delivery was cancelled.", popularity: 616 }, { id: 277, title: "misrepresentation", description: "A routine follow-up: the payment was confirmed. The booking was refunded after an automatic check. The reviewer confirmed the details and the record was rejected. The payment was replaced following a minor review.", popularity: 553 }, { id: 278, title: "liability discrimination", description: null, popularity: 418 }, { id: 279, title: "damages liability", description: "A standard booking was approved the same day. An unusual delivery was reviewed the same day.", popularity: null }, { id: 280, title: "privacy", description: "A partial refund was confirmed the same day. The reviewer reported a minor issue; the account was resolved. Flagged as minor. The reviewer closed the shipment. Flagged as duplicate. Support cancelled the refund.", popularity: 748 }, { id: 281, title: "contract privacy", description: "A late appointment was completed the same day. No response from the courier, so the report was completed.", popularity: 569 }, { id: 282, title: "dispute misrepresentation", description: "A duplicate follow-up: the request was replaced. The claim was rescheduled following an automatic review. The booking was reopened following a manual review.", popularity: 615 }, { id: 283, title: "arbitration settlement employment", description: "The order was escalated — routine case, no further action. An unusual follow-up: the session was refunded. The order was closed — urgent case, no further action. A standard follow-up: the request was processed.", popularity: 188 }, { id: 284, title: "arbitration", description: "The team reported a manual issue; the appointment was updated. An urgent follow-up: the invoice was cancelled. A partial transfer was resolved the same day.", popularity: 198 }, { id: 285, title: "arbitration intellectual", description: null, popularity: 571 }, { id: 286, title: "negligence compliance dispute", description: "Support reported an automatic issue; the order was completed. The payment was replaced after an unusual check. The team confirmed the details and the document was confirmed.", popularity: 562 }, { id: 287, title: "litigation regulation", description: "No response from the supplier, so the account was escalated. The request was approved after an unusual check.", popularity: null }, { id: 288, title: "liability compliance", description: "A minor ticket was refunded the same day. Flagged as unusual. The team refunded the claim. The customer reported a repeat issue; the delivery was processed. The account owner reported a duplicate issue; the request was closed.", popularity: 375 }, { id: 289, title: "tort", description: "The item was processed following a routine review. The supplier confirmed the details and the claim was rejected. An operator reported an unusual issue; the record was refunded.", popularity: 507 }, { id: 290, title: "dispute", description: "A routine shipment was rejected the same day. Flagged as manual. The team rescheduled the session.", popularity: 616 }, { id: 291, title: "negligence property", description: "No response from the reviewer, so the document was processed. The refund was closed after a partial check. No response from the account owner, so the session was closed.", popularity: 382 }, { id: 292, title: "settlement", description: "No response from an operator, so the order was refunded. The customer reported a minor issue; the payment was closed. The courier reported a duplicate issue; the record was rescheduled.", popularity: 478 }, { id: 293, title: "liability rights damages", description: "No response from the reviewer, so the record was replaced. A standard shipment was replaced the same day.", popularity: 272 }, { id: 294, title: "dispute", description: "The supplier reported a late issue; the appointment was replaced. The shipment was completed after a routine check.", popularity: 412 }, { id: 295, title: "compliance", description: "The team asked for a change and the payment was cancelled. The payment was processed after a standard check.", popularity: 765 }, { id: 296, title: "fraud", description: "Support confirmed the details and the appointment was updated. The request was replaced after a manual check. No response from the courier, so the report was approved.", popularity: 432 }, { id: 297, title: "employment intellectual breach", description: "The appointment was rescheduled after a routine check. The reviewer reported a manual issue; the claim was confirmed. Flagged as manual. An operator closed the order.", popularity: 336 }, { id: 298, title: "tort", description: null, popularity: null }, { id: 299, title: "employment liability", description: "An unusual delivery was reopened the same day. An incomplete report was delayed the same day.", popularity: 807 }, { id: 300, title: "compliance fraud", description: "The invoice was delayed following an unusual review. The session was processed after an unusual check.", popularity: 327 }, ], }); await prisma.jurisdictions.createMany({ data: [ { id: 1, name: "magistrate local", legal_topic_id: 125, population: 3633297, area_size: "243089.00" }, { id: 2, name: "commission territorial magistrate", legal_topic_id: 234, population: 5966628, area_size: "215281.42" }, { id: 3, name: null, legal_topic_id: 84, population: 3881343, area_size: "193867.06" }, { id: 4, name: "county", legal_topic_id: 127, population: 7256808, area_size: "203970.15" }, { id: 5, name: "international", legal_topic_id: 206, population: 3963430, area_size: "311396.95" }, { id: 6, name: "board", legal_topic_id: 243, population: 3839600, area_size: "243909.01" }, { id: 7, name: null, legal_topic_id: 224, population: 6844374, area_size: "236493.45" }, { id: 8, name: "appellate", legal_topic_id: 246, population: 2943803, area_size: "186400.72" }, { id: 9, name: "municipal regional state", legal_topic_id: 36, population: 5579161, area_size: "211569.67" }, { id: 10, name: "local magistrate commission", legal_topic_id: 236, population: 2257881, area_size: "259603.58" }, { id: 11, name: "district administrative", legal_topic_id: 199, population: 5518702, area_size: "211332.42" }, { id: 12, name: "circuit", legal_topic_id: 14, population: 4001206, area_size: "313524.62" }, { id: 13, name: null, legal_topic_id: 38, population: 3495407, area_size: "420465.71" }, { id: 14, name: "superior state district", legal_topic_id: 54, population: 2606984, area_size: "308483.50" }, { id: 15, name: "territorial", legal_topic_id: 240, population: 4483347, area_size: "185189.64" }, { id: 16, name: "local", legal_topic_id: 103, population: 5078507, area_size: "226828.09" }, { id: 17, name: "board", legal_topic_id: 89, population: 4137040, area_size: "271296.28" }, { id: 18, name: "supreme municipal", legal_topic_id: 65, population: 3348636, area_size: "375289.00" }, { id: 19, name: "local administrative", legal_topic_id: 215, population: 5901481, area_size: "305497.26" }, { id: 20, name: "regional appellate superior", legal_topic_id: 103, population: 4260015, area_size: "242636.78" }, { id: 21, name: "district administrative", legal_topic_id: 35, population: 2498624, area_size: "144924.02" }, { id: 22, name: "supreme", legal_topic_id: 205, population: 3791324, area_size: "257866.58" }, { id: 23, name: "local county federal", legal_topic_id: 199, population: 7204416, area_size: "288671.54" }, { id: 24, name: "state tribal", legal_topic_id: 236, population: 3401001, area_size: "134515.07" }, { id: 25, name: "federal state circuit", legal_topic_id: 219, population: 6090877, area_size: "162539.36" }, { id: 26, name: null, legal_topic_id: 269, population: 2798890, area_size: "262034.39" }, { id: 27, name: "local magistrate", legal_topic_id: 291, population: 3336622, area_size: "333704.80" }, { id: 28, name: "circuit", legal_topic_id: 269, population: 4162443, area_size: "236443.84" }, { id: 29, name: "appellate territorial county", legal_topic_id: 274, population: 8451598, area_size: "253192.10" }, { id: 30, name: "district local county", legal_topic_id: 186, population: 5995636, area_size: "144532.90" }, { id: 31, name: "commission county", legal_topic_id: 283, population: 5429408, area_size: "256093.69" }, { id: 32, name: "magistrate", legal_topic_id: 297, population: 5315914, area_size: "259648.83" }, { id: 33, name: "county tribal", legal_topic_id: 107, population: 6152219, area_size: "375292.21" }, { id: 34, name: "local", legal_topic_id: 198, population: 7148515, area_size: "181780.87" }, { id: 35, name: "board supreme commonwealth", legal_topic_id: 34, population: 5304079, area_size: "172266.17" }, { id: 36, name: "county", legal_topic_id: 233, population: 6413141, area_size: "403046.38" }, { id: 37, name: "tribal commission", legal_topic_id: 254, population: 4972771, area_size: "181651.57" }, { id: 38, name: "appellate regional territorial", legal_topic_id: 71, population: 5890665, area_size: "420916.73" }, { id: 39, name: "territorial magistrate", legal_topic_id: 85, population: 3745780, area_size: "320687.39" }, { id: 40, name: "state county", legal_topic_id: 159, population: 7135175, area_size: "341816.71" }, { id: 41, name: "county", legal_topic_id: 16, population: 4212084, area_size: "162102.90" }, { id: 42, name: "appellate tribal", legal_topic_id: 27, population: 5974954, area_size: "268768.17" }, { id: 43, name: "state", legal_topic_id: 118, population: 4085096, area_size: "352157.54" }, { id: 44, name: "federal commission district", legal_topic_id: 269, population: 4029227, area_size: "230756.14" }, { id: 45, name: "administrative local court", legal_topic_id: 114, population: 4002154, area_size: "217817.86" }, { id: 46, name: "appellate court", legal_topic_id: 14, population: 2725525, area_size: "205699.81" }, { id: 47, name: null, legal_topic_id: 20, population: 4998878, area_size: "336453.16" }, { id: 48, name: "administrative appellate court", legal_topic_id: 193, population: 4671797, area_size: "337152.66" }, { id: 49, name: "county", legal_topic_id: 42, population: 7430454, area_size: "262790.49" }, { id: 50, name: "tribal territorial", legal_topic_id: 174, population: 3528694, area_size: "301538.79" }, { id: 51, name: "territorial", legal_topic_id: 114, population: 5697385, area_size: "342819.92" }, { id: 52, name: "district territorial commission", legal_topic_id: 47, population: 4355705, area_size: "289464.99" }, { id: 53, name: "international supreme circuit", legal_topic_id: 104, population: 4920126, area_size: "233075.04" }, { id: 54, name: "county", legal_topic_id: 30, population: 6405811, area_size: "261733.38" }, { id: 55, name: null, legal_topic_id: 110, population: 4834638, area_size: "360464.94" }, { id: 56, name: null, legal_topic_id: 218, population: 6089195, area_size: "266108.28" }, { id: 57, name: "appellate county", legal_topic_id: 180, population: 3358064, area_size: "354604.94" }, { id: 58, name: "commission", legal_topic_id: 71, population: 3729519, area_size: "276815.85" }, { id: 59, name: "federal municipal", legal_topic_id: 204, population: 4085928, area_size: "305417.51" }, { id: 60, name: "territorial appellate", legal_topic_id: 221, population: 5337072, area_size: "141607.95" }, { id: 61, name: "commission superior circuit", legal_topic_id: 141, population: 4304223, area_size: "273116.71" }, { id: 62, name: "agency", legal_topic_id: 143, population: 6368459, area_size: "285225.40" }, { id: 63, name: null, legal_topic_id: 63, population: 5610173, area_size: "123212.59" }, { id: 64, name: "superior commonwealth", legal_topic_id: 72, population: 2959243, area_size: "247685.40" }, { id: 65, name: null, legal_topic_id: 249, population: 4731638, area_size: "301122.84" }, { id: 66, name: "international county magistrate", legal_topic_id: 204, population: 3060036, area_size: "404520.36" }, { id: 67, name: null, legal_topic_id: 29, population: 4272248, area_size: "150296.87" }, { id: 68, name: "superior commission", legal_topic_id: 175, population: 5933123, area_size: "245982.58" }, { id: 69, name: "international appellate", legal_topic_id: 140, population: 3537456, area_size: "122731.43" }, { id: 70, name: "federal", legal_topic_id: 238, population: 5216465, area_size: "98060.83" }, { id: 71, name: null, legal_topic_id: 109, population: 5947655, area_size: "275027.67" }, { id: 72, name: null, legal_topic_id: 237, population: 6132044, area_size: "369526.23" }, { id: 73, name: "district commission", legal_topic_id: 41, population: 4488503, area_size: "241880.19" }, { id: 74, name: "commonwealth federal", legal_topic_id: 113, population: 4646396, area_size: "312623.32" }, { id: 75, name: "superior", legal_topic_id: 61, population: 4199735, area_size: "182737.81" }, { id: 76, name: "commission commonwealth international", legal_topic_id: 238, population: 2444956, area_size: "334240.27" }, { id: 77, name: "circuit commonwealth", legal_topic_id: 212, population: 3629678, area_size: "226749.10" }, { id: 78, name: "federal district regional", legal_topic_id: 109, population: 6646792, area_size: "106850.95" }, { id: 79, name: "district magistrate commonwealth", legal_topic_id: 209, population: 4824410, area_size: "220816.90" }, { id: 80, name: "district appellate", legal_topic_id: 50, population: 3316701, area_size: "248725.12" }, { id: 81, name: "commonwealth", legal_topic_id: 287, population: 3947258, area_size: "341745.46" }, { id: 82, name: "municipal administrative", legal_topic_id: 57, population: 4728345, area_size: "283724.13" }, { id: 83, name: "circuit commission state", legal_topic_id: 198, population: 5991779, area_size: "341838.75" }, { id: 84, name: "board court", legal_topic_id: 126, population: 3771621, area_size: "271666.39" }, { id: 85, name: "municipal", legal_topic_id: 7, population: 6118234, area_size: "198357.50" }, { id: 86, name: "appellate federal agency", legal_topic_id: 71, population: 3424092, area_size: "274210.23" }, { id: 87, name: "district", legal_topic_id: 76, population: 4614840, area_size: "405810.55" }, { id: 88, name: "commonwealth tribal appellate", legal_topic_id: 159, population: 4932125, area_size: "116290.71" }, { id: 89, name: "local commission board", legal_topic_id: 247, population: 6645822, area_size: "399144.42" }, { id: 90, name: "commonwealth board", legal_topic_id: 81, population: 6521145, area_size: "237130.52" }, { id: 91, name: "international", legal_topic_id: 210, population: 7870177, area_size: "176680.08" }, { id: 92, name: "territorial court board", legal_topic_id: 105, population: 7094541, area_size: "220219.19" }, { id: 93, name: "tribal", legal_topic_id: 82, population: 3579472, area_size: "208846.56" }, { id: 94, name: null, legal_topic_id: 62, population: 2699317, area_size: "332826.19" }, { id: 95, name: "tribal commission", legal_topic_id: 36, population: 6129628, area_size: "250214.62" }, { id: 96, name: "district superior", legal_topic_id: 13, population: 4637831, area_size: "294363.61" }, { id: 97, name: "supreme magistrate commonwealth", legal_topic_id: 121, population: 3465273, area_size: "219238.61" }, { id: 98, name: "magistrate federal", legal_topic_id: 262, population: 5833309, area_size: "283222.77" }, { id: 99, name: null, legal_topic_id: 265, population: 7348045, area_size: "256145.74" }, { id: 100, name: "international", legal_topic_id: 275, population: 1759612, area_size: "258211.41" }, { id: 101, name: "administrative", legal_topic_id: 162, population: 2341074, area_size: "149304.72" }, { id: 102, name: "municipal", legal_topic_id: 241, population: 5165437, area_size: "320873.22" }, { id: 103, name: "territorial", legal_topic_id: 186, population: 1996038, area_size: "238853.84" }, { id: 104, name: "circuit court", legal_topic_id: 175, population: 6254252, area_size: "26115.88" }, { id: 105, name: "state federal", legal_topic_id: 77, population: 6043297, area_size: "181521.96" }, { id: 106, name: "federal court appellate", legal_topic_id: 298, population: 6016441, area_size: "255227.14" }, { id: 107, name: "court administrative", legal_topic_id: 23, population: 5025476, area_size: "279494.17" }, { id: 108, name: "supreme county municipal", legal_topic_id: 297, population: 4896265, area_size: "194321.15" }, { id: 109, name: "administrative magistrate", legal_topic_id: 92, population: 4325758, area_size: "97212.08" }, { id: 110, name: "district circuit", legal_topic_id: 250, population: 5282209, area_size: "222826.06" }, { id: 111, name: "tribal", legal_topic_id: 240, population: 7437988, area_size: "354678.85" }, { id: 112, name: "municipal tribal", legal_topic_id: 223, population: 7809996, area_size: "169190.56" }, { id: 113, name: null, legal_topic_id: 52, population: 6787398, area_size: "242515.84" }, { id: 114, name: "local commonwealth tribal", legal_topic_id: 275, population: 5279143, area_size: "312805.63" }, { id: 115, name: "district state", legal_topic_id: 107, population: 5752318, area_size: "281549.22" }, { id: 116, name: "federal municipal state", legal_topic_id: 231, population: 4620149, area_size: "296233.91" }, { id: 117, name: null, legal_topic_id: 50, population: 6884959, area_size: "194677.41" }, { id: 118, name: "superior", legal_topic_id: 122, population: 3298305, area_size: "285179.84" }, { id: 119, name: "state", legal_topic_id: 26, population: 3701594, area_size: "252868.45" }, { id: 120, name: "district", legal_topic_id: 194, population: 3164066, area_size: "173481.34" }, { id: 121, name: "commission state supreme", legal_topic_id: 79, population: 6051195, area_size: "188823.99" }, { id: 122, name: "board local", legal_topic_id: 245, population: 3613966, area_size: "297934.38" }, { id: 123, name: "magistrate supreme", legal_topic_id: 207, population: 4901364, area_size: "254571.85" }, { id: 124, name: "district", legal_topic_id: 110, population: 5223815, area_size: "295853.41" }, { id: 125, name: "regional county commonwealth", legal_topic_id: 273, population: 3756909, area_size: "126544.43" }, { id: 126, name: "magistrate municipal tribal", legal_topic_id: 102, population: 5416672, area_size: "217811.23" }, { id: 127, name: "circuit regional", legal_topic_id: 254, population: 5956891, area_size: "247696.67" }, { id: 128, name: "superior circuit", legal_topic_id: 221, population: 6649936, area_size: "284024.46" }, { id: 129, name: "appellate circuit", legal_topic_id: 91, population: 4088872, area_size: "324309.05" }, { id: 130, name: "board", legal_topic_id: 175, population: 5029781, area_size: "185808.53" }, { id: 131, name: "appellate international administrative", legal_topic_id: 269, population: 3820742, area_size: "178760.27" }, { id: 132, name: "supreme state tribal", legal_topic_id: 228, population: 4059235, area_size: "300797.29" }, { id: 133, name: "commonwealth", legal_topic_id: 153, population: 3679358, area_size: "144000.65" }, { id: 134, name: "tribal state commonwealth", legal_topic_id: 287, population: 5459049, area_size: "374751.58" }, { id: 135, name: "district agency", legal_topic_id: 240, population: 5334691, area_size: "249504.55" }, { id: 136, name: "state administrative commission", legal_topic_id: 61, population: 6071312, area_size: "328458.39" }, { id: 137, name: "district", legal_topic_id: 284, population: 4145710, area_size: "315607.96" }, { id: 138, name: "international county", legal_topic_id: 233, population: 5860210, area_size: "267890.90" }, { id: 139, name: "local", legal_topic_id: 151, population: 2279988, area_size: "239124.01" }, { id: 140, name: "administrative board", legal_topic_id: 273, population: 8502719, area_size: "219856.45" }, { id: 141, name: "court", legal_topic_id: 108, population: 6018539, area_size: "191603.23" }, { id: 142, name: "local", legal_topic_id: 285, population: 3676031, area_size: "246445.12" }, { id: 143, name: "court superior appellate", legal_topic_id: 197, population: 8740912, area_size: "323132.48" }, { id: 144, name: "board", legal_topic_id: 114, population: 3930195, area_size: "204054.22" }, { id: 145, name: "county", legal_topic_id: 99, population: 5720909, area_size: "294154.00" }, { id: 146, name: "state", legal_topic_id: 176, population: 4935331, area_size: "437895.93" }, { id: 147, name: "magistrate court international", legal_topic_id: 87, population: 4455114, area_size: "183541.34" }, { id: 148, name: null, legal_topic_id: 267, population: 6409935, area_size: "286064.97" }, { id: 149, name: "state commission", legal_topic_id: 68, population: 3145350, area_size: "317709.79" }, { id: 150, name: "tribal district federal", legal_topic_id: 191, population: 5110176, area_size: "181514.92" }, ], }); await prisma.case_opinions.createMany({ data: [ { id: 1, case_number: "No", jurisdiction_id: 113, opinion_text: "A routine appointment was confirmed the same day. A repeat shipment was resolved the same day. The reviewer confirmed the details and the shipment was rejected.", date: "2011-11-18" }, { id: 2, case_number: "002", jurisdiction_id: 140, opinion_text: "The refund was reopened following a partial review. An unusual refund was processed the same day. The appointment was cancelled after a routine check. No response from the account owner, so the request was cancelled.", date: "2016-01-25" }, { id: 3, case_number: "Docket 123", jurisdiction_id: 143, opinion_text: "The customer asked for a change and the request was updated. The shipment was approved after a manual check. No response from the supplier, so the transfer was rejected. An incomplete follow-up: the account was delayed.", date: "2011-03-17" }, { id: 4, case_number: "789 R", jurisdiction_id: 142, opinion_text: "An incomplete shipment was resolved the same day. The courier reported a routine issue; the refund was completed.", date: "2001-12-27" }, { id: 5, case_number: "002", jurisdiction_id: 137, opinion_text: "The account owner asked for a change and the ticket was replaced. The request was rescheduled after an unusual check. A manual item was cancelled the same day. The session was delayed following a minor review.", date: "2014-08-17" }, { id: 6, case_number: "123 CR", jurisdiction_id: 88, opinion_text: "A duplicate shipment was rescheduled the same day. Support confirmed the details and the invoice was escalated.", date: "2010-11-09" }, { id: 7, case_number: "S No", jurisdiction_id: 64, opinion_text: "The request was closed following a manual review. The team reported a late issue; the item was cancelled.", date: "2012-07-11" }, { id: 8, case_number: "001", jurisdiction_id: 39, opinion_text: null, date: "2016-10-07" }, { id: 9, case_number: "No X Z", jurisdiction_id: 79, opinion_text: "The refund was closed — late case, no further action. A late follow-up: the delivery was escalated. Support asked for a change and the booking was completed. An incomplete follow-up: the request was cancelled.", date: "2017-04-02" }, { id: 10, case_number: "001", jurisdiction_id: 67, opinion_text: "The reviewer confirmed the details and the request was cancelled. An automatic payment was rescheduled the same day. No response from the supplier, so the refund was delayed.", date: "2023-07-11" }, { id: 11, case_number: "R 123", jurisdiction_id: 42, opinion_text: "The customer confirmed the details and the delivery was refunded. A duplicate shipment was cancelled the same day. A partial follow-up: the delivery was refunded. The session was confirmed following a standard review.", date: "2005-02-22" }, { id: 12, case_number: "S A", jurisdiction_id: 36, opinion_text: "Flagged as routine. An operator updated the session. A standard follow-up: the refund was replaced. Flagged as manual. An operator rescheduled the refund. The account owner confirmed the details and the payment was processed.", date: "2015-10-29" }, { id: 13, case_number: "2023 002 CV", jurisdiction_id: 102, opinion_text: "The ticket was escalated after a minor check. A late follow-up: the document was rejected. Flagged as urgent. The courier reopened the refund.", date: "2012-05-12" }, { id: 14, case_number: "T", jurisdiction_id: 146, opinion_text: "An operator reported a partial issue; the shipment was reviewed. A manual document was rejected the same day. No response from support, so the item was closed.", date: "2018-12-05" }, { id: 15, case_number: "B Z", jurisdiction_id: 32, opinion_text: "Flagged as minor. The supplier rejected the delivery. The ticket was rejected — routine case, no further action.", date: "2022-03-31" }, { id: 16, case_number: "X 003", jurisdiction_id: 67, opinion_text: "No response from an operator, so the payment was completed. No response from the supplier, so the order was completed.", date: "2013-06-02" }, { id: 17, case_number: "Z CR 123", jurisdiction_id: 148, opinion_text: "A routine refund was closed the same day. The claim was delayed following a repeat review. Flagged as partial. The reviewer updated the payment.", date: "2001-03-14" }, { id: 18, case_number: "CV 789 A", jurisdiction_id: 83, opinion_text: "The team reported a standard issue; the appointment was completed. A partial ticket was reviewed the same day.", date: "2006-01-17" }, { id: 19, case_number: "Y CR", jurisdiction_id: 115, opinion_text: "The record was processed — duplicate case, no further action. Flagged as routine. Support processed the appointment. The order was resolved — minor case, no further action.", date: "2008-01-10" }, { id: 20, case_number: "Y 003 2023", jurisdiction_id: 74, opinion_text: "The shipment was reviewed following a minor review. The record was updated following an incomplete review. The payment was rejected — manual case, no further action.", date: "2023-08-01" }, { id: 21, case_number: "456", jurisdiction_id: 115, opinion_text: "Support confirmed the details and the report was replaced. The item was reviewed after an unusual check. The claim was closed following a late review.", date: "2004-12-07" }, { id: 22, case_number: "CR 789 T", jurisdiction_id: 131, opinion_text: "The supplier asked for a change and the refund was rejected. The account was delayed following a minor review. The session was delayed following a duplicate review.", date: "2023-01-31" }, { id: 23, case_number: "CR C T", jurisdiction_id: 71, opinion_text: "The reviewer confirmed the details and the request was processed. The account owner asked for a change and the shipment was delayed.", date: "2003-06-02" }, { id: 24, case_number: "123", jurisdiction_id: 37, opinion_text: "The request was cancelled — urgent case, no further action. The report was replaced after a partial check. Flagged as duplicate. The supplier escalated the shipment.", date: "2020-12-26" }, { id: 25, case_number: "Docket", jurisdiction_id: 107, opinion_text: "The appointment was rejected — repeat case, no further action. The document was rejected following a repeat review.", date: "2005-02-02" }, { id: 26, case_number: "CV 001 T", jurisdiction_id: 53, opinion_text: "An incomplete follow-up: the report was rescheduled. The ticket was reopened — partial case, no further action.", date: "2018-01-30" }, { id: 27, case_number: "002", jurisdiction_id: 67, opinion_text: "No response from the team, so the request was approved. The courier confirmed the details and the report was rescheduled. The invoice was closed after a routine check. The ticket was updated — manual case, no further action.", date: "2011-11-23" }, { id: 28, case_number: "2023 R", jurisdiction_id: 9, opinion_text: "The transfer was reopened following a repeat review. The request was resolved — routine case, no further action. A minor follow-up: the order was resolved.", date: "2017-04-06" }, { id: 29, case_number: "CV", jurisdiction_id: 2, opinion_text: "An operator confirmed the details and the session was resolved. The account owner reported a minor issue; the transfer was replaced. Support confirmed the details and the claim was reopened. A standard invoice was reviewed the same day.", date: "2005-11-09" }, { id: 30, case_number: "789 456", jurisdiction_id: 41, opinion_text: "The item was processed following a routine review. An operator confirmed the details and the payment was resolved. A minor follow-up: the record was refunded.", date: "2005-04-08" }, { id: 31, case_number: "Z CV S", jurisdiction_id: 48, opinion_text: "The account owner reported a standard issue; the appointment was resolved. Flagged as late. The account owner delayed the ticket. The record was closed after an unusual check.", date: "2010-10-12" }, { id: 32, case_number: "Y Docket T", jurisdiction_id: 69, opinion_text: "Support confirmed the details and the booking was completed. A manual account was rescheduled the same day. Flagged as urgent. The courier confirmed the session. Flagged as partial. An operator replaced the session.", date: "2014-03-25" }, { id: 33, case_number: "123 Docket CV", jurisdiction_id: 130, opinion_text: "The payment was updated following a late review. The report was reopened after a minor check.", date: "2003-02-12" }, { id: 34, case_number: "B X", jurisdiction_id: 97, opinion_text: "Flagged as repeat. The customer updated the ticket. No response from an operator, so the appointment was refunded. The account was approved following a repeat review.", date: "2020-01-08" }, { id: 35, case_number: "CR Docket T", jurisdiction_id: 38, opinion_text: "A duplicate appointment was completed the same day. The team confirmed the details and the payment was processed.", date: "2004-02-25" }, { id: 36, case_number: "Z 123 789", jurisdiction_id: 130, opinion_text: "The session was escalated after a routine check. An operator confirmed the details and the ticket was cancelled. The supplier reported a minor issue; the ticket was approved. The ticket was approved following a partial review.", date: "2023-07-06" }, { id: 37, case_number: "001", jurisdiction_id: 76, opinion_text: "Flagged as unusual. Support resolved the account. No response from the team, so the ticket was refunded. The booking was delayed after a repeat check. The report was rejected after a repeat check.", date: "2006-02-04" }, { id: 38, case_number: "No", jurisdiction_id: 101, opinion_text: null, date: "2003-07-03" }, { id: 39, case_number: "S", jurisdiction_id: 52, opinion_text: "The transfer was updated — incomplete case, no further action. Support reported an automatic issue; the request was cancelled. The report was rejected after an automatic check. The account owner reported an automatic issue; the ticket was completed.", date: "2020-10-11" }, { id: 40, case_number: "456", jurisdiction_id: 18, opinion_text: null, date: "2003-12-14" }, { id: 41, case_number: "002 No 2023", jurisdiction_id: 6, opinion_text: "The reviewer confirmed the details and the report was replaced. The customer reported an incomplete issue; the refund was confirmed.", date: "2015-08-08" }, { id: 42, case_number: "CR X", jurisdiction_id: 67, opinion_text: "An urgent follow-up: the invoice was confirmed. An automatic request was confirmed the same day. Flagged as repeat. Support approved the report. An operator confirmed the details and the booking was escalated.", date: "2015-02-05" }, { id: 43, case_number: "Docket A 2023", jurisdiction_id: 108, opinion_text: "No response from the team, so the booking was delayed. The team asked for a change and the session was resolved. The reviewer asked for a change and the claim was refunded. The customer asked for a change and the refund was escalated.", date: "2014-01-05" }, { id: 44, case_number: "Z 003 456", jurisdiction_id: 98, opinion_text: "The supplier confirmed the details and the ticket was cancelled. A duplicate follow-up: the account was reviewed.", date: "2018-11-06" }, { id: 45, case_number: "B 003", jurisdiction_id: 63, opinion_text: "A standard follow-up: the document was closed. Support reported an automatic issue; the report was rejected. The payment was resolved following a routine review.", date: "2015-11-28" }, { id: 46, case_number: "C S T", jurisdiction_id: 139, opinion_text: "The record was processed after a repeat check. Flagged as standard. The team updated the booking.", date: "2009-01-28" }, { id: 47, case_number: "C 001 Z", jurisdiction_id: 36, opinion_text: "The order was completed — routine case, no further action. No response from the account owner, so the item was updated. The refund was processed following a manual review. The record was reviewed after a repeat check.", date: "2001-10-21" }, { id: 48, case_number: "Y CR", jurisdiction_id: 130, opinion_text: "The supplier reported a routine issue; the document was completed. The supplier confirmed the details and the order was rejected.", date: "2016-01-07" }, { id: 49, case_number: "2023 123", jurisdiction_id: 128, opinion_text: "The invoice was approved — duplicate case, no further action. The report was reviewed after an incomplete check. Flagged as automatic. The team confirmed the refund.", date: "2014-10-14" }, { id: 50, case_number: "X A", jurisdiction_id: 73, opinion_text: "The customer asked for a change and the shipment was resolved. The appointment was confirmed after a duplicate check.", date: "2011-02-01" }, { id: 51, case_number: "C S 002", jurisdiction_id: 110, opinion_text: "No response from the account owner, so the report was updated. The customer asked for a change and the transfer was processed.", date: "2013-09-08" }, { id: 52, case_number: "CV B A", jurisdiction_id: 133, opinion_text: "Flagged as duplicate. Support cancelled the document. The booking was updated after a manual check.", date: "2016-10-19" }, { id: 53, case_number: "123 X 001", jurisdiction_id: 133, opinion_text: "The payment was refunded — repeat case, no further action. Flagged as standard. The courier processed the refund. The account owner reported an incomplete issue; the payment was replaced. The supplier reported an urgent issue; the report was closed.", date: "2018-10-22" }, { id: 54, case_number: "001", jurisdiction_id: 15, opinion_text: "The claim was delayed after an urgent check. Support reported a minor issue; the claim was resolved.", date: "2015-08-01" }, { id: 55, case_number: "456 S 003", jurisdiction_id: 94, opinion_text: "Flagged as standard. The team completed the report. The account owner confirmed the details and the invoice was rejected. The shipment was confirmed following a repeat review. Flagged as manual. The account owner reviewed the request.", date: "2012-08-02" }, { id: 56, case_number: "X", jurisdiction_id: 54, opinion_text: "The team reported an automatic issue; the invoice was delayed. The report was reviewed — standard case, no further action. An operator asked for a change and the claim was delayed.", date: "2011-09-19" }, { id: 57, case_number: "001 2023 T", jurisdiction_id: 86, opinion_text: "A standard ticket was delayed the same day. The appointment was refunded — partial case, no further action. A minor session was resolved the same day. Flagged as automatic. The courier escalated the refund.", date: "2004-12-18" }, { id: 58, case_number: "789", jurisdiction_id: 34, opinion_text: "An operator confirmed the details and the claim was closed. A repeat account was replaced the same day.", date: "2011-12-02" }, { id: 59, case_number: "A", jurisdiction_id: 72, opinion_text: "An incomplete transfer was processed the same day. Flagged as duplicate. The courier reopened the transfer.", date: "2022-08-07" }, { id: 60, case_number: "X Z 123", jurisdiction_id: 79, opinion_text: "The order was completed after an unusual check. Flagged as routine. An operator reviewed the invoice. An operator reported an unusual issue; the appointment was resolved.", date: "2011-01-17" }, { id: 61, case_number: "S A", jurisdiction_id: 127, opinion_text: "The customer reported a late issue; the request was resolved. An automatic follow-up: the invoice was refunded. No response from the supplier, so the account was completed.", date: "2018-04-05" }, { id: 62, case_number: "2023 456 S", jurisdiction_id: 89, opinion_text: "An urgent follow-up: the ticket was completed. The claim was replaced following an urgent review.", date: "2023-12-09" }, { id: 63, case_number: "R 003", jurisdiction_id: 136, opinion_text: "An automatic follow-up: the ticket was delayed. The team reported a standard issue; the transfer was refunded. Flagged as partial. The courier completed the record.", date: "2022-12-09" }, { id: 64, case_number: "789 B S", jurisdiction_id: 84, opinion_text: "Flagged as unusual. The customer rescheduled the document. Flagged as incomplete. The reviewer reviewed the ticket. The transfer was reviewed following a manual review.", date: "2007-10-13" }, { id: 65, case_number: "C B 789", jurisdiction_id: 129, opinion_text: "The record was delayed after an incomplete check. The delivery was resolved following an urgent review. The order was rejected — repeat case, no further action. The shipment was cancelled after a repeat check.", date: "2000-12-08" }, { id: 66, case_number: "X 002 C", jurisdiction_id: 21, opinion_text: null, date: "2001-07-18" }, { id: 67, case_number: "X S 001", jurisdiction_id: 92, opinion_text: "A duplicate report was rejected the same day. The customer reported a duplicate issue; the record was refunded.", date: "2009-08-25" }, { id: 68, case_number: "456 T", jurisdiction_id: 39, opinion_text: null, date: "2000-01-27" }, { id: 69, case_number: "C", jurisdiction_id: 20, opinion_text: "The customer reported a minor issue; the appointment was rejected. The team confirmed the details and the transfer was reviewed. The courier reported a routine issue; the account was approved.", date: "2001-09-25" }, { id: 70, case_number: "S", jurisdiction_id: 38, opinion_text: "A late session was reopened the same day. An operator asked for a change and the report was reopened. Flagged as manual. The customer refunded the shipment. The supplier reported a late issue; the request was closed.", date: "2019-08-19" }, { id: 71, case_number: "123", jurisdiction_id: 82, opinion_text: null, date: "2021-09-29" }, { id: 72, case_number: "2023", jurisdiction_id: 43, opinion_text: null, date: "2014-02-17" }, { id: 73, case_number: "Y R Docket", jurisdiction_id: 147, opinion_text: "Flagged as duplicate. Support delayed the order. A routine appointment was updated the same day. An operator confirmed the details and the transfer was delayed.", date: "2013-10-28" }, { id: 74, case_number: "A", jurisdiction_id: 61, opinion_text: "Flagged as partial. The customer cancelled the payment. The ticket was replaced — unusual case, no further action. The refund was completed following a partial review.", date: "2021-08-01" }, { id: 75, case_number: "789 X", jurisdiction_id: 45, opinion_text: "The courier asked for a change and the appointment was closed. The reviewer confirmed the details and the payment was confirmed. No response from the reviewer, so the claim was confirmed.", date: "2023-02-07" }, { id: 76, case_number: "123 R C", jurisdiction_id: 98, opinion_text: "Flagged as automatic. An operator processed the report. Flagged as automatic. The customer delayed the refund. Support confirmed the details and the invoice was replaced.", date: "2007-02-12" }, { id: 77, case_number: "T 002 456", jurisdiction_id: 116, opinion_text: "The ticket was cancelled after a standard check. No response from the reviewer, so the shipment was escalated. The supplier reported an automatic issue; the report was closed. The team reported an incomplete issue; the account was updated.", date: "2015-06-15" }, { id: 78, case_number: "A 001 C", jurisdiction_id: 30, opinion_text: "The customer confirmed the details and the ticket was delayed. Flagged as routine. The reviewer confirmed the record.", date: "2019-02-05" }, { id: 79, case_number: "No C CR", jurisdiction_id: 8, opinion_text: "The item was rejected following an automatic review. No response from the courier, so the order was reviewed. The customer confirmed the details and the ticket was confirmed. The reviewer confirmed the details and the account was closed.", date: "2004-07-05" }, { id: 80, case_number: "S No CR", jurisdiction_id: 98, opinion_text: "Flagged as partial. The team approved the item. The supplier reported a standard issue; the transfer was completed.", date: "2004-07-14" }, { id: 81, case_number: "B", jurisdiction_id: 13, opinion_text: "No response from the team, so the record was completed. The team reported an automatic issue; the ticket was reviewed. The transfer was completed following a partial review.", date: "2006-01-24" }, { id: 82, case_number: "Z S", jurisdiction_id: 150, opinion_text: "Flagged as repeat. An operator reopened the ticket. The delivery was processed after an incomplete check. Support reported a late issue; the report was rescheduled.", date: "2003-09-28" }, { id: 83, case_number: "456 R", jurisdiction_id: 148, opinion_text: "The booking was escalated following an automatic review. Flagged as repeat. The courier resolved the order. The account owner asked for a change and the claim was replaced.", date: "2018-09-02" }, { id: 84, case_number: "002 T", jurisdiction_id: 116, opinion_text: "A manual delivery was delayed the same day. An operator asked for a change and the item was updated. The invoice was rescheduled — partial case, no further action.", date: "2002-08-29" }, { id: 85, case_number: "C 001 A", jurisdiction_id: 28, opinion_text: "The ticket was updated after a late check. An automatic transfer was resolved the same day. An operator confirmed the details and the session was approved. The supplier confirmed the details and the record was approved.", date: "2014-11-14" }, { id: 86, case_number: "B", jurisdiction_id: 139, opinion_text: "Support reported a repeat issue; the booking was escalated. The courier confirmed the details and the session was updated.", date: "2023-11-10" }, { id: 87, case_number: "2023", jurisdiction_id: 22, opinion_text: "The supplier asked for a change and the delivery was reviewed. The appointment was confirmed — automatic case, no further action.", date: "2016-10-07" }, { id: 88, case_number: "002 No", jurisdiction_id: 49, opinion_text: "The session was rejected following an urgent review. The courier confirmed the details and the item was closed.", date: "2007-07-10" }, { id: 89, case_number: "789", jurisdiction_id: 100, opinion_text: "The document was completed — standard case, no further action. An incomplete follow-up: the claim was replaced. Flagged as urgent. The reviewer approved the record.", date: "2020-09-21" }, { id: 90, case_number: "Z", jurisdiction_id: 33, opinion_text: "The team asked for a change and the report was reopened. A standard claim was resolved the same day. An operator asked for a change and the order was reopened.", date: "2001-02-04" }, { id: 91, case_number: "456 2023 CV", jurisdiction_id: 77, opinion_text: "The account owner reported an unusual issue; the ticket was updated. Flagged as automatic. Support completed the invoice. A repeat booking was reopened the same day.", date: "2013-09-21" }, { id: 92, case_number: "2023", jurisdiction_id: 55, opinion_text: "Support asked for a change and the transfer was updated. Support reported a partial issue; the item was completed.", date: "2003-05-22" }, { id: 93, case_number: "Z 2023", jurisdiction_id: 143, opinion_text: "An urgent follow-up: the account was confirmed. The customer asked for a change and the request was refunded. A manual follow-up: the claim was rescheduled.", date: "2013-01-01" }, { id: 94, case_number: "Y No", jurisdiction_id: 45, opinion_text: "No response from support, so the claim was closed. The account owner confirmed the details and the item was cancelled. The order was reopened after a duplicate check. The supplier confirmed the details and the session was updated.", date: "2006-03-06" }, { id: 95, case_number: "001", jurisdiction_id: 94, opinion_text: "No response from the team, so the delivery was refunded. Flagged as urgent. Support replaced the order. Flagged as incomplete. The reviewer refunded the document.", date: "2002-11-12" }, { id: 96, case_number: "CV", jurisdiction_id: 34, opinion_text: "The report was completed following a repeat review. No response from an operator, so the delivery was resolved. Flagged as standard. The team processed the session. No response from the reviewer, so the shipment was rescheduled.", date: "2003-11-28" }, { id: 97, case_number: "C CV 002", jurisdiction_id: 4, opinion_text: "A routine follow-up: the booking was cancelled. The team reported a minor issue; the transfer was escalated. The reviewer confirmed the details and the account was delayed.", date: "2011-11-14" }, { id: 98, case_number: "001", jurisdiction_id: 112, opinion_text: "The booking was replaced after a late check. The appointment was replaced after a manual check.", date: "2007-11-03" }, { id: 99, case_number: "C 456", jurisdiction_id: 67, opinion_text: "A duplicate follow-up: the request was rejected. No response from an operator, so the item was processed. The ticket was resolved after a late check. The team reported a late issue; the item was closed.", date: "2004-04-14" }, { id: 100, case_number: "2023 A B", jurisdiction_id: 26, opinion_text: "No response from the team, so the session was processed. An incomplete follow-up: the ticket was refunded. The customer reported an unusual issue; the session was escalated.", date: "2008-12-19" }, { id: 101, case_number: "A", jurisdiction_id: 100, opinion_text: "The supplier confirmed the details and the report was closed. The ticket was updated following an incomplete review. The delivery was approved after a standard check.", date: "2000-01-14" }, { id: 102, case_number: "123 Z CR", jurisdiction_id: 113, opinion_text: "The report was reviewed after an incomplete check. An incomplete shipment was updated the same day. The booking was closed following an incomplete review.", date: "2020-11-05" }, { id: 103, case_number: "T No", jurisdiction_id: 6, opinion_text: "The supplier confirmed the details and the payment was escalated. The account owner reported an unusual issue; the invoice was rescheduled. Support asked for a change and the item was escalated.", date: "2019-04-23" }, { id: 104, case_number: "CV X 001", jurisdiction_id: 124, opinion_text: "A minor follow-up: the account was refunded. Flagged as routine. The account owner reviewed the claim. No response from an operator, so the report was rescheduled. Flagged as urgent. The supplier reopened the report.", date: "2020-10-24" }, { id: 105, case_number: "No", jurisdiction_id: 82, opinion_text: "The team confirmed the details and the record was confirmed. The shipment was replaced following a partial review. No response from the account owner, so the booking was cancelled.", date: "2016-10-29" }, { id: 106, case_number: "R X C", jurisdiction_id: 62, opinion_text: "The request was confirmed — late case, no further action. The ticket was approved following a minor review. The record was processed — automatic case, no further action.", date: "2018-07-10" }, { id: 107, case_number: "No CR 456", jurisdiction_id: 146, opinion_text: null, date: "2014-01-25" }, { id: 108, case_number: "Y X S", jurisdiction_id: 146, opinion_text: "The reviewer reported a manual issue; the document was reopened. The ticket was updated after a routine check.", date: "2010-11-23" }, { id: 109, case_number: "No 003 S", jurisdiction_id: 53, opinion_text: null, date: "2002-11-13" }, { id: 110, case_number: "789 123", jurisdiction_id: 17, opinion_text: "Flagged as manual. The customer closed the report. Support reported an incomplete issue; the claim was replaced. An incomplete delivery was confirmed the same day. The account was closed after a standard check.", date: "2009-11-18" }, { id: 111, case_number: "A X", jurisdiction_id: 30, opinion_text: "The claim was reopened after an urgent check. Support asked for a change and the payment was rescheduled. The order was closed following a minor review.", date: "2014-12-10" }, { id: 112, case_number: "Z B 003", jurisdiction_id: 58, opinion_text: "The team reported an automatic issue; the shipment was reviewed. An urgent follow-up: the appointment was rescheduled.", date: "2008-09-21" }, { id: 113, case_number: "456 003", jurisdiction_id: 114, opinion_text: "The session was processed after a repeat check. The refund was processed — duplicate case, no further action.", date: "2020-11-07" }, { id: 114, case_number: "Y CR R", jurisdiction_id: 62, opinion_text: "No response from an operator, so the invoice was updated. The appointment was escalated after a late check.", date: "2013-08-01" }, { id: 115, case_number: "CV 001", jurisdiction_id: 139, opinion_text: "The booking was closed — manual case, no further action. Flagged as automatic. The customer closed the refund.", date: "2015-09-01" }, { id: 116, case_number: "123 003 456", jurisdiction_id: 141, opinion_text: "The team reported a partial issue; the report was replaced. The team asked for a change and the request was processed. The order was updated — repeat case, no further action.", date: "2009-12-11" }, { id: 117, case_number: "T CR 003", jurisdiction_id: 82, opinion_text: "The payment was completed after a duplicate check. A repeat payment was confirmed the same day. A standard follow-up: the order was confirmed.", date: "2002-03-06" }, { id: 118, case_number: "A Y", jurisdiction_id: 136, opinion_text: null, date: "2014-01-26" }, { id: 119, case_number: "C 123 789", jurisdiction_id: 34, opinion_text: null, date: "2021-04-08" }, { id: 120, case_number: "R Y", jurisdiction_id: 123, opinion_text: "The transfer was rescheduled — repeat case, no further action. The transfer was escalated after an unusual check. The account owner asked for a change and the claim was resolved.", date: "2021-10-25" }, { id: 121, case_number: "R", jurisdiction_id: 4, opinion_text: "The delivery was updated after a standard check. The booking was completed following a partial review. The shipment was replaced — late case, no further action. The team asked for a change and the appointment was refunded.", date: "2004-03-05" }, { id: 122, case_number: "456 B", jurisdiction_id: 133, opinion_text: "An operator confirmed the details and the session was replaced. The customer asked for a change and the request was closed. An operator reported a standard issue; the session was replaced.", date: "2004-08-21" }, { id: 123, case_number: "CR 789", jurisdiction_id: 99, opinion_text: "Support asked for a change and the booking was escalated. A partial ticket was delayed the same day. The order was replaced — partial case, no further action.", date: "2013-10-11" }, { id: 124, case_number: "C", jurisdiction_id: 66, opinion_text: "A partial follow-up: the transfer was cancelled. An operator reported a manual issue; the shipment was resolved.", date: "2013-09-05" }, { id: 125, case_number: "2023", jurisdiction_id: 18, opinion_text: "The claim was closed — partial case, no further action. The document was escalated following a repeat review. The delivery was updated following an urgent review.", date: "2017-02-26" }, { id: 126, case_number: "CR Z", jurisdiction_id: 56, opinion_text: "No response from the customer, so the report was delayed. An operator reported a standard issue; the refund was delayed. The appointment was cancelled — manual case, no further action. The delivery was processed following an urgent review.", date: "2009-01-10" }, { id: 127, case_number: "No Z B", jurisdiction_id: 35, opinion_text: "The report was rejected — routine case, no further action. An urgent appointment was approved the same day. A partial item was completed the same day.", date: "2023-02-01" }, { id: 128, case_number: "789 A S", jurisdiction_id: 48, opinion_text: "The courier reported a manual issue; the request was resolved. No response from the team, so the record was completed. The reviewer reported a standard issue; the delivery was reviewed. The courier asked for a change and the document was processed.", date: "2002-03-11" }, { id: 129, case_number: "123", jurisdiction_id: 120, opinion_text: "The account owner reported an urgent issue; the record was updated. The ticket was confirmed following an automatic review. An operator confirmed the details and the report was rescheduled. A minor follow-up: the booking was closed.", date: "2023-07-18" }, { id: 130, case_number: "T C", jurisdiction_id: 23, opinion_text: "Flagged as repeat. The supplier escalated the refund. The team asked for a change and the order was replaced. An urgent ticket was cancelled the same day.", date: "2007-05-08" }, { id: 131, case_number: "Y", jurisdiction_id: 11, opinion_text: "The supplier confirmed the details and the request was rejected. A routine request was resolved the same day. The account was confirmed following a standard review. Support confirmed the details and the ticket was cancelled.", date: "2002-11-02" }, { id: 132, case_number: "X 003 CR", jurisdiction_id: 15, opinion_text: "The payment was closed after a manual check. The account owner confirmed the details and the shipment was reopened. The document was delayed following an incomplete review. The customer reported a routine issue; the booking was resolved.", date: "2006-06-01" }, { id: 133, case_number: "No CV T", jurisdiction_id: 147, opinion_text: "Support asked for a change and the delivery was reopened. Support asked for a change and the ticket was updated. No response from the customer, so the shipment was approved. The claim was updated after a routine check.", date: "2018-09-18" }, { id: 134, case_number: "001 2023 456", jurisdiction_id: 139, opinion_text: "A repeat follow-up: the claim was reopened. The transfer was replaced — incomplete case, no further action. An operator reported an incomplete issue; the payment was updated.", date: "2018-09-10" }, { id: 135, case_number: "002 T X", jurisdiction_id: 145, opinion_text: "The customer asked for a change and the ticket was processed. An operator reported a duplicate issue; the transfer was closed. No response from the reviewer, so the booking was replaced. A partial claim was reopened the same day.", date: "2008-05-17" }, { id: 136, case_number: "Z S A", jurisdiction_id: 46, opinion_text: "The appointment was processed following an incomplete review. A duplicate item was escalated the same day.", date: "2015-08-03" }, { id: 137, case_number: "001 003", jurisdiction_id: 124, opinion_text: "The item was resolved following a partial review. No response from support, so the account was closed.", date: "2016-10-19" }, { id: 138, case_number: "CV CR X", jurisdiction_id: 33, opinion_text: null, date: "2008-04-03" }, { id: 139, case_number: "003 X", jurisdiction_id: 53, opinion_text: "An operator reported an urgent issue; the invoice was escalated. An operator reported a routine issue; the refund was reopened. Flagged as urgent. An operator resolved the delivery. Support confirmed the details and the delivery was closed.", date: "2000-02-17" }, { id: 140, case_number: "CR", jurisdiction_id: 9, opinion_text: "A repeat account was escalated the same day. The invoice was approved following a manual review.", date: "2003-03-17" }, { id: 141, case_number: "002 Y No", jurisdiction_id: 112, opinion_text: null, date: "2002-01-29" }, { id: 142, case_number: "002", jurisdiction_id: 37, opinion_text: "Flagged as standard. The courier processed the transfer. An incomplete booking was reviewed the same day. Flagged as minor. The supplier rescheduled the refund. No response from support, so the document was processed.", date: "2006-10-29" }, { id: 143, case_number: "No", jurisdiction_id: 40, opinion_text: "No response from the reviewer, so the delivery was escalated. The reviewer confirmed the details and the order was refunded. An operator confirmed the details and the delivery was updated. No response from support, so the claim was processed.", date: "2010-09-16" }, { id: 144, case_number: "Y Docket R", jurisdiction_id: 33, opinion_text: "A partial record was approved the same day. The courier asked for a change and the ticket was resolved.", date: "2022-04-05" }, { id: 145, case_number: "No", jurisdiction_id: 118, opinion_text: "Flagged as routine. The supplier rescheduled the ticket. An incomplete follow-up: the request was escalated. Flagged as routine. The account owner refunded the session. Flagged as routine. Support cancelled the payment.", date: "2012-10-11" }, { id: 146, case_number: "001 Docket C", jurisdiction_id: 23, opinion_text: "The appointment was processed — automatic case, no further action. No response from an operator, so the invoice was escalated.", date: "2001-06-26" }, { id: 147, case_number: "002 003", jurisdiction_id: 34, opinion_text: null, date: "2018-12-05" }, { id: 148, case_number: "456", jurisdiction_id: 114, opinion_text: "The team asked for a change and the payment was confirmed. An operator confirmed the details and the delivery was replaced. The account was approved — duplicate case, no further action.", date: "2019-06-08" }, { id: 149, case_number: "S 456 Z", jurisdiction_id: 79, opinion_text: "A late document was updated the same day. The session was approved following an automatic review. The account was resolved — manual case, no further action. The transfer was resolved after a partial check.", date: "2017-02-09" }, { id: 150, case_number: "R CV", jurisdiction_id: 128, opinion_text: "The account owner reported a repeat issue; the invoice was resolved. No response from the courier, so the report was rejected. Flagged as routine. The supplier cancelled the claim. The document was rescheduled — incomplete case, no further action.", date: "2011-02-22" }, { id: 151, case_number: "123 B", jurisdiction_id: 19, opinion_text: "No response from the courier, so the report was updated. The payment was updated after an automatic check. No response from support, so the booking was delayed.", date: "2021-01-07" }, { id: 152, case_number: "B X 002", jurisdiction_id: 115, opinion_text: "The account owner confirmed the details and the session was processed. Flagged as routine. The supplier resolved the appointment. The account was confirmed following an urgent review. A minor delivery was reviewed the same day.", date: "2005-03-08" }, { id: 153, case_number: "C No X", jurisdiction_id: 149, opinion_text: "Flagged as automatic. An operator escalated the refund. Flagged as routine. The supplier cancelled the session. Flagged as partial. The reviewer completed the item. A duplicate transfer was closed the same day.", date: "2019-08-21" }, { id: 154, case_number: "No T", jurisdiction_id: 92, opinion_text: "The shipment was updated — manual case, no further action. No response from support, so the payment was processed. Support asked for a change and the document was completed. Flagged as late. The customer processed the refund.", date: "2011-02-15" }, { id: 155, case_number: "S B A", jurisdiction_id: 134, opinion_text: "The delivery was resolved after a manual check. A minor shipment was updated the same day. The account was closed following an incomplete review.", date: "2005-01-08" }, { id: 156, case_number: "T A", jurisdiction_id: 29, opinion_text: "An incomplete follow-up: the report was rescheduled. The reviewer asked for a change and the account was closed. The record was approved — routine case, no further action.", date: "2018-11-18" }, { id: 157, case_number: "456 X", jurisdiction_id: 84, opinion_text: "The request was reopened following a partial review. The order was rescheduled following an unusual review.", date: "2020-09-20" }, { id: 158, case_number: "789 2023 CR", jurisdiction_id: 95, opinion_text: "The record was updated — automatic case, no further action. An incomplete follow-up: the ticket was resolved.", date: "2006-03-11" }, { id: 159, case_number: "B 002", jurisdiction_id: 95, opinion_text: "An incomplete record was escalated the same day. The supplier confirmed the details and the delivery was reopened.", date: "2014-09-27" }, { id: 160, case_number: "No Z", jurisdiction_id: 81, opinion_text: "A minor follow-up: the document was confirmed. The customer asked for a change and the booking was replaced. The shipment was rescheduled following a routine review.", date: "2005-07-19" }, { id: 161, case_number: "2023", jurisdiction_id: 36, opinion_text: "Flagged as unusual. An operator escalated the invoice. The customer confirmed the details and the refund was rejected. A minor follow-up: the shipment was escalated.", date: "2009-04-02" }, { id: 162, case_number: "T 003 S", jurisdiction_id: 75, opinion_text: null, date: "2016-05-18" }, { id: 163, case_number: "C", jurisdiction_id: 3, opinion_text: "The account owner confirmed the details and the refund was replaced. A manual follow-up: the session was approved. An incomplete order was cancelled the same day.", date: "2014-02-09" }, { id: 164, case_number: "Docket C", jurisdiction_id: 59, opinion_text: "A manual follow-up: the shipment was closed. Flagged as minor. The account owner processed the refund. The report was replaced following a standard review.", date: "2022-04-17" }, { id: 165, case_number: "CV Y", jurisdiction_id: 33, opinion_text: "The courier reported a routine issue; the record was completed. The courier asked for a change and the account was escalated.", date: "2006-08-01" }, { id: 166, case_number: "001 C A", jurisdiction_id: 60, opinion_text: "A manual appointment was cancelled the same day. An urgent invoice was rescheduled the same day.", date: "2022-07-01" }, { id: 167, case_number: "R", jurisdiction_id: 54, opinion_text: "No response from the courier, so the ticket was processed. The shipment was closed after an automatic check. The customer confirmed the details and the session was processed. The supplier reported a late issue; the payment was resolved.", date: "2012-09-20" }, { id: 168, case_number: "S No", jurisdiction_id: 58, opinion_text: "The appointment was approved following a late review. Support reported a partial issue; the record was confirmed. The team asked for a change and the item was updated. An urgent report was replaced the same day.", date: "2001-10-01" }, { id: 169, case_number: "Y T S", jurisdiction_id: 125, opinion_text: "No response from support, so the refund was processed. An urgent follow-up: the payment was cancelled. A manual shipment was cancelled the same day.", date: "2016-11-24" }, { id: 170, case_number: "R C 003", jurisdiction_id: 27, opinion_text: "A routine shipment was escalated the same day. The reviewer reported a late issue; the payment was updated.", date: "2014-12-02" }, { id: 171, case_number: "003 B", jurisdiction_id: 126, opinion_text: "The invoice was escalated — manual case, no further action. A manual follow-up: the delivery was closed. Flagged as manual. The courier completed the refund. Flagged as partial. The customer confirmed the appointment.", date: "2000-09-26" }, { id: 172, case_number: "C 123", jurisdiction_id: 87, opinion_text: "An unusual follow-up: the appointment was updated. Flagged as automatic. An operator rejected the refund. An urgent delivery was processed the same day.", date: "2009-11-04" }, { id: 173, case_number: "002 CV", jurisdiction_id: 123, opinion_text: "The ticket was processed — unusual case, no further action. The account owner asked for a change and the payment was closed.", date: "2013-05-03" }, { id: 174, case_number: "B", jurisdiction_id: 120, opinion_text: "The account owner confirmed the details and the document was closed. A partial order was approved the same day.", date: "2021-08-13" }, { id: 175, case_number: "B", jurisdiction_id: 117, opinion_text: null, date: "2017-04-29" }, { id: 176, case_number: "123 001 CV", jurisdiction_id: 35, opinion_text: "No response from the customer, so the record was closed. The courier asked for a change and the invoice was processed.", date: "2013-10-27" }, { id: 177, case_number: "CV", jurisdiction_id: 101, opinion_text: "An urgent follow-up: the claim was escalated. The session was reopened following a duplicate review. An urgent ticket was updated the same day. An automatic booking was confirmed the same day.", date: "2008-11-01" }, { id: 178, case_number: "C", jurisdiction_id: 59, opinion_text: null, date: "2006-07-21" }, { id: 179, case_number: "No 003", jurisdiction_id: 77, opinion_text: "The invoice was closed following an urgent review. The team confirmed the details and the transfer was rescheduled.", date: "2016-08-08" }, { id: 180, case_number: "No R", jurisdiction_id: 148, opinion_text: "No response from the customer, so the delivery was refunded. Flagged as manual. The reviewer delayed the payment.", date: "2019-12-22" }, { id: 181, case_number: "T C CV", jurisdiction_id: 69, opinion_text: "The item was completed after an incomplete check. The claim was cancelled following a standard review. An automatic transfer was completed the same day.", date: "2013-03-25" }, { id: 182, case_number: "C R 003", jurisdiction_id: 124, opinion_text: "Support asked for a change and the shipment was closed. The account owner reported a manual issue; the booking was completed.", date: "2016-08-26" }, { id: 183, case_number: "CV", jurisdiction_id: 140, opinion_text: "An automatic follow-up: the shipment was delayed. Support asked for a change and the transfer was cancelled. An unusual follow-up: the document was processed. No response from the reviewer, so the account was resolved.", date: "2007-11-16" }, { id: 184, case_number: "T", jurisdiction_id: 118, opinion_text: "A standard follow-up: the invoice was resolved. The claim was approved — incomplete case, no further action.", date: "2021-11-01" }, { id: 185, case_number: "Z", jurisdiction_id: 15, opinion_text: "The report was closed after a manual check. Flagged as partial. The reviewer closed the order.", date: "2016-01-11" }, { id: 186, case_number: "001 Docket", jurisdiction_id: 143, opinion_text: "The courier reported a routine issue; the order was refunded. The order was escalated — partial case, no further action. The reviewer confirmed the details and the delivery was rescheduled.", date: "2001-03-24" }, { id: 187, case_number: "CR Y", jurisdiction_id: 30, opinion_text: "No response from the courier, so the account was reopened. The delivery was rescheduled — routine case, no further action. The request was reopened following a manual review. The invoice was rescheduled after a repeat check.", date: "2009-12-30" }, { id: 188, case_number: "T R Docket", jurisdiction_id: 41, opinion_text: "The account owner confirmed the details and the shipment was resolved. A repeat booking was rescheduled the same day.", date: "2006-11-05" }, { id: 189, case_number: "123 A", jurisdiction_id: 118, opinion_text: "A routine follow-up: the order was refunded. The reviewer asked for a change and the report was cancelled.", date: "2023-12-05" }, { id: 190, case_number: "003 C CV", jurisdiction_id: 145, opinion_text: null, date: "2018-08-13" }, { id: 191, case_number: "003 Y", jurisdiction_id: 83, opinion_text: "The supplier reported an urgent issue; the booking was rescheduled. The invoice was reviewed after a minor check.", date: "2014-02-15" }, { id: 192, case_number: "T Docket", jurisdiction_id: 23, opinion_text: "An unusual claim was rejected the same day. The account owner asked for a change and the refund was processed.", date: "2014-01-26" }, { id: 193, case_number: "789 A", jurisdiction_id: 135, opinion_text: "No response from the reviewer, so the ticket was rejected. Support asked for a change and the booking was closed. The refund was escalated — unusual case, no further action. No response from the supplier, so the report was refunded.", date: "2015-08-19" }, { id: 194, case_number: "789 002", jurisdiction_id: 120, opinion_text: null, date: "2009-03-15" }, { id: 195, case_number: "002", jurisdiction_id: 68, opinion_text: "A partial follow-up: the request was resolved. A duplicate refund was updated the same day. Flagged as partial. The team approved the claim.", date: "2017-10-04" }, { id: 196, case_number: "C 002 B", jurisdiction_id: 126, opinion_text: "The account owner confirmed the details and the payment was delayed. The courier reported an incomplete issue; the refund was updated. An operator reported a duplicate issue; the delivery was updated. The ticket was confirmed following a late review.", date: "2014-10-23" }, { id: 197, case_number: "X T A", jurisdiction_id: 106, opinion_text: "No response from the account owner, so the order was closed. The record was refunded after a manual check.", date: "2002-01-24" }, { id: 198, case_number: "Docket S 456", jurisdiction_id: 100, opinion_text: "Flagged as manual. The supplier escalated the report. The courier asked for a change and the shipment was completed. Flagged as automatic. Support closed the item. A routine follow-up: the claim was replaced.", date: "2019-01-17" }, { id: 199, case_number: "Docket 789", jurisdiction_id: 11, opinion_text: "A routine follow-up: the record was updated. An urgent invoice was confirmed the same day. Flagged as repeat. The customer escalated the delivery. The account owner confirmed the details and the request was reopened.", date: "2017-08-30" }, { id: 200, case_number: "CV", jurisdiction_id: 66, opinion_text: "The team asked for a change and the transfer was replaced. The customer reported a late issue; the report was updated. An operator reported a repeat issue; the item was closed.", date: "2020-04-10" }, ], }); await prisma.judges.createMany({ data: [ { id: 1, full_name: "Liam Kowalski", case_opinion_id: 4, court_rank: "district", years_on_bench: 21 }, { id: 2, full_name: "Mei Larsen", case_opinion_id: 12, court_rank: "supreme", years_on_bench: 20 }, { id: 3, full_name: "Daniel Shah", case_opinion_id: 101, court_rank: "appellate", years_on_bench: 19 }, { id: 4, full_name: "Marco Lopez", case_opinion_id: 187, court_rank: "district", years_on_bench: 12 }, { id: 5, full_name: null, case_opinion_id: 151, court_rank: "appellate", years_on_bench: 26 }, { id: 6, full_name: "Deniz Pereira", case_opinion_id: 123, court_rank: "district", years_on_bench: 25 }, { id: 7, full_name: "Paula Young", case_opinion_id: 94, court_rank: "district", years_on_bench: 17 }, { id: 8, full_name: "Elif Lee", case_opinion_id: 81, court_rank: "district", years_on_bench: 17 }, { id: 9, full_name: "Fatima Baker", case_opinion_id: 33, court_rank: "appellate", years_on_bench: 10 }, { id: 10, full_name: "Chloe Brown", case_opinion_id: 92, court_rank: "supreme", years_on_bench: 23 }, { id: 11, full_name: "Ibrahim Wright", case_opinion_id: 144, court_rank: "appellate", years_on_bench: 25 }, { id: 12, full_name: "Mateo Nguyen", case_opinion_id: 15, court_rank: "supreme", years_on_bench: 18 }, { id: 13, full_name: null, case_opinion_id: 159, court_rank: "district", years_on_bench: 20 }, { id: 14, full_name: "Elif Johnson", case_opinion_id: 158, court_rank: "appellate", years_on_bench: 17 }, { id: 15, full_name: "Mohamed Wang", case_opinion_id: 187, court_rank: "appellate", years_on_bench: 16 }, { id: 16, full_name: "Jonas Castro", case_opinion_id: 77, court_rank: "supreme", years_on_bench: 10 }, { id: 17, full_name: "Sam Yilmaz", case_opinion_id: 72, court_rank: "district", years_on_bench: 26 }, { id: 18, full_name: "Sara Khan", case_opinion_id: 70, court_rank: "district", years_on_bench: 16 }, { id: 19, full_name: "Marco Chen", case_opinion_id: 146, court_rank: "district", years_on_bench: 12 }, { id: 20, full_name: "James Lopez", case_opinion_id: 119, court_rank: "district", years_on_bench: 22 }, { id: 21, full_name: "Sara Baker", case_opinion_id: 70, court_rank: "district", years_on_bench: 24 }, { id: 22, full_name: "Theo Pereira", case_opinion_id: 73, court_rank: "district", years_on_bench: 14 }, { id: 23, full_name: "James Hansen", case_opinion_id: 59, court_rank: "district", years_on_bench: 12 }, { id: 24, full_name: "Liam Martin", case_opinion_id: 1, court_rank: "supreme", years_on_bench: 22 }, { id: 25, full_name: "Nour Schneider", case_opinion_id: 74, court_rank: "district", years_on_bench: 18 }, { id: 26, full_name: null, case_opinion_id: 154, court_rank: "district", years_on_bench: 16 }, { id: 27, full_name: "Maya Hoffmann", case_opinion_id: 152, court_rank: "appellate", years_on_bench: 32 }, { id: 28, full_name: "Fatima Wagner", case_opinion_id: 179, court_rank: "appellate", years_on_bench: 21 }, { id: 29, full_name: null, case_opinion_id: 107, court_rank: "district", years_on_bench: 19 }, { id: 30, full_name: "Kai Hassan", case_opinion_id: 159, court_rank: "district", years_on_bench: 20 }, { id: 31, full_name: "Diego Mendes", case_opinion_id: 61, court_rank: "district", years_on_bench: 13 }, { id: 32, full_name: "Zara Novak", case_opinion_id: 179, court_rank: "district", years_on_bench: 24 }, { id: 33, full_name: "Yara Davis", case_opinion_id: 166, court_rank: "district", years_on_bench: 26 }, { id: 34, full_name: "Lena Lee", case_opinion_id: 129, court_rank: "district", years_on_bench: 22 }, { id: 35, full_name: "Yusuf Zhang", case_opinion_id: 105, court_rank: "appellate", years_on_bench: 28 }, { id: 36, full_name: "Tomas Dubois", case_opinion_id: 200, court_rank: "district", years_on_bench: 22 }, { id: 37, full_name: "Ana Oliveira", case_opinion_id: 62, court_rank: "district", years_on_bench: 15 }, { id: 38, full_name: null, case_opinion_id: 195, court_rank: "supreme", years_on_bench: 26 }, { id: 39, full_name: null, case_opinion_id: 77, court_rank: "appellate", years_on_bench: 20 }, { id: 40, full_name: "Jade Silva", case_opinion_id: 26, court_rank: "district", years_on_bench: 19 }, { id: 41, full_name: "James Lopez", case_opinion_id: 64, court_rank: "district", years_on_bench: 13 }, { id: 42, full_name: "Andre Evans", case_opinion_id: 49, court_rank: "district", years_on_bench: 15 }, { id: 43, full_name: "Uma Walker", case_opinion_id: 187, court_rank: "district", years_on_bench: 16 }, { id: 44, full_name: "Felix Singh", case_opinion_id: 26, court_rank: "district", years_on_bench: 28 }, { id: 45, full_name: "Omar Shah", case_opinion_id: 143, court_rank: "district", years_on_bench: 18 }, { id: 46, full_name: "Olivia Evans", case_opinion_id: 127, court_rank: "district", years_on_bench: 12 }, { id: 47, full_name: "Zara Mendes", case_opinion_id: 190, court_rank: "district", years_on_bench: 38 }, { id: 48, full_name: "Mila Singh", case_opinion_id: 184, court_rank: "supreme", years_on_bench: 33 }, { id: 49, full_name: "Tomas Patel", case_opinion_id: 18, court_rank: "district", years_on_bench: 17 }, { id: 50, full_name: "Omar Taylor", case_opinion_id: 11, court_rank: "district", years_on_bench: 29 }, { id: 51, full_name: null, case_opinion_id: 160, court_rank: "district", years_on_bench: 28 }, { id: 52, full_name: "Ben Tanaka", case_opinion_id: 99, court_rank: "district", years_on_bench: 22 }, { id: 53, full_name: "Diego Weber", case_opinion_id: 126, court_rank: "district", years_on_bench: 10 }, { id: 54, full_name: "Hana Schmidt", case_opinion_id: 147, court_rank: "appellate", years_on_bench: 23 }, { id: 55, full_name: "Sara Kaya", case_opinion_id: 3, court_rank: "appellate", years_on_bench: 18 }, { id: 56, full_name: "Anna Ali", case_opinion_id: 197, court_rank: "appellate", years_on_bench: 15 }, { id: 57, full_name: "Victor Reyes", case_opinion_id: 13, court_rank: "district", years_on_bench: 11 }, { id: 58, full_name: "Elif Hassan", case_opinion_id: 71, court_rank: "appellate", years_on_bench: 21 }, { id: 59, full_name: "Zara Jansen", case_opinion_id: 65, court_rank: "district", years_on_bench: 19 }, { id: 60, full_name: null, case_opinion_id: 69, court_rank: "district", years_on_bench: 19 }, { id: 61, full_name: "Amir Costa", case_opinion_id: 147, court_rank: "supreme", years_on_bench: 20 }, { id: 62, full_name: "Sara Klein", case_opinion_id: 139, court_rank: "supreme", years_on_bench: 22 }, { id: 63, full_name: "Emma Smith", case_opinion_id: 65, court_rank: "district", years_on_bench: 16 }, { id: 64, full_name: "Alice Lopez", case_opinion_id: 158, court_rank: "supreme", years_on_bench: 21 }, { id: 65, full_name: "Pedro Dubois", case_opinion_id: 110, court_rank: "supreme", years_on_bench: 14 }, { id: 66, full_name: "Maja Klein", case_opinion_id: 200, court_rank: "district", years_on_bench: 20 }, { id: 67, full_name: "Paula Wilson", case_opinion_id: 169, court_rank: "appellate", years_on_bench: 20 }, { id: 68, full_name: "Hana Almeida", case_opinion_id: 59, court_rank: "district", years_on_bench: 18 }, { id: 69, full_name: "Ibrahim Nguyen", case_opinion_id: 171, court_rank: "district", years_on_bench: 21 }, { id: 70, full_name: "Ben Moreau", case_opinion_id: 55, court_rank: "appellate", years_on_bench: 12 }, { id: 71, full_name: "Jack Brown", case_opinion_id: 82, court_rank: "supreme", years_on_bench: 16 }, { id: 72, full_name: "Marco Fischer", case_opinion_id: 106, court_rank: "district", years_on_bench: 21 }, { id: 73, full_name: "Olivia Lopez", case_opinion_id: 98, court_rank: "appellate", years_on_bench: 19 }, { id: 74, full_name: "Grace Ibrahim", case_opinion_id: 41, court_rank: "district", years_on_bench: 21 }, { id: 75, full_name: "Ines Gupta", case_opinion_id: 2, court_rank: "appellate", years_on_bench: 30 }, { id: 76, full_name: "Sam Nguyen", case_opinion_id: 20, court_rank: "supreme", years_on_bench: 34 }, { id: 77, full_name: "Wei Kim", case_opinion_id: 159, court_rank: "appellate", years_on_bench: 30 }, { id: 78, full_name: "Felix Andersen", case_opinion_id: 34, court_rank: "appellate", years_on_bench: 22 }, { id: 79, full_name: "Maria Park", case_opinion_id: 84, court_rank: "appellate", years_on_bench: 22 }, { id: 80, full_name: null, case_opinion_id: 36, court_rank: "appellate", years_on_bench: 20 }, { id: 81, full_name: "Ravi Schneider", case_opinion_id: 10, court_rank: "district", years_on_bench: 25 }, { id: 82, full_name: "Maria Schmidt", case_opinion_id: 151, court_rank: "appellate", years_on_bench: 23 }, { id: 83, full_name: "Andre Torres", case_opinion_id: 170, court_rank: "supreme", years_on_bench: 15 }, { id: 84, full_name: "Alice Fischer", case_opinion_id: 198, court_rank: "district", years_on_bench: 22 }, { id: 85, full_name: "Elif Jansen", case_opinion_id: 14, court_rank: "district", years_on_bench: 26 }, { id: 86, full_name: "Victor Nguyen", case_opinion_id: 72, court_rank: "district", years_on_bench: 30 }, { id: 87, full_name: "Mia Hansen", case_opinion_id: 1, court_rank: "district", years_on_bench: 16 }, { id: 88, full_name: "Jack Sato", case_opinion_id: 45, court_rank: "district", years_on_bench: 19 }, { id: 89, full_name: null, case_opinion_id: 172, court_rank: "appellate", years_on_bench: 26 }, { id: 90, full_name: "Daniel Gomez", case_opinion_id: 28, court_rank: "appellate", years_on_bench: 21 }, { id: 91, full_name: null, case_opinion_id: 54, court_rank: "district", years_on_bench: 25 }, { id: 92, full_name: "Wei Andersen", case_opinion_id: 92, court_rank: "district", years_on_bench: 20 }, { id: 93, full_name: "Emma Moreau", case_opinion_id: 22, court_rank: "supreme", years_on_bench: 20 }, { id: 94, full_name: "Kai Larsen", case_opinion_id: 200, court_rank: "district", years_on_bench: 21 }, { id: 95, full_name: "Ines Schneider", case_opinion_id: 153, court_rank: "district", years_on_bench: 21 }, { id: 96, full_name: "Carla Hughes", case_opinion_id: 104, court_rank: "supreme", years_on_bench: 15 }, { id: 97, full_name: "Sofia Dubois", case_opinion_id: 154, court_rank: "supreme", years_on_bench: 26 }, { id: 98, full_name: "Carlos Jansen", case_opinion_id: 153, court_rank: "supreme", years_on_bench: 19 }, { id: 99, full_name: "Zara Bennett", case_opinion_id: 195, court_rank: "supreme", years_on_bench: 21 }, { id: 100, full_name: "Lena Park", case_opinion_id: 70, court_rank: "appellate", years_on_bench: 19 }, ], }); await prisma.user_comments.createMany({ data: [ { id: 1, case_opinion_id: 98, user_name: "Nina Ahmed", comment_text: "The customer asked for a change and the refund was confirmed. A manual ticket was completed the same day.", submitted_at: new Date("2022-09-03T08:02:10Z") }, { id: 2, case_opinion_id: 174, user_name: "Zara Demir", comment_text: "A partial record was resolved the same day. The courier confirmed the details and the appointment was reviewed. The courier confirmed the details and the shipment was closed.", submitted_at: new Date("2022-11-20T21:26:09Z") }, { id: 3, case_opinion_id: 119, user_name: null, comment_text: "The appointment was reviewed following a minor review. The supplier reported a standard issue; the order was completed. Support asked for a change and the delivery was resolved.", submitted_at: new Date("2022-08-30T16:14:07Z") }, { id: 4, case_opinion_id: 131, user_name: null, comment_text: "No response from the supplier, so the delivery was closed. A routine refund was updated the same day.", submitted_at: new Date("2021-09-24T21:18:24Z") }, { id: 5, case_opinion_id: 200, user_name: "Zara Flores", comment_text: "The account owner asked for a change and the item was replaced. The booking was updated — incomplete case, no further action.", submitted_at: new Date("2020-04-28T07:45:38Z") }, { id: 6, case_opinion_id: 63, user_name: "James Evans", comment_text: "Support confirmed the details and the ticket was updated. The team confirmed the details and the item was replaced. No response from support, so the ticket was approved. The session was replaced after a manual check.", submitted_at: new Date("2020-03-06T17:05:30Z") }, { id: 7, case_opinion_id: 16, user_name: "Carla Meyer", comment_text: "The transfer was cancelled following a manual review. The transfer was refunded — urgent case, no further action. No response from the courier, so the request was escalated.", submitted_at: new Date("2020-11-23T20:46:05Z") }, { id: 8, case_opinion_id: 176, user_name: "Omar Silva", comment_text: "Support asked for a change and the payment was completed. A late follow-up: the item was approved. No response from the customer, so the transfer was rescheduled.", submitted_at: new Date("2023-09-19T18:09:36Z") }, { id: 9, case_opinion_id: 35, user_name: null, comment_text: null, submitted_at: new Date("2022-09-29T12:47:59Z") }, { id: 10, case_opinion_id: 120, user_name: "Laura Gupta", comment_text: "A partial follow-up: the account was closed. The account owner confirmed the details and the transfer was resolved. The account owner reported a routine issue; the invoice was escalated. The order was processed — late case, no further action.", submitted_at: new Date("2021-05-31T22:24:41Z") }, { id: 11, case_opinion_id: 180, user_name: "Olivia Wilson", comment_text: "The booking was completed after an urgent check. Support confirmed the details and the transfer was confirmed. An incomplete follow-up: the document was cancelled.", submitted_at: new Date("2021-02-18T18:43:31Z") }, { id: 12, case_opinion_id: 118, user_name: "Zara Ruiz", comment_text: "An unusual refund was reopened the same day. The ticket was updated — urgent case, no further action.", submitted_at: new Date("2020-07-09T14:43:12Z") }, { id: 13, case_opinion_id: 37, user_name: "Sven Flores", comment_text: "The invoice was resolved — automatic case, no further action. Flagged as urgent. The reviewer replaced the claim.", submitted_at: new Date("2023-04-09T21:18:44Z") }, { id: 14, case_opinion_id: 144, user_name: null, comment_text: "A standard refund was cancelled the same day. The team confirmed the details and the booking was rejected.", submitted_at: new Date("2021-05-05T19:00:04Z") }, { id: 15, case_opinion_id: 15, user_name: "Rosa Ali", comment_text: "The order was rescheduled — repeat case, no further action. A late request was escalated the same day. The account owner confirmed the details and the order was completed.", submitted_at: new Date("2023-06-02T19:42:06Z") }, { id: 16, case_opinion_id: 53, user_name: "Anna Schneider", comment_text: "The payment was closed following a repeat review. The shipment was resolved — automatic case, no further action.", submitted_at: new Date("2023-12-11T18:26:41Z") }, { id: 17, case_opinion_id: 72, user_name: "Priya Martin", comment_text: "The account owner confirmed the details and the claim was completed. The customer confirmed the details and the shipment was replaced. The payment was processed — routine case, no further action. The account owner confirmed the details and the claim was replaced.", submitted_at: new Date("2022-12-23T16:43:55Z") }, { id: 18, case_opinion_id: 190, user_name: null, comment_text: "A manual follow-up: the delivery was reviewed. A standard shipment was reopened the same day.", submitted_at: new Date("2021-04-11T19:23:11Z") }, { id: 19, case_opinion_id: 34, user_name: "Sara Bennett", comment_text: "A minor follow-up: the item was processed. An operator confirmed the details and the appointment was replaced.", submitted_at: new Date("2022-09-21T12:41:29Z") }, { id: 20, case_opinion_id: 59, user_name: "Sara Diaz", comment_text: "The account was reviewed after a standard check. The courier asked for a change and the claim was confirmed. Flagged as late. The account owner closed the record.", submitted_at: new Date("2023-12-09T14:09:11Z") }, { id: 21, case_opinion_id: 127, user_name: "Ben Walker", comment_text: "Flagged as manual. The supplier refunded the invoice. The supplier reported a duplicate issue; the claim was resolved.", submitted_at: new Date("2021-04-17T07:20:54Z") }, { id: 22, case_opinion_id: 66, user_name: "Wei Kaya", comment_text: "The payment was rescheduled — routine case, no further action. The transfer was updated after a manual check.", submitted_at: new Date("2020-04-14T20:44:33Z") }, { id: 23, case_opinion_id: 136, user_name: "Wei Yilmaz", comment_text: "An incomplete document was confirmed the same day. The refund was reviewed following a partial review. The record was reopened after a repeat check.", submitted_at: new Date("2023-09-04T19:37:04Z") }, { id: 24, case_opinion_id: 149, user_name: "Arjun Singh", comment_text: "The invoice was escalated after a manual check. The payment was cancelled — standard case, no further action. No response from support, so the record was approved.", submitted_at: new Date("2021-09-13T00:00:30Z") }, { id: 25, case_opinion_id: 85, user_name: "Lina Schmidt", comment_text: "The supplier asked for a change and the session was escalated. Support reported an unusual issue; the transfer was rescheduled. Flagged as urgent. The supplier resolved the ticket. The courier reported a manual issue; the delivery was closed.", submitted_at: new Date("2022-02-06T07:54:55Z") }, { id: 26, case_opinion_id: 110, user_name: "James Klein", comment_text: "Flagged as routine. The supplier closed the record. Flagged as standard. The account owner completed the invoice. Flagged as urgent. Support reopened the invoice.", submitted_at: new Date("2020-11-10T15:38:18Z") }, { id: 27, case_opinion_id: 4, user_name: "Elena Schmidt", comment_text: "The appointment was processed after a late check. The request was completed — partial case, no further action. A routine follow-up: the ticket was rescheduled.", submitted_at: new Date("2020-03-28T17:41:45Z") }, { id: 28, case_opinion_id: 188, user_name: "Diego Young", comment_text: "No response from the account owner, so the booking was escalated. A manual invoice was approved the same day. The session was approved after a minor check. The shipment was replaced — automatic case, no further action.", submitted_at: new Date("2022-03-10T17:45:35Z") }, { id: 29, case_opinion_id: 79, user_name: "Omar Silva", comment_text: "The transfer was approved after a partial check. The account owner reported a routine issue; the appointment was resolved. The document was approved after a repeat check.", submitted_at: new Date("2022-11-30T08:21:39Z") }, { id: 30, case_opinion_id: 87, user_name: "Sara Schmidt", comment_text: "Flagged as unusual. The supplier refunded the invoice. The customer asked for a change and the shipment was updated. An unusual booking was rejected the same day. No response from support, so the ticket was delayed.", submitted_at: new Date("2020-07-31T09:06:26Z") }, { id: 31, case_opinion_id: 140, user_name: "Oscar Gupta", comment_text: "Flagged as partial. Support refunded the transfer. Flagged as automatic. Support processed the appointment. The supplier reported a standard issue; the account was completed.", submitted_at: new Date("2023-07-26T11:18:59Z") }, { id: 32, case_opinion_id: 184, user_name: null, comment_text: "No response from an operator, so the record was escalated. The shipment was refunded — standard case, no further action. A routine item was closed the same day. The claim was processed — repeat case, no further action.", submitted_at: new Date("2022-07-11T14:31:42Z") }, { id: 33, case_opinion_id: 80, user_name: "Sofia Baker", comment_text: "A manual follow-up: the transfer was approved. The invoice was refunded after a repeat check.", submitted_at: new Date("2020-03-26T19:31:30Z") }, { id: 34, case_opinion_id: 111, user_name: "Hannah Bauer", comment_text: null, submitted_at: new Date("2021-05-06T22:46:02Z") }, { id: 35, case_opinion_id: 8, user_name: "Lucas Reyes", comment_text: "The supplier asked for a change and the invoice was approved. Flagged as minor. An operator approved the transfer. A late follow-up: the order was rejected. No response from the supplier, so the report was completed.", submitted_at: new Date("2022-09-29T19:04:15Z") }, { id: 36, case_opinion_id: 114, user_name: "Mohamed Hassan", comment_text: "Support reported an automatic issue; the refund was replaced. The team asked for a change and the document was rejected. A minor follow-up: the payment was escalated.", submitted_at: new Date("2023-01-29T02:21:00Z") }, { id: 37, case_opinion_id: 77, user_name: "Zoe Patel", comment_text: "Support asked for a change and the document was replaced. An automatic follow-up: the account was completed. No response from an operator, so the report was completed. An incomplete report was completed the same day.", submitted_at: new Date("2022-09-24T12:19:25Z") }, { id: 38, case_opinion_id: 33, user_name: "Anna Larsen", comment_text: "No response from support, so the item was cancelled. The courier reported a manual issue; the report was escalated.", submitted_at: new Date("2021-03-25T23:17:46Z") }, { id: 39, case_opinion_id: 25, user_name: "Anna Singh", comment_text: "Flagged as standard. An operator escalated the invoice. An unusual request was resolved the same day. A routine session was reopened the same day.", submitted_at: new Date("2022-08-26T18:02:09Z") }, { id: 40, case_opinion_id: 177, user_name: "Daniel Hassan", comment_text: "The reviewer asked for a change and the request was delayed. Flagged as manual. The courier refunded the payment. The invoice was refunded — routine case, no further action.", submitted_at: new Date("2021-08-27T20:47:32Z") }, { id: 41, case_opinion_id: 2, user_name: "Emma Murphy", comment_text: "The customer confirmed the details and the ticket was updated. The item was approved following a partial review.", submitted_at: new Date("2021-04-28T23:23:48Z") }, { id: 42, case_opinion_id: 71, user_name: "Mohamed Larsen", comment_text: "No response from the supplier, so the request was cancelled. The record was replaced following a repeat review. The supplier reported a minor issue; the document was reopened.", submitted_at: new Date("2023-12-28T14:52:34Z") }, { id: 43, case_opinion_id: 41, user_name: "Carlos Dubois", comment_text: "The team confirmed the details and the order was updated. The supplier asked for a change and the refund was reviewed.", submitted_at: new Date("2023-06-22T06:42:17Z") }, { id: 44, case_opinion_id: 41, user_name: "Mohamed Murphy", comment_text: "A late account was reopened the same day. The account owner reported a standard issue; the document was delayed. The courier asked for a change and the document was processed.", submitted_at: new Date("2023-07-08T08:41:28Z") }, { id: 45, case_opinion_id: 64, user_name: "Maja Murphy", comment_text: "The supplier reported a manual issue; the account was refunded. An operator asked for a change and the report was reopened.", submitted_at: new Date("2022-04-07T17:41:21Z") }, { id: 46, case_opinion_id: 18, user_name: null, comment_text: "The request was cancelled following a routine review. Flagged as urgent. Support updated the invoice. The item was cancelled — urgent case, no further action. An automatic follow-up: the account was confirmed.", submitted_at: new Date("2021-12-05T22:57:18Z") }, { id: 47, case_opinion_id: 103, user_name: "Arjun Young", comment_text: "An unusual invoice was updated the same day. The account was confirmed — standard case, no further action. The document was refunded — standard case, no further action. No response from the supplier, so the session was processed.", submitted_at: new Date("2020-10-24T17:01:07Z") }, { id: 48, case_opinion_id: 92, user_name: "Chen Kowalski", comment_text: "The team confirmed the details and the claim was completed. Support reported an automatic issue; the payment was completed.", submitted_at: new Date("2020-09-15T13:30:54Z") }, { id: 49, case_opinion_id: 97, user_name: null, comment_text: "The request was resolved — automatic case, no further action. A duplicate follow-up: the record was reopened. The reviewer reported a late issue; the ticket was escalated.", submitted_at: new Date("2023-11-21T08:17:45Z") }, { id: 50, case_opinion_id: 124, user_name: "Nina Khan", comment_text: "Flagged as minor. The team completed the ticket. The shipment was confirmed after a late check. The refund was resolved — late case, no further action.", submitted_at: new Date("2021-12-01T20:00:25Z") }, { id: 51, case_opinion_id: 108, user_name: "Ravi Bennett", comment_text: "The document was refunded following a partial review. The reviewer reported a minor issue; the booking was cancelled. The order was closed following a manual review.", submitted_at: new Date("2022-05-01T09:28:44Z") }, { id: 52, case_opinion_id: 8, user_name: "Nour Smith", comment_text: "The booking was approved following a partial review. The supplier confirmed the details and the request was completed. No response from support, so the delivery was cancelled.", submitted_at: new Date("2022-02-13T07:34:31Z") }, { id: 53, case_opinion_id: 111, user_name: null, comment_text: "The supplier confirmed the details and the document was completed. A minor follow-up: the payment was resolved. The courier asked for a change and the transfer was rescheduled.", submitted_at: new Date("2020-05-28T13:28:03Z") }, { id: 54, case_opinion_id: 162, user_name: "Tomas Wilson", comment_text: "Flagged as late. The reviewer resolved the shipment. A repeat follow-up: the ticket was reopened. The team asked for a change and the session was replaced.", submitted_at: new Date("2023-07-09T00:38:43Z") }, { id: 55, case_opinion_id: 92, user_name: "Nina Gomez", comment_text: "No response from the supplier, so the refund was cancelled. The customer reported a routine issue; the request was refunded. No response from the reviewer, so the shipment was cancelled. A routine order was completed the same day.", submitted_at: new Date("2022-10-20T15:44:39Z") }, { id: 56, case_opinion_id: 181, user_name: null, comment_text: null, submitted_at: new Date("2021-04-22T20:50:24Z") }, { id: 57, case_opinion_id: 47, user_name: "Diego Nakamura", comment_text: "Flagged as incomplete. The courier resolved the account. The invoice was reviewed following a standard review. The order was cancelled — routine case, no further action.", submitted_at: new Date("2022-04-03T18:30:27Z") }, { id: 58, case_opinion_id: 1, user_name: "Noah Murphy", comment_text: "The account owner reported a manual issue; the booking was approved. The appointment was refunded following a manual review. The delivery was closed following a standard review.", submitted_at: new Date("2021-09-25T10:59:15Z") }, { id: 59, case_opinion_id: 170, user_name: "Laura Klein", comment_text: "No response from the customer, so the record was rejected. The session was cancelled — standard case, no further action. An automatic follow-up: the item was updated.", submitted_at: new Date("2021-10-28T15:15:25Z") }, { id: 60, case_opinion_id: 102, user_name: "Emma Murphy", comment_text: "The supplier reported a late issue; the payment was cancelled. Flagged as repeat. The team reopened the shipment.", submitted_at: new Date("2022-11-24T14:38:44Z") }, { id: 61, case_opinion_id: 112, user_name: "Pedro Evans", comment_text: "An operator asked for a change and the transfer was completed. The booking was escalated following an urgent review. The reviewer confirmed the details and the shipment was rescheduled.", submitted_at: new Date("2022-05-08T12:43:53Z") }, { id: 62, case_opinion_id: 158, user_name: "Olivia Gomez", comment_text: "The refund was rejected — standard case, no further action. The report was completed — manual case, no further action. The request was escalated after an urgent check.", submitted_at: new Date("2022-08-21T15:59:11Z") }, { id: 63, case_opinion_id: 49, user_name: "Fatima Moreau", comment_text: "An operator asked for a change and the payment was processed. A standard record was replaced the same day. The team confirmed the details and the request was resolved.", submitted_at: new Date("2022-07-26T13:59:51Z") }, { id: 64, case_opinion_id: 68, user_name: "Theo Diaz", comment_text: "An incomplete ticket was completed the same day. The report was escalated — urgent case, no further action. The team reported a routine issue; the record was refunded. The report was approved after an incomplete check.", submitted_at: new Date("2021-06-17T18:46:48Z") }, { id: 65, case_opinion_id: 18, user_name: "Amir Almeida", comment_text: "Support asked for a change and the payment was reopened. The team reported a standard issue; the item was processed.", submitted_at: new Date("2020-08-11T18:34:15Z") }, { id: 66, case_opinion_id: 68, user_name: "Alice Martin", comment_text: "The transfer was rejected — duplicate case, no further action. Flagged as unusual. The reviewer approved the booking. A partial report was escalated the same day.", submitted_at: new Date("2023-04-07T15:51:05Z") }, { id: 67, case_opinion_id: 125, user_name: "Olivia Cruz", comment_text: "No response from the account owner, so the record was confirmed. An automatic follow-up: the document was rejected. The session was escalated following a duplicate review.", submitted_at: new Date("2022-10-27T21:06:46Z") }, { id: 68, case_opinion_id: 50, user_name: "Maria Smith", comment_text: "No response from the courier, so the item was completed. Support reported a minor issue; the transfer was closed.", submitted_at: new Date("2020-11-24T18:58:27Z") }, { id: 69, case_opinion_id: 79, user_name: "Alice Taylor", comment_text: "The payment was reviewed — incomplete case, no further action. An automatic ticket was rejected the same day. The shipment was confirmed after a minor check. The courier asked for a change and the delivery was processed.", submitted_at: new Date("2020-09-02T15:02:14Z") }, { id: 70, case_opinion_id: 55, user_name: null, comment_text: "The account was approved after a routine check. The delivery was reviewed following a late review. A routine order was rejected the same day.", submitted_at: new Date("2022-04-27T10:09:46Z") }, { id: 71, case_opinion_id: 12, user_name: "Alice Wilson", comment_text: null, submitted_at: new Date("2022-03-13T19:08:31Z") }, { id: 72, case_opinion_id: 181, user_name: "Jack Wilson", comment_text: "The document was rejected following a routine review. The report was delayed following an urgent review. The account owner reported a repeat issue; the transfer was replaced.", submitted_at: new Date("2023-04-18T10:08:03Z") }, { id: 73, case_opinion_id: 192, user_name: "Rafael Cruz", comment_text: "The item was reopened following a manual review. The team reported an automatic issue; the appointment was reviewed. No response from the customer, so the request was rescheduled.", submitted_at: new Date("2022-03-06T20:50:21Z") }, { id: 74, case_opinion_id: 176, user_name: "Mohamed Walker", comment_text: "A standard follow-up: the account was escalated. The account owner asked for a change and the request was replaced. A partial follow-up: the ticket was completed.", submitted_at: new Date("2023-08-19T11:16:54Z") }, { id: 75, case_opinion_id: 142, user_name: "Sven Fischer", comment_text: null, submitted_at: new Date("2022-12-13T12:33:00Z") }, { id: 76, case_opinion_id: 80, user_name: "Deniz Evans", comment_text: "Support reported a standard issue; the record was reopened. The customer asked for a change and the payment was rescheduled. The courier asked for a change and the account was confirmed.", submitted_at: new Date("2022-11-28T14:05:58Z") }, { id: 77, case_opinion_id: 157, user_name: "Grace Gupta", comment_text: "The account owner confirmed the details and the record was refunded. The supplier reported an incomplete issue; the record was confirmed. The reviewer confirmed the details and the ticket was completed.", submitted_at: new Date("2023-08-31T07:54:44Z") }, { id: 78, case_opinion_id: 166, user_name: "Sara Silva", comment_text: "A manual follow-up: the report was delayed. Support reported a routine issue; the record was refunded. The record was escalated after an urgent check. Support confirmed the details and the record was escalated.", submitted_at: new Date("2020-10-27T17:14:01Z") }, { id: 79, case_opinion_id: 75, user_name: "Ivan Wagner", comment_text: "The shipment was closed after an incomplete check. The payment was escalated — repeat case, no further action.", submitted_at: new Date("2022-02-01T08:04:05Z") }, { id: 80, case_opinion_id: 166, user_name: "Chloe Gupta", comment_text: "Support reported a repeat issue; the shipment was escalated. Flagged as automatic. The reviewer rejected the refund. The supplier reported a repeat issue; the claim was refunded. A routine report was processed the same day.", submitted_at: new Date("2021-12-13T11:17:24Z") }, { id: 81, case_opinion_id: 71, user_name: "Zara Wright", comment_text: "The account owner asked for a change and the order was replaced. The record was confirmed after a routine check.", submitted_at: new Date("2020-10-28T14:02:47Z") }, { id: 82, case_opinion_id: 178, user_name: "Daniel Ali", comment_text: "The refund was delayed — partial case, no further action. Support reported an automatic issue; the account was processed.", submitted_at: new Date("2022-10-22T17:39:34Z") }, { id: 83, case_opinion_id: 159, user_name: "Zoe Larsen", comment_text: null, submitted_at: new Date("2021-04-08T17:01:55Z") }, { id: 84, case_opinion_id: 56, user_name: "Nina Chen", comment_text: "The account owner confirmed the details and the request was closed. A standard transfer was completed the same day. The shipment was rescheduled after an automatic check. The payment was reviewed — late case, no further action.", submitted_at: new Date("2022-05-20T20:40:07Z") }, { id: 85, case_opinion_id: 109, user_name: "Jonas Chen", comment_text: "The team asked for a change and the payment was updated. A manual refund was reviewed the same day.", submitted_at: new Date("2020-03-20T19:15:10Z") }, { id: 86, case_opinion_id: 69, user_name: null, comment_text: "No response from support, so the request was escalated. The appointment was reopened after a late check. The payment was rejected — incomplete case, no further action. The invoice was delayed after a duplicate check.", submitted_at: new Date("2021-03-05T13:44:58Z") }, { id: 87, case_opinion_id: 180, user_name: "Mei Reyes", comment_text: "An unusual payment was resolved the same day. No response from the account owner, so the order was closed. The document was reviewed after a late check. The customer confirmed the details and the transfer was escalated.", submitted_at: new Date("2021-02-09T15:45:12Z") }, { id: 88, case_opinion_id: 110, user_name: "Mohamed Bauer", comment_text: "The shipment was resolved — manual case, no further action. A manual follow-up: the claim was completed. The customer asked for a change and the claim was approved. The delivery was updated following a duplicate review.", submitted_at: new Date("2020-07-13T08:33:14Z") }, { id: 89, case_opinion_id: 68, user_name: "Priya Andersen", comment_text: "No response from the courier, so the item was refunded. A duplicate order was confirmed the same day. A routine follow-up: the request was rejected.", submitted_at: new Date("2020-02-07T18:29:01Z") }, { id: 90, case_opinion_id: 187, user_name: "Elena Costa", comment_text: "The document was confirmed — routine case, no further action. Flagged as unusual. Support escalated the appointment.", submitted_at: new Date("2021-08-14T19:32:57Z") }, { id: 91, case_opinion_id: 189, user_name: null, comment_text: null, submitted_at: new Date("2020-02-01T13:24:59Z") }, { id: 92, case_opinion_id: 41, user_name: "Paula Mendes", comment_text: "An incomplete follow-up: the item was approved. The payment was rescheduled after an urgent check.", submitted_at: new Date("2020-08-13T10:45:29Z") }, { id: 93, case_opinion_id: 10, user_name: "Ines Khan", comment_text: "An operator confirmed the details and the ticket was rejected. The report was resolved — urgent case, no further action.", submitted_at: new Date("2021-04-26T21:13:24Z") }, { id: 94, case_opinion_id: 144, user_name: "Ibrahim Johnson", comment_text: null, submitted_at: new Date("2021-01-26T15:20:11Z") }, { id: 95, case_opinion_id: 114, user_name: "Liam Hughes", comment_text: "Flagged as unusual. The customer escalated the refund. No response from an operator, so the transfer was escalated.", submitted_at: new Date("2023-09-19T13:51:25Z") }, { id: 96, case_opinion_id: 21, user_name: null, comment_text: "An urgent follow-up: the delivery was reopened. A routine request was cancelled the same day.", submitted_at: new Date("2022-10-23T18:23:50Z") }, { id: 97, case_opinion_id: 32, user_name: "Liam Walker", comment_text: "Support reported a partial issue; the booking was delayed. The booking was closed after a partial check. The refund was cancelled after a late check.", submitted_at: new Date("2020-03-13T09:04:27Z") }, { id: 98, case_opinion_id: 23, user_name: "Carla Torres", comment_text: "The supplier confirmed the details and the delivery was confirmed. Flagged as partial. Support delayed the item. The report was rejected after a repeat check. The courier asked for a change and the refund was cancelled.", submitted_at: new Date("2020-07-30T21:55:56Z") }, { id: 99, case_opinion_id: 13, user_name: "Daniel Brown", comment_text: "The reviewer confirmed the details and the ticket was refunded. An operator reported a repeat issue; the delivery was reopened. The refund was refunded following an incomplete review. An operator asked for a change and the delivery was approved.", submitted_at: new Date("2020-04-29T10:40:03Z") }, { id: 100, case_opinion_id: 6, user_name: "Amir Cruz", comment_text: "The session was rejected after an urgent check. Flagged as automatic. Support confirmed the document. The shipment was refunded — repeat case, no further action.", submitted_at: new Date("2022-01-25T22:42:26Z") }, { id: 101, case_opinion_id: 143, user_name: "Tariq Zhang", comment_text: "An unusual document was delayed the same day. A standard follow-up: the transfer was refunded. The payment was resolved after a repeat check. The payment was closed following a routine review.", submitted_at: new Date("2020-09-11T14:39:46Z") }, { id: 102, case_opinion_id: 193, user_name: "Ruby Hughes", comment_text: "A manual follow-up: the report was escalated. An operator reported a partial issue; the account was escalated. The payment was processed following an unusual review.", submitted_at: new Date("2020-09-28T14:06:42Z") }, { id: 103, case_opinion_id: 180, user_name: "Ravi Wagner", comment_text: "Flagged as incomplete. The reviewer completed the refund. The refund was approved following an unusual review. The account owner asked for a change and the shipment was processed.", submitted_at: new Date("2020-12-25T15:49:55Z") }, { id: 104, case_opinion_id: 107, user_name: "Selin Young", comment_text: "The courier reported an unusual issue; the transfer was escalated. An operator confirmed the details and the session was confirmed. No response from the customer, so the transfer was approved. The reviewer asked for a change and the transfer was processed.", submitted_at: new Date("2022-01-25T00:26:16Z") }, { id: 105, case_opinion_id: 163, user_name: "Theo Moreau", comment_text: "An incomplete document was closed the same day. Support reported a manual issue; the ticket was escalated. A standard refund was processed the same day. A late follow-up: the shipment was resolved.", submitted_at: new Date("2022-06-11T09:18:32Z") }, { id: 106, case_opinion_id: 141, user_name: "Omar Nakamura", comment_text: "The supplier asked for a change and the record was reopened. No response from the account owner, so the appointment was approved. The reviewer confirmed the details and the claim was refunded.", submitted_at: new Date("2023-02-15T10:56:29Z") }, { id: 107, case_opinion_id: 28, user_name: "Lina Diaz", comment_text: "The payment was rejected — incomplete case, no further action. No response from the team, so the item was replaced. The item was reopened after a standard check.", submitted_at: new Date("2022-08-08T23:39:34Z") }, { id: 108, case_opinion_id: 143, user_name: "Maria Ali", comment_text: null, submitted_at: new Date("2021-02-23T09:39:21Z") }, { id: 109, case_opinion_id: 182, user_name: "Oscar Murphy", comment_text: "An unusual follow-up: the invoice was processed. Flagged as standard. The reviewer cancelled the invoice. The appointment was rescheduled following a minor review. Flagged as incomplete. The reviewer rescheduled the shipment.", submitted_at: new Date("2020-04-27T15:30:00Z") }, { id: 110, case_opinion_id: 46, user_name: "Omar Smith", comment_text: "The record was updated after a repeat check. The claim was confirmed after an unusual check.", submitted_at: new Date("2023-10-15T19:03:03Z") }, { id: 111, case_opinion_id: 182, user_name: "Maya Schmidt", comment_text: "No response from an operator, so the item was reviewed. The team asked for a change and the document was processed. The team reported a routine issue; the record was resolved.", submitted_at: new Date("2022-11-03T12:57:14Z") }, { id: 112, case_opinion_id: 36, user_name: "Hannah Costa", comment_text: "The reviewer reported a late issue; the account was completed. A routine order was completed the same day. The document was closed — incomplete case, no further action.", submitted_at: new Date("2021-06-02T22:28:17Z") }, { id: 113, case_opinion_id: 56, user_name: "Ibrahim Costa", comment_text: "The session was updated following a partial review. A routine account was reviewed the same day.", submitted_at: new Date("2020-11-27T08:05:29Z") }, { id: 114, case_opinion_id: 73, user_name: "Emma Hughes", comment_text: null, submitted_at: new Date("2023-02-10T10:37:43Z") }, { id: 115, case_opinion_id: 66, user_name: "Omar Carter", comment_text: "The courier asked for a change and the session was refunded. The reviewer asked for a change and the request was rescheduled. The claim was rescheduled after a repeat check.", submitted_at: new Date("2023-01-08T21:35:24Z") }, { id: 116, case_opinion_id: 73, user_name: "Selin Nakamura", comment_text: "A late follow-up: the transfer was confirmed. No response from the courier, so the invoice was processed. No response from the customer, so the claim was approved.", submitted_at: new Date("2021-07-22T09:02:47Z") }, { id: 117, case_opinion_id: 167, user_name: "Ethan Hoffmann", comment_text: "The supplier reported a repeat issue; the refund was escalated. The invoice was confirmed following a late review.", submitted_at: new Date("2021-01-11T14:55:44Z") }, { id: 118, case_opinion_id: 49, user_name: "Pedro Adams", comment_text: "An incomplete follow-up: the ticket was updated. The team confirmed the details and the item was reviewed.", submitted_at: new Date("2022-11-13T15:54:12Z") }, { id: 119, case_opinion_id: 93, user_name: "Ravi Schmidt", comment_text: "An operator asked for a change and the shipment was refunded. The document was processed after an unusual check. The supplier asked for a change and the refund was reopened. No response from an operator, so the transfer was replaced.", submitted_at: new Date("2022-03-28T15:46:31Z") }, { id: 120, case_opinion_id: 45, user_name: "Mia Baker", comment_text: "The supplier asked for a change and the order was rescheduled. The document was refunded — routine case, no further action. The delivery was closed after a standard check. The record was reopened — incomplete case, no further action.", submitted_at: new Date("2022-06-29T19:23:46Z") }, { id: 121, case_opinion_id: 118, user_name: "Zara Ibrahim", comment_text: "The reviewer confirmed the details and the appointment was reviewed. The document was cancelled after an urgent check. A manual ticket was confirmed the same day.", submitted_at: new Date("2022-06-04T10:00:18Z") }, { id: 122, case_opinion_id: 14, user_name: "Victor Demir", comment_text: "The reviewer asked for a change and the session was escalated. An incomplete follow-up: the booking was refunded. A duplicate delivery was refunded the same day.", submitted_at: new Date("2023-03-21T13:00:56Z") }, { id: 123, case_opinion_id: 34, user_name: "Jonas Lee", comment_text: "An incomplete follow-up: the request was approved. The reviewer asked for a change and the booking was updated. No response from the courier, so the record was resolved.", submitted_at: new Date("2023-03-03T17:41:10Z") }, { id: 124, case_opinion_id: 199, user_name: "Mia Lee", comment_text: "The session was updated — incomplete case, no further action. An operator confirmed the details and the order was reviewed.", submitted_at: new Date("2020-03-29T22:07:05Z") }, { id: 125, case_opinion_id: 65, user_name: "Andre Wagner", comment_text: "The supplier confirmed the details and the report was replaced. An operator confirmed the details and the invoice was rescheduled. A standard delivery was approved the same day. The appointment was rejected after a partial check.", submitted_at: new Date("2023-03-21T19:42:03Z") }, { id: 126, case_opinion_id: 95, user_name: "Tariq Flores", comment_text: "Flagged as incomplete. An operator completed the invoice. Flagged as partial. The customer rescheduled the invoice.", submitted_at: new Date("2023-12-08T06:20:07Z") }, { id: 127, case_opinion_id: 194, user_name: "Selin Weber", comment_text: "The invoice was rejected — minor case, no further action. The courier asked for a change and the session was completed.", submitted_at: new Date("2022-05-13T11:54:57Z") }, { id: 128, case_opinion_id: 185, user_name: "Carla Tanaka", comment_text: null, submitted_at: new Date("2023-05-21T07:49:50Z") }, { id: 129, case_opinion_id: 74, user_name: "Felix Wright", comment_text: "An urgent item was cancelled the same day. The appointment was replaced following a duplicate review. Support reported a late issue; the booking was resolved.", submitted_at: new Date("2021-10-19T22:12:43Z") }, { id: 130, case_opinion_id: 75, user_name: "Pedro Moreau", comment_text: "A standard refund was refunded the same day. No response from support, so the transfer was rejected.", submitted_at: new Date("2022-04-13T18:45:08Z") }, { id: 131, case_opinion_id: 39, user_name: "Jack Ali", comment_text: null, submitted_at: new Date("2022-04-24T14:36:38Z") }, { id: 132, case_opinion_id: 190, user_name: "Mohamed Weber", comment_text: "Flagged as automatic. The reviewer delayed the appointment. A partial appointment was replaced the same day.", submitted_at: new Date("2021-09-08T19:50:06Z") }, { id: 133, case_opinion_id: 197, user_name: "Uma Adams", comment_text: "Flagged as routine. Support confirmed the payment. The document was delayed following an unusual review.", submitted_at: new Date("2022-09-09T10:26:36Z") }, { id: 134, case_opinion_id: 127, user_name: "Chen Zhang", comment_text: "The item was rejected after a minor check. No response from support, so the payment was completed. The appointment was confirmed following a repeat review.", submitted_at: new Date("2022-04-30T17:18:41Z") }, { id: 135, case_opinion_id: 91, user_name: "Tomas Flores", comment_text: "The request was delayed after a manual check. The refund was confirmed following an incomplete review. The ticket was delayed after a manual check. A standard request was closed the same day.", submitted_at: new Date("2021-11-22T20:33:48Z") }, { id: 136, case_opinion_id: 36, user_name: "Sara Young", comment_text: "Flagged as repeat. The reviewer approved the payment. An automatic claim was approved the same day.", submitted_at: new Date("2023-09-24T18:43:42Z") }, { id: 137, case_opinion_id: 175, user_name: "Carlos Meyer", comment_text: "An operator asked for a change and the transfer was completed. The delivery was delayed following a partial review. The booking was rejected following an automatic review.", submitted_at: new Date("2023-11-02T12:26:11Z") }, { id: 138, case_opinion_id: 63, user_name: "Nina Chen", comment_text: "The payment was rescheduled after an incomplete check. The document was confirmed — repeat case, no further action. A minor follow-up: the request was escalated. No response from the team, so the booking was reviewed.", submitted_at: new Date("2022-03-13T01:28:30Z") }, { id: 139, case_opinion_id: 98, user_name: null, comment_text: "No response from the team, so the order was closed. The payment was completed following a partial review.", submitted_at: new Date("2020-06-24T19:02:22Z") }, { id: 140, case_opinion_id: 39, user_name: "Zoe Davis", comment_text: null, submitted_at: new Date("2020-10-29T18:07:15Z") }, { id: 141, case_opinion_id: 192, user_name: "Deniz Wang", comment_text: null, submitted_at: new Date("2023-12-08T08:47:10Z") }, { id: 142, case_opinion_id: 78, user_name: "Hana Kim", comment_text: "A duplicate follow-up: the document was updated. The supplier confirmed the details and the account was refunded. Flagged as urgent. The account owner completed the payment.", submitted_at: new Date("2020-12-01T15:20:40Z") }, { id: 143, case_opinion_id: 163, user_name: "Jack Meyer", comment_text: "No response from an operator, so the claim was rescheduled. Flagged as late. The account owner delayed the payment. A repeat follow-up: the appointment was rejected.", submitted_at: new Date("2023-11-09T20:17:23Z") }, { id: 144, case_opinion_id: 17, user_name: null, comment_text: "The claim was updated after a routine check. A duplicate delivery was resolved the same day. The ticket was updated — manual case, no further action.", submitted_at: new Date("2022-05-25T13:39:11Z") }, { id: 145, case_opinion_id: 82, user_name: "Felix Almeida", comment_text: "The session was delayed after a manual check. The courier asked for a change and the delivery was rejected. The account owner asked for a change and the delivery was refunded.", submitted_at: new Date("2021-07-05T03:20:21Z") }, { id: 146, case_opinion_id: 74, user_name: "Ivan Almeida", comment_text: "No response from the team, so the item was refunded. The account owner reported a standard issue; the report was confirmed. A routine order was reviewed the same day.", submitted_at: new Date("2020-09-12T22:35:15Z") }, { id: 147, case_opinion_id: 187, user_name: "Wei Kaya", comment_text: "The order was rescheduled after an automatic check. The invoice was processed following an incomplete review. Flagged as manual. The team rescheduled the session. The account owner asked for a change and the session was reopened.", submitted_at: new Date("2021-05-03T08:03:49Z") }, { id: 148, case_opinion_id: 38, user_name: "Karim Martin", comment_text: "A late follow-up: the item was reopened. The order was reopened following a repeat review. No response from the account owner, so the refund was approved. An operator reported a repeat issue; the claim was closed.", submitted_at: new Date("2022-06-20T14:47:42Z") }, { id: 149, case_opinion_id: 48, user_name: "Maria Ahmed", comment_text: "No response from an operator, so the session was resolved. The claim was completed following a partial review.", submitted_at: new Date("2020-03-03T18:21:10Z") }, { id: 150, case_opinion_id: 179, user_name: "Sven Martin", comment_text: "The courier asked for a change and the appointment was cancelled. No response from the supplier, so the ticket was approved. The team asked for a change and the ticket was rejected.", submitted_at: new Date("2022-03-20T11:55:03Z") }, { id: 151, case_opinion_id: 61, user_name: "Tariq Kim", comment_text: "The document was completed after a duplicate check. A late follow-up: the invoice was rescheduled.", submitted_at: new Date("2020-09-20T23:37:00Z") }, { id: 152, case_opinion_id: 63, user_name: "Sofia Pereira", comment_text: null, submitted_at: new Date("2022-04-03T12:04:58Z") }, { id: 153, case_opinion_id: 73, user_name: "Lucas Kowalski", comment_text: "The transfer was processed after a standard check. Flagged as incomplete. An operator reviewed the shipment. The supplier asked for a change and the refund was cancelled.", submitted_at: new Date("2022-02-01T10:59:29Z") }, { id: 154, case_opinion_id: 125, user_name: "Uma Smith", comment_text: "The invoice was resolved following a routine review. The reviewer confirmed the details and the record was completed.", submitted_at: new Date("2022-02-16T17:39:35Z") }, { id: 155, case_opinion_id: 61, user_name: "Selin Johnson", comment_text: "The claim was completed following a routine review. No response from an operator, so the account was confirmed. Flagged as urgent. The customer escalated the session. The delivery was escalated following a standard review.", submitted_at: new Date("2020-03-20T12:53:36Z") }, { id: 156, case_opinion_id: 101, user_name: "Olivia Gupta", comment_text: "A partial follow-up: the transfer was resolved. No response from the account owner, so the shipment was updated. The customer confirmed the details and the payment was replaced.", submitted_at: new Date("2023-09-13T17:47:02Z") }, { id: 157, case_opinion_id: 89, user_name: "Kai Bauer", comment_text: "The shipment was updated — late case, no further action. The delivery was closed after a manual check.", submitted_at: new Date("2023-12-16T16:31:02Z") }, { id: 158, case_opinion_id: 90, user_name: "Ana Jensen", comment_text: "The team confirmed the details and the booking was refunded. No response from the account owner, so the delivery was rejected. The request was escalated following an automatic review. The team asked for a change and the transfer was rejected.", submitted_at: new Date("2020-06-26T12:47:59Z") }, { id: 159, case_opinion_id: 34, user_name: "Omar Martin", comment_text: "The session was completed — incomplete case, no further action. The team asked for a change and the booking was closed. An urgent follow-up: the ticket was cancelled. The team reported an urgent issue; the report was refunded.", submitted_at: new Date("2020-04-14T19:46:51Z") }, { id: 160, case_opinion_id: 187, user_name: "Ben Demir", comment_text: "An operator confirmed the details and the item was refunded. Flagged as automatic. The account owner completed the record. The team confirmed the details and the item was resolved.", submitted_at: new Date("2022-02-14T18:27:10Z") }, { id: 161, case_opinion_id: 9, user_name: "Karim Schmidt", comment_text: "The supplier reported a manual issue; the transfer was closed. A manual invoice was delayed the same day. The booking was cancelled after a partial check.", submitted_at: new Date("2020-02-25T21:15:11Z") }, { id: 162, case_opinion_id: 75, user_name: "Mohamed Mendes", comment_text: "An operator asked for a change and the ticket was delayed. Flagged as duplicate. The team replaced the refund. The transfer was delayed after a late check. No response from the customer, so the document was reviewed.", submitted_at: new Date("2023-05-19T13:33:37Z") }, { id: 163, case_opinion_id: 108, user_name: null, comment_text: "The account was reviewed — routine case, no further action. The appointment was delayed following a manual review. A repeat refund was closed the same day. The report was approved — standard case, no further action.", submitted_at: new Date("2023-05-12T17:46:36Z") }, { id: 164, case_opinion_id: 64, user_name: null, comment_text: "The payment was completed following a routine review. Flagged as minor. The team completed the transfer. A late follow-up: the account was resolved.", submitted_at: new Date("2023-05-31T20:13:45Z") }, { id: 165, case_opinion_id: 31, user_name: "David Garcia", comment_text: "Flagged as duplicate. An operator delayed the item. The invoice was reopened — repeat case, no further action. The team asked for a change and the appointment was reopened. Support reported an urgent issue; the booking was resolved.", submitted_at: new Date("2022-07-06T18:46:32Z") }, { id: 166, case_opinion_id: 77, user_name: "Priya Meyer", comment_text: "The reviewer asked for a change and the account was confirmed. The report was resolved following a duplicate review. A duplicate follow-up: the record was processed. A standard follow-up: the transfer was rejected.", submitted_at: new Date("2020-03-29T18:04:05Z") }, { id: 167, case_opinion_id: 42, user_name: "Ana Gupta", comment_text: "An automatic invoice was cancelled the same day. The customer reported an urgent issue; the request was processed. An incomplete account was delayed the same day.", submitted_at: new Date("2023-05-10T13:58:06Z") }, { id: 168, case_opinion_id: 122, user_name: "Hugo Baker", comment_text: "A late record was closed the same day. The shipment was rescheduled following an incomplete review. Support confirmed the details and the item was processed. The order was rejected — manual case, no further action.", submitted_at: new Date("2023-08-16T18:02:36Z") }, { id: 169, case_opinion_id: 12, user_name: "Zoe Wright", comment_text: "Flagged as partial. The account owner updated the ticket. Flagged as routine. The supplier updated the session. The record was rescheduled after a partial check. The account owner asked for a change and the order was cancelled.", submitted_at: new Date("2023-07-24T20:08:13Z") }, { id: 170, case_opinion_id: 175, user_name: "Zoe Reyes", comment_text: "The document was completed — minor case, no further action. An unusual follow-up: the session was replaced. No response from the courier, so the shipment was delayed. No response from support, so the session was rejected.", submitted_at: new Date("2022-07-18T05:43:34Z") }, { id: 171, case_opinion_id: 113, user_name: null, comment_text: "No response from the supplier, so the transfer was processed. Support asked for a change and the booking was resolved. A routine shipment was completed the same day. The request was refunded — automatic case, no further action.", submitted_at: new Date("2022-11-27T11:43:10Z") }, { id: 172, case_opinion_id: 185, user_name: "Ruby Smith", comment_text: "No response from the supplier, so the account was resolved. No response from the reviewer, so the request was cancelled. No response from support, so the document was escalated.", submitted_at: new Date("2021-12-11T08:04:38Z") }, { id: 173, case_opinion_id: 122, user_name: "Omar Bennett", comment_text: "The item was processed following a minor review. No response from the account owner, so the document was reviewed. The reviewer reported a duplicate issue; the invoice was approved. A late session was cancelled the same day.", submitted_at: new Date("2020-12-15T18:14:29Z") }, { id: 174, case_opinion_id: 80, user_name: "Lucas Nguyen", comment_text: "The supplier asked for a change and the report was updated. An unusual item was rescheduled the same day. The reviewer asked for a change and the report was escalated. The appointment was completed after an incomplete check.", submitted_at: new Date("2023-12-06T09:33:23Z") }, { id: 175, case_opinion_id: 155, user_name: "Ivan Zhang", comment_text: null, submitted_at: new Date("2023-12-11T20:17:55Z") }, { id: 176, case_opinion_id: 125, user_name: "Kai Novak", comment_text: "The supplier confirmed the details and the item was cancelled. The record was closed following a minor review. The account owner reported a duplicate issue; the shipment was reopened. A late refund was delayed the same day.", submitted_at: new Date("2023-05-17T18:21:37Z") }, { id: 177, case_opinion_id: 18, user_name: "Oscar Torres", comment_text: "An operator asked for a change and the session was processed. An operator asked for a change and the report was rescheduled. Support reported a partial issue; the payment was refunded.", submitted_at: new Date("2023-02-05T06:32:08Z") }, { id: 178, case_opinion_id: 139, user_name: "Karim Gupta", comment_text: "The refund was completed — partial case, no further action. An operator reported an unusual issue; the shipment was closed. Flagged as manual. The team delayed the payment. A standard ticket was cancelled the same day.", submitted_at: new Date("2021-08-04T05:51:58Z") }, { id: 179, case_opinion_id: 24, user_name: "Paula Novak", comment_text: "The reviewer reported an urgent issue; the invoice was approved. The invoice was reviewed — partial case, no further action.", submitted_at: new Date("2023-01-28T08:46:13Z") }, { id: 180, case_opinion_id: 5, user_name: null, comment_text: "An operator reported an unusual issue; the transfer was reviewed. The report was confirmed following a routine review. The shipment was approved after an urgent check.", submitted_at: new Date("2021-04-30T19:11:49Z") }, { id: 181, case_opinion_id: 77, user_name: "Mateo Young", comment_text: "The request was refunded — partial case, no further action. Flagged as partial. The account owner reopened the claim. The report was approved after an unusual check.", submitted_at: new Date("2021-09-06T15:39:08Z") }, { id: 182, case_opinion_id: 73, user_name: "Felix Young", comment_text: "An operator reported a late issue; the ticket was updated. No response from the reviewer, so the payment was approved.", submitted_at: new Date("2022-02-23T23:09:25Z") }, { id: 183, case_opinion_id: 187, user_name: "Paula Ahmed", comment_text: "The report was closed after a minor check. A late follow-up: the order was completed.", submitted_at: new Date("2022-05-27T07:48:34Z") }, { id: 184, case_opinion_id: 64, user_name: "Anna Fischer", comment_text: "A manual request was approved the same day. Flagged as incomplete. The team updated the claim. The ticket was rejected after an unusual check. The customer asked for a change and the account was replaced.", submitted_at: new Date("2022-07-03T09:13:11Z") }, { id: 185, case_opinion_id: 44, user_name: "Diego Pereira", comment_text: "The supplier confirmed the details and the ticket was completed. Flagged as manual. Support reviewed the invoice.", submitted_at: new Date("2023-05-10T20:04:43Z") }, { id: 186, case_opinion_id: 81, user_name: "Carla Hansen", comment_text: "The booking was resolved following a manual review. The claim was processed after a manual check. The transfer was processed — automatic case, no further action. Flagged as manual. The customer rescheduled the appointment.", submitted_at: new Date("2021-04-28T14:41:24Z") }, { id: 187, case_opinion_id: 178, user_name: "Carla Silva", comment_text: null, submitted_at: new Date("2023-05-10T01:05:30Z") }, { id: 188, case_opinion_id: 142, user_name: "James Lopez", comment_text: "The order was reopened — standard case, no further action. The document was approved — manual case, no further action.", submitted_at: new Date("2020-11-28T21:18:23Z") }, { id: 189, case_opinion_id: 87, user_name: "Laura Kowalski", comment_text: "The booking was approved after a late check. The customer asked for a change and the order was approved. The record was processed — repeat case, no further action. A partial follow-up: the report was reopened.", submitted_at: new Date("2021-05-01T16:47:41Z") }, { id: 190, case_opinion_id: 77, user_name: null, comment_text: "A minor follow-up: the session was cancelled. No response from support, so the ticket was updated. The team confirmed the details and the document was rescheduled.", submitted_at: new Date("2023-03-24T21:33:39Z") }, { id: 191, case_opinion_id: 170, user_name: "Zara Fischer", comment_text: "The report was approved — routine case, no further action. A standard follow-up: the delivery was reviewed. The customer asked for a change and the order was reviewed. A routine follow-up: the booking was confirmed.", submitted_at: new Date("2023-06-13T17:53:34Z") }, { id: 192, case_opinion_id: 199, user_name: "Oscar Novak", comment_text: "The invoice was processed after an urgent check. The session was updated following a duplicate review. Flagged as standard. The account owner refunded the request. A routine follow-up: the session was cancelled.", submitted_at: new Date("2020-02-10T09:21:23Z") }, { id: 193, case_opinion_id: 128, user_name: "Ruby Pereira", comment_text: "The account owner asked for a change and the invoice was replaced. A repeat follow-up: the item was closed.", submitted_at: new Date("2021-09-27T06:55:48Z") }, { id: 194, case_opinion_id: 59, user_name: "Nadia Schmidt", comment_text: "Support confirmed the details and the claim was approved. Flagged as repeat. The supplier updated the transfer. The account was confirmed — minor case, no further action.", submitted_at: new Date("2022-05-02T12:59:12Z") }, { id: 195, case_opinion_id: 101, user_name: "Hana Young", comment_text: "The order was rescheduled after an incomplete check. The report was rescheduled following an urgent review. A late item was rejected the same day. No response from support, so the transfer was replaced.", submitted_at: new Date("2023-04-29T07:59:46Z") }, { id: 196, case_opinion_id: 41, user_name: "Mia Gupta", comment_text: "Flagged as duplicate. The courier rejected the report. Flagged as standard. The supplier reviewed the record. The customer asked for a change and the shipment was updated.", submitted_at: new Date("2021-07-26T07:59:42Z") }, { id: 197, case_opinion_id: 198, user_name: "Isaac Brown", comment_text: "The request was reopened following a late review. A manual item was updated the same day. The shipment was delayed — standard case, no further action. An incomplete report was escalated the same day.", submitted_at: new Date("2021-09-16T07:02:58Z") }, { id: 198, case_opinion_id: 86, user_name: "Rosa Torres", comment_text: "The account owner confirmed the details and the shipment was processed. An urgent follow-up: the report was processed. No response from an operator, so the item was resolved.", submitted_at: new Date("2022-12-25T04:49:42Z") }, { id: 199, case_opinion_id: 181, user_name: "Arjun Flores", comment_text: "The delivery was reopened — unusual case, no further action. No response from the account owner, so the item was approved. The reviewer asked for a change and the invoice was delayed. The customer asked for a change and the refund was confirmed.", submitted_at: new Date("2020-01-09T17:24:38Z") }, { id: 200, case_opinion_id: 177, user_name: "Mila Diaz", comment_text: null, submitted_at: new Date("2022-01-12T19:20:47Z") }, ], }); } main() .then(() => prisma.$disconnect()) .catch(async error => { console.error(error); await prisma.$disconnect(); process.exit(1); });