Contact Support
Account-specific support works best after you sign in. Helm can attach your site, plan, role, and safe request context without asking you to repeat details.
Ready to send the request?
The dashboard support form captures category, impact, affected area, subject, message, and an optional relevant URL. Product feedback has its own structured form for requests, objections, missing integrations, and confusing UX areas.
What to include
Tell us what happened, where it happened, what you expected, and any safe customer, order, booking, invoice, or page reference that helps us find the issue.
Keep private
Do not include passwords, login codes, API keys, bearer tokens, cookies, full card details, or private customer message bodies in a support request.
The fastest requests describe the affected Helm area, the exact customer-facing or dashboard page, the last safe action taken, and the result the business expected. Clear context helps support separate account access, billing, website, booking, order, invoice, receipt, customer record, team role, and setup questions without asking for secrets or private customer message bodies.
Sign in before sending billing, subscription, site, team, customer, booking, order, invoice, or receipt questions. Authenticated support can attach the correct Helm site and plan context, which is safer than trying to identify an account from public form text.
Public help articles cover setup paths, website publishing, forms, bookings, store orders, customers, invoices, receipts, referrals, team roles, and troubleshooting. Check those guides first when the question is about how Helm works in general.
Feature ideas, missing integrations, pricing objections, cancellation reasons, and confusing workflow notes belong in the dashboard feedback form. That keeps support requests focused on issues that need account review or operational follow-up.
Plan and trial questions should start from the pricing page. Agents and crawlers can also use the structured pricing markdown or plain-text pricing summary when they need a compact version of Helm plan scope.
Public Help Center articles can solve setup, billing, booking, website, customer, document, and account-access questions without waiting for an account-specific reply.
Set up Helm around real customer activity: public presence, bookings, orders, CRM records, invoices, follow-up, and daily insights.
Plans / billingManage your plan and billingUnderstand Helm plan boundaries, billing portal changes, pricing lanes, subscription expectations, and planned advanced scope.
TroubleshootingTroubleshoot public pages and checkoutWork through common Helm public page, booking, checkout, invoice, receipt, and account issues before creating a support ticket.
Helm keeps public help, account support, and product feedback separate so merchants can get a useful answer without exposing private data in a public form. Use the dashboard when the question depends on a specific site, plan, billing account, customer record, booking, order, invoice, receipt, staff member, location, or support thread.
Sign in before asking about trial status, Stripe checkout, renewal timing, plan changes, failed payments, cancellation timing, account credit, or referral rewards. Dashboard support can connect the request to the correct Helm site and billing context without asking for private card or login details.
Include the public page URL, dashboard area, expected result, last safe action, and any non-sensitive service, form, or booking reference. Do not include passwords, login codes, cookies, bearer tokens, private customer message text, or full payment details.
Use dashboard support for order history, checkout, product catalog, invoice delivery, payment status, receipt resend, refund context, or customer timeline questions. Include safe reference numbers and affected URLs so support can find the relevant records after you sign in.
Account owners should send role, staff seat, invite, location, onboarding, and setup-checklist requests from the dashboard. That keeps ownership checks, site context, and permissions attached to the support record before Helm reviews the issue.
Use feedback for missing integrations, pricing objections, confusing workflow notes, cancellation reasons, and feature ideas. Feedback is reviewed as product input, while support requests are reserved for account-specific issues that need investigation or follow-up.
Use public Help Center articles when the question is reusable and does not depend on private account data. Public guides cover setup, website publishing, bookings, store orders, customers, invoices, receipts, billing concepts, staff roles, referrals, and troubleshooting basics.
Helm help articles are written around the operating work merchants repeat every week: setting up the business, publishing public pages, taking bookings or orders, keeping customer records useful, creating documents, reviewing billing, and troubleshooting customer-facing links before they are shared.
Most setup questions are easier to answer when you follow the same path a customer follows. Check the public website or link page first, then the booking, form, menu, store, invoice, receipt, or checkout step that the customer is supposed to use. If that path is clear, the dashboard record is usually easier to understand.
Helm works best when bookings, orders, invoices, receipts, forms, notes, reviews, and customer records are updated in the module that owns the work. A chat message or spreadsheet can explain context, but the durable record should live in Helm when the workflow is supported there.
Some features are available on Starter, some on Growth, and some are planned for a future tier. Before treating a missing control as a bug, confirm whether the plan supports the workflow, whether the page or item is published, and whether the customer-facing link points to the right site.
Public Help Center articles cover reusable product guidance. Account-specific support is for questions that require your site, plan, role, customer record, booking, order, invoice, receipt, payment state, or audit context. Use the dashboard request form when private merchant details are needed.