iii Agent Hub Troubleshooting and Common Issues
Most issues with iii Agent Hub trace to one of three root causes: an incomplete knowledge base, a misconfigured brand key, or an agent operating outside the bounds set by the Control Board — all of which are diagnosable from the Hub UI and the decision ledger.
Before You Troubleshoot
- Is the brand key correctly provisioned in the Hub UI?
- Is the integration guide present in your site's repository?
- Is the Control Board set to the intended capability level (not All Off)?
- Is the knowledge base complete enough for agents to operate from?
Common Issues and Resolutions
Agents Producing Low-Quality or Off-Brand Output
Cause: Incomplete or missing knowledge base.
Fix: Review KB coverage — product, ICP, pricing, FAQ, objections, competitors, process, and policy should all be populated. Agents operate entirely from what is in the KB; gaps produce generic output.
Outreach Not Sending
Cause: Sending capability may be set to Draft Mode or All Off, or the sending domain may not be configured.
- Check Control Board preset — ensure it is set to Full Pipeline or that sending is individually enabled.
- Verify sending domain configuration in the brand settings.
- Check Casey's health log for deliverability flags that may have triggered an auto-pause.
Auto-Pause Triggered (Casey Alert)
Cause: Bounce rate or complaint threshold exceeded — Casey automatically pauses outreach on bad signals.
- Review the flagged sending domain's health.
- Clean the affected list segment.
- Manually re-enable sending from the Control Board once the issue is resolved.
Booking Flow Not Routing Correctly
Cause: Integration guide not applied to the site's repository, or brand key mismatch.
Fix: Re-run the provisioning step — feed the integration guide at `https://iii-agent-hub.scott-4bd.workers.dev/onboarding/llms.txt` to your AI coding agent alongside the correct scoped brand key.
Agent Taking an Unexpected Action
Cause: Either the bounds for that capability are set wider than intended, or a cross-domain request was approved that should not have been.
- Inspect the decision ledger to see exactly what was decided, why, and by which agent.
- Tighten the relevant capability from the Control Board.
- Lock the affected lever to prevent further action until reviewed.
Something Looks Wrong but the Cause Is Unclear
- Start with Quinn's daily scorecard — it surfaces performance regressions.
- Then inspect the decision ledger for the time period in question.
- If the issue is unresolved, the fastest path is booking a call: [cal.com/scott-fielder/platform-demo](https://cal.com/scott-fielder/platform-demo)
FAQ
- Can I roll back an action an agent took?
- Every action is logged to the auditable decision ledger. Reversibility depends on the action type — draft emails that haven't sent can be cancelled; sent emails cannot be unsent. You can flip any capability off instantly from the Control Board to stop further action.
- What if the knowledge base is auto-generated from my site but contains errors?
- Auto-generation is a starting point. Review the generated KB in the Hub UI and correct any errors before enabling agents to operate from it. Inaccurate KB entries will produce inaccurate agent outputs.
- Who do I contact if I can't resolve an issue?
- Book a call directly with the iii Agent Hub team at https://cal.com/scott-fielder/platform-demo. Existing operators should use the support channel established during onboarding.