Bot Studio setup

WRNexus Bot Studio lives at bots.wrnexus.com. You build one bot, give it knowledge and forms, publish a version, and the same published bot answers on every connected surface — an embeddable website widget, a hosted chat page, the REST runtime inside your own app, and (as channels are enabled) WhatsApp, Instagram, Messenger and Telegram.

This page walks the full setup: create → configure → knowledge → forms → publish → connect channels. The two integration surfaces have their own pages: the embed & widget SDK for putting a bot on a website or app, and the client REST API & webhooks for reading bot data back out and receiving lead submissions.

Plan & flag. Bot Studio is gated behind the BOTS_ENABLED master switch (see deployment) and your workspace plan. While the flag is off the dashboard still loads, but the public runtime accepts no traffic.

The mental model

Create bot once
  → add knowledge (FAQs, services, documents)
  → build lead-capture forms
  → test the draft in the in-app preview
  → publish a version
Website widget · Hosted page · REST API · WhatsApp · Telegram · …
  all serve THAT published version
End users chat & submit data
  → conversations, contacts & submissions are stored in WRNexus
  → submissions are delivered to your API via signed webhooks

Three rules follow from this model and are worth keeping in mind:

• A bot has a draft and a published version. Editing changes the draft. Nothing reaches a live channel until you publish.
• Only an active bot with a published version is reachable. A paused, draft-only or deleted bot resolves to a graceful “unavailable” state on every public surface and leaks nothing about your workspace.
• Every conversation, contact and submission is scoped to one bot, workspace and organization. A bot can only ever see its own data.

1. Create a bot

1. Open bots.wrnexus.com and sign in with your WRNexus account. Pick the workspace the bot belongs to.
2. Go to Bots → New bot.
3. Give the bot a name, an optional description, and a primary language/locale (e.g. en, hi). The name and a URL-safe slug are used in the hosted page link and the widget teaser.
4. Save. WRNexus creates the bot together with its first draft version.

At this point the bot exists but is not yet reachable from any channel — it has no published version. You will publish in step 5.

2. Configure the bot

Open the bot and edit its settings. The fields that drive the public surfaces:

Setting	Where it shows up
Name	Widget header, hosted page title, chat greeting.
Avatar / logo	Widget launcher and header (falls back to the avatar URL).
Brand color	Widget accent + button color. Stored under settings.branding.color — see branding options.
Greeting / tone	The opening line. Tone (formal / playful / default) selects the greeting wording.
Locale	Default language tag surfaced to the widget and stored on contacts.

Branding is sourced from the bot’s own settings, so changing the brand color or logo and re-publishing updates every channel at once — you never edit the embed snippet to restyle the bot. The accepted keys and fallbacks are documented under Branding.

3. Add knowledge & services

A bot grounds its answers in the knowledge you give it. Two structured stores back every reply:

• Knowledge sources — FAQs and question/answer pairs the bot can quote. Add them under Knowledge. Each source has a title, body, language and status.
• Services / products — structured catalogue entries (name, description, price, etc.) the bot uses for service discovery, price questions and quote flows. Add them under Services.

Knowledge is bot-scoped, not version-scoped, so the published bot always answers from the single live knowledge base — update a FAQ or a price once and publish to roll it out everywhere.

Test as you go. Use the in-app Preview on the bot page to chat with the draft exactly the way the runtime will, grounded in the current knowledge and services, before you publish.

4. Build lead-capture forms

Forms turn a free-text chat into structured data you can act on.

1. On the bot, open Forms → New form.
2. Add fields. Each field has a key (used in API payloads and webhook values), a question/label, a type, and a required/optional flag.
3. Save the form. The published bot offers the form in chat; a completed form becomes a submission.

Every completed form creates a submission record tied to the conversation and contact. Submissions are:

• stored in WRNexus and visible under Submissions (and exportable),
• readable through the client REST API,
• and, if you register a webhook, delivered to your own endpoint as a signed submission.created event.

5. Publish a version

Publishing is what makes your edits live.

1. On the bot, review the draft (preview it one more time).
2. Click Publish. WRNexus snapshots the current draft as a new published version and points the bot’s active_version_id at it.
3. The bot’s status must be active for it to be reachable.

From this moment the website widget, hosted page, REST runtime and any connected channel all serve the new version. To undo, use Rollback to re-point the bot at an earlier published version — a one-click, confirmable operation.

Draft vs published. Editing after publishing only changes the draft again; live traffic keeps seeing the last published version until you publish anew. This is what lets you safely iterate on a bot that is already in production.

6. Connect channels

A published bot is reachable on these surfaces today:

Website widget

The fastest install. Copy the snippet from the bot’s Install panel (it is gated on publish status) and paste it into your site’s HTML. It only ever carries the bot’s public id — never a secret:

<script
  src="https://app.wrnexus.com/bots/widget.js"
  data-bot-id="BOT_PUBLIC_ID"
  async></script>

Full attribute list, theming and the programmatic chat API are on the embed & widget SDK page.

Hosted chat page

For clients without a website, every published bot has a shareable hosted page:

https://bots.wrnexus.com/c/{bot_public_id}

It frames the same chat runtime as the widget, is public (not login-gated), and degrades to a friendly “chat unavailable” message for an unknown or unpublished bot.

REST runtime (in your own app)

To embed the bot inside a native or server-rendered app, drive the public chat runtime directly: start a conversation, then post messages with the returned per-conversation token. See Programmatic chat.

Messaging channels

WhatsApp, Instagram, Messenger and Telegram connect through the Channels page. Each channel stores its provider credentials encrypted at rest and maps the platform’s inbound events onto the same runtime, so the same published bot answers there too. Channel availability depends on your plan and on the platform setup being completed.

7. Watch conversations come in

Once a channel is live:

• Conversations / Inbox shows every thread across all channels. An agent can take over a conversation, which pauses the bot’s automatic replies so a human answers from the inbox.
• Contacts unifies the people who chatted, with the identity and profile data each channel provides.
• Submissions lists captured form data with its delivery status.
• Analytics summarises conversations, contacts and submissions.

Next steps

• Embed & widget SDK — the snippet, its data-* options, branding, and the programmatic chat runtime.
• Client REST API & webhooks — read bots, conversations, contacts and submissions back out, and receive signed lead webhooks.
• Deployment & environment — every env var the Bot Studio app and runtime need, and how to deploy bots.wrnexus.com.