Skip to main content
Everyone

September 2026

New​

Your dashboard tells you what is broken. The workspace overview now opens with a REQUIRED ATTENTION panel that checks your apps and lists what failed — a stalled Voice conversation, a knowledge base that could not index, a connector that stopped. When there is nothing wrong it says so rather than showing an empty box. Beside it, JUMP BACK IN lists what you opened recently and anything you have pinned.

A Developers tab on every knowledge base. Open a knowledge base and select Developers to find its API reference — the endpoints, and the permission each one checks — and Embeddable widget, which generates the code to put an Elie chat launcher on your own website. You issue and revoke the scoped tokens it uses from the same screen. Full details in the API reference.

Re-run a document. A document that has finished processing now carries a Re-run action in its header, so a document that classified or extracted badly can go back through the workflow without being uploaded again. Where re-running would discard work, you are asked to confirm first.

Map speakers on a Voice conversation. You can now say who each speaker in a call is, and the transcript, grading and exports follow that mapping. Conversations processed before this existed say so, and can be re-run to pick it up.

A contact form on the public site. The Contact us button on askelie.com now opens a form — pick a reason, leave a reply address, and you get a copy of what you sent.

Improved​

  • Voice — clearer detail when only part of a conversation fails, per-speaker colours in the transcript, and a persona sidebar that keeps its place.
  • Knowledge Base — long question-and-answer entries are no longer truncated, and access granted through a group now cascades correctly to the documents inside.
  • IntelieKonnect — the connector list keeps your filters in the address bar, so a filtered view can be bookmarked and shared.

Fixed​

  • Voice exports could sit at Pending forever without ever failing.
  • Deleting a conversation from a knowledge base did not always remove it.
  • A connector's status could disagree with what it was actually doing until the page was reloaded.
  • Grading a call against a rubric could reject valid output.
  • Signing out could leave the browser on a page that kept trying to load data.

Next​

Steps verified on . Something wrong with this page?