Tool stack overview
Every tool a CS person will touch, grouped by what you’re trying to do — not by product name. Use this page as the map; deep-dives live in the sub-pages.
The map
Which tool for what
| If you’re trying to… | Reach for | Page |
|---|---|---|
| See how a live agent is doing right now | AgentFleet Dashboard | → |
| Configure a new agent without engineering | AgentFlow | → |
| Tweak a deeper/bespoke agent | AgentFleet Builder | → |
| Build a custom dashboard or report | Shipsy BI | → |
| Normalise messy addresses | Address Intelligence engine | → |
| Route orders to carriers by rules | Auto-allocation engine | → |
| Trigger alerts on SLA breaches | Alert management engine | → |
| Show the customer the TMS / WMS product | TMS / WMS consoles | → |
| Add a new system integration | MCP server registry | → |
| Look up a customer-facing how-to | Shipsy KB | link |
| Find a deck for a meeting | Decks library | → |
Runtime & orchestration
AgentFleet — the runtime
Where deployed agents live, get invoked, and execute. CS folks mostly view here, not configure. Every agent listed in Part 4 · Agent catalog runs on AgentFleet.
AgentFleet Dashboard — observability
Real-time view over AgentFleet. HITL queue, escalation status, per-agent SLA, latency, accuracy, alert feed. CS lives here when monitoring a live deployment.
Builder / no-code & low-code (the platformization layer)
This group is the most important for new joiners to get hands-on with. It’s what lets Shipsy ship value to customers without a custom engineering project for every new use case.
AgentFlow — the n8n of Shipsy
Visual workflow/agent builder. Drag-and-drop nodes, connect them, configure each, ship. Lets customers (and CS) compose agents without engineering.
This is the platformization play — reduces customer dependency on Shipsy eng for every new automation. New joiners must spend time here in week 1. See the AgentFlow page.
Placeholder — needs input from AgentFlow PM: node types available, common patterns, sample flows to study, sandbox URL, current limitations vs. the deeper AgentFleet Builder.
AgentFleet Builder
The configuration surface for agents that don’t go through AgentFlow — typically the more bespoke ones where the visual canvas doesn’t fit. Worth knowing when to use which:
| Use case | AgentFlow | AgentFleet Builder |
|---|---|---|
| Standard pattern (CX agent, control tower, etc.) | ✓ | |
| Customer wants to self-serve the build | ✓ | |
| Heavy customisation / new orchestration pattern | ✓ | |
| Tight integration with Shipsy-internal services | ✓ | |
| Engineering will own the agent long-term | ✓ |
Shipsy BI (Advanced)
No-code dashboard builder over the BI datamarts. Custom metrics, calculated fields, joins across datamarts. CS uses this to answer customer reporting questions and ship dashboards as part of an engagement.
Always pair with the bi-skill when working in this tool — it knows the joins, field definitions, and common SQL patterns.
Engines (pre-built capabilities)
Engines are the deterministic, non-LLM building blocks that agents call. Configure-once, then any agent can use them.
| Engine | What it does | Where it’s used |
|---|---|---|
| Address Intelligence / Address Checker | Validate + normalise + geocode addresses | Vera, Address Checker |
| Auto-Allocation | Rule-driven carrier/fleet allocation | BDO carrier orchestration |
| Alert Management | Trigger rules, escalations, SLA breach detection | Most agents that act on time |
| Geocoding Service | Text address → lat/long | Standalone + behind Address Checker |
| LIA (Logistics Intelligence Assistant) | Incident management co-pilot | Multi-customer |
| Route Optimisation | Pickpath + driver route planning | LSP B2C deployments |
| Territory Optimisation | Polygon-based delivery territories | LSP B2C, retail own-fleet |
System-of-record consoles
Shipsy TMS
The customer-facing transportation management product. CS folks must be able to navigate it to demo, debug, and answer questions. Get hands-on access via your manager.
Shipsy WMS
Same, for warehouse management. Separate product, separate access.
Integrations & extensibility
MCP server registry
Where the tools that agents can call are registered. CS won’t write MCP servers, but should know what exists and how to request a new one for a customer integration.
Open APIs & low-code integrations
How Shipsy connects to customer ERPs (SAP, Oracle), CRMs (Salesforce, HubSpot), OMS, and telephony (SIP trunking via Aviva, Unifonic, Exotel). The pattern is well-established — see the agent-platform repo.
Knowledge & docs
- Shipsy KB (Atlassian) — customer-facing knowledge base. Useful for self-learning and for pointing customers at the right article.
- Internal Confluence / Drive / decks library — covered in Where stuff lives.
Watch-out
The platformization layer (AgentFlow, Shipsy BI, AgentFleet Builder) is evolving fastest. Pages in this section are flagged for quarterly review. If you spot a drift between what’s documented here and what the tool actually does, file an issue.
Sources
- BDO & Carrix decks (most engines and platform components referenced)
- “All decks & videos” sheet — see Solution Overview rows for module-by-module decks
- AgentFlow deep-dive (in progress)
Changelog
- 26 May 2026: Initial draft, grouped by purpose. Pending input from AgentFlow PM.