Skip to content
ketryon
Book a call

Four tools, one database.

Behind bojakt are four tools of its own: a dashboard to follow the service, an inbox for support, a CMS for the blog and an API for partners. All with the same look as bojakt itself.

What it looks like.The whole case
4

tools of its own behind the service

0

writes to the database from the dashboard

14

days' right of withdrawal, visible on every ticket

For the team behind bojakt, and for partners building on bojakt's own listings.

What it does

  • A read-only dashboard: saved searches over time, channels, demand per city and time of day
  • A support tool where email and the contact form land in one inbox, with the customer beside the conversation
  • Cancelling and refunding straight from the ticket, and a log of everything done
  • A CMS for the blog in Swedish and English, with a preview before publishing
  • A partner API with its own keys, usage per key and webhooks for new listings

What it looks like.

Illustrations of the real screens, drawn from the code with made-up data. The apps hold other people's data, so no screenshots are shown. The interface is drawn in Swedish.

  1. 01

    Support

    The inbox, the conversation and the customer in three columns. Beside the conversation: the subscription, how long the right of withdrawal lasts and the customer's saved searches — and cancelling or refunding from right there.

  2. 02

    The CMS

    The blog is written in its own CMS. An article goes from draft through preview to published, and the site updates the moment it is published.

  3. 03

    The API

    Partners create their own keys and see usage per key. A key is shown once; after that only a hash is kept. The API covers only listings landlords published on bojakt.

Step by step

  1. 1A customer writes through the form or replies to an email
  2. 2The ticket lands in the inbox, with the customer beside it
  3. 3Support replies, or leaves an internal note
  4. 4Cancelling or refunding is done from the ticket
  5. 5Every action goes into the log

Under the hood

  • The dashboard runs on a database role that may only read
  • Every chart can be shown as a table
  • Risky actions in support always ask once more
  • API keys are only stored as hashes

The rest of the platform.

The whole case: bojakt

Let's build
the next thing.

You talk to me, not a salesperson. The first call is free.

— Kenny

Book a free callChat on WhatsApp

psst, it takes 15 min

Write, and I reply the same working day.