Enterprise flow

From first contact to go-live: who does what

Six steps. Each box says who acts. This page promises no dates; what we agree is written in your order form.

The flow

Six steps, three kinds of actor

Enterprise flow in six stepsLeft to right, top row then bottom row: you get in touch; discovery and scoping; signed order form; workspace and keys; install the chat kit; go live. Each box names who acts. The same steps are listed below as text.STEP 1Who: YouYou get in touchEmail us or use the contactform with your use case.STEP 2Who: You and VedikaDiscovery and scopingA call, then sandbox accesswhile we scope the work.STEP 3Who: You and VedikaSigned order formAccess, capacity, integrationand support are agreed.STEP 4Who: Vedika, then youWorkspace and keysWe invite your owner. Youcreate a server key.STEP 5Who: Your engineersInstall the chat kitSDK, widget or embed, plus abackend token mint.STEP 6Who: You, with Vedika supportGo liveIntegration review, any agreedload test, then launch. Enterprise flow in six stepsTop to bottom: you get in touch; discovery and scoping; signed order form; workspace and keys; install the chat kit; go live. Each box names who acts. The same steps are listed below as text.STEP 1Who: YouYou get in touchEmail us or use the contactform with your use case.STEP 2Who: You and VedikaDiscovery and scopingA call, then sandbox accesswhile we scope the work.STEP 3Who: You and VedikaSigned order formAccess, capacity, integrationand support are agreed.STEP 4Who: Vedika, then youWorkspace and keysWe invite your owner. Youcreate a server key.STEP 5Who: Your engineersInstall the chat kitSDK, widget or embed, plus abackend token mint.STEP 6Who: You, with Vedika supportGo liveIntegration review, any agreedload test, then launch.
  • You act
  • You and Vedika act
  • Vedika acts first

In words

What happens at each step

  1. You get in touch

    Who: you

    Email [email protected] or use the contact page. Tell us your use case, your expected volume and what you need to integrate.

  2. Discovery and scoping

    Who: you and Vedika

    We talk through your use case. While we scope the work, you can try the fixed sample sandbox and read the documented request contracts.

  3. Signed order form

    Who: you and Vedika

    We agree access, capacity, integration scope, launch and support responsibilities in a signed order form. Uptime and support terms are set there, not on public pages. See the enterprise page.

  4. Workspace and keys

    Who: Vedika, then your owner

    We set up your workspace and invite your owner by email. The invitation can be accepted once, and it expires after 72 hours; we can resend it. Your owner signs in to the admin console, creates a server key and copies the secret once into your backend secret manager, then publishes each exact HTTPS site that may show the chat.

    Your own users keep signing in to your app. Workspace invitations are for your operators. See Getting started.

  5. Install the chat kit

    Who: your engineers

    Choose a surface: the JavaScript SDK, the chat widget or a platform embed. On your backend, authenticate your user, mint an origin-bound token and hand the browser a single-use ticket. The server key never reaches the browser. See Bring your own login.

    We give your engineers access to the kit sources during onboarding. The documentation is public at the developer docs.

  6. Go live

    Who: you launch, with Vedika support as agreed

    Before launch, check an answer, Stop, the receipt and renewal from your approved HTTPS site, and test mobile on real devices. Confirm your billing arrangement and how your app handles a low balance. Support requests go through the console support page. The scope of Vedika support after launch is whatever your order form says.

Good to know

What this page does not say

  • It gives no timelines, uptime figures, response times, certifications or prices.
  • There is no separate kit download to hunt for. If your team needs the kit sources, we share them at step 5.
  • Not sure whether you need the API or the harness? Read Vedika vs harness, in plain English.

Ready to start step 1?

Send us your use case and expected volume. We will reply by email.

[email protected]talk to us Vedika vs harnessplain English