Fenn, the AI co-pilot

By the end of this guide you will have asked Fenn, the AI co-pilot inside FoxReach, to build a campaign from one sentence: name, sending window, daily limit, and the warmed inboxes to send from. You will have read its plan, approved it, opened the campaign it created, and kept going in the same chat to write the sequence and add leads. You will also know what Fenn may do on its own, what it has to ask you for, and what each conversation costs in AI credits.

​

Where Fenn lives

Fenn is available on every page of the app. In the sidebar there is a Chat with Fenn entry with a Beta badge. Click it and a panel slides in from the right, splitting the screen so the page you were on stays in view. A floating orb in the bottom-right corner opens the same panel. The panel header has a New chat button, a Chat history button, and a Close button. On desktop you can drag the panel’s left edge to widen it; on a phone it takes the whole screen. Old /chat links still open the same panel. On a fresh chat you see a welcome screen titled Your outreach co-pilot with starter prompts under Try asking. If Fenn has found something worth looking at, a Needs your attention list appears above them: a disconnected account, a campaign with many sends and no replies, leads outside any campaign. Each is a prefilled prompt you can click.

​

Step 1: Open the panel and describe the campaign

Go to any page, for example the dashboard, and click Chat with Fenn in the sidebar. Click into the composer at the bottom of the panel, where the placeholder reads “Message Fenn…”. Describe what you want in plain words: who to reach, when to send, and which inboxes to send from. The prompt from the video is a good template:

Prompt: “Build a campaign for SaaS founders who are hiring SDRs. Weekdays 9 to 5, from my warmed inboxes.”

Press Enter to send; Shift+Enter adds a new line.

​

Step 2: Watch Fenn read your workspace and lay out a plan

Fenn does not guess at what you have. Before proposing anything it checks the workspace, and you see that in the thread. For the prompt above, a line reading “Fetching email accounts” appears while Fenn looks up your connected inboxes and their warmup status, and the panel header shows an activity readout such as “Fenn is searching your workspace”. Then Fenn writes the plan. In the demo workspace, FoxReach Academy Demo, it lists the campaign name (SaaS Founders - SDR Hiring), the schedule (Monday to Friday, 9:00 to 17:00 Eastern), the two warmed accounts it will send from (jordan@tryfoxreach.com and maria@getfoxreach.com), and a daily limit of 100 emails. It also says the campaign will be created as a draft, so nothing sends until you have reviewed the sequence. If a detail is wrong, say so in the chat. Fenn revises the plan and asks again.

​

Step 3: Approve the plan (nothing runs without you)

Below the plan a box appears with the heading “Fenn is waiting for your go-ahead” and the note “Nothing has run yet. Read the plan above, then approve it or say no.” It has two buttons: Approve and run, and Not now. This is the rule that makes Fenn safe on a live workspace. Reading is free: Fenn can list campaigns, look up a lead, or pull stats without interrupting you. Anything that creates or changes data is blocked in FoxReach itself, not just discouraged, until you approve it: creating, updating, and deleting campaigns, sequences, templates, and leads; importing a CSV; assigning accounts or leads; starting, pausing, and resuming a campaign; and sending an inbox reply. Approval is scoped to the exact actions you just read. If Fenn wants to do something different afterwards, for example start the campaign rather than just create it, it proposes that separately and waits again. Click Approve and run.

​

Step 4: Open the campaign Fenn created

Fenn creates the campaign, and the panel shows a card for SaaS Founders - SDR Hiring with a draft status and both inboxes attached. Click the card to open the campaign page; the panel stays open beside it. Under the card, Fenn offers follow-up chips. In the demo they read Write a 3-step sequence, Add leads tagged series-a-saas, and Show campaign settings; on your own workspace you will see Add sequence steps, Assign sending accounts, and Add leads to campaign. Clicking a chip drops that text into the composer to edit before sending.

​

Step 5: Keep going in the same thread

The thread remembers what you have done, so you do not need to repeat the campaign name:

• Write the sequence. “Write a 3-step sequence for this campaign: a short intro, a follow-up with a case study, and a final bump.” Fenn drafts the steps, shows them, and waits for approval before saving them.
• Add leads. “Add every lead tagged series-a-saas to this campaign.” Fenn looks up the tag, says how many leads matched, and asks before assigning them.
• Check stats. “How is this campaign doing?” once it has been running. Reading stats needs no approval, so the answer comes straight back.
• Start it. “Start the campaign.” Starting is a state change, so Fenn confirms first.

For a new task, click New chat in the header rather than extending an old thread; Fenn carries only the recent part of a long thread into each answer.

​

What Fenn can do

Fenn works with the same tools FoxReach exposes to external agents, grouped here by the jobs you would ask for:

• Campaigns: list, create, update, and delete campaigns; start, pause, or resume them; attach or detach sending accounts.
• Sequences and templates: list a campaign’s steps, write new ones, edit or delete them; draft, update, and delete reusable templates.
• Leads and imports: search, create, update, and delete leads; assign them to a campaign or remove them; look up a lead’s activity; run a guided CSV import.
• Inbox replies: list threads, open a conversation, summarize what is unread, and send a reply on your behalf (with approval).
• Analytics and insights: workspace overview, per-campaign stats, inbox stats, and the Needs your attention cards.
• Email accounts: list connected inboxes and check an account’s health and connection status.

Each Fenn message has hover actions: Copy, a thumbs up or down, and Regenerate on the last message. Your own last message has an Edit and resend pencil that rewrites the prompt and reruns the answer.

​

The guided CSV import

Importing leads is the one job where Fenn drives a process rather than a single action. Click Import CSV in the composer and pick a .csv file up to 10 MB. Fenn reads the headers and a few sample rows, proposes a column mapping (which column is the email, which is the first name), and shows it to you. Confirm or correct the mapping, and only then does Fenn ask for approval to import. It skips duplicates and tags every imported lead with the file name, so you can add the batch to a campaign in one line later.

​

Prompts that work

Fenn behaves best when the request already carries the specifics. When it does not, Fenn asks a clarifying question first, which costs you a turn. Name the campaign, the tag, the account, or the person. Give the schedule and the limit when they matter. Fenn fills in what it can look up, but not who you want to reach.

​

Credits

Fenn is metered in AI credits. One credit is charged per completed Fenn response, regardless of how many lookups it ran. Regenerate charges one more. A response that fails partway through, for example on a dropped connection, is not charged. Credits reset every month. Lifetime tiers have their own allowances: Solo 1,000, Professional 5,000, Scale 25,000, and Enterprise 100,000 per month. The full breakdown is on the pricing page. To see where you stand, open Settings, Billing, where the AI Credits bar shows this month’s usage. Inside the panel, a header chip reads “12 AI credits left” (or “No AI credits left”) when you are on Free or close to your limit, and clicking it opens billing.

​

Threads, pinning, and archiving

Every conversation is a thread. Threads belong to you and to the workspace you are in, so switching workspaces shows a different history. Titles come from the first message and are refined after Fenn’s first reply. Click Chat history in the panel header to open the list, with a Search conversations box, a New Chat entry, and an Archived toggle. Hover a thread for three actions: Pin to top keeps it at the top (Unpin releases it), Archive hides it without deleting it, and Delete removes the thread and every message in it for good after a confirmation.

​

Fenn versus the MCP server

Fenn and the hosted FoxReach MCP server run the same 36 tools. Fenn is the assistant inside the app, with the approval box, the campaign cards, and the credit meter. The MCP server hands the same abilities to an agent you already use, such as Claude Desktop, Cursor, or a ChatGPT connector, over the Model Context Protocol. To say “build a campaign” from inside FoxReach, use Fenn. To have an outside agent plan, build, and report across your workspace as part of a bigger workflow, connect the MCP server and follow the MCP integration guide. New to the protocol? Start with what MCP is. The approval gate is a design choice, not a limitation. Anthropic’s building effective agents recommends human checkpoints before consequential actions, and OpenAI’s practical guide to building agents says the same about high-risk actions like sending messages. Cold email is that kind of action, so FoxReach enforces the pause in code. More in human-in-the-loop cold email.

​

Troubleshooting

“No AI credits left” or an upgrade prompt when you send. This month’s allowance is used up. Open Settings, Billing to check the AI Credits bar and upgrade, or wait for the reset. Campaigns keep running; only Fenn is paused. Fenn cannot find an account or a lead. Fenn only sees the current workspace. Check the workspace switcher at the bottom of the sidebar, confirm the inbox is connected under Email Accounts, and use the exact tag or lead email rather than a description. You clicked Not now and changed your mind. Nothing ran, so ask again with the correction. To undo something that already ran, ask Fenn to pause or delete it; that is a new action and it asks for approval first. Fenn stopped mid-task and offered a Continue chip. Fenn does a limited number of lookups per message. Click Continue and it picks up where it left off. A thread has become long. Older messages collapse behind a “Show earlier messages” pill, and Fenn carries only the recent part of a thread into each answer. Start a New chat for the next task.

​

Next step

Now that Fenn has built the shell, finish a campaign by hand at least once so you know what Fenn is filling in: the campaign setup guide covers sequences, lead lists, and launch settings screen by screen. If you have never connected an inbox, the getting started guide comes first. When you are ready to drive the same tools from outside the app, the MCP integration guide shows how to connect Claude or Cursor to your workspace through the FoxReach MCP server.

​

Frequently asked questions