Why we built Deskruby

In a small team, most questions go to one person: the owner. How do we reply to this customer? Where is the price list? What do we do when a delivery is late?

The answers are often written down somewhere. But it is faster to ask the boss, so people ask the boss. That works until the owner is busy, on leave or asleep. Then the work waits.

We built Deskruby so the work does not have to wait.

What it does

You add your team's own documents: price lists, policies, how-to notes, past replies. Your staff ask Deskruby a question in plain words, and Deskruby answers from those documents.

Every answer shows its source. Staff can open the passage the answer came from and check it. When the documents do not cover a question, Deskruby says so.

Three jobs

Deskruby is for small teams where the owner still runs the day. In those teams, three jobs come up again and again.

Customer replies. A customer writes in. Staff ask Deskruby, and it drafts a reply from your documents. They read it, change what they need, and send it.

New starters. A new person has many small questions in their first weeks. They can ask Deskruby first and get an answer with its source, instead of waiting for someone to be free.

What would the owner do. Some questions need judgement, not facts. An owner can write down how they decide: when to give a refund, when to say no, who to call. That goes into its own Space, and staff ask it when they would otherwise wait for the boss.

What it is not

Deskruby only knows what your documents say. It does not invent a policy for you. The better your documents, the better the answers.

If you run a small team and spend your day answering the same questions, write to us at hello@jasoncjs.com.