How support is structured
Support is not one undifferentiated inbox. Baseline coverage can include account access help, platform issues, billing questions, launch stabilization, and guidance on features included in your plan.
Custom work, major redesign, extensive content rewrites, and third-party vendor problems may require added scope, add-ons, or package upgrades depending on complexity.
Ownstack uses business-hours support with priority levels by plan, launch stabilization windows, and critical outage response — not default 24/7 human coverage unless a separate agreement says otherwise.
How to reach the team
Use the contact paths published for your brand and on ownstack.co. Demo bookings and inquiries route through official forms so requests are tracked and qualified correctly.
Clients of your brand should use your published support path first — the email or help flow shown in your app or public handoff page. Ownstack assists you when an issue appears platform-related, payment-related, or tied to a supported feature.
Feature requests are welcome after launch but are reviewed as included guidance, an add-on, an upgrade, custom scope, or a future roadmap item — not automatically bundled into monthly subscription.
Launch stabilization support
Launch stabilization is the short post-go-live window focused on confirming core flows work in real use: booking, payments, account access, and critical client paths within your scope.
It covers fixing launch-critical issues and guiding early use — not unlimited redesign, open-ended content projects, or major new features requested immediately after go-live.
Treat stabilization as a partnership window. Report issues promptly, participate in verification, and save larger creative changes for scoped follow-on work after core operations are steady.
Realistic response expectations
Response time depends on plan tier, issue severity, business hours, and whether the problem is platform-related. Ownstack avoids fixed response-time promises unless they are written into your support agreement.
A critical outage means a severe platform issue blocking core operations — app unavailable, booking blocked, payment-critical flows failing, or account access incorrectly locked for platform reasons. Those receive prioritized handling.
Third-party issues with Stripe, Apple, Google, domain registrars, or email providers follow vendor timelines. Ownstack can help diagnose supported integrations but does not control external resolution speed.
Updates and maintenance
Standard platform updates, maintenance, and improvements are included in the monthly subscription. Routine maintenance may happen as needed; major visible or brand-specific changes are communicated or coordinated when practical.
Brand-specific redesign, custom features, extra quality cycles, or large content changes may require added scope beyond baseline maintenance.
You should not expect silent breaking changes to business-critical behavior without coordination when those changes affect client-facing flows you rely on.
Get help
Browse FAQ support topics for quick answers on billing, launch, and platform behavior. Contact the team for questions not covered there or to book a demo.
If you have not launched yet, read the launch process and pre-launch checklist guides so support conversations start from a shared understanding of scope and timeline.