Skip to main content

Read, export & sync results

Ellie's replies are formatted text — headings, lists, and tables render cleanly in the chat. When Ellie produces something structured (a table of job profiles, a skills list, a training document), it appears as an exportable card with its own actions.

What you can do with a result​

Each exportable card gives you three actions:

  • Preview — open the content in a viewer to inspect it (CSV, HTML, or PDF views) before doing anything with it.
  • Save to File — store it in your workspace as a File, so you can reuse it later in another chat or a workflow.
  • Download — export it to your computer. Common formats include CSV and Excel for tables, and text/Markdown for documents.
Save first, reuse later

"Save to File" is the bridge between a one-off answer and ongoing work — a generated skills list becomes a document you can attach to your next analysis or feed into a workflow.

Seeing what a result cost​

JobKred is transparent about usage. Individual replies can show a cost badge — the tokens used, the price, and how long the response took — and the chat header shows the running total for the whole conversation. This makes it easy to see what an analysis costs before you scale it up into a recurring workflow.

Who pays

Usage is always attributed to the person who runs the request. If you run something from a chat a colleague shared with you, it counts against your usage — see Sharing and cost.

Pushing results back to your systems​

If your company has connected JobKred Lithium, certain generated outputs — such as job profiles and company skills — can be pushed back to Lithium directly from the result preview with a Sync to Lithium action. This keeps what you generate in JobKred in step with your system of record, with no manual re-entry.

Each job profile is checked on its own, so one problem row doesn't block the rest:

  • Names must be unique. If Lithium already has a job profile with the same name, that row is skipped and reported. JobKred never overwrites or renames the existing profile for you.
  • Job levels must already exist in Lithium. A row whose job level isn't one of your Lithium job levels is reported rather than created. Turning on Lithium as a chat source shares your job levels with the agent, so generated profiles use them.
  • Name, job function and job level are required. A missing business title falls back to the name.

Company skills work the same way, one row at a time:

  • Names must be unique. If Lithium already has a company skill with the same name, that row is skipped and reported. JobKred never overwrites or renames the existing skill for you.
  • Categories are matched by name. A skill category is matched case-insensitively, and a category that doesn't exist yet is created for you. Turning on Lithium as a chat source shares your existing skills and categories with the agent, so generated skills avoid taken names and reuse your categories.
  • Only the name is required. Description and category are optional.

Rows that sync get a check mark. Rows that don't get a red marker; hover it to see why. The preview itself can't be edited, so to fix a row either ask the agent to regenerate it (for example with a different name or level), or change things in Lithium (rename or remove the existing profile or skill, or add the job level) and upload the row again.

Next step​

Keep your conversations organized → Manage chats & projects.