FAQ
Clear answers for the launch path.
HelixPilot is meant to stay understandable: one domain, one workflow, and a small number of manual touchpoints before the system can take over the repetitive parts.
Who is HelixPilot for?
HelixPilot is built for service businesses and intake teams that still win work on the phone. If missed calls mean missed revenue, the product is designed for you.
Does the website and the product use the same domain?
Yes. HelixPilot is set up so helixpilot.com can host marketing, signup, onboarding, billing, dashboard routes, and callback surfaces on one production origin.
What happens when a call needs a human?
HelixPilot can save the lead, notify staff, trigger a callback workflow, or send the follow-up text while preserving the context collected on the call.
Is onboarding self-serve?
Yes. The default path is signup into a guided onboarding flow, then into the dashboard. Manual tuning is still possible later inside the workspace.
Do I need a separate staging site or app subdomain?
No. The launch plan keeps one app and one Vercel project. Preview deployments handle pre-merge checks without forcing a permanent staging surface or app subdomain.
What setup still needs manual input?
The main manual steps are domain DNS, Vercel environment variables, and live phone routing or webhook configuration with providers like Vapi, Twilio, Stripe, and Inngest.
How does billing work?
Customers start through Stripe checkout inside the app and manage their subscription through the billing portal. The website and the in-product billing controls stay on the same flow.
Where do calls and leads end up?
Call and lead data lands in the dashboard and the underlying Supabase-backed records, giving operators one place to review recent call activity and captured leads.
Next step
Move from questions to a live workspace.
The fast path is still the same: create the account, run onboarding, and keep the rest of the setup limited to the few provider touchpoints that matter.