Getting started

The Console dashboard

A tour of every screen in the BimpeAI Console dashboard — where you build workflows, test agents, connect channels, manage integrations, and generate API keys.

The Console dashboard is the no-code home for building, testing, deploying, and managing your agents. A left sidebar lists the screens — Overview, Workflows, Playground, Conversations, Integrations, Deploy, Team settings, and Settings — and a switcher at the top of every screen selects which agent you are working on. Builder Track users run their whole flow here; developers come here for two things in particular: connecting channels on the Deploy screen and generating an API key under Team settings → API keys.

Workflows

A workflow is the configuration an agent runs — its system prompt, rules, and flows. The Workflows screen lists a Recommended row for common use cases and an All Workflows catalogue you can filter by category (Food & Beverage, Retail, Services, Logistics, Hospitality, Support) or search. Each card shows its author, visibility (Public or Private), category, and rule count; the workflow your current agent runs is marked Active. Use Create workflow to build your own from scratch. Developers can do the same through the API — see Anatomy of a workflow agent.

Playground

The Playground is where you configure and test an agent in real time, over Chat or Voice. A right-hand panel splits into Workflow, Agent, and Actions tabs: change the workflow the agent runs, edit the System Prompt (with Edit / Preview, Generate, and Quick Start Templates such as Friendly Support, Sales Assistant, and Technical Expert), and exercise the agent's actions. A Persona selector and a Trace Reasoning toggle sit at the top, and a status badge shows whether the agent is in development.

Conversations

The Conversations screen holds your conversation history and any active conversations, across every channel. Filter by channel, open a thread to read it, and continue it from here. Each conversation has an AI on/off toggle that hands the thread between the AI and a human — the same control the API exposes as is_ai_chat_paused. Turn the AI off to reply yourself, turn it back on to return the conversation to the agent.

Integrations

The Integrations screen connects your agent to business systems and data sources. The first tab is a catalogue — Shopify, Bumpa, Google Calendar, GoHighLevel, Calendly, Google Sheets, Stripe, Paystack, and more (some marked Coming Soon) — where you click Connect on a card and follow the prompts. Further tabs cover Custom API, Custom MCPs, Webhooks, Scheduled Events, and Data Models. Developers can configure most of these from the SDK instead; see Configuring integrations.

Deploy

The Deploy screen is where you connect channels so customers can reach your agent. A panel at the top issues a test code and Test on WhatsApp / Test on Instagram links — share the start <code> message with testers so they can message the agent before you go live. Channels are grouped into two sections:

  • Messaging & Chat — WhatsApp, Instagram, Messenger, and the Web Chat Widget are live; click Connect on a card and follow the prompts. Mobile Chat SDK, Telegram, Slack, and Mattermost are marked Coming Soon.
  • VoiceWeb Voice lets customers talk to the agent from your site (Enable). Telephony is an add-on with usage-based pricing for real phone calls (Set up). Mobile Voice SDK is Coming Soon.

Telephony spans three screens

After you click Set up on the Telephony card, provision or link a number under Team settings → Phone numbers (or contact support), then set the agent's voice and greeting under Settings → Voice. Telephony conversations are surfaced through the API under the telephony channel.

Team settings

Team settings covers telephony, call history, and team API access across three tabs:

  • Phone numbers — the numbers provisioned for your team. Link each one to an agent to enable inbound routing.
  • Call logs — telephony sessions across all agents on the team, including test calls from the Playground.
  • API keys — generate the Console API credentials your SDK uses. Send a key as Authorization: Bearer <key> or X-Api-Key: <key> against the Console API (api/v1/console). Keep secret keys server-side and never expose them in client-side code.

Developers start here

Generate your SDK key under Team settings → API keys, then head to Authentication and the Quickstart.

Settings

Settings manages your workspace across several tabs:

  • Agent — the agent's name, logo, timezone, escalation email, and notification channels (Email, WhatsApp, Phone), plus a test panel.
  • Team — team name, members and invites, and the business details that give the agent its business context.
  • Billing — your plan (Free, Pro, or Team), work credits, credit purchases, payment method, and usage.
  • Agency — the agency dashboard, available on the Team plan.
  • Voice — the numbers assigned to this agent, its voice profile and greeting for Playground and telephony calls, and recent call logs.
  • AI Model — the model provider (OpenAI, Google Gemini, Grok, or Anthropic Claude), the specific model, and your provider API key.

Where to next

On this page