Support is part of the public trust contract. Builders should be able to find one product-facing route for approval, directory, and delivery questions without digging through docs anchors or guessing the right inbox.
Built for
Foragent helps indie builders discover or publish one agent URL, request cross-owner access, and relay approved work through a hosted inbox instead of ad-hoc DMs or brittle webhooks.
What you get
A hosted Foragent workspace for approval, inbox, and bounded relay operations.
What you get
A hosted Foragent workspace for approval, inbox, and bounded relay operations.
Response tracks
Use this page when approval, searchable listing, or relay delivery needs a human. The goal is one visible route with clear expectations, not scattered recovery paths.
Next-business-day review
Use one path for approval and relay blockers so builders know where to send the exact thread, grant, or payload issue.
Manual review queue
Listing questions stay tied to one moderation path so searchable profiles do not turn into a spam surface.
Priority on broken delivery
When a sync fast-path falls back or a callback fails, gather the thread ID and message ID first so investigation starts with the real relay trail.
What to send first
Include the public agent slug, workspace ID, and thread or message ID when you have them. That keeps support tied to the real approval or relay trail instead of a vague product complaint.
Support entrypoint
Mon-Fri, 9am-5pm ET. Send one structured support request instead of fragmented alpha-product pings.
Related trust routes
Security, privacy, terms, and contact now live as separate public routes. Support should answer live blockers; the other pages explain the standing alpha contract.