AI features

The AI features are usually the first thing your team falls in love with and the first thing they hit a wall on. Most issues come down to either the demo cap, a stale chat context, or an output that needs a human pass before you trust it.

”Demo limit reached — please upgrade”

What you saw: a modal blocks your Ask Fola message or AI Autofill run and points at the billing page.

What it means: your firm has used the demo plan’s monthly AI quota — 5 chats, 2 Autofills, 2 Reviews per seat. The demo plan is hard-capped (no overage path); upgrading is the only way to keep running AI today.

What to do:

1. Upgrade at Settings → Billing if you’re ready to commit.
2. Or wait until the 1st of next month — caps reset at 00:05 UTC.
3. Or finish the work without AI: every form Fola fills with AI you can also fill manually from the Identity tab data.

”Ask Fola says it can’t find my client”

What you saw: you typed fill I-130 for Maria and Fola responded that it can’t see Maria.

What it means: Ask Fola binds to one active client at a time. The active client got switched, archived, or your role no longer gives you access to that client.

What to do:

1. Click the client picker at the top of the chat surface and pick Maria from the dropdown.
2. If she’s not in the dropdown, open the Clients list — she may be archived. Unarchive from the Archive tab.
3. If she’s not anywhere, your role was changed. Check Settings → Members → [your row] to confirm visibility.

”AI Autofill output is wrong on a specific field”

What you saw: the rendered PDF has the wrong value in one or two fields, or has the right value but on the wrong line.

What it means: either the source data on the Identity tab is wrong/missing, or our form’s field mapping has a bug.

What to do:

1. Open the client’s Identity tab and check the source field (e.g. if the wrong A-number landed on I-130, check the A-number field under Personal Information).
2. If the source data is correct, the form’s mapping is buggy. Email forms@folaform.com with:
   • The form ID (e.g. i-130)
   • The field label that’s wrong
   • A screenshot of the wrong output

We fix YAML mapping bugs the same day, usually within hours.

”Three Attorney Level Intelligence Review has been running for 10+ minutes”

What you saw: you kicked off an Attorney Level Intelligence Review and the spinner hasn’t gone away.

What it means: either the AI provider is having a slow moment, or your draft is unusually large (200+ pages of evidence in the review packet).

What to do:

1. Open Settings → AI insights and look for failed AI runs in the last hour.
2. If you see failures, cancel the stuck run from the chat surface and try again.
3. If the run is still in-flight at 15+ minutes, treat it as failed — cancel, downsize the evidence packet (extract pages 1-50), and retry.

”AI made up a value”

What you saw: Ask Fola or AI Autofill produced an A-number, SSN, address, or other concrete value you never gave it.

What it means: a bug. Fola is explicitly instructed never to fabricate values — when a field is missing it should ask you, not guess.

What to do: email support@folaform.com with the chat run ID (visible at the top of the chat surface) immediately. We pull the agent’s tool log for review and ship a fix. This is treated as a P0.

Always read the AI output before filing

Even when AI is working perfectly, you remain responsible for what gets filed. Walk every AI-filled draft field-by-field before finalizing. The AI output is a starting point, not a finished work product.

”I got a ‘Payment Required’ error when sending a chat”

What you saw: Ask Fola refused your message with a 402-style error and a payment prompt.

What it means: your firm exceeded its monthly AI Chat cap AND has no card on file to pay the per-chat overage.

What to do:

• Demo org: upgrade. No overage path on demo.
• Paid org: add a saved card at Settings → Billing → Payment method, or top up the firm’s account balance, then retry.

”Mandamus generator failed”

What you saw: you clicked Generate mandamus and got a server error or no PDF.

What it means: the federal-court packet generator hit an internal error (uncommon) or the client’s data didn’t have enough to draft a complaint (more common).

What to do:

1. Check the client’s Identity tab — for a mandamus you need full name, current address, A-number, the type of underlying filing (I-130, I-485, etc.), and the receipt number.
2. If all that’s there and the generator still fails, email support@folaform.com with the client name + the receipt number you tried.

When to email vs when to retry

• A single chat felt slow — retry.
• Three chats in a row failed — email support@folaform.com.
• The same wrong output keeps appearing on a form — email forms@folaform.com.
• Hallucinated value — email support@folaform.com (P0).