Define a successful first shift before connecting anything
Your first Gorgias milestone should be one complete support exchange: receive a message, identify the right order, reply, and hand the conversation to another person. Automating every queue is a separate project.
Gorgias organizes customer conversations as tickets. Its Shopify integration brings order and customer information into the support workspace. That makes it worth evaluating when agents repeatedly move between a shared inbox and Shopify to understand a request. Shopify connection overview
This guide is for a small Shopify team preparing its first Gorgias rollout. Official sources were checked September 14, 2026. The test cases are our suggested exercises, not a deployment we performed or results from a merchant account.
Already connected? Our macro guide addresses reusable replies, while tags and rules covers organization. Here, the scope is the initial connection and a dependable human support workflow.
Bring a connection brief to the demo
Identify the store, mailbox, people and costs before selecting a setup path. A tool can fit your long-term needs while a particular entry plan does not support the connection you expected.
Write down the Shopify store, support address, email provider, setup owner and first-shift responder. For multiple storefronts, include an unambiguous store identifier. Keep passwords out of this brief; authorized people should sign in through their normal accounts.
The Shopify listing starts with a $10/month Starter Helpdesk plan containing 50 tickets. Treat that as a limited entry point, not an unlimited AI package. Request a quote for the actual Helpdesk, AI and channel requirements. Official app listing and pricing
Trial duration differs across official sources. Confirm the offer for your signup route, the expiration date, outbound email limits and the features you can test. Account creation and trial limitations
A useful demo request is specific: “We use this email provider and need these people to handle these order questions. Show us the supported connection and the billable units.” Our pricing guide explains what to include in that discussion.
Separate setup access from day-to-day response access
Choose permissions by the work each person must perform. The person approving integrations does not have to give every responder account-wide administrative access.
Gorgias distinguishes viewing, replying and executing integration actions. Observer cannot reply to customers. Lite can reply; the Basic user role can perform actions such as Shopify refunds. “Basic” here names a user role, not the Basic subscription. Permission reference
For your first shift, name a configuration owner, a responder and an escalation owner. They may be fewer than three people, but the responsibilities should still be clear.
Use a controlled conversation to distinguish an internal note from a customer-facing reply. A note asking a colleague to review an exception is not itself a promise to the customer. Decide who will check unresolved internal requests before anyone ends their shift.
Connect Shopify and check the correct order
An authorized person must approve the connection on both sides. Gorgias requires its owner or an admin, plus a Shopify store owner or administrator.
The documented path is Settings → Workspace → Store → Add new store → Shopify. Continue through the app installation, check the selected store and requested access, and return to Gorgias. Initial data import can take time. Connection steps
Verify a test customer and order you control. Compare the order reference, product and date instead of relying on a matching name. Include an older purchase in the exercise so “latest order” does not silently become your team's definition of “the right order.”
If the expected data is absent, check the store selection and import status before creating another integration. If the interface differs from the guide, reconcile it with current documentation rather than guessing which similarly named control to use.
The first exercise only needs to establish that agents can inspect the right information. You do not need to refund or cancel a real order to prove that an action is visible.
Connect email using the method your plan supports
Test both directions of email delivery. A message appearing in Gorgias proves receipt; it does not prove that the reply reaches the sender with the intended address and signature.
The Gmail integration documentation lists Basic and Pro Helpdesk plans and requires an admin. It directs Advanced and Enterprise accounts to automatic forwarding. Do not assume the same Gmail integration path applies to Starter; confirm the supported method for your account. Gmail integration requirements
Send a plainly labeled test message from an address your team controls. Reply, then inspect arrival, sender name, reply address, signature and spam placement. For a custom sending domain, complete the required verification through the official setup instructions.
During transition, tell the team where replies should be sent from. Keep the old inbox under explicit ownership until you have accounted for outstanding work. Otherwise, a successful technical connection can still produce duplicate replies or a queue nobody checks.
Historical imports are a separate decision. Define the period and purpose before importing an archive, and distinguish background context from unresolved requests that someone still needs to answer.
Run three handoff tests before expanding the rollout
Test ownership as well as message delivery. Use controlled examples with no live customer records.
| Scenario | What to inspect | Pass condition |
|---|---|---|
| Shipping question about a test order | Store, order and sender identity | The intended reply reaches the controlled address |
| The first responder goes off shift | Visibility and ownership of unfinished work | A named person takes over without a duplicate reply |
| A return outside the written policy | Internal note and escalation route | The decision reaches the owner without an unapproved refund promise |
Record expected behavior, actual behavior, the fix owner and a retest. Categorize failures as store data, delivery, permissions or team procedure. This is more useful than a single “setup complete” checkbox.
Add AI only after deciding how exceptions return to people
A connected store does not settle which actions AI should perform. Choose the scope, human handoff and account-specific billing before enabling automation.
Gorgias documents Helpdesk tickets and automated interactions separately, with legacy billing considerations. Ask how AI-only resolutions and human involvement are counted for your subscription. Billing definitions
Your initial scope might be a verified shipping-policy question, or entirely manual replies. Exceptions involving refunds, unusual delivery circumstances or missing product facts need a named decision-maker. A successful canned example is not evidence that every exception is ready for automation.
The official chat redesign article was updated August 21, 2026. Its newer shopping interface is useful context, but feature availability must still be verified in your account. Official chat update
FAQ and the next step
Take your connection brief and three tests to a Gorgias demo. They give the presenter a concrete workflow to demonstrate.
Do we have to migrate every channel at once?
Our recommendation is to validate one channel and a complete shift handoff first. Plan additional channels around the same checks and retain a clear owner for unfinished work in the old inbox.
Is a received test email enough?
No. Verify the outgoing reply, the right order context and another person's ability to take over. Technical receipt is only one stage of the workflow.
How long is the trial?
Confirm the accepted offer for your route; official sources do not state one consistent duration. Write down the end date and sending limits before scheduling your test work.
The next action is to request a demo covering your store, email method, roles, trial and quote. Once those conditions are clear, you can carry out a limited rollout with an explicit finish line.
See whether Gorgias fits your businessBook a demoA free trial is availableAsk about the trial length and included features during your demoRequest a Gorgias demo
