How Do You Automate "Where Is My Order?" Tickets in Freshdesk With Shopify and AI? (2026)

What are the ways to answer order-status tickets in Freshdesk?

There are four options, three of them AI, and they differ in who does the reading and which channel they cover.

The first option is the baseline. It makes a human faster but still needs one per ticket. The other three put an AI agent on the question, and the split between them is mostly about channel: Freshdesk's Shopify templates are chatbot templates, while an agent layer starts from the ticket, which is where email order-status questions land.

What do Freshdesk's Shopify app and Freddy AI Agent already do?

Start with what Freshdesk gives you, because for some stores it's enough.

The Shopify app. Freshdesk's Shopify integration article (modified 11 March 2026) says the app shows a customer's current and past orders, order status, payment status and shipping information in the ticket sidebar, including the carrier and tracking numbers with links to the carrier's site. It also lets a human agent issue a full or partial refund, with restock and notify options, and cancel an order while payment is pending or items haven't shipped. It installs from the Freshworks Marketplace using a custom app you create in Shopify's Dev Dashboard, which Freshdesk says is required for new connections from 1 January 2026. The same article has a section on Shopify placeholders in canned responses, so a human can send an order-status reply in two clicks.

Freddy AI Agent's Order Status workflow. AI Agent Studio's workflow library lists three Shopify workflows: Order Status, View Past Orders and Refund Status. Freshdesk describes its Order Status workflow as one that can collect the customer's order ID, fetch the order, "display the current status or delivery date" and hand off to a human when needed. Freshdesk's article lists 52 workflows, though the screenshot on the same page shows a Pre-built workflows tab badge of 54; we use the article's list of 52, which is the one we could read entry by entry. Freddy's Shopify workflows read; they don't cancel or refund. Freshdesk's refund and cancel templates are for PayPal, Stripe and Shiprocket, which our actions matrix compares cell by cell with the other help desks' AI agents.

The Shopify chatbot templates. Freshdesk's integration chatbot templates (modified 23 September 2026) include Shopify Bot, Shopify Bot for WhatsApp and Shopify Advanced Bot. Their Track Order flow shows order details and status, the tracking URL, each line item's price and quantity, and payment and fulfillment status. They're on Pro and Enterprise only, and Freshdesk says your Shopify account "must be integrated with your Freshmarketer or Freshsales Suite account before these templates work."

Two more lines in Freshdesk's docs apply here. First, Freshdesk's workflows article (modified 18 August 2026) tells you to collect the order ID and email and "cross-verify both against your backend before returning order details" when the widget doesn't pass the user's identity. Second, Freshdesk's API actions article says confirmation blocks are skipped on email AI agents. A read-only order lookup doesn't need confirmation, but the identity check has to live in the workflow, not in a confirmation step.

Freshworks puts the Shopify chatbot templates on Pro and Enterprise. Order status is a question every store gets daily, so gating the ready-made version turns it into a reason to move up a plan; the Order Status workflow in AI Agent Studio is the route on other plans, billed per session.

What does an AI agent need to answer "where is my order?" from Shopify?

Three facts: which order, whether it has shipped, and where the parcel is now. Shopify holds the first two. The third often lives with the carrier or a tracking app.

On our test, Macha's Shopify Get Order tool returned 20 fields for an order, including createdAt, financialStatus, fulfillmentStatus, lineItems, fulfillments, refunds, cancelledAt and the order's email. The agent uses that email to check the requester against the order before it says anything. The order we read was unfulfilled, so its fulfillments list was empty and we couldn't see which tracking fields a shipped order carries through this tool. On Shopify's side, a fulfillment stores a tracking number, tracking URL, carrier and a shipment_status, and Shopify notes that a clickable tracking number "doesn't mean that Shopify automatically updates the fulfillment's shipment_status field."

So the agent's reply has three tiers:

• Unfulfilled: say it hasn't shipped and quote your processing window as a number.
• Fulfilled, Shopify only: give the carrier, tracking number and tracking link from the fulfillment.
• Fulfilled, tracking app connected: add the latest scan and the carrier's estimated date, quoted exactly.

The third tier needs a tracking app's API. AfterShip, 17TRACK, CWILL (formerly ParcelPanel) and similar apps have no built-in Macha connector; each connects through a custom API tool that Macha's team sets up during onboarding, using the app's API key. Which apps can look a parcel up by order number, and which plans include API access, is compared in which order-tracking apps an AI agent can use; AfterShip's lookup options are covered in what an AI agent can do with AfterShip.

How do you set up the agent on Freshdesk?

Macha's Freshdesk connector authenticates with a Freshdesk API key and exposes 15 tools, from Get Ticket and Search Contacts to Add Public Reply, Add Internal Note, Update Status, Update Tags and Assign Ticket. It has three triggers: Ticket Created, Ticket Updated and a custom webhook fired by your Freshdesk automation rules. The Shopify connector is built in too, with 8 tools; an order-status agent needs only Get Order and Search Orders.

These are the instructions we'd paste into the agent for a Freshdesk store. The tool names are Macha's.

Job: answer "where is my order" tickets using Shopify order data.

1. Read the ticket. Note the requester's email and any order number
   (a # followed by digits).
2. Find the order.
   - If the ticket has an order number, call Get Order with it.
   - If not, call Search Orders with the requester's email. If more than
     one order is unfulfilled or in transit, list the two most recent
     (order number, date, first item) and ask which one. Stop.
   - If no order is found, send the NOT-FOUND REPLY (below). Tag wismo_ai.
     Set status to Pending. Stop.
3. Check identity. If the order's email is not the requester's email, treat
   the order as not found: send the NOT-FOUND REPLY word for word, and don't
   say whether the order exists, has shipped or has been paid. Add an
   internal note: order number, "email mismatch", no other order details.
   Tag wismo_ai and wismo_verify. Set status to Pending. Stop.
4. If the order is unfulfilled: say it hasn't shipped yet and that orders
   ship within 2 business days of purchase. Don't promise a date. If the
   order is more than 5 business days old, also hand off (step 6).
5. If the order is fulfilled: give the carrier, the tracking number and the
   tracking link from the fulfillment. Quote only dates the carrier gives.
   Never add a date of your own.
6. Hand off instead of answering when tracking says delivered but the
   customer says it didn't arrive, there has been no carrier scan for 5
   business days, the customer asks to cancel, change the address or get a
   refund, or this is their third message about the same order. To hand
   off: send a short public reply saying a teammate will pick this up, add
   an internal note with the order number, order date, fulfillment status
   and the reason, and tag wismo_handoff.
7. Tag every ticket you handle wismo_ai.

NOT-FOUND REPLY: "Thanks for getting in touch. I couldn't match an order to
this email address. Could you reply with your order number and the email
address you used at checkout? I'll check it straight away."

Never: issue a refund, cancel or edit an order, or say a parcel is lost.

On Freshdesk, add "and assign to the Orders group" to the handoff in step 6 if you attach Assign Ticket. The 2 and 5 business days are example values; use your own.

Step 3 is where an order-status runbook can leak data. A reply that says "that order belongs to a different email" confirms the order exists, and a reply that says "it hasn't shipped yet, but please write from your checkout email" leaks the status it was meant to protect. Making the mismatch reply identical to the not-found reply means a stranger who types a guessed order number learns nothing. Store order numbers usually count up, as #1096 and #1097 do in our test store, so guessing one is easy.

Put a loop guard on the trigger too: skip tickets already tagged wismo_ai, so the agent's own status and tag updates don't fire it again when you use Ticket Updated.

What happened when we tested the order lookup?

Our test account has no Freshdesk connected, so we didn't run this on Freshdesk. On 28 September 2026 we created a Macha agent with the instructions above, word for word, and attached the equivalent tools on our Zendesk sandbox (Get Ticket, Add Public Reply, Add Internal Note, Update Ticket Status, Update Ticket Tags) plus Shopify Get Order and Search Orders. The Shopify side is Macha's development store. The Shopify lookup and the reply logic are the same on either help desk; only the ticket tool names change.

We used Macha's Test run, which opens a real ticket in the sandbox and runs the agent the way a ticket-created trigger would. That's why each customer message shows "Via API" and an "Internal" badge; the agent's replies, signed "Team Ride", our made-up demo brand, are public. The customers are made up. The agent was inactive with no trigger throughout.

Ticket 1: "Where is my order #1097?" from [email protected]. Order #1097 exists in the store, paid and unfulfilled, placed on 14 September, under a different email. The agent called Get Ticket, then Get Order, saw the mismatch and sent the not-found reply word for word. It added the internal note "Order #1097 - email mismatch", tagged the ticket wismo_ai and wismo_verify, and set it to Pending. The run finished 11 seconds after the ticket was created. The public reply says nothing about the order's status, payment or date.

Ticket 2: "Order #2045 not here yet" from [email protected]. There's no order #2045. Get Order returned "Order 2045 not found", the agent retried without the # and got the same answer, then sent the same not-found reply, tagged wismo_ai and set Pending, 13 seconds after creation. It added no internal note, which matches the instructions: only the mismatch branch asks for one.

Ticket 3: "Where's my stuff" with no order number, from [email protected]. The agent searched Shopify orders by that email, got zero results and sent the same reply, again in 13 seconds, tagged wismo_ai and set Pending.

So a customer with no order, a customer with a wrong order number and a stranger quoting a real order number all got the same 34-word reply. The only difference was internal: the mismatch left a note and a wismo_verify tag, so a human can see which tickets were identity problems rather than typos.

Two things we couldn't test. Every order in the development store is under a teammate's email, so no made-up requester could pass the identity check, and we didn't send a ticket from a real address to get one through. And both orders are unfulfilled, so the fulfilled branch, the tracking link reply and the handoff rules in step 6 didn't run. Test those on your own shipped orders before going live, starting with a ticket from an address you own.

What does it cost per order-status ticket?

Freshdesk sells Freddy AI Agent by the session. Per the Freshdesk pricing breakdown, each account gets 500 sessions once, then pays $49 per 100 sessions, resolved or not, on top of the seat plan. At 1,000 order-status conversations a month, that's 10 packs, or $490 a month once the free 500 are used.

Macha bills per ticket, about $0.40 per ticket, with one ticket covering one thread with one person however many replies it takes. If the Freshdesk trigger sends the agent only order-status tickets, 1,000 a month fits the 1,500-ticket tier at $599. If the agent takes every ticket, size the tier from total volume instead. The price includes the setup: the Macha team writes the runbook, connects the tools, tests the agent on a sample of your past tickets and runs it in safe mode, with drafts as internal notes in Freshdesk, until the drafts are right. A dedicated success manager then handles your changes, such as a new ticket category, an instruction edit or a tracking-app tool.

Both models bill for work done, not outcomes: a session or ticket that ends in a handoff costs the same as one the agent answers. That's a better incentive for order status than per-resolution pricing, where the vendor earns more the more tickets it closes and has less reason to hand off an identity mismatch. The real difference is what else the price needs. Freddy AI Agent comes with every Freshdesk plan from Growth, but the ready-made Shopify chatbot templates need Pro or Enterprise. Macha needs a Freshdesk API key and whatever Freshdesk plan you already run.

If you're working out volume for November, our holiday order-status guide does the peak arithmetic, and the same runbook pattern for other desks is in automating WISMO in Zendesk and in Gorgias.

Where Macha fits

Macha fits teams on Zendesk, Freshdesk, Gorgias, Front, HubSpot or Intercom with a Shopify store whose order-status questions arrive by email and who want an agent that works on the ticket itself, including the identity check, rather than a separate chat widget. It's the wrong fit if your order-status questions come only through chat and you're already on Freshdesk Pro or Enterprise: Freshdesk's Shopify chatbot templates cover that without another vendor. On Freshdesk, the built-in Freshdesk connector reads the ticket and posts the reply, note, tags and status; the built-in Shopify connector's Get Order and Search Orders do the lookup; tracking apps connect through a custom API tool that Macha's team sets up during onboarding. Macha is the done-for-you option. You connect Freshdesk and Shopify, which takes about 15 minutes; the Macha team analyzes your past tickets, builds the knowledge base and the order-status agent, and runs it in safe mode until the drafts are right. Freddy's workflows, by contrast, are configured by your own team in AI Agent Studio. Pricing starts at $299/month for 750 tickets, about $0.40 a ticket, and that includes the setup and a dedicated success manager who handles your changes after go-live. The order-status use case shows the flow. For the wider Freshdesk picture, including returns and refunds, see how an ecommerce brand should add AI to Freshdesk, and for other apps worth connecting, the best Freshdesk integrations.

How we researched this

• Sources, accessed 28 September 2026: Freshdesk help center articles on the Shopify integration (modified 11 March 2026), the AI Agent Studio workflow library (modified 29 June 2026), workflows for AI agents (modified 18 August 2026), integration chatbot templates (modified 23 September 2026) and API actions; Shopify's Admin API fulfillment reference; Narvar's 2025 State of Post-Purchase press release (6 November 2025, 3,461 US online shoppers); Macha's integrations list for the Freshdesk connector's 15 tools and 3 triggers. Freddy AI Agent session pricing comes from our Freshdesk pricing post, checked 24 September 2026.
• Arithmetic: 1,000 sessions / 100 = 10 packs; 10 x $49 = $490. 1,000 Macha tickets falls in the 1,500-ticket tier, $599. Run times are the conversation's first and last message timestamps: 14:32:05.8 to 14:32:16.9 UTC (11 seconds), 14:32:06.6 to 14:32:19.7 (13 seconds) and 14:32:07.3 to 14:32:20.8 (13 seconds). The not-found reply is 34 words.
• What we ran: three Test runs on 28 September 2026 on Macha's own test account, against our Zendesk sandbox and Macha's Shopify development store, with made-up customers. No Freshdesk account was connected, so no Freshdesk tickets were created; the Freshdesk tool names in the setup table and instructions come from Macha's connector documentation. The fulfilled-order, tracking and handoff branches weren't exercised.
• What we didn't verify: Freshdesk's workflow and template behavior is from its documentation, not a Freshdesk account.

Frequently asked questions

Does Freshdesk have a Shopify integration? Yes. Freshdesk's Shopify app, installed from the Freshworks Marketplace, shows a customer's orders, payment and fulfillment status, shipping details and tracking numbers in the ticket sidebar, and lets a human agent refund or cancel an order. It's on Growth, Pro and Enterprise, not the Free plan.

Can Freddy AI Agent answer "where is my order?" Yes. AI Agent Studio has a prebuilt Order Status – Shopify workflow that collects the order ID, fetches the order and shows its status, and the Shopify chatbot templates on Pro and Enterprise add a Track Order flow with the tracking URL.

How should an AI agent verify the customer before sharing order status? Match the order's email to the requester's email, as Freshdesk's own workflow guidance recommends for order ID and email. If they don't match, send the same reply you'd send for an order that doesn't exist, so the reply confirms nothing.

Can an AI agent get live tracking scans from Shopify alone? Usually not. Shopify stores the carrier, tracking number and link on the fulfillment, and Shopify says its shipment status field isn't always updated. Scan history and estimated dates come from the carrier or a tracking app through an API.

Should an AI agent cancel or refund orders from a WISMO ticket? Not from an order-status runbook. Cancellations, address changes, refunds and delivered-but-missing parcels should go to a person with an internal note, even though Freshdesk's Shopify app lets humans refund and cancel from the sidebar.

How much does automating order status on Freshdesk cost? Freddy AI Agent is $49 per 100 sessions after a one-time 500, so 1,000 conversations a month cost $490. Macha bills per ticket, and 1,000 order-status tickets fit its 1,500-ticket tier at $599, which includes the Macha team building and running the agent for you and a dedicated success manager for changes.

To run the order-lookup runbook on your own Freshdesk tickets, start a trial with $50 of free usage (about 125 tickets), no credit card, no time limit.