Sell with Store + Orders

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.