Skip to content

Product · nine screens

Every screen, and why it is there.

Kirkle is small on purpose. Each part exists because an agency needed it on a Tuesday, and each part can be shaped to yours.

How a client moves through Kirkle

  1. 01

    Sales

    Gate: Agreement signed, client details in, account manager named.
    allows 48 hours
  2. 02

    Onboarding

    Gate: Home set up: details, photos, access, house rules, listings.
    allows 5 days
  3. 03

    Pricing

    Gate: Rates and rules set for every listing.
    allows 2 days
  4. 04

    Guest comms

    Gate: Guest support takes over; messages and reply times logged.
    allows 1 day

01Pipeline · 4 stages by default

A gate between every team.

Stages, each owned by a department, each with a checklist and an allowed time. A client moves only when the required tasks are done.

  1. 01Required tasks and optional ones, with task templates per stage set in Settings.
  2. 02A photo can be required before a task is ticked; a reason can be required when a stage runs late.
  3. 03Late clients are flagged on the board and on Home, and the owning team is notified.
  4. 04Board and table views of the same items, with Assign on every card.

Fig. 01The pipeline board with four stage columns; one client finishes its checklist and moves to the next stage.

02Settings · stages, rules, teams and roles

Your pipeline, your rules, your teams.

Nothing about the way you work is fixed. Stages, their order and allowed time, the company rules, departments, roles, activity types and home tiles are all settings.

  1. 01Rename, add, remove and reorder stages; set how long each may take.
  2. 02Two company rules: photo proof before a task is ticked, a reason when a stage runs late.
  3. 03Departments receive tickets and own stages. Roles decide every page and every button.
  4. 04Start from a template that sets it all up, then change anything.

Fig. 02A live copy of the pipeline settings with rule switches and stage controls.

Try it. This is a live demo built from the real settings controls, not a picture. Nothing you change here is saved.

03Home · 12 tiles, one layout per role

One page per role, and the work on it.

Home is a set of tiles. An owner sets the standard arrangement per role; each person can drag their own. The checklist tile is tickable in place.

  1. 01Today's figures: tasks, late clients, tickets on you, tickets waiting for an owner.
  2. 02Twelve tiles: your checklist, your tickets, past their deadline, the funnel, open tickets by team, announcements, today's numbers, response time, and more.
  3. 03Drag and resize, keyboard moves, and a Start again button.

Fig. 03The Home page as seen by four roles, switched with a control. Shown in the light theme; Midnight is the default and the switch is in the top bar.

04Tickets · one queue per department

Route it to a team. See who has it.

Guest issues, client complaints and internal jobs are tickets. Each one has a department, a priority, a status, a thread and a history.

  1. 01Queues: everything, mine, my team, and nobody has it.
  2. 02Filters that always show what is applied; a search that understands ticket numbers.
  3. 03Announcements are tickets for everybody, with a start and an end date, shown on Home.
  4. 04A comment thread and a history nobody can edit afterwards.

Fig. 04The ticket queue with its scope control and rows; an unowned ticket gets a person.

05Reports · replies against a 15 minute target

Numbers the team fills in, and what they add up to.

Each person logs a daily tally of the activities their team counts. Guest support logs messages and reply times. Reports turn both into charts against a target.

  1. 01Activity types are yours to define, pointed at a department.
  2. 02Response time measured against the company's target, with the share within target.
  3. 03A person by activity matrix, and CSV download of activity and messages.

Fig. 05The reports page: the week's figures, a bar chart of replies within target per day, and how each agent did.

Fig. 06A person's activity page: everything they logged, newest first.

06Knowledge base · 6 sections per home

Everything about a home, in one place.

Details, Q&A, amenities, important info, nearby, sleeping arrangements. Guest support answers from it.

  1. 01Inline editing per section; counts in the section headers.
  2. 02Access codes are masked by default, revealed per field, and copied with one click.
  3. 03Notes and files on every client and property, in one timeline with tickets.

Fig. 07The knowledge base sections and a masked door code, in the light theme.

07Roles · every page and button checks a permission

Your org chart, not ours.

Roles and departments are rows you create. Every page and every button checks a permission, so a role sees exactly what it should.

  1. 01Invite by email with a link that expires; roles set at invite time.
  2. 02Per-person permission overrides for the exceptions.
  3. 03Departments receive tickets and own pipeline stages.

Fig. 08Three roles with different permissions.

08Your data · 35 tables isolated per company

Your data stays yours.

Every company sits on its own island. Nothing from one company can be read from another, whoever asks, and Kirkle staff see companies as counts, never their records.

Fig. 09Three separate islands, one of them yours.

  1. 01

    Enforced by the database

    Every business table carries the company it belongs to, and the database checks it on every row.
  2. 02

    Checked, not promised

    A probe signs two companies up and, as the owner of one, tries every table of the other. Nothing comes back.
  3. 03

    Files too

    Uploads live in storage scoped to the company, under the same rules.

Put your agency in the circle.

Create your company, pick a template, invite the team, and move the first client through the pipeline this week.

Start freeSign in