Platform/Admin - All plans

Choose a setup path by business type

Pick the shortest Helm setup path for service, restaurant, cafe, menu, retail, store, or event-based businesses starting setup.

Quick answer

Pick the shortest Helm setup path for service, restaurant, cafe, menu, retail, store, or event-based businesses starting setup.

Service businesses

Start with a public website page, one service, real availability, and one customer record. Then test the booking path, create a receipt or invoice when money is involved, and invite staff only when the plan and daily workflow need it.

Good fits include salons, clinics, training, consulting, repairs, wellness, and appointment-led operators that need customers to understand the service and pick a time.

Restaurant, cafe, and menu businesses

Start with site basics, a customer-ready menu, hours, contact paths, and a clear public next step. Use Store + Orders only when you are ready to sell products or accept checkout-backed orders through Helm.

Menu guidance should stay practical: names, prices, availability, dietary notes where helpful, and a page customers can read on mobile.

Retail, store, and event businesses

Retail merchants should launch with a small product catalog, inventory policy, checkout path, customer record, order workflow, and receipt expectations. Events businesses should publish the event, registration or ticket path where supported, check-in process, and customer history expectations.

Helm supports website-first commerce and Business event operations within the implemented scope. It is not a POS, carrier-label platform, tax engine, marketplace, or seating-map system.

Continue with Helm support

Public Helm help is organized around operational workflows. Use the next guide when this article depends on setup, website publishing, bookings, customers, invoices, receipts, billing, staff access, or troubleshooting context.

Getting startedGetting started with Helm

Set up Helm around real customer activity: public presence, bookings, orders, CRM records, invoices, follow-up, and daily insights.

Helm works best when you set it up around the way your business already runs: get discovered, take a booking or order, keep the customer record useful, collect payment or documents, follow up, and review the business in Overview and Insights.

Website / CMSSet up your website

Use Helm Presence tools to publish a clear customer-facing website without turning the CMS into a separate product or workflow.

Your Helm website is the public home for customers who need to understand your business, services, contact details, forms, menu, booking links, and store links. Keep the first version clear rather than broad: explain what you sell, where or how you operate, and what the customer should do next.

Bookings / servicesTake bookings

Configure Helm services, availability, bookings, waitlist, and events around customer-ready workflows the product actually supports.

Create services with names customers understand, clear durations, pricing where relevant, buffers, booking limits, and availability rules. Keep the public booking page easy to use so customers can pick a service and time without needing manual back-and-forth.

Store / ordersSell with Store + Orders

Operate products, checkout, order records, receipts, and Business commerce tools within Helm's website-first merchant scope.

Growth includes Store + Orders for a product catalog, inventory-aware storefront, cart, Stripe checkout, durable order records, fulfillment status, receipts, customer history, and exports.

CRM / customersManage customer records and Timeline

Manage Helm customer records, timeline notes, reviews, tags, follow-up work, and context from bookings, orders, invoices, and forms.

Customers are the shared record behind bookings, orders, invoices, receipts, forms, review requests, notes, tags, segments, and follow-up work. A good customer profile gives the merchant a clear history without forcing them to jump across modules.

Invoices / receiptsSend invoices and receipts

Create, send, track, print, recover, and connect Helm invoices, receipts, and commercial documents from Money/Documents workflows.

Invoices support draft creation, editing, customer association, line items, sending by email, resend, status tracking, mark-paid flows, cancellation, print/download, search, filtering, and CSV export.

Getting startedHow to get the most out of Helm

Connect Helm modules into one launchable merchant workflow across website, bookings, CRM, invoices, receipts, follow-up, and insights.

Helm is most useful when modules connect around real customer work. A simple launch path is website page, first offer, first customer, first booking or order, first invoice or receipt, and a short review of staff and support preferences.

Website / CMSCreate a menu

Create customer-readable Helm menus, connect browsing to public pages, and decide when menu demand should move into Store + Orders.

Create a menu when customers need to browse items before they call, visit, book, or order. Keep item names, prices, availability, categories, and dietary notes accurate enough for mobile browsing.

Website / CMSUse forms for leads

Use Helm forms for leads, quotes, registrations, and customer questions without creating dead-end submissions or lost follow-up.

Use forms when a customer needs to ask a question, request a quote, register interest, or send details before your team decides the next step.

Getting startedRead Insights

Use Helm Insights to understand Helm-owned activity, connect signals to customer and follow-up work, and decide what to improve next.

Insights become useful after Helm has real source activity: website views, bookings, forms, customers, invoices, receipts, orders, and reviews where those modules are enabled.

Plans / billingUnderstand advanced features scope

Understand planned advanced Helm scope, feature boundaries, account preparation, and how to avoid promising advanced workflows before release.

Advanced features like roles/rights, audit trail, location-aware operations, events, gift cards, loyalty, and additional staff seats are planned for a future tier.

Plans / billingManage your plan and billing

Understand Helm plan boundaries, billing portal changes, pricing lanes, subscription expectations, and planned advanced scope.

Starter and Growth are self-serve checkout plans. Starter is the core operating system for Presence basics, bookings, menu, CRM, forms, invoices, receipts, insights, and one staff seat.

Plans / billingReferral program FAQ

Understand Helm referral links, eligible trial bonuses, pending rewards, disqualification rules, public sharing, and manual account-credit review.

The Referral program is a signed-in merchant feature for sharing Helm with other merchants. Owners and permitted managers can find their referral code and link in dashboard Settings under Referral program at /helm/settings/referrals.

Team / securityWork with staff roles

Invite Helm staff, manage seats and roles, protect owner boundaries, and understand security scope across Starter and Growth.

Team management lives in Settings. Owners and permitted managers can invite team members, resend invites, update roles where allowed, deactivate or reactivate users, and stay within the seat limits for the active plan.

TroubleshootingTroubleshoot public pages and checkout

Work through common Helm public page, booking, checkout, invoice, receipt, and account issues before creating a support ticket.

If customers cannot open a public page, confirm the site is live, the feature is enabled on the current plan, the item is published or visible, and the URL uses the right site slug. Draft previews and published pages are different surfaces.

Account accessRecover account access

Recover Helm account access, accept staff invites, use configured sign-in options, and keep owner control tied to the right business site.

Helm supports the dashboard authentication methods configured for the environment, including email/password, magic-link flows, and Google Sign-In where Google OAuth is configured.

How Helm support is organized

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.

Start from the customer path

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.

Keep source records authoritative

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.

Use plan scope before troubleshooting

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.

Separate public help from account support

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.