Skip to content

Boreon MCP Layer · LLM Portal

Help that listens first. A person when you need one.

Boreon Support lives inside the portal. It answers from a knowledge base it can cite, works the problem with you for as many turns as it takes, and when it can't prove an answer, it says so and opens a case with your whole conversation attached. Email gets the same care: every reply is drafted with kindness and sent only after a person has read it.

Book a working session See it live at ai.boreon.com
Boreon Support

Why did my extract refresh fail last night?

Checking your site and the knowledge base

  1. 1Refresh history on your siteLive, read-only
  2. 2Extract refresh failuresKnowledge base
  3. 3Refresh extracts on a scheduleTableau help

The Sales Weekly extract stopped at 2:10 AM because its saved database password changed1. Update the embedded credentials on the data source, then run the refresh again23.

Still stuck? Open a case with this conversation.

Illustration · sample data

Answers it can prove.

Every answer comes from indexed documentation, and every answer shows where it came from. When the knowledge base doesn't cover a question, the agent doesn't guess. It tells you it will check with the team, and "I don't know" becomes a case.

  • Indexed, never invented

    Real documentation is split into passages and indexed in Postgres with pgvector. Only real, verifiable text goes in.

  • Sources on every answer

    Each answer lists the documents it drew on, so you can read them for yourself.

  • Your documents too

    Administrators can add their own Markdown or text documents and re-index the knowledge base in one click.

  • Tableau help, built in

    How-to answers draw on about 3,000 pages of official Tableau help for Tableau Server and Tableau Cloud.

It works the problem with you.

Ask once, in your own words. Boreon Support reads your account and your connected Tableau Server or Tableau Cloud site, read-only, and troubleshoots with you the way a good engineer would. While it works, you can see what it's doing, so waiting feels like progress, not silence.

  1. 01

    You ask

    In plain words, right in the portal. There's no form to fill in.

  2. 02

    It looks

    It reads your account, the knowledge base and your site: workbooks, data sources and refresh health, all read-only.

  3. 03

    It asks

    When something is unclear, it asks a gentle question instead of guessing.

  4. 04

    It answers

    Only what it can prove, with the sources it used.

  5. 05

    Or it opens a case

    One click carries the whole conversation to a person, so you never explain twice.

A case that already knows the story.

When it's time for a person, the case opens with your entire conversation attached. Our team works it from a queue with the full timeline. The agent may suggest a reply, but nothing reaches you until a person has read it. You hear from us by email when the case opens, when we reply and when its status changes.

Every case carries its own first-response and resolution clocks, and they're honest: a missed target stays on the record, even after the case is closed.

Case timeline Met
  1. Case opened with your conversation attached
  2. First-response clock started
  3. Suggested reply, held for a person to review
  4. Our team replied, and you got an email
  5. Resolved
Illustration · sample data

Kindness, built in.

Our support agent has a fixed personality: warm, patient and honest. The warmth doesn't depend on an AI model at all. Greetings, empathy and closings come from words we wrote ourselves, chosen for each message, so the kindness never drifts. The model only writes the part that has to be grounded.

  1. Listen first

    It acknowledges how you feel before anything else, and asks a gentle question when it isn't sure what you need.

  2. Read the room

    It notices when someone is frustrated, worried or up against a deadline, and meets it with extra gentleness.

  3. Never guess

    If it can't stand behind an answer, it says so kindly and checks with the team.

    I want to be sure I get this exactly right for you, so rather than guess, I'm going to confirm the details with our team and follow up.

  4. Never unkind

    No sarcasm and no foul language, not even a little. It never assumes the worst of anyone.

  5. Honest about its scope

    It talks about your platform and your Tableau Server or Tableau Cloud site, and about nothing it can't stand behind.

Kindness Procedures, designed by people.

In the Agentic Studio, our team lays out how the agents should treat people on a drag-and-drop canvas, starting from ten ready-made Kindness Procedures. Any step that would write or change something is gated by a person, and a procedure that would send a message without a person is refused.

  1. A message arrives
  2. Read the mood
  3. Check the knowledge base
  4. Draft with warmth
  5. A person approves Human gate
  6. Send once

Saved procedures are drafts our team designs and reviews. The inbox itself always keeps a person on the send button.

The Agentic Inbox.

Email to support lands in the same place as the portal. The agent matches the sender to their account, ties the email into the same conversation as their chats, reads the mood and drafts a kind, grounded reply. Then it waits. A person reads every draft and clicks Send.

Agentic Inbox
  1. Marco · Operations Our extract refresh failed again Frustrated
  2. Priya · Sales How do I share a view with my team? Draft ready
  3. Dana · Finance Board meeting at 9, dashboard is blank Urgent
  4. Lee · IT Thank you for the quick fix! Thankful

Marco · Operations

Our Sales Weekly extract failed again last night. This is the third time this month.

Draft reply · waiting for a person

Hi Marco, thank you for writing in, and I'm sorry this keeps happening. That's frustrating, especially when your team is waiting on the numbers. The refresh stopped because the data source's saved password changed. Once it's updated, the next run should go through.

Warmly, The Boreon Support Team

Send replySent once · logged on the account

Illustration with sample messages

  • One conversation

    Email and portal chat live in the same thread, so the whole story is always in one place.

  • Matched to the account

    Every message is tied to the sender's account and logged there.

  • Drafted, never auto-sent

    Customer mail is always drafted, never sent on its own. A person clicks Send.

  • Sent exactly once

    A double click can't send a reply twice. The inbox checks before anything goes out.

Honest by design.

  • Read-only on your site

    It reads your Tableau Server or Tableau Cloud site and never writes to it. The only thing it creates is a case.

  • Swiss-sovereign support

    Support runs on Boreon-controlled infrastructure in Switzerland, with Swiss-hosted open-source models by default.

  • Never a faked resolution

    "I don't know" is an honest answer here, and it always comes with a next step.

Bring us a real support question.

In a working session we'll ask Boreon Support something real about your Tableau Server or Tableau Cloud site, open a case and walk through the inbox together.

Book a working session See it live at ai.boreon.com