A Shopify support ticket form in SK Form Builder starts as a normal submission. If that submission includes a customer email, it becomes a ticket on its own. The ticket gets an SLA due date, an open status, and the submission as the first message. Agents work in a separate portal, with canned replies, and the customer can receive a 1 to 5 satisfaction email after the case is resolved.
That is the documented helpdesk inside the form app. It is aimed at a small brand whose email threads keep losing the order. It is not a full shared inbox from a dedicated support company, and web push is not in the catalog. The catalog also does not assign the ticket system to Starter, Basic, or Pro. Prices are free, $4.99 a month or $49.90 a year, and $12.99 a month or $129.90 a year. There is no feature-to-plan matrix, so confirm tickets on the plan screen before you retire the shared mailbox.
What you get when the form becomes a ticket
There is no manual "convert to ticket" step for a submission that has a customer email. The first message is the form content. Support sees the answers the shopper typed, not a blank case they have to retype from Gmail.
The portal is white-label and uses its own email and password login. That login is independent of the merchant's Shopify session. You can add more than one agent. Permissions can be set for reply, delete, assign, status and priority, and canned responses. Agents can merge tickets, run bulk actions, add tags, and open a stats dashboard.
- SLA due date: each new ticket carries a due time so the queue can be sorted by what is late.
- Canned replies: agents save responses they send often, such as a return address or a shipping-delay note.
- Email replies from the customer: a reply can thread back into the ticket. Inbound mail is parsed through Postmark, Mailgun, or SendGrid, with protection against a spoofed sender.
- CSAT: after resolution, a satisfaction link is emailed and scored from 1 to 5.
Ask for the order number on the form so the first message already has it. A photo field can use an extension allowlist. There is no published file-size cap. The catalog does not say the ticket looks up the Shopify order on its own.
The inbox you already have, before you call it a helpdesk
Every form also has a submissions inbox with approve, reject, or pending status, assignment, and CSV, Excel, and PDF export. A CSV over 1,000 rows is emailed as a download link. That inbox is the record. The portal is the conversation: replies, merge, priority, canned text, and the satisfaction score. The catalog does not say either one is withheld from a named plan. If you see submissions and not the portal, use the plan screen in the app as the answer.
A contact form that never collects an email still stores a submission. It does not become this ticket, because the ticket requires a customer email. Put the email field on every support form and make it required. Smart prefill can fill it for a logged-in Shopify customer. A guest still has to type it.
A contact form versus a ticket
A contact form is the page the shopper fills. A ticket is the case your team works after that. The Shopify helpdesk form in this app is both, as long as the email is present. The merchant notification email still goes out, with reply-to set to the customer, and you can send an autoresponder. Those emails are not a substitute for the portal. If agents answer only from their personal inboxes, you lose the SLA, the merge, and the threaded history.
Use the portal when a case needs a second reply. Use submission status for a one-step decision, such as a wholesale application with no back-and-forth. Spam filters still run first, including a honeypot, an IP limit of 10 submissions per hour by default, and server-side reCAPTCHA v2, reCAPTCHA v3, or hCaptcha. Turnstile is not in the catalog. Junk that gets through can still open a ticket, so reject it.
SLA and CSAT in plain language
The SLA due date is a clock on the ticket. The catalog documents that a due date is set. It does not publish the number of hours. Read the due date on a test ticket and match the promise on the contact page to what you see. Do not advertise a window you have not observed.
CSAT is the 1 to 5 email after resolution. It is a private score for people who click the link, not a public store review. Read the ticket if you need to know why someone chose a low number.
Save canned replies for questions you always ask and for facts that do not change, such as the returns address. A saved line that says a refund has already been issued will be wrong if the agent sends it too early.
When a dedicated helpdesk is the better buy
Gorgias and similar products are a different category. This article does not compare their feature lists. Buy that kind of inbox when you need a support suite this catalog does not describe. Web push is one example: it is not documented here. A shared social inbox, a voice channel, and a workforce of dozens of agents are other reasons to look outside a form app. This portal is a ticket tied to a form submission, with email threading, roles, merge, tags, a dashboard, canned replies, an SLA due date, and a 1 to 5 email.
Stay with the form app when the contact page is the main way customers reach you and the team can work a single portal. Add a dedicated helpdesk when agents already live in another product and a form would only create a second queue.
Include the order number, the email on the order, and a topic menu. Conditional logic can show a photo upload only when the topic needs a picture. That keeps the first message useful. It does not pull fulfillment status into the ticket by itself.
Questions from a support lead
Does every submission become a ticket?
A submission that includes a customer email becomes a ticket, with no separate convert button. A submission without that email stays a submission.
Is the helpdesk a Pro-only feature?
The catalog does not assign the ticket system to Pro, Basic, or Starter. Confirm it on the plan screen in the app. The prices exist. The feature map does not.
Can customers reply by email?
Yes. A customer reply can thread back into the ticket through Postmark, Mailgun, or SendGrid, with sender-spoofing protection. Agents still need to work in the portal if you want the thread, the SLA, and the later satisfaction email in one place.
Put a required email on the support form, send one test, and confirm the ticket, the due date, and a canned reply before you close the old shared mailbox. The product page is SK Form Builder.