Boardbox
Get access

Support

Support that investigates before it replies.

Every report is investigated against your code, your billing and what each launch changed, then answered with a reply you edit and approve. Support works from the same workspace that designed and built the product.

Watch one launchRequest early access

How it works

  1. 1

    Connect your source

    Connect a Gmail support mailbox read-only, or your own support system through the CX connector, and import conversations.

  2. 2

    It investigates

    The agent reads the report, your code and its history, billing records and company docs, and asks you when it needs to.

  3. 3

    Edit the reply

    A drafted reply and a status recommendation wait beside the case for you to edit and save.

  4. 4

    Approve and confirm

    You approve the exact reply. Delivery is confirmed by reading the report back from the source.

Investigation

Investigated before it is answered

Before it drafts anything, the agent reads the evidence: the report, the relevant code and its history, billing, and what recent launches changed.

  • Reads code, Stripe, RevenueCat and company docs
  • Raises questions for you instead of guessing
  • Never promises a refund, fix or date without evidence

Replies

Replies you approve exactly

The drafted reply and any status change are dispatched only after you edit, save and approve the exact text. Each approval is bound to the version of the report you saw.

  • Edit, save and send from the case
  • Status recommendations you accept or ignore
  • An approval goes stale if the report changes

Reliability

Writes that settle honestly

A reply applies at most once. When an answer from the source is lost, Boardbox reads the report back to settle what happened instead of blindly retrying.

  • Awaiting source confirmation, then confirmed by source
  • Silence or age never counts as resolved
  • Defects hand off to Product as an opportunity with evidence

Where it stops for you

Runs on its own

  • Imports and refreshes cases from your source
  • Investigates each report against the evidence
  • Drafts replies and recommends a status
  • Runs as the Support Responder when you turn it on

Waits for you

  • Every reply, as the exact text you approve
  • Every status change and closure
  • Answers to the questions it raises

What it works with

Reads

  • Gmail support mailboxes
  • Your support system via the CX connector
  • Your code and its history
  • Stripe
  • RevenueCat
  • Library

Produces

  • Investigations
  • Drafted replies
  • Status recommendations
  • Product opportunities

Where founders use it

A launch-day question

Support already knows what the launch changed, so the reply explains the new behavior correctly.

A billing complaint

The agent checks the subscription records before it drafts a word.

A real bug

The investigation becomes a product opportunity with the evidence a Build needs to fix it.

How it compares with an AI help desk bot

Answers fromHelp desk bot: Help-center articles.Boardbox: Your code, billing records and what each launch changed.
Who repliesHelp desk bot: The bot, directly to the customer.Boardbox: You, after editing and approving the exact draft.
BugsHelp desk bot: Escalated to a person.Boardbox: Handed to Product with the investigation attached.

In the Tablebird launch

Support already knows about the launch.

When a location manager asks why they can’t see another location, the reply explains the permission design, because support works from the same Initiative that designed it.

Follow the whole launch

What people ask

Which support tools connect?
Gmail mailboxes read-only, or any support system that implements the CX connector contract. There is no Zendesk or Intercom connector.
What is the Support Responder?
A built-in Automation that investigates when a report arrives or a customer replies. It starts paused until you turn it on.
Can it see my code?
It reads the working folders you choose on your Mac, and their history.
What if sending fails halfway?
Boardbox reads the report back from the source to settle what happened, and never sends the same reply twice.
Is this the Operations tab in the app?
Yes. In the app, customer support lives under Operations.

How it connects to the rest of the company

Every capability reads the same Library and reports into the same Initiatives.

InitiativesOne conversation that plans and runs work across the whole company.BuildCoding sessions in your own repo, on your Claude Code or Codex plan.DesignScreens drawn from your design system, approved one exact version at a time.VideoScripts, storyboards, generated takes and the exported cut.GrowthYour website, email, organic posts and ads, judged against the outcome.SalesProspect research, outreach, conversations and deals.AutomationsAgents on a schedule or a trigger that report back into the workspace.ObserveThe questions an Initiative keeps checking long after launch.LibraryWho you serve, how you sound and what you've decided, read first by every capability.

Early access · macOS

Run your next launch from one conversation.

We’re onboarding a few founders and small teams each week, one at a time, starting with the launch you’re planning next.

We email you once, when your seat is ready.