SAVHN Support & Reliability: Frequently Asked Questions
Getting stuck on something in SAVHN shouldn't mean guessing. This FAQ covers the real support surfaces available — the Documentation Portal, the Developer Console, and the ticket-based support paths — plus basic troubleshooting steps worth trying before you reach out, and honest answers about what's confirmed versus what's worth asking the team directly.
Getting Help
What's the first place to look if something isn't working as expected?
The Documentation Portal (/docs) is the primary self-serve resource — it covers the API reference, developer guidance, and how the platform's core mechanics (authentication, module entitlement, data isolation) actually work. For most "how does X behave" questions, this is faster than waiting on a support response, and it reflects the real, current behavior of the platform rather than an aspirational description.
What is the Developer Console, and who is it for?
The Developer Console is a dedicated admin surface (separate from a regular organization's admin area) covering things like the Product Catalog, Package Builder, demo environments, subscriptions, billing engine, coupons, upgrade requests, platform APIs, and a knowledge base tab — the operational tooling behind how modules, packages, and billing get configured and administered. It's most relevant to the team building and operating packages and pricing on the platform, alongside the developer-facing documentation for anyone building an integration.
How do I reach a real person if documentation doesn't answer my question?
/book-demo connects you with a real conversation — use the general form for sales, pricing, or onboarding questions, or /book-demo?interest=developer-support specifically when your question is technical (API behavior, authentication, integration questions) so it routes to the right team rather than getting stuck in a general inquiry queue.
Is there a ticketing system for support requests?
Yes — Tickets is one of SAVHN's core modules, and it's also the underlying mechanism used in parts of the platform's own internal support workflow (referenced in the Developer Console as a Ticket Center). If your organization has Tickets enabled, the same real queue-and-stage mechanics you'd use for your own customer support are available to you, which means you can also see firsthand how the module behaves by using it for your own team's support needs.
What kind of response times can I expect from support?
Specific response-time commitments (like a formal SLA) are the kind of concrete number worth confirming directly through /book-demo rather than a generic figure stated here, since the right commitment depends on your license tier and the nature of the issue. Documentation-answerable questions are typically faster to resolve by checking /docs first than by waiting on a queued response.
Troubleshooting Basics
I'm not seeing a module I expect to have access to. What should I check first?
Two separate things control this, and it's worth checking both: whether the module is actually enabled for your organization (check the Module Marketplace in your admin area), and whether your specific role has visibility into it (module visibility can be restricted per role even for modules the organization has enabled). A module can be fully enabled organization-wide and still be invisible to a role that's been scoped down.
My session got logged out unexpectedly. Is that a bug?
Not necessarily — sessions are tracked by token ID and can be revoked in real time, whether by an admin action, a security event, or normal expiry. If you believe your session was revoked incorrectly, that's worth raising with your organization's admin first (since they control session and access decisions) before assuming it's a platform issue.
An AI feature is showing placeholder-style output instead of a real generated response. Is that broken?
Not necessarily a bug — it's the expected behavior when no AI model provider is connected for your organization. SAVHN's AI features explicitly mark placeholder output rather than fabricating a response, so seeing a labeled placeholder means the honesty pattern is working as designed. If you expect a real model to be connected and you're still seeing placeholder output, check AI Studio's provider configuration first.
A module I disabled is still showing old data when I check its records. Is that expected?
Yes — disabling a module removes it from navigation and stops new activity, but it does not delete existing historical data. If you re-enable the module, you'll see that data still there. This is intentional, not a sync issue, and it's actually the behavior you'd want if you disabled the module temporarily rather than permanently.
An integration credential I connected shows "not configured" even though I entered it. What's happening?
Credentials are encrypted at rest and never returned to the client in API responses — only a configured true/false flag is shown. If a save didn't go through correctly, the flag would read as not-configured; try re-entering and saving the credential, and if it still doesn't reflect as configured after a clean save, that's worth raising with the developer team rather than assuming the value itself is wrong.
Where do I check the status of a specific API domain if I'm not sure it's live yet?
The /developers page lists domains as they're actually deployed, each labeled AUTH or PUBLIC — that's the accurate current reference rather than assuming a domain exists because it seems like it should based on a related feature you've seen elsewhere.
Does SAVHN publish uptime or reliability statistics?
Specific uptime figures and reliability commitments are the kind of concrete, verifiable numbers worth confirming directly with the team — through /book-demo — rather than accepting a general assurance, consistent with SAVHN's approach of not stating specifics it can't back up in this kind of content.
Is there a status page I can check during an outage?
If you're experiencing what looks like a platform-wide issue rather than something specific to your organization's configuration, the fastest way to get a real, current answer is reaching out through /book-demo?interest=developer-support rather than guessing from indirect signals, since this is exactly the kind of time-sensitive question worth confirming directly.
What's the best way to report a bug versus ask a "how do I" question?
A "how do I" question is usually fastest resolved through the Documentation Portal first. If you've found something that looks like a genuine defect — data not behaving as documented, a permission not enforcing correctly — that's worth routing to the developer team directly through /book-demo?interest=developer-support so it reaches the right people rather than getting lost in a general inquiry queue.
If I'm evaluating SAVHN during the trial and hit a question, is support still available?
Yes — trial organizations are real organizations running the real product, so the same Documentation Portal and /book-demo paths apply during your 7-day free trial as they do after you convert to a paid license. You're not evaluating a reduced-support trial mode.
Does SAVHN back up my data, and can I request a restore if something is deleted by mistake?
Data durability and backup/restore specifics for your organization are exactly the kind of operational detail worth confirming directly with the team through /book-demo, since a generic answer here wouldn't tell you anything you could actually rely on if you were facing a real data-loss situation.
Are there planned maintenance windows, and will I be notified in advance?
Planned maintenance practices and notification norms are worth confirming directly with the team if this matters to how your organization schedules critical work — rather than assumed from this FAQ, since the honest answer is specific operational detail rather than something to generalize about.
If my organization is on a trial and hits an issue that blocks evaluation, does that affect my trial period?
If a genuine platform issue interferes with your evaluation during the 7-day free trial, raising it directly through /book-demo?interest=developer-support is the right step — that's a conversation the team can have directly with you about your specific situation, rather than something a general FAQ answer can resolve for you.
How do I escalate an issue that the initial support contact hasn't resolved?
/book-demo?interest=developer-support is the direct line to the developer team for technical issues; if an issue remains unresolved after your first contact, following up through the same channel with the earlier context (what you reported, when) is the most effective way to get it escalated, rather than starting a fresh, disconnected inquiry.
Does the Documentation Portal cover module-specific "how do I" questions, or just the API and platform mechanics?
The Documentation Portal is the broader developer guide covering platform mechanics and the API in depth; for module-specific workflow questions — how a particular field behaves in CRM, for instance — the module itself, its own dedicated product page, and hands-on exploration during your trial are often the fastest way to get a concrete answer, alongside asking the team directly if something is still unclear.
If I'm not technical, is the Developer Console relevant to me at all?
Probably not directly — the Developer Console is oriented around Product Catalog, packaging, billing engine, and platform-API administration, which is more relevant to the team operating the platform's commercial and technical configuration than to a general end user. A regular organization's day-to-day support needs are better served by the Documentation Portal and /book-demo than by the Developer Console.
What information should I have ready before contacting support about a specific issue?
Having the specific module or API domain involved, roughly when the issue occurred, and what you expected to happen versus what actually happened makes it much faster for the developer team to verify and resolve an issue when you reach out through /book-demo?interest=developer-support, compared to a general description without those specifics.
Does SAVHN offer any self-service way to check whether an issue is on my end (configuration) versus a platform issue?
Checking the Module Marketplace for enablement status, your role's module visibility, and AI Studio's provider configuration covers a large share of "why isn't this working" situations that turn out to be configuration rather than a platform defect — worth ruling those out first using the troubleshooting steps above before assuming something is broken on SAVHN's side.
Is there a community forum or user group where I can ask other SAVHN users questions?
The primary supported channels are the Documentation Portal for self-serve answers and /book-demo?interest=developer-support for direct contact with the team — if a community forum or user group exists or is planned, that's worth confirming directly with the team rather than assumed, since this FAQ should only describe what's actually confirmed rather than a nice-to-have that may not exist.
If something in this FAQ doesn't fully answer your question, the Documentation Portal has deeper detail, and the developer team is a direct message away through /book-demo?interest=developer-support. Ready to see the product firsthand rather than read about it? Start a 7-day free trial — no card required — and configure the modules you need through the Visual Pricing Configurator.