REQUIRE EVIDENCE BEFORE SWITCHING
Prove the order handoff and the exit path in a trial
The following are proposed acceptance checks; ToolMerit has not run these tests in vendor accounts. Use approved test environments and synthetic customer details. Do not connect live refund permissions or upload real customer histories just to explore a feature.
Match the right shopper and order
Try two orders for one test customer and a message from an unrecognized address. Pass only when the agent can identify the intended order without exposing someone else’s details. A convenient email match is not, by itself, authorization to change an order.
Compare tracking with action permissions
Have a restricted test agent view delivery status, then attempt a prohibited refund. Record the permitted result, rejection and escalation owner. Do not accept a hidden button as proof of a server-side permission check.
Exercise a handoff that cannot finish
Use a simulated fulfillment lock or disconnected connector. The conversation must keep an owner and an honest pending state. Check what the customer sees outside business hours and how they reach a person when automation cannot answer.
Inspect what the export actually contains
Export a small permitted sample and open it independently. Check messages, notes, attachments, timestamps and order references against the original. In Gorgias, view exports contain metadata; analytics exports can include public message text but exclude internal notes and have time/volume limits. Export options and limits.
Before cutover: decide how old conversations remain readable, where help-center URLs redirect, who owns unanswered tickets and when the old connector loses access. For Gorgias, message-content analytics exports cover the most recent 30 days of the selected period, up to 100,000 tickets—not a full historical migration by default. Ask for the missing export scope before canceling the old service.
A help desk moves customer and order data into another system. Review access, retention, deletion, subprocessors and contractual requirements for your situation. Keep payment secrets and unnecessary sensitive information out of support records. For cross-system approvals, use the decision criteria in our automation tools guide.