Fini
Self-improving AI for customer experiences
157 followers
Self-improving AI for customer experiences
157 followers
Fini is the self-improving AI agent for customer support. It resolves 90% of tickets at 99% accuracy across voice, chat, and email, built for fintech, banking, and other regulated industries where a hallucination isn't an option.
Most support AI needs constant re-tuning. Fini detects its own knowledge gaps, learns from real resolutions, and gets sharper on its own. Live in 14 days. Fully autonomous in 30. Works on your existing helpdesk, no migration.
This is the 2nd launch from Fini. View more
Knowledge Atlas by Fini
Launching today
Fini's self-maintaining knowledge layer. It writes help articles from resolved tickets, flags conflicts, and grounds every AI answer in one cited source.
Free
Launch Team
Fini
the part that gives me pause is "every resolved ticket becomes a new article automatically." a resolved ticket isn't the same thing as a correct or generalizable answer, sometimes a resolution is a one-off workaround, a support agent's judgment call that shouldn't be policy, or honestly just the AI getting lucky on an edge case. auto-promoting that into a permanent cited article feels like it could bake exceptions in as rules over time, which seems like exactly the kind of slow-drift problem you're trying to solve with the conflict flagging. is there a review step before a ticket-derived article goes live, or does it publish straight into the tree and rely on the conflict detector to catch it later
@galdayan Hi Gal, thank you for your question. CTO of Fini here. There is a strict relevancy filter (checking generalizability, correctness, etc) before a candidate resolution is suggested for review. Only a certain (usually single-digit) tuneable percentage makes it past that filter. Post that, a human has to check the draft update that was created before approving it and turning it live. We got inspiration from Pull Requests - so indeed we have gated this appropriately as our clients have stringent requirements for accuracy.
Fini
@galdayan great obsrvation Gal, and people are really skeptical about it as well. To give clarity:
1. Yes, considering a resolved ticket might be correct every time, that's why we have a test suite + a separate AI agent evaluating each answer before suggesting any article update.
2. And Yes, there is a review step for every suggestion our AI agents takes before updating an article. It shows the diff suggestion to a human agent, and then human agents takes the last and final action (screenshot attached)
@akash_29 that review screenshot actually answers it well, the diff view with reject/publish as separate steps is basically the guardrail I was asking about. good to see it's not just a policy statement but an actual UI gate. appreciate the detail
Fini
@galdayan I'm glad it makes it clear Gal. Thank you so much :)
DocsHound
Congrats on the launch. Looks impresive. Do you have any support for images / screenshots also?
Fini
@k_piotr Thanks Piotr. Yes, we support images, screenshots, PDFs, and text files... Would love to give you a walkthrough if you want :)
Took it for a spin on our support inbox last week and it actually flagged its own gaps instead of guessing, which is rare. Loved that it dropped into Zendesk without forcing a migration.
Fini
@ule882420426780 Thanks for giving it a shot Şule. Do spread the word :)
plugged it into our helpdesk last week and it caught gaps in our knowledge base we hadn't noticed for months, which was a nice surprise.
Fini
@smailryet Glad you tried and liked it Ismail :)