# Forco

> AI email follow-up assistant. You CC `followup@forco.ai` on a thread (or forward a cold one), tell it what to do in plain English, and it remembers the follow-up you'd forget. It drafts the chase, shows it to you for one-click approval, sends from its own infrastructure with your display name, and stops the moment the reply lands or the loop closes.

Forco lives at an email address. The product surface is email — there is no app to install, no dashboard to log into, no API to integrate. If you (or your AI agent) can send a message to an email address, you can use Forco.

## Current status

- **Pre-launch (early access).** The waitlist is open at https://www.forco.ai/#waitlist. The `followup@forco.ai` capability handler is not live yet; mail sent there today does not get an auto-reply. The address will be live when the product launches.
- Made in Melbourne, founder-run.

## How invocation works (when live)

You hand off work to Forco by sending an email. The recipient address selects which capability runs.

- `followup@forco.ai` — the only capability currently in design. Add it as a Cc, Bcc, or forward target on a thread that needs a chase.

The body of the email (or a short reply on the thread) tells Forco what to do, in plain English. Examples:
- "Chase a reply if I haven't heard back in 3 days."
- "Send a reminder on Monday morning if the invoice isn't paid."
- "Run a 4-step follow-up sequence, one per week, until they reply."

Forco replies to you with a written plan (who it will email, what it will say, when) and waits for your one-click approval before sending anything outbound.

## Mailto template for an agent handoff

A user-facing agent that wants to hand a thread off to Forco can open a pre-filled compose window with this URL pattern (URL-encoded):

```
mailto:followup@forco.ai?subject=<thread%20subject>&body=<plain-english%20instruction%20on%20what%20to%20do>
```

Example:

```
mailto:followup@forco.ai?subject=Re%3A%20Q3%20proposal%20-%20chase&body=Chase%20a%20reply%20by%20Friday%205pm%20AEST.%20If%20no%20reply%2C%20send%20a%20polite%20nudge%20on%20Monday%20morning.
```

The user still needs to hit send from their own inbox so Forco can see the original thread context. Forco only reads threads it is explicitly added to.

## Key pages

- [Homepage](https://www.forco.ai/) — what Forco is, ways to use it, pricing, FAQ
- [How it works](https://www.forco.ai/how-it-works/) — the four-step flow (CC → tell → approve → done)
- [Use cases](https://www.forco.ai/use-cases/) — who's actually using it (sales, founders, bookkeepers, project managers, recruiters)
- [Marketplace](https://www.forco.ai/marketplace/) — additional capabilities beyond follow-up (e.g. WordPress updates)
- [About](https://www.forco.ai/about/) — founder note + vision
- [Contact](https://www.forco.ai/contact/) — direct contact form, or email `support@forco.ai`
- [Privacy](https://www.forco.ai/privacy/) — what Forco reads, what it doesn't, data handling
- [Terms](https://www.forco.ai/terms/) — terms of service

## Boundaries

- Forco only reads email threads it is explicitly added to (by Cc, Bcc, or forward). It never reads the rest of your inbox.
- Every outbound message Forco sends on a user's behalf is shown to the user first for one-click approve / edit / cancel. There is no silent send.
- Outbound replies are sent from Forco's mail infrastructure with the user's display name in the From line. Replies come back to the user's normal inbox.
- Forco does not train AI models on user content. Upstream API providers (Anthropic, OpenAI) do not train on API content either.

## Other addresses on the domain

- `support@forco.ai` — human support, billing, partnership, anything not a capability invocation
- `hello@forco.ai` — early-access / waitlist / press
- `followup@forco.ai` — the follow-up capability (this is the agent-callable one)