Chatbot studio

Design, publish, and run chatbots your team can stand behind.

Spire Bot is a visual studio for building customer conversations. Draw each flow on a canvas, test it before customers see it, publish it as a versioned release, and run it on web chat and WhatsApp Business with a handover to your own agents.

The Spire Bot flow designer showing a sample bot as connected steps on a canvas.
The flow designer. Each box is a step in the conversation.

How it works

From first draft to live conversation in four steps

  1. Design

    Drag steps onto the canvas and connect them. Split the bot into flows, one per customer goal.

  2. Test

    Validate the draft for structural problems, then talk to it in the playground and read the trace of every step.

  3. Publish

    Publishing creates a numbered release that cannot be edited. Republish an earlier release at any time.

  4. Deploy

    Embed the web chat widget on your site, connect a WhatsApp Business number, or do both.

Channels

Web chat and WhatsApp Business from the same bot

Build the conversation once. Spire Bot adapts text, buttons, lists, and carousels to each channel.

  • A web chat widget you can style to match your site, with no code, and embed with one script.
  • WhatsApp Business Cloud API support, including media, locations, contacts, approved templates, WhatsApp Flows, products, and catalogs.
  • The 24-hour customer service window is enforced for you; only approved templates can be sent outside it.

Web chat details · WhatsApp details

The Deploy page listing channel deployments.

Live support

Hand over to a person when the bot should stop

A Live Agent step passes the conversation to the right department. Agents claim it from a shared inbox with the transcript in front of them.

  • Departments route chats to the team that owns the topic.
  • Canned responses and chat tags keep replies fast and reporting consistent.
  • Customers see the nickname and avatar an agent chooses, never the account email.

More about live support

The Agent inbox.

Security and governance

Controls for teams that answer to someone

  • Role-based access: people see only the menus and actions their roles allow.
  • Each bot keeps an audit log of who published or changed something, and when.
  • API credentials are encrypted when stored and never copied into a bot.
  • Outbound API calls go only to hosts you have saved as connections.
  • Published releases cannot be edited, so what you tested is what runs.
  • Values marked sensitive are kept out of traces and transcripts.

More about roles and audit

The audit log for a bot.

See Spire Bot with your own use case

Tell us what you want your bot to do. We will walk you through building it, from the first flow to a live conversation.