Question 1

Can Avalon send email without my approval?

Accepted Answer

No. Avalon can draft replies, but sending always stays with you. The only way an email leaves your mailbox is if you review it and hit send yourself.

Question 2

What happens to my email content?

Accepted Answer

Avalon uses direct provider APIs to classify mail and run your rules. Only the subject, body, and sender details go to the model. Attachments are never uploaded, your mail is not used for training, and message bodies are not retained beyond the decision window.

Question 3

What if the AI gets it wrong?

Accepted Answer

Avalon avoids irreversible automation by default: sending, spam, and delete-type actions require explicit confirmation. Routine actions such as archive, move, label, and draft creation can usually be changed from your provider mailbox.

Question 4

Can I use my own model provider?

Accepted Answer

Yes. Avalon supports bring-your-own API keys for OpenAI, Anthropic, OpenRouter, and other major providers. You pay the provider directly—no markup, no lock-in.

Question 5

Where's the pricing?

Accepted Answer

The pricing page shows the planned BYO, Indie, Pro, and Enterprise packaging while we wire subscriptions, credits, entitlements, and billing safeguards. We are not pretending checkout is finished before the backend is ready.

Question 6

How long does setup take?

Accepted Answer

Connect Microsoft or Google once, then Avalon starts with default rules for cold email, receipts, and newsletters. Most users have their first custom rule running in a few minutes.

Question 7

Which provider permissions does Avalon request?

Accepted Answer

Avalon uses Microsoft and Google sign-in plus provider mailbox, calendar, people, and settings scopes so it can classify mail, organize threads, and keep automations running. If sending is enabled for your workspace, Avalon requests the matching send scope so approved drafts can be sent from your mailbox.

Question 8

Which email providers are supported?

Accepted Answer

Avalon supports Microsoft and Google workspaces. Provider-specific actions run through direct first-party APIs, and each provider needs to meet the same depth for rules, board state, and mailbox actions.

Question 9

How is this different from native rules or filters?

Accepted Answer

Native rules mostly match keywords and headers. Avalon reads thread context and intent, then runs multi-step workflows like drafting a reply, moving a thread, forwarding it, or triggering a follow-up action.

Your inbox, finally under control.

A board that shows who owns the next move.

Flowboard

Partner launch timeline

Q2 budget approval

Contract redlines ready

Re: vendor invoice

Expansion follow-up synced

Beta feedback summary

Canceled: roadmap review

Workspace access confirmed

Renewal checklist completed

Automations that understand the thread, not just the subject line.

The assistant layer across mail, calendar, memory, and integrations.

Flowboard

Thread summaries

AI drafts

Semantic search

Due dates

Meeting intelligence

AI workflow automations

Mailbox cleanup

MCP connectors

Powerful automation, constrained where it matters.

Recoverable actions

BYO model keys

No training on mail

Pricing is published before billing turns on.

The practical questions before you connect a mailbox.