The assistant gets things wrong sometimes: usually by reading an unclear question one way when you meant another. This article is the recovery guide — how to nudge it onto the right track without starting over.
First: push back in chat
The simplest fix is also the most effective. Tell the assistant what's wrong:
"That's not right — I meant rows where the carrier is State Farm, not the broker."
"You filtered to last month, but I asked about Q1."
"The tag should only apply to small group, not all accounts."
The assistant remembers the last few things you said. Pointing out exactly what it got wrong usually gets you a corrected proposal in one message.
If a gate fired with the wrong proposal
Click Reject. Then say what was wrong:
"Reject — affected count was 11k but should be ~800. Try again with carrier filtered to State Farm only."
The assistant takes Reject as a cue to try again, often narrowing things down on the second attempt. You don't lose the conversation; only the proposal goes away.
When the conversation has drifted too far
After a long back-and-forth, the assistant can lose track of the original question. Signs to watch for: it starts bringing up rules you've already rejected, or it mixes up two different field names.
When that happens, start a fresh conversation:
Click the new conversation icon in the drawer header.
Restate the question in one sentence with the exact field name and the exact carrier or value you mean.
The old conversation isn't deleted — you can switch back to it from the conversation history if you need to look at it again.
When the assistant suggests something destructive
Caution: If the gate shows a proposal you didn't ask for — say, "delete all rules for Broker ID" when you only asked about one specific value — reject immediately and re-ask with stronger language ("just edit the one rule, don't delete anything").
If this keeps happening, contact Support — your admin may need to adjust the assistant's settings.
When the answer is just wrong on facts
If the assistant says "we processed 8,400 statements last month" but you know it was closer to 3,200, don't trust the number. Check it yourself by filtering the Data tab. The assistant may be counting wrong or looking at the wrong set of rows; the grid is always the real answer.
Reporting a bug
Persistent wrong-answer patterns are worth flagging:
Copy a brief example (your question + the wrong answer) using the drawer's copy conversation action.
Open a support ticket with the example attached. See [How to reach Stateable Support](contacting-stateable-support).
Get help
Still need a hand? Start a conversation from the Support button in the app, or email [email protected]. We reply within one business day for most tickets.
Related articles
Last reviewed: 2026-05-27