Fannie: Your AI Coach in the Editor

What Fannie does for you

Fannie is your editor-side coach. She opens with an audit of the fanflet in front of you, points out specific weak spots like a generic URL or a sponsor block missing its logo, and offers fixes one at a time. You approve each change before she touches your content. Outside the audit flow, you chat with her to update public URLs, rewrite block titles, edit event details, and check subscriber counts across your fanflets.

Where Fannie lives

Open any fanflet in the editor and look at the bottom-right corner. The green round button with the sparkles mark is Fannie (same green as With Fannie when you create a fanflet). Click it to slide her coach panel in from the right. Close the panel with the X in the header or by clicking outside the panel.

Visibility is controlled by the fannie_enabled flag on your speaker profile. New accounts have it set to on by default. Turn it off in Settings and the floating button disappears from every fanflet you open.

Auditing on request

When you open Fannie, she greets you and waits. Choose Audit this fanfletfrom the welcome suggestions, or type your own request. An audit looks at the fanflet's metadata and blocks, then shows interactive issue cards so you know what to fix first. You can also ask about a single field without running a full audit.

The audit catches:

• Generic public URLs like untitled-a3f9k2 from a placeholder URL.
• Filenames used as titles, for example a block titled keynote-slides-final.pptx instead of "Keynote Slides".
• Missing event details: no event name, no event date, or no fanflet description.
• Partner blocks without a logo uploaded.
• Zero blocks. A fanflet with nothing in it has nothing for attendees to grab.

Each issue is a card with actions: Show me jumps to the field or block in the editor; Fix with Fannie starts a guided chat for that item; Walk me through these fixes issues one at a time (highest severity first). Fannie still waits for your approval before changing anything.

Approving or skipping a proposed fix

Fannie never edits your fanflet without permission. When she proposes a change, the chat shows you the exact value she wants to write: the new public URL, the rewritten title, the corrected event name. Approve it and she applies the change, then re-fetches the fanflet to confirm it landed. Skip it and the proposal disappears, your content untouched.

Chatting with Fannie

The audit is the opening move. After it runs, type whatever you need. Fannie has eight tools she pulls from to answer you:

• Read this fanflet."What blocks do I have?" pulls the full list with titles and descriptions.
• List your fanflets."Show me everything I've published this year" returns a roster with status and event info.
• Read your speaker profile."What's my bio say right now?" fetches your name, public link, bio, and headshot URL.
• Count subscribers."How many people subscribed last week?" returns a total. Add a fanflet name and she scopes the count to a single fanflet.
• Audit a fanflet.Re-run the audit any time. "Run the audit again" gives you a fresh issue list.
• Update the public URL."Change my public URL to invisalign-planning-2026" describes the change first, waits for your yes, then writes it.
• Edit fanflet details."Fix the event name to ADA SmileCon 2026" or "Set the event date to October 12, 2026."
• Edit a block."Rename the slides block to Implant Planning Workflow" or "Add a description to the second block."

Block deletion is held back behind an explicit instruction. Fannie will not remove a block unless you say "delete it."

Threads and history

Each fanflet has its own conversation thread. Open the same fanflet tomorrow and Fannie picks up where you left off, with the audit history and your prior questions in view. Threads are stored server-side and keyed to the fanflet you were editing, so swapping between fanflets gives you the right context every time.

Feedback

Every assistant message has a thumbs-up and thumbs-down button. Hitting one logs the response with your rating so the team tunes Fannie's prompt and tool selection over time. Use it freely. A thumbs-down on a wrong answer is more useful than a polite "thanks" in chat.

Rate limits and the kill switch

Speaker chats with Fannie are capped at 20 messages per hour per user. When you hit the cap, Fannie returns a short retry message and the limit resets sixty minutes after your first message in the window. The cap is a platform-wide setting and gets adjusted as usage patterns change.

A platform-wide kill switch sits behind the same config. If a model provider has an outage or pricing spike, the Fanflet team flips Fannie off for everyone at once. The FAB stays visible but opening it returns a short "Fannie is offline" notice. Service resumes the moment the flag flips back on.

Turning Fannie off

If you prefer a quiet editor, open Settings and toggle Fannie off. The floating button disappears from every fanflet you open from then on. Toggling back on brings her back with all your prior threads intact.

Related guides