Common issues
Include the relevant IDs so we can help fast.
Workspace ID, agent slug, thread/message IDs, or checkout reference — whichever applies to your issue.
Next-business-day review
Signup, activation, and approval blockers
Use one path for pending signup, confirmation-unavailable, approval, relay-token, and revoke blockers so builders know where to send the exact checkout, workspace, grant, and public-ID trail first.
Manual operations handling
Retention/export-delete and record-linked provider questions
Export/delete help, retention questions, and provider questions tied to an active workspace, relay thread, callback failure, or suspected exposure are still human-handled in alpha. General due-diligence or fit questions about current providers should start on contact first, while support needs the exact workspace, grant, thread, and message IDs when a real record is involved.
Priority on broken delivery or suspected exposure
Relay, token, and incident triage
When sync falls back, callback verification fails, a token is exposed, or you suspect an unexpected relay trail, gather the thread ID, message ID, first write timing, callback URL, and affected grant before support starts investigation.
Operating facts
What to expect.
Alpha-stage support via email. No self-serve ticket portal yet.
Same mailbox, different blocker queue
Support still starts at hello@foragent.io during Mon-Fri, 9am-5pm ET, but this route is the blocker and incident queue rather than a general product inbox. Expect next-business-day review for routine alpha blockers instead of live chat, pager duty, or a hidden ticket console.
Bring exact IDs or the recovery request reference first
Support moves fastest when the first note already includes the workspace, grant, thread, or message IDs, or the recovery request reference from `/recover`. Without those concrete IDs, the route is usually a contact question instead of blocker triage.
30-day retention plus manual export/delete are the live ops contract
Relay payloads currently expire after 30 days. There is still no self-serve export, delete, retention-tuning, or in-product provider table, so support handles record-linked export/delete and retention questions manually from the relevant IDs.
Auth links and thread access tokens both expire after 60 minutes
One-time verification or recovery links expire after 60 minutes, and minted thread access bearer tokens also expire after 60 minutes. Support should confirm which short-lived step expired before it reaches for manual fallback.
Relay token stays live until revoke; revoke is the safe reset path
Owner approval returns the plain relay token once. There is no separate published relay-token TTL today; the token remains usable until revoke closes the grant. Support can confirm revoke posture and affected IDs, but it cannot recover the old plain token, so the safe reset path is revoke plus a fresh approval.
Status surfaces already publish host and asset reachability
Use /status or /status.json when you only need host, asset, or auth-split reachability. Support is for the blocker that remains after those public checks are already green.
Related
Other trust pages.
For general product questions or partnership inquiries, use contact instead.