Custom Plan Builder
Overview
The Custom Plan Builder lets you compose a tailored Survanta commercial request by choosing a base plan, selecting limit groups, adjusting numeric limits and Boolean capabilities, reviewing a server-authoritative estimate and discount, entering company details, and submitting the request. The browser summary is a preview; the server validates the current effective plan and limit prices before submission.
Step-by-Step Guide
Stage 1 — Choose a Base Plan
The builder opens with plans that are active and explicitly visible in the custom builder. Each plan supplies included values, supported billing period, and effective price rows. Click Select on the plan that best matches your starting point.
You can change the base plan at any time while building your configuration.
Stage 2 — Select Limit Groups and Capabilities
Choose at least one active limit group. The current catalog contains six groups:
- Survey operations (
CORE) — total and concurrently active surveys. - Responses and reporting (
RESPONSES) — response capacity and Excel export. - Team (
TEAM) — active tenant-user capacity. - Storage (
STORAGE) — managed storage, individual upload size, and file-compression capability. - Access and integrations (
ACCESS) — single-survey links/QR, portal and viewer tokens, integration clients, and reports/raw-response API capabilities. - Communications (
COMMUNICATIONS) — tenant notification batches, recipients, and mobile pushes.
The old “add-ons” concept is retained as a compatibility explanation: optional capabilities are not stored in a parallel PlanFeature model. They are Boolean limit rows and accept 0 for disabled or 1 for enabled. The four current capability keys are Excel export, file compression, Reports API access, and Raw Response API access.
Stage 3 — Adjust Limits and Add-Ons
Within the selected groups, adjust values exposed by the catalog. The current 17 active keys include 13 numeric limits and four Boolean capabilities. Common numeric examples include:
- Users — maximum active tenant user accounts.
- Surveys / Active surveys — total survey records and concurrently active surveys.
- Responses — accepted response capacity for the entitlement's configured usage period; this is tenant-wide, not “per survey.”
- Storage / Maximum upload size — total managed storage and one-file upload size.
- Public links, Portal tokens, and Viewer tokens — separate active-token capacities.
- External integrations — active integration-client capacity.
- Notification batches, recipients, and mobile pushes — communication quotas in their configured periods.
Numeric values cannot go below the plan baseline or catalog minimum and cannot exceed the catalog maximum. An included value of -1 means unlimited and cannot be increased. Byte-based values are displayed in GiB or MiB as appropriate. Toggle Boolean capabilities on or off; their server values remain 1 or 0.
Planned, not currently selectable: MaxSurveyVersionsPerSurvey will be one numeric CORE value from 0 through 50, never a Boolean and never unlimited. 0 disables customer-visible Version History/Restore; 1..50 sets the visible/restorable count including current. The planned Custom baseline is 0. Do not expect this control until the catalog key, server pricing/configuration, and versioning feature are implemented; runtime contentHash will not be paywalled by it.
Stage 4 — Review the Server Quote and Discount
The summary panel shows a running total, and the builder posts the current selection to the quote endpoint after changes. The server resolves the active effective-dated plan price and incremental limit prices, validates bounds and pricing context, and returns the quote used by the review:
| Item | Amount |
|---|---|
| Base plan monthly price | Shown per base plan |
| Capability additions | Server-priced Boolean capability increases |
| Numeric limit additions | Server-priced increases above the included values |
| Subtotal | Base price plus additions |
| Discount | Validated discount amount, if an eligible code is applied |
| Tax | Current quote value; currently zero in this workflow |
| Final estimated price | Server-calculated total for the displayed billing period |
The current builder uses the platform-default country and currency as the effective market; company country input does not switch the quote market. Review the displayed country, currency, and billing period. If pricing is unavailable, a discount is invalid/not started/expired/restricted, or a per-user discount requires sign-in, correct the issue before continuing. This remains an estimate; the submitted order and invoice snapshot are authoritative, and the platform review precedes application.
Stage 5 — Enter Company Details
Enter the organization name and pricing-context country, then provide industry and team size when relevant. Enter the primary contact name, contact email, activation/invoice email, phone number, and optional notes. Required fields are checked before the builder advances. These details are assembled into the request's customer notes; review them for accuracy and do not include payment credentials or unnecessary personal data.
Stage 6 — Review and Submit
The final stage summarizes the plan, selected scope, company/contact details, billing period, and latest successful server quote. Confirm the contact-consent checkbox, then:
- Click Submit Request to send the configuration to the platform team. You must be signed in and have the website submission permission.
- Use Save & Exit to return to pricing while supported selections remain in the current browser session. This is not a named, account-level server draft.
On submit, the server prices and validates the request again, creates a commercial Draft, and immediately attempts to move it to Submitted. A failure leaves no basis for assuming the request entered review; read the displayed error, correct the pricing/limit/discount/session issue, and retry.
Submitting Without Being Signed In
If you click Submit Request while not signed in, a login/register prompt opens. The return path targets stage 6, and plan, group, limit, discount, and step selections are retained in the same browser session. Company/contact fields are not included in the stored session payload, so re-enter and review them after returning. Clearing session storage, switching browser/profile, or ending the session can lose the selection.
After Submission
Once successfully submitted, the configuration becomes a Submitted commercial order visible on My Requests. Track its order/invoice details and website notifications. The normal lifecycle is Draft → Submitted → Approved → Applied, with Rejected or Cancelled as terminal alternatives. A built-in conversation is not exposed on the current order details page; quote the order number in an approved support channel when follow-up is needed.
Frequently Asked Questions
Can I submit more than one plan configuration? Yes. You can submit multiple plan requests if you are evaluating different configurations. Each is reviewed independently.
Can I go back and change a submitted request? Submitted requests cannot be edited on the website details page. Cancel an eligible Submitted order with no payment record and create a corrected request, or quote its order number when contacting the platform team.
Does submitting a plan request charge my card? No card is charged by submission, and no online payment gateway is currently implemented. Submission creates an order and invoice in Draft/Submitted commercial state. After approval, the details page can expose the applicable offline payment-proof workflow; entitlements are applied only after the approved order reaches Applied.