Keep your playbook in one place.
AgentHub is a private, system-focused space for documentation, training flows, scripts, and live tools used by people on the front lines — agents, dispatchers, supervisors, and support teams who need answers fast without digging through ten different tabs.
AgentHub is not a public product. Access is created for specific teams or organizations and maintained directly by Joe Cruz.
For people who live in the work, not the docs.
Most “knowledge bases” are built once and forgotten. AgentHub is different: it’s a working manual that sits right next to the systems people actually use, with layouts and language tuned around how one specific team operates.
What AgentHub holds
- Account-by-account call flows and decision trees
- Supervisor checklists, rundowns, and daily routines
- Training paths for new hires and cross-training
- Quick reference cards for edge cases and “weird” scenarios
Who it’s for
- Call centers and support teams with complex accounts
- Supervisors who need one place to point people to
- Teams going through system or process changes
- Anyone tired of “where’s the doc for that?” every day
More like a cockpit than a wiki.
AgentHub isn’t just a pile of pages. It’s structured around how a shift actually feels: what you need at the start of the day, during live calls, when something breaks, and when you’re coaching people.
For agents
- Account tiles and dashboards with key info at the top
- Step-by-step flows for the most common situations
- “If this, then that” logic they can follow under pressure
- Links out to systems and forms in the right order
For supervisors
- Daily rundown and escalation paths in one place
- Sections for coaching notes and feedback templates
- Pages for outage handling, surge plans, and coverage
- Spaces for experiments and “in testing” workflows
Built with the people actually using it.
We map your reality first
Before anything is built, we walk through how your team currently works: systems, accounts, pain points, and what people wish they had in front of them during a busy day.
AgentHub is structured around that
The hub is then designed around your actual workflows — navigation, sections, and layout reflect the way your team thinks, not a generic template.
It evolves as the work changes
Because it’s private and purpose-built, AgentHub can be updated, reorganized, and refined as your accounts, tools, or team structure shifts over time.
Some systems make more sense off the shelf. This isn’t one.
AgentHub touches how people actually work: how they learn, how they make decisions, how they handle pressure. Keeping it private means it can be honest about the messy parts and specific about the details without needing to be “generic enough for everyone.”
Honest about edge cases
Real teams have exceptions, legacy processes, and “we do it this way for this one client” rules. AgentHub can capture those without pretending they don’t exist.
Safe to adapt and experiment
Because it’s not a public template, AgentHub can include experimental flows, draft ideas, and work-in-progress sections without confusing anyone outside the team.
If you think your team needs a hub, tell me about them.
AgentHub is only worth building when there’s a real team behind it: people taking calls, handling tickets, running operations, or managing complex accounts that can’t live in a spreadsheet forever.
If that sounds like your world, share a bit about your team size, tools, and where things feel scattered right now.