ChatFrom
In development
Use case

In-app assistant

Inside Beacon's signed-in app, the assistant knows who the user is: it answers from the docs, and creates projects for them through Beacon's own API, as that user and no further.

In developmentHow it's built
STARTvisitor messageCConditionintentcreateotherAtAsk the Visitorproject_nameAtAsk the VisitorwebsiteTCTool Callcreate_projectCMChat Modelcreated_reply

Each step lights as the agent runs it.

BBeacon AssistantSigned in as Leo
Ask a question…↑
How it's built

What it knows, what it can do, and the steps it follows.

The same three parts make every chatbot, set up in the dashboard without code: knowledge you add, tools you switch on or connect, and a workflow you draw.

01

Knowledge

How the product works comes from the docs, with the source. What the user has comes from your API.

  • docs.beacon.appWebsite · 60 pages
  • docs/sharing.mdMarkdown · 7 passages
  • Campaigns guide.pdfPDF · 24 passages
02

Tools

The widget goes in your app with one script tag, and passes the signed-in user's token on to your own server.

Your APIYour own endpoints as actions: the chatbot calls them with your keys, which stay on our server and never reach the model.create_projectlist_projects
Your tool serverOr the tools your MCP server offers. Your site signs a token for its user, and only your server sees it.create_project
03

Workflow

Each visitor message runs these steps: a condition reads what they want, and each answer has its own path. A question none of them takes is answered from the knowledge.

More use cases
Customer supportOrders and returnsSubscriptionsBookingsLeads and quotesInternal assistantIt can be anything →