HELP & ANSWERS
Answers before your first launch.
Understand accounts, APIs, provider requirements and the difference between publishing a version and activating a real service.
COMMON QUESTIONS
Before you start
A few essentials for your first Sandbox, your integrations and your launch.
Getting started
Can anyone create a Sandbox?
Yes. Use a verified Google account from any email domain to create your Developer account and an isolated workspace. A company email or Servinexa invitation is not required.
What happens when I reach a Sandbox limit?
Limits, reset periods and automated controls depend on the configuration enabled for your workspace. Agree additional capacity with Servinexa. Sandbox does not become paid Production automatically.
Do people using my service need Developer accounts?
No. The Developer account is for the person building and managing the workspace. People using your service interact through its configured channel, not through Studio.
Is AI required, and is it included?
You can build workflows manually. Where configured, AI assistance produces proposals for your review, not automatic publication. AI credits are separate from your workspace plan and provider fees.
Integrations & data
Which channels and APIs can I connect?
The platform has USSD, Web Chat and WhatsApp channel models and HTTPS API integration contracts. Actual availability depends on the qualified adapter and configured provider. Managed Production currently supports approved Web Chat releases; creating a Sandbox does not activate a telecom or messaging provider.
Can I test real provider APIs in Sandbox?
Real HTTPS tests require a separately enabled, qualified Sandbox configuration with isolated credentials and bounded usage. Otherwise, use the no-call Studio simulator. Inbound webhooks and outbound channel adapters require separate provider qualification; an API test is not a complete channel activation.
Do I need separate provider accounts or a shortcode?
Arrange provider registration, access approval, numbers or shortcodes directly with your channel provider. Servinexa does not automatically create provider accounts, allocate shortcodes or include third-party charges.
Where will my data and credentials be handled?
Runtime placement determines where execution and conversation storage run. Credentials are separate from authored workflows. Confirm data location, access, retention and backup requirements with Servinexa before Production.
Going live & support
Does publishing make my app live?
No. Publishing saves an immutable version. Production requires agreed commercial terms, supported channel configuration and explicit Servinexa operator activation.
What moves from Sandbox to Production?
An explicit promotion copies the chosen published workflow into a separate Production draft. Test credentials, integrations, bindings, sessions and approvals are not copied. Configure Production separately and obtain operator activation before serving real traffic.
How do I arrange Production, support or an on-premises rollout?
Start with a Developer account and Sandbox. Agree the service scope, pricing, support and deployment requirements directly with Servinexa before activation. On-premises delivery requires separate qualification; signing up does not create an installation or service-level commitment.
An idea is enough to get started.
Create your Developer account and make your first flow.