STATE2026.11
The state of Foliosio.
Foliosio is live and in active development.
Manual snapshot · updated
Current state
User adapted.
Foliosio now bends to how you already work. Your own AI agent can set up the workspace and draft replies. Alerts reach you by email or Slack. Your existing support address forwards in, and on Pro the replies leave from your own address.
Recent activity
A short record of the changes that moved Foliosio forward.
Recent activity
EMAIL
Replies from your own address.
On Pro, add your domain, add the DNS records Foliosio shows you, and customers get replies from support@yourdomain instead of ours. Their answers still land in your inbox, and a downgrade sends replies from the Foliosio address again.
NOTIFICATIONS
You hear about it first.
Foliosio emails you, and posts to Slack if you connect it, when a customer writes. You get one alert per conversation every five minutes, and you can leave the message text out of it.
EMAIL
Your support address, forwarded.
Settings now walks you through forwarding the support address you already have to Foliosio, for Gmail, Google Workspace, Microsoft 365, Cloudflare and other hosts. A status line tells you when the first email arrives.
AGENTS
Your agent sets it up.
Onboarding asks how you want to set up. If you pick your own agent, it reads your site, writes your product context, drafts help articles and saved replies, and hands you the widget snippet. Articles stay unpublished until you say so.
AGENTS
Bring your own agent.
Claude Code, Cursor and other MCP clients can read your inbox, tag conversations and save draft replies. Drafts wait for you, labeled Agent Draft. Nothing reaches a customer until you send it.
RELIABILITY
Failed sends try again.
Customer emails and webhooks run from a queue and retry on a widening schedule, from 30 seconds to an hour. The delivery log shows each webhook attempt, and you can resend one. Reply-by-email addresses carry a signature, and a repeated delivery of the same email adds nothing.
INBOX
Conversations load ahead of you.
Foliosio keeps opened conversations in memory and fetches the top five in your list ahead of time. Switching between them takes about a millisecond, down from two to six seconds in our tests.
LAUNCH
Live on Product Hunt.
Foliosio launched publicly on Product Hunt. The widget, email pipeline, AI reply queue, help center CDN, and API all came up clean. First customers are signing in.
LAUNCH
All systems green.
Every service passed the final pre-launch check. The widget, email pipeline, AI reply queue, help center CDN, and API all reported healthy.
LANDING
A new home for Foliosio.
The public site now gives the product room to explain what it does, how it works, and why a solo founder should not need a support team to support customers.
INSIGHT
Your inbox has something to say.
Analytics can group recurring conversation topics and surface those patterns as possible product improvements.
EMAIL
Threads stay threads.
Inbound email replies return to the existing conversation when the thread identifier matches.
AUTOMATION
Send it elsewhere.
Automation rules can fire webhooks alongside conversation events, keeping the rest of a founder's stack in sync.
Now
What is taking shape.
- Responding to first customers in the inbox
- Phone alerts for founders who do not use Slack
- Hardening onboarding from first real signups
- Choosing the AI reply model from measured cost and quality
- Search that covers the whole inbox
System health
A quiet check-in.
Checked live on page load. Refreshes every minute.
- Web appOperational
- Live chatOperational
- EmailOperational
- AI repliesOperational
- Help centersOperational
- APIOperational
Next
Real customers,real feedback.
Foliosio shrinks the inbox over time. Real usage will show what the AI gets right and where it needs work. That data shapes the next round. The goal stays the same: a founder using Foliosio should log fewer support hours each month.
The work continues.