A customer emails "do you ship to Norway and how much" two hours before checkout, and the founder loses 11 minutes deciding whether to offer free shipping to close the sale. Most pre-purchase shipping tickets follow this exact pattern: low effort to answer, high stress to triage, and almost never require the refund or discount the merchant assumes they do. Handling them well is about routing the right data to the right surface, not throwing money at the close.
Key takeaways
- Four question types cover ~90% of pre-sale shipping tickets: zones, times, customs/duties, cost objections.
- Reply time, not refund generosity, drives conversion on shipping tickets — sub-5-minute responses lift checkout completion by 38%.
- Proactively surface rates on PDP and cart; let AI answer the edge cases (Norway, split shipments, PO boxes).
- Heylio ingests your Shopify shipping policy plus live carrier rates and drafts replies in your tone — it won't quote duties, by design.
What does a pre-purchase shipping question actually cost?
A pre-purchase shipping question typically costs a 7–15 minute cycle: 2 minutes to read, 3–8 minutes to confirm zones/rates in Shopify, 2 minutes to write a reply, and another minute to tag the ticket. Across 20 such tickets per week, that's 4–5 founder hours burned on work that an AI can close in under 90 seconds per conversation. The hidden cost isn't the refund — it's the founder's context switches away from sourcing, ads, or product work.
The second hidden cost is consistency. Humans paraphrase rates differently every time: "around 5–7 business days" on Monday becomes "usually a week" on Friday. Shoppers notice, and the variance itself erodes trust more than a slow shipment would.
What are the four question types you need to template?
Every pre-sale shipping ticket falls into one of four buckets. Templating each one cuts average handling time from 9 minutes to under 2.
| Question type | % of tickets (typical) | Data the AI needs from Shopify |
|---|---|---|
| Delivery zones (countries/regions) | ~35% | Shipping zones, enabled rates, restricted country list |
| Delivery times (ETA, cutoff, weekends) | ~30% | Carrier transit times, order cutoff times, fulfillment SLA |
| Customs, duties, import taxes | ~20% | DDP/DAP policy, HS codes, tax-inclusive rates |
| Shipping cost objections ("too expensive") | ~15% | Rate cards by weight/zone, free shipping threshold, discount eligibility |
Templating these four — and only these — covers roughly 90% of pre-purchase volume on a typical Shopify store. The remaining 10% (lost parcels, damaged-on-arrival, address changes after dispatch) are post-purchase WISMO tickets, a different workflow.
How do you answer delivery zone questions without overselling coverage?
"Do you ship to [country]?" is the highest-volume pre-purchase ticket. The wrong move is to say "yes, everywhere" — customers then blame you when customs seizes the parcel. The right move is a precise answer in under 30 seconds.
Copy-paste reply template:
Hi [first name], yes — we ship to [country] via [carrier, e.g., DHL Express / PostNL]. Estimated transit is [X–Y] business days after dispatch, and you'll see the exact rate at checkout once you enter your address. Heads up: import duties are paid on delivery (DAP), so the courier will collect those separately.
What the AI needs from Shopify to generate this: the active shipping zones, the carrier per zone, the transit time configured on each rate, and whether the rate is DDP or DAP. In Heylio, the KB ingestion pulls your shipping policy plus the live zone/rate matrix from Shopify on setup, then re-checks nightly — so when Norway adds a new rate or restricts a region, the drafted reply updates without you editing anything.
How do you handle delivery time questions and weekend cutoffs?
"When will it arrive?" and "if I order now will it ship today?" are the same question phrased differently. Both depend on three variables: order cutoff time, fulfillment SLA, and carrier transit time. The mistake most stores make is quoting only carrier transit and ignoring the cutoff — which is why a Friday 4pm order still ships Monday and the customer feels misled.
Copy-paste reply template:
Hi [first name], orders placed before [cutoff, e.g., 2pm CET] on a business day ship the same day. After cutoff, it's the next business day. From dispatch, [carrier] delivers in [X–Y] business days, so you'll get it by [rough date]. We don't process or dispatch over the weekend — orders placed Friday after cutoff ship Monday.
Concrete decision rule for the AI: if the question contains "today", "tomorrow", "by Friday", or a specific date, the reply must include both the cutoff time AND the calculated expected delivery date. The AI needs the order cutoff (configurable in your KB), the fulfillment SLA (set in Shopify → Settings → Shipping and delivery → Processing time), and the carrier transit window per zone.
How do you respond to customs and duties questions honestly?
This is the one question type where AI automation has a hard ceiling, and being honest about it builds more trust than faking precision. Customs duties depend on the destination country's de minimis threshold, the HS code of the product, the declared value, and the customer's local tax rules — variables you don't control and can't reliably compute for every shopper.
Copy-paste reply template:
Hi [first name], import duties and taxes for [country] depend on the declared value and the local customs regime. As a guide, orders under €[$X] typically enter duty-free under Norway's [€X] de minimis threshold, but anything above that will be collected by the courier on delivery. We can't quote the exact figure in advance — your local customs authority has a calculator at [link] if you want a precise estimate.
The honest note: Heylio's KB ingestion links to your shipping policy and live Shopify rates, but it will not quote a specific duty amount to the customer. That's a deliberate scope choice — quoting a number that turns out wrong costs you more than saying "we can't quote this in advance." What it will do is route the question to your human team when the customer pushes back, with the full conversation context attached.
How do you handle "shipping is too expensive" without giving free shipping?
About 15% of pre-sale tickets are disguised price objections — the customer actually wants the product but the shipping line item broke their mental math. Offering free shipping to close the sale trains them to ask every time. The better move is to redirect to the value lever you already have: the free-shipping threshold.
Copy-paste reply template:
Hi [first name], shipping to [country] is [€X] via [carrier] for orders under [€Y]. Orders over [€Y] ship free, so adding [one specific related product or category] would cover it. Want me to point you to a few options that pair well?
What the AI needs: your free-shipping threshold (configured in Shopify shipping rates), the current cart value (visible via Shopify cart lookup if you're connected), and ideally a 1–2 product suggestion. The "add a related product" angle is what converts the objection without dropping margin — a €9 pair of socks is cheaper than €15 of free shipping, and the customer feels clever rather than pressured.
When should shipping info live on the PDP and cart vs. be answered reactively?
Proactive disclosure beats reactive answering on roughly 80% of pre-sale shipping questions, because it removes the friction that triggers the ticket in the first place. But not all info belongs on every surface.
Simple decision rule:
- PDP (product page): show the range of shipping costs ("€5–€18 depending on destination") and the general ETA ("3–7 business days"). Specific country rates don't belong here because they change the layout for everyone.
- Cart page: show the exact rate for the customer's entered address, plus the free-shipping threshold progress bar ("€12 away from free shipping"). This is where the cost objection dies.
- Shipping policy page: the full matrix — zones, carriers, DDP/DAP split, weekend cutoff, processing time, PO box restrictions.
- Reactive (AI/chat): edge cases — split shipments, PO box delivery, specific date promises, military/APO addresses, and any question that mentions "by Friday" or a deadline.
The principle: high-traffic surfaces get high-traffic answers, and AI handles the long tail without bothering the founder.
How does Heylio actually close these tickets without you?
When a pre-purchase shipping email lands in Gmail or a WhatsApp DM comes in, Heylio drafts a reply in your tone using two data sources: the KB ingestion (your shipping policy, FAQ, and any playbook you write) and live Shopify lookups (zones, rates, cart value, product weight). The AI only sends when its confidence passes your threshold; anything ambiguous routes to a human with the full thread attached. Auto-learning tracks every correction you make and suggests KB or playbook updates — so the third "do you ship to Norway" ticket of the week drafts itself better than the first.
One honest scope: Heylio will not quote duties or import taxes to the customer, because the data isn't reliably available at conversation time and a wrong quote costs you the trust you just built. It will tell the customer to check their local customs calculator, and it will flag the conversation for your human team if the customer pushes for a number.
What to do next
Pick the single highest-volume pre-sale shipping ticket on your store this week — for most Shopify stores it's either "do you ship to X" or "when will it arrive." Write the reply template once, paste it into your KB or playbook, and let Heylio draft against it for the next 50 tickets. You'll recover 3–5 founder hours per week and stop offering free shipping you never needed to give.
Pricing is per ticket resolved by the AI (€0.49), or with prepaid monthly packs from €39 for 100 resolutions, at heylio.io.