Delivery Process
The process page explains how customers move from public service pages into configuration, checkout, provisioning, access delivery, support, billing, and renewal operations.
Core Flow
5
Fit, configure, pay, provision, operate.
Records
Unified
Orders, payments, support, and subscriptions stay connected.
Handoff
Managed
Access and operational notes are assigned after provisioning.
The public site explains service families, plan categories, and operational outcomes. Customers can compare managed servers, AI services, workflow automation, Vicidial support, cybersecurity, and development support before entering the portal.
Public pages explain the service category and use cases.
Plans show pricing, features, and supported billing cycles.
Contact-sales services route to the correct department before checkout.
The portal captures the choices needed for fulfillment: plan, billing cycle, region, storage, operating image, add-ons, and final deployment notes. This reduces back-and-forth after payment.
Configuration choices are tied to the order record.
Deployment notes guide the provisioning team.
Pricing summary updates before order creation.
Orders and wallet funding are reviewed through structured billing flows. Card payments and manual payment submissions can be connected to invoices, wallet balances, and subscription status.
Manual payments are verified before account credit is applied.
Wallet balance can support future renewals.
Invoices and payment activity remain visible to the customer.
After review, the team provisions the service, records access details, adds operational notes, and connects the active service to ongoing support and billing records.
Credentials and service details are assigned after setup.
Subscriptions show status and renewal information.
Support tickets can reference the affected service directly.
The customer journey continues after launch. Support, renewals, billing, service notes, and account changes remain inside the portal instead of splitting across unrelated channels.
Support requests remain attached to customer history.
Renewals can use wallet balance first, then payment fallback.
Service updates and admin actions are tracked operationally.
Loading workspace data
Fetching the latest account details.