Feature referencePlans and usage · 05 of 05

Plans and usage

Business onboarding and integration support

Business includes hands-on help applying Stand to a website UI and support for one mutually agreed backend API workflow, plus invoicing and purchasing coordination.

Availability
Business
Configured in
Arrange scope with Stand through the Business purchasing and onboarding process
Category
Plans and usage
Reference status
Current
01

What the support covers

  • Hands-on onboarding for how Stand entry points should fit the customer website interface.
  • Help choosing between the floating widget, behavior rules, Stand button, Stand card, and public JavaScript API.
  • Support for one agreed backend API workflow that connects a specific customer use case.
  • Business invoicing, purchase, and internal procurement assistance.
02

Agree the scope first

  • Identify the website, user journey, and desired visitor outcome.
  • Define the exact backend system, operation, authentication boundary, inputs, and expected result for the one workflow.
  • Assign customer and Stand owners for implementation, testing, and acceptance.
  • Document data sensitivity, authorization, failure handling, and the handoff after launch.
  • Confirm what is customer implementation, Stand configuration, or Stand-delivered support.
03

Relationship to self-serve features

Business support sits on top of the same supported product surfaces documented in this reference. Customers can still use widget installation, declarative components, visitor identification, private context, and the JavaScript API directly. The support entitlement adds coordinated design and integration help; it does not turn private internal APIs into public contracts.

04

Typical delivery sequence

  • Discovery and selection of one concrete journey.
  • Technical and security review of the agreed boundaries.
  • Website UI implementation and Stand configuration.
  • Backend workflow implementation where included.
  • Joint testing in the agreed environment, then launch and documented ownership.
05

Explicit boundaries

  • Only one agreed backend API workflow is included unless a broader commercial scope is separately agreed.
  • General custom application development, unrelated integrations, and indefinite engineering capacity are not implied.
  • The customer remains responsible for its systems, credentials, authorization decisions, and legal basis for data use.
  • Timelines and deliverables depend on the agreed scope and prerequisites rather than the plan name alone.