Skip to content

Balt learns how you work, and does not forget it.

Every rule, correction and detail he comes across, Balt writes into a skill. Next time he already knows, and the whole team benefits.

Written as he works

Balt writes down what he learns himself: your rules, your formats, the corrections you make. Nobody has documentation to write.

Shared across the company

What Balt learns with one person serves everyone else. A skill belongs to the company, not to whoever taught it.

An open format

A skill is a readable folder with its instructions and scripts. You can import one, read it and edit it in the console.

Switched on when you want

Each skill turns on or off in one click. Editing is for administrators, and Balt asks before deleting one.

Examples

  • Your quote templates
  • The tone of your reminders
  • Your invoicing rules
  • The format of your write-ups
  • How you qualify a lead
  • Each client’s habits
  • Your way of working

Frequently asked questions

  • How is this different from a prompt?

    A prompt is forgotten when the conversation ends. A skill stays: Balt reads it whenever he needs it, and adds to it when he learns something new.

  • Can we write our own skills?

    Yes. Import one as an archive, or simply tell Balt how you work: he will write it himself.

  • What happens to what he learned when a skill is updated?

    It is kept. When a library skill changes, the part where Balt notes what he learned with you stays as it is.

Our guides on the subject

Give Balt its first job.

Thirty seconds to add it to Teams and get to work.

Try for free