SWITCHBOARD Book a discovery call

Every request, routed to the right agent.

Switchboard is the intake layer for your AI agents. It takes documents and requests from every channel, checks them, sorts them into your own categories and patches each one through to the right agent, person or process.

Book a discovery call See how it works

Designed for the AI era. Developed by AI.

Live board · illustration with invented documents

Channels

SWITCHBOARD

Destinations

Your agents are ready. Your intake isn't.

01

Documents arrive everywhere

One customer case comes in by email, a portal upload, a phone photo and a partner feed, each with its own format and failure modes.

02

Every agent rebuilds intake

Each agent project writes its own mailbox polling, file parsing and classification, and maintains it alone.

03

Nobody can say where a document is

Between channel and agent there is no shared record of what arrived, what happened to it and who has it now.

Five steps. One record.

Every document takes the same path, whatever channel it came from. Each step writes to the document's status record, so operations, IT and the receiving agent all see the same thing.

  1. 1

    Receive

    Inboxes, upload endpoints, chat, partner APIs and SFTP folders become intake channels of one tenant.

  2. 2

    Check

    A file edited after it was created, or one whose structure could not be verified, goes to a person.

  3. 3

    Classify

    The model you chose sorts the document into one of your own categories, with a confidence score.

  4. 4

    Read

    Text and tables come out of PDFs, scans and photos, so the agent gets content, not just a file.

  5. 5

    Route

    Your rules pick the destination: an AI agent, a review queue or a downstream system. The outcome flows back.

It runs in your AWS account.

Switchboard is installed into your AWS account as a versioned package. Documents are stored and processed there, in the region you choose, and you decide which model reads them.

Your AWS account · your region

SWITCHBOARDIntake, checks, status records
Your agentsReceive routed events
Your reviewersWork the review queue
Amazon BedrockOptional: the model stays in your account

Outside, only if you choose

Another model provider Set per kind of document in the model registry. Switching is configuration, not code.

Signed releases

Each version ships with a signature, a software bill of materials and a licence list.

Upgrades on your schedule

You apply each release when it suits you. The current and the previous version are supported.

Your logs, your tooling

Everything Switchboard does is visible to the security tooling you already run.

Pilot installations

Ask us about the pilot programme in a discovery call.

Your agent gets one clean event.

No mailbox polling, no file sniffing, no guessing what a PDF is. Subscribe an agent to a route and it receives each matching document with its category, source and extracted content.

→ one versioned event per routed document
→ the original file plus the extracted text
→ report the outcome back into the record
→ any agent framework, any language

POST /claims-intake200 OK
{
  "event": "document.routed",
  "version": 1,
  "document_id": "doc_7Hq2vX",
  "tenant": "motor-claims",
  "channel": "email",
  "classification": {
    "category": "claim_notification",
    "confidence": 0.97
  },
  "route": { "rule": "fnol-default",
             "target": "agent:claims-intake" },
  "files": [{ "name": "claim-form-01.pdf" }],
  "report_outcome": "/v1/documents/doc_7Hq2vX/status"
}

Your categories. Your routes.

Insurance

first_notice_of_loss → claims-agent
policy_change → policy-agent
complaint → person

Banking and finance

onboarding_document → kyc-agent
loan_application → credit-agent
statement → archive

Logistics

bill_of_lading → shipping-agent
customs_document → person
proof_of_delivery → archive

Shared services

supplier_invoice → invoice-agent
hr_document → person
contract → archive

Built to pass an architecture review.

For companies where documents carry personal and contractual data, and where IT needs to know exactly what runs where.

Tenant separation

Channels, rules, models and documents belong to a tenant. One business unit never sees another's traffic.

A record for every decision

Each classification, routing decision and handover is recorded with its time and the model or rule that made it.

Models as configuration

Decide which models may read which documents, and change that centrally without touching your agents.

People in the loop

Flagged and uncertain documents wait in a review queue. A person confirms or corrects, and the document carries on.

Bring one document flow. We'll patch it through.

In a 30-minute discovery call we walk through your channels, the agents you are building, and what a pilot in your AWS account would look like. The demo runs on invented sample documents.

Write to us

contact@agenticswitchboard.net