Kahrbon OS: powerful work intelligence, every module zoomed in

1. 01Open the Dashboard; the Visitors card shows today's visits and who is checked in now.
2. 02Compare today's traffic with the same day last week.
3. 03Switch to Full view to see overdue actions, tickets assigned to you and tasks due this week beside the next 24 hours of meetings.

• The Visitors card shows today's visit count, how many people are checked in right now, and the latest five arrivals with host, location and an In/Out badge.
• Today's visitor traffic is compared with the same day last week, as a percentage.
• Admins get a four-step setup checklist (add a location, turn on a kiosk, invite your team, connect Microsoft 365 or Google Workspace) that hides itself once you're done.
• Full view lines up your overdue actions, tickets assigned to you and tasks due this week next to your meetings for the next 24 hours.
• Switch between Operator and Executive layouts, pick a density and show or hide eight cards. Your layout is saved in this browser.
• In Full view, an occupancy chart compares each location's current checked-in count with its capacity.

In the app: /dashboard

1. 01Click Check In Visitor and walk through six steps: details, company, host, purpose, NDA, confirm.
2. 02The host is e-mailed and gets an in-app notification; a visitor who gave an e-mail receives a Check Out Now link.
3. 03When a visitor leaves, click Check Out on their row in Currently In; the visit stays in History.

• Staff check visitors in with a six-step wizard: contact details, company, host, purpose, NDA acknowledgement, confirm. Host search autocompletes from your active users.
• Real names only: check-in requires a first and last name and rejects placeholders like "Visitor Guest".
• When a visitor checks in, the host gets an e-mail saying they're waiting at the front desk, with company, purpose, location and badge number, plus an in-app notification.
• Visitors who give a real e-mail receive a "You are checked in" message with a Check Out Now button that is unique to their visit and valid for 24 hours.
• One click on Check Out stamps the departure time and the length of the visit, and e-mails the host.
• Currently In shows checked-in visitors with host, location, purpose and check-in time. Click the host's name to e-mail them.
• Filter visit history by status, location and date range, then export the page you're viewing to CSV.

In the app: /visitors

1. 01Add a location and set its timezone and capacity.
2. 02Turn on its kiosk, then set the welcome message, colors and mode.
3. 03Open the kiosk on an iPad in Safari and add it to the home screen, as the Locations guide shows.

• Set a timezone and a capacity for each location. Kiosk times follow that timezone, and capacity feeds the dashboard occupancy chart.
• Brand each lobby's kiosk: a welcome message with company and location placeholders, background and accent colors, and an idle timeout.
• Building Security mode can require a suite number, company or visit reason, offer your own list of visit reasons, and capture parking space, vehicle and licence plate.
• Launch Kiosk App opens a location's kiosk at kiosk.kahrbon.com in a new tab. The button stays disabled until that location's kiosk is enabled.
• An in-app guide shows how to pin the kiosk to an iPad home screen (Safari, Share, Add to Home Screen) and lock the iPad with Guided Access.
• Optional per location: paste a Microsoft Teams Workflows URL, send a test, switch it on, and each check-in there posts an arrival card to that Teams channel.

In the app: /locations

1. 01The visitor taps Check In and enters an e-mail; returning visitors find their name and company filled in.
2. 02Next they type their host's full name; by default only an exact match goes through.
3. 03The host is notified, and the kiosk resets for the next guest.

• A branded welcome screen: your logo (imported from your website or uploaded), your welcome message and colors, and two big buttons: Check In and Check Out.
• Returning visitors type their e-mail and find their name and company already filled in.
• Your staff directory stays private: by default visitors type their host's full name, and only an exact match in that location's organization goes through.
• The confirmation screen tells visitors their host has been notified, then resets for the next guest.
• Self check-out by name shows only first name, last initial, company, host and check-in time. E-mail addresses and phone numbers are not displayed.
• Visitor-facing times on the kiosk show in the location's timezone, not the device's.

In the app: /locations

1. 01The kiosk shows a one-time QR code that lasts 10 minutes.
2. 02The visitor scans it and finishes check-in on their own phone; the kiosk greets them by first name.
3. 03On the way out, they tap Check Out Now in their check-in e-mail and confirm.

• Check in on your phone: the kiosk shows a one-time QR code, the visitor finishes the same steps on their own phone, and the kiosk greets them by first name.
• Each phone code is a random 192-bit value with no location or personal data inside. It lives 10 minutes and works once.
• A typo doesn't burn the code: if the check-in fails validation, the code is restored for five more minutes so the visitor can fix it and resubmit.
• Check out from the inbox: one tap on Check Out Now in the check-in e-mail.
• Mail link scanners can't check anyone out: opening the link only asks "Ready to check out?" and the visitor has to press the button.
• Check-out links are signed, bound to one visit, organization and location, and expire after 24 hours.

In the app: /locations

1. 01Pick the emergency type, write a message and choose one location or all of them.
2. 02Each active alert shows on the Emergency page with who activated it and a Resolve button.
3. 03The history shows who raised and who resolved each alert, and both actions are written to the audit log.

• Log an emergency by type (evacuation, fire, medical, security, lockdown, severe weather or other) with a message, for one location or every location.
• Active alerts stay pinned in a banner until someone resolves them, and the history shows who raised and who resolved each one.
• Keep an emergency contact directory (name, e-mail, phone, role and a primary flag) per location or company-wide.
• Raising and resolving an alert both write to the audit log.

In the app: /emergency

1. 01Start from a quick-start card or a blank announcement.
2. 02Choose the recipient group and preview the exact list.
3. 03Send once SMS delivery is configured for your workspace.

• Write an SMS announcement of up to 1,600 characters with a live segment count, tagged as general, facility notice, weather event or emergency.
• Target all contacts, hosts and staff, visitors from the last 30 days, visitors on site now, emergency contacts, or a custom list.
• Preview the exact recipient list before anything goes out.
• Quick-start cards for Facility Notice, Weather Alert and Emergency Broadcast open the composer prefilled with that announcement type.

In the app: /announcements

1. 01Visitors check in at the kiosk or the front desk.
2. 02Pick a range: 7 days, 30 days, 90 days or a year.
3. 03Read the trends, or export every visit in the range to CSV.

• Switch the range in one click (7 days, 30 days, 90 days or a year) and every chart and total refreshes.
• See total visits and unique visitors for the range, a daily check-in trend and a peak-hours chart.
• See how visits split across locations and who your 10 busiest hosts are.
• See your 10 most frequent visitors of all time, with company and visit count.
• Export every visit in the selected range to CSV.

In the app: /analytics

1. 01Add the bot's mailbox to a Teams invite, or paste a meeting link.
2. 02The bot joins as a guest and records; it leaves when the call ends or it's alone.
3. 03AssemblyAI transcribes it with speaker labels and Claude drafts the minutes.

• Paste a Teams meeting link and the bot is queued straight away.
• Invite the bot's mailbox to a Teams meeting and Kahrbon sends the bot in two minutes before it starts.
• Joins Teams as a guest, with no Microsoft credentials needed.
• Records the meeting, up to 4 hours, and sends the recording for transcription when the session ends.
• The bot leaves once it has been alone in the meeting for two minutes, or when the call ends.
• Reads Teams captions and active-speaker signals, so names come from the meeting, not the roster order.
• Turn on invite prompts and Kahrbon e-mails hosts whose Teams meetings leave the bot out, with a reminder 30 minutes before.

In the app: /meetings/notetaker

1. 01When a Note Taker session ends, its recording is queued for processing.
2. 02AssemblyAI transcribes with speaker separation, and Claude matches voices to attendees.
3. 03Claude drafts the minutes; you review them, tag speakers and decide on sharing.

• Transcripts get speaker labels from AssemblyAI, with the expected number of speakers taken from the attendee list.
• Claude names a voice only from the meeting's attendees, and only when it can quote the proof: an introduction, a name said aloud or a role match.
• Your speaker tags outrank automatic names and survive re-processing.
• Click any line to play from that moment. Search the transcript and filter by speaker.
• Claude drafts the summary, decisions, action items with owners and due dates, and open questions. Timestamps jump the player.
• With sentiment on, a card shows the overall mood, each speaker's tone and the moments to note.
• Recordings reach attendees only when the host, or a sharing rule the host or org set, says share.
• Take it with you: Word, text, WebVTT or SRT captions, or a full Markdown report.

In the app: /meetings

1. 01Create a meeting, or let Note Taker add the call it recorded.
2. 02Each row shows the meeting's source and its stage, from No Agenda to Confirmed.
3. 03Import to Board moves a meeting onto a board, with its actions and decisions.

• Board meetings, standalone meetings and recorded calls share one list, with Upcoming, Recent and All tabs.
• Each row shows a source badge and a stage badge, from No Agenda to Confirmed.
• Processed Note Taker recordings appear on the schedule, with attendees marked.
• Create a standalone meeting with a title, date, time and timezone. No board required.
• Import to Board moves a meeting onto a board, with its actions and decisions.

In the app: /plan-room/schedule

1. 01Join a board and it appears on your hub with its next meeting.
2. 02Board actions assigned to you line up by due date.
3. 03Recent decisions appear with their source: minute, vote, flying minute or recording import.

• A card for every board you sit on, with your role and its next meeting.
• The next five board meetings, each one click from its workspace.
• Your open board actions, soonest due first, with overdue ones flagged.
• The latest decisions, each tagged with its source: minutes, vote, flying minute or recording.
• Search transcripts, notes, ideas, decisions and actions by meaning, and jump straight to the moment.

In the app: /plan-room

1. 01Schedule the meeting; every active member is invited and notified in the app.
2. 02Build the agenda, then capture minutes and votes as you go.
3. 03Decision minutes land in the register; action minutes notify their owners.

• A Decision minute files itself in the decision register. An Action minute assigns its owners and notifies them in the app.
• Run formal votes, anonymous if you like. A passed motion records its own decision.
• Link a recording to a board meeting and Claude drafts notes, decisions and actions against its agenda for an admin to approve.
• Recurring Note Taker meetings group into project boards by the people and client domains involved, never by title alone.
• A meeting is added to an auto board only after its recording is shared.
• Each board gets a 0-100 health score and a Healthy, Watch or At risk band, shown on the board and in the Boards list.
• The board page shows a project timeline of milestones, deadlines and dated actions, grouped by month.
• Add members as Chair, Secretary, Member, Observer or Executive. Chairs and secretaries run the agenda, minutes and votes.

In the app: /plan-room/boards

1. 01Record a meeting; Claude extracts the minutes and reads the tone.
2. 02Insight scores the meeting and adds its open items to your panel.
3. 03Act in place: assign, set due dates, or create tasks and tickets.

• Six live tiles: your overdue items, what's due soon, open questions, open concerns, this week's decisions and 30 days of meetings.
• Next best actions: a short ranked list of what to do now, each with its reason.
• An explainable 0-100 health score per meeting, weighing decisions, ownership, participation, conflict and follow-through.
• Expand a meeting in the table to see its summary, key decisions, action items, open issues and next steps.
• Turn a meeting's open issue into a board ticket with one click.
• See each speaker's share of talk time and a participation equity score.
• A conflict timeline marks escalations, objections and frustration with the quote and the moment.
• Insight shows only the meetings you're allowed to open, re-checked on every read. Org admins see the whole organization.

In the app: /plan-room/insight

1. 01A recorded board meeting is linked and shared; its actions and decisions are imported.
2. 02Each attendee gets a digest and marks their own actions done from a link.
3. 03Your open board actions and tickets wait in the Execution inbox.

• Four counters on one screen: pending actions, assigned tickets, recent decisions and meetings that need follow-up.
• Change an action's status right in the inbox. Overdue items are flagged red.
• Escalate a decision into one follow-through ticket. Ask again and you get the same ticket, not a duplicate.
• Acknowledge a decision and it's recorded on its follow-through ticket.
• Share a board-linked recording and every attendee gets a digest of their actions, the decisions and the open questions.
• The digest's signed link opens a page, no login needed, where attendees mark their own actions done.
• Unanswered questions from a shared board meeting become tickets on their own.

In the app: /plan-room/execution

1. 01Resolve lists the concerns and open questions found in processed meetings.
2. 02Someone takes ownership, then answers, resolves or tickets each item.
3. 03Decisions are filed in each board's register, searchable and filterable by date and source.

• Concerns, negative moments and open questions are pulled from each meeting once it's processed.
• High-severity escalations, risks, objections and frustration become concerns with an owner slot.
• Assign it, resolve it, dismiss it or turn it into a ticket, right from the queue.
• One click makes one board ticket per item, assignee included. Click again and you get the same ticket.
• Each item links to the exact second in the recording, for people who can open it.
• Items from private meetings become tickets with generic text, so no meeting content leaks.
• A decision register per board, searchable by title and details and filtered by date and source.
• A passed vote, a decision minute or an approved recording decision each creates a decision register entry.

In the app: /plan-room/decisions

1. 01A meeting is processed: Claude extracts its action items and decisions, and they sync into Track.
2. 02Assign owners and due dates in Track's list or board.
3. 03Assigned owners get an e-mail, then due-soon and overdue reminders.

• Track stays in step with your meetings: each processed recording's items are synced in automatically.
• Re-syncing keeps the status, assignee, due date, priority, title and description a person changed in Track.
• Changes to an item's owner, status, title, due date or priority in Track are written back to the recording's outputs.
• Switch Track to Kanban and drag cards between Open, In progress and Done.
• Assign an owner inline and they get an e-mail and an in-app notice.
• An hourly sweep reminds owners when items are due soon or overdue, batched and held during quiet hours.
• Items link back to their recording, at the right second when there's a timestamp.

In the app: /plan-room/actions

1. 01A meeting leaves board actions, open questions and concerns.
2. 02Turn a Resolve item or a board meeting action into a ticket in one click.
3. 03Change its status or priority from the ticket and discuss it in comments.

• A ticket board per board: Open, In Progress, Resolved and Closed, sorted by priority.
• Raise a ticket with a title, a description and a priority from Low to Critical.
• Create a board ticket from a meeting action, an Insight open issue, a Resolve item or a decision.
• Board tickets share the Service Desk's per-organization numbering.
• Board ticket comments run through the Service Desk's comment rules, and non-agents never see internal notes or SLA fields.
• Each ticket has an 'Open in the Service Desk' link for replies, internal notes and SLA.

In the app: /plan-room/tickets

1. 01Note Taker records your meeting and Claude extracts its minutes.
2. 02Coach scores it and writes up to six tips from fixed rules.
3. 03Review your trend, then pick a meeting to see how its tone moved.

• Up to six tips per meeting: missing owners or dates, no decision, one voice dominating, tense moments, open concerns, unanswered questions.
• Private by design: only the organizer and org admins see a meeting's tips.
• A health trend across your last ten meetings, in green, amber and red.
• Your average health score, meetings analyzed and the theme that comes up most.
• Pick a meeting to see how the tone moved and how each speaker came across.
• Tips also call out what went well, such as every action having an owner or balanced participation.

In the app: /plan-room/coach

1. 01Meetings come from boards, Note Taker recordings and manual scheduling.
2. 02Admins see the whole organization; everyone else counts only meetings they can open.
3. 03Slice by date range and source to compare periods.

• Total meetings, unique organizers and the average per day, at a glance.
• A day-by-day volume chart, quiet days included.
• A Meeting Sources pie chart shows how many meetings came from each source, with percentages.
• Know who runs the meetings: the top ten organizers, ranked.
• Switch between 7 days, 30 days, 90 days and a year, and filter by source.
• Admins see the whole organization. Everyone else counts only the meetings they can open.

In the app: /plan-room/analytics

1. 01Turn on a template or build a rule.
2. 02Test it with a dry run against a real recent event.
3. 03Enabled rules run when their trigger fires, within your caps.

• Build rules from a catalogue of 8 triggers, 14 conditions and 9 actions.
• Test any rule against a real recent event. Dry runs change nothing and are logged.
• Seven built-in rule templates, each off until an admin turns it on.
• With the Negative meeting template on, a meeting at or below the negative threshold opens a high-priority ticket and notifies the host.
• People without full access to a meeting get a generic notice from a rule, not the meeting's content.
• Rules run within caps: by default 50 runs per rule per day and 120 per organization per hour, with a loop guard.
• A run history records each run's outcome: succeeded, partial, failed, skipped, deferred or dry run.
• Suggested rules from your meeting activity, built from counts, never names or content. You approve or dismiss.

In the app: /meetings/automation

1. 01Add your key terms and spelling fixes.
2. 02Set sharing defaults per meeting type.
3. 03Pick the meeting e-mails, quiet hours and limits for the org.

• Teach it your words: up to 100 key terms and 100 spelling fixes, sent to AssemblyAI with each recording.
• Per meeting type, internal, 1:1, external or board: ask each time, always share or keep private.
• Admins set the org's sharing defaults and which extra domains count as internal.
• Each person switches each of six meeting e-mail types on or off, from post-meeting summaries to weekly digests.
• Admins set quiet hours and hourly send caps for meeting e-mails across the organization.
• One switch turns Claude meeting sentiment on or off for the organization.
• Set the transcription language, or auto-detect, and switch on AssemblyAI PII redaction.

In the app: /meetings/settings

1. 01Pick a planner and answer one question at a time.
2. 02Click Draft agenda to build a timed agenda, then edit it.
3. 03Schedule it into Plan Room with the agenda already in place.

• One question per step, with hint chips so no answer starts blank. Answers save as you go.
• As you plan, Brief suggests your past meetings, vault files, open actions and mind maps as context.
• Draft agenda builds a timed four-part agenda with topics, risks, a prep checklist and a notes plan.
• Edit the draft's agenda sections, topics, risks and prep checklist before you schedule.
• Schedule puts the meeting on the Plan Room schedule with its agenda sections already in place.
• Import a past meeting's guests into Attendees, or its accepted actions into Prep, with one click.

In the app: /brief

1. 01Open Templates and review the built-in planners.
2. 02Pick the org default, or paste in your own template.
3. 03Your planners appear as start cards on the Brief hub.

• Four planners ready to use: Standard, Agile/Scrum, Stakeholder and Waterfall.
• Admins pick which planner new briefs start with.
• Add your own question sets, or override a built-in by its id, in JSON.
• Custom planners get the same default hint chips as the built-ins for their standard questions.

In the app: /brief/settings

1. 01Tasks are assigned on a project board, or created from a meeting action item for its owner.
2. 02They show up here, grouped by status.
3. 03Click a task to update it or leave a comment.

• Every task assigned to you, across all projects, grouped To Do, In Progress, In Review and Done.
• Project, priority and due date on every row. Overdue dates turn red.
• Open a task to change its status, owner or due date, or leave a comment.
• Tasks created from meeting action items land here for their assignee.

In the app: /my-tasks

1. 01Claude extracts action items from a recorded meeting.
2. 02One click, or an opt-in rule, turns them into tasks.
3. 03The team moves them across the board to Done.

• Drag tasks across To Do, In Progress, In Review and Done on each project's board.
• Create task turns a meeting action item into an assigned task with its due date. Click twice, still one task.
• Optional auto-tasks: when an admin turns it on, confident action items with a known owner become tasks once the recording is shared.
• Tasks have an assignee, due date, priority and a comment thread.
• Filter projects by status and search them by name.
• Add an action item from Insight to a project as a task. Kahrbon matches the assignee by name.

In the app: /projects

1. 01Pick a domain template in the Build a Loop wizard.
2. 02Enter goals and constraints, and preview the mind map.
3. 03Spawn child loops or export the package.

• Live counts of open meeting actions, open tasks, mind maps and your methodology.
• Six PM discipline cards, from Scope to Comms, each counting its items.
• Switch the org between Waterfall, Agile/Scrum and Lean, each with its own stages.
• A five-step wizard turns goals, constraints and stakeholders into a mind map you preview before saving.
• Spawn child loops from the nodes of a loop's mind map.
• Export a loop as a ZIP with a README, outlines and starter files for each build target.

In the app: /loop

1. 01Pick a discipline.
2. 02Add an item by title; it lands in the backlog.
3. 03Move it through status and stage as the work moves.

• A workspace for each of the six disciplines, from Scope & Planning to Stakeholder & Comms.
• Type a title and the item lands in the backlog.
• Change an item's status and methodology stage from its card.
• Admins tailor each discipline's status columns.
• Items link back to the meeting action, task or mind map they came from.

In the app: /loop/disciplines

1. 01Admins switch each lane on or off.
2. 02Set each lane's adoption stage.
3. 03Tag Loop items with a lane as you promote them.

• Six function lanes: Engineering, Sales, Purchasing, Design, Research and Ops.
• Admins turn each lane on or off.
• Track each lane's adoption: Aware, Piloting, Adopting, Scaling, Optimizing.
• Pick a function lane when you promote a meeting action into the Loop.

In the app: /loop/lanes

1. 01Your 20 most recent mind maps are listed.
2. 02Spot an open meeting action.
3. 03Promote it, with a task, in one click.

• Your 20 most recent mind maps, each a click from the map viewer.
• Lists your 25 most recent open meeting actions, each with a link to its meeting.
• Promote + task makes a Loop item and a task from a meeting action in one click.
• Actions already in the Loop are marked, so nothing is promoted twice.

In the app: /loop/graph

1. 01Pick the meeting action.
2. 02Choose the discipline, and optionally a lane and stage.
3. 03Promote it, with a task for the owner included.

• Pick an open meeting action, a discipline, and optionally a lane and stage.
• With 'Also create Task' on, the default, the action's first assignee gets a To Do task with the same due date.
• Promoting the same meeting action again returns the existing Loop item instead of a duplicate.
• The new item links back to its meeting and its task.

In the app: /loop/from-meeting

1. 01Pick a methodology and preview its stages.
2. 02Adjust stages, fields and statuses in JSON.
3. 03Save; the server rejects config that fails its schema.

• Preview a methodology's stages before you switch.
• Admins edit stages, fields, statuses and lanes in a JSON editor, and the server rejects config that fails its schema.
• Configure up to 40 stages, 20 statuses per discipline and 20 lanes.
• The Loop config is created with defaults the first time it's opened.

In the app: /loop/settings

1. 01Create your starter team of AI Employees.
2. 02Write a brief, set its priority and pick an Employee, or let Kahrbon route it.
3. 03Approve the draft, send it back with notes, or reassign it.

• Named AI Employees, each with a role prompt, skills, allowed tools, its own model on Claude or Grok, and a monthly budget.
• With one click, admins seed a starter team of four AI Employees when the organization has none.
• Give an Employee a brief with a priority and an approval policy, or let Kahrbon route it.
• Review is on by default: approve the draft, send it back with notes, or reassign it to another Employee.
• Tools only draft. Employees never send e-mail, create tickets or write outside Kahrbon.
• Every Employee has a monthly budget, $20 by default, and a run stops when the budget is reached.
• Each task's flow view shows its run history, model steps, tool calls, tokens and cost per step.
• Admins get per-provider kill switches and org keys encrypted with AES-256-GCM.

In the app: /neural-links

1. 01Open the map and pick a module.
2. 02Follow the staged guide to its next step.
3. 03Ask the OS when you're stuck.

• A map of 43 Kahrbon modules in 8 layers and the 47 data flows between them, each module showing your organization's status.
• Each module shows its status, setup checks, 30-day activity and next step.
• A staged playbook, Connect, Configure, Automate, Operate, plus a guide for each module.
• Company admins mark each guide step done or dismissed, saved for the whole organization.
• Ask the OS in plain words and Claude answers from the guide and your module states.
• Before a question is stored or sent to Claude, links, e-mails, phone numbers and long numbers are removed.
• Cached per organization for five minutes, and a failing count never breaks the map.
• Pan and zoom the map on desktop; get a clean list on your phone.

In the app: /ai-os

1. 01Open Pulse from any dashboard page.
2. 02Pick a guided tour for the page you are on.
3. 03Follow the tour step by step.

• Guided tours play inside Pulse, with no AI call.

1. 01Each user signs in with their own Microsoft 365 mailbox.
2. 02Once connected, keyword rules flag sales signals in recent mail.
3. 03Then act on each opportunity, snooze it or ignore it.

• Your opportunities are private to you. Admins can't read another user's mailbox or results.
• Keyword rules flag pricing asks, demo requests, competitors, timelines, budgets, referrals, objections and stale threads.
• Once your mailbox is connected, each opportunity comes with a suggested next move and a one-line coaching tip.
• Once your mailbox is connected, open an objection session or a pitch draft from an opportunity, pre-filled with the e-mail.
• Once your mailbox is connected, snooze an opportunity for 24 hours or ignore it; the choice is kept for 90 days.

In the app: /sales-inbox

1. 01Pick a document type and tone, then add your hints.
2. 02Generate the draft from your hints and sources.
3. 03Export a PDF and download it to send.

• Four sales documents, one-pager, proposal outline, ROI brief and battle card, in four tones.
• Generate drafts from your hints, uploads, Folio documents and objection notes, with Claude told not to invent logos, metrics or customer names.
• Describe a deal and Claude writes a proposal, estimate or quote: narrative, investment table, appendices and service-agreement clauses.
• Battle cards can pull talk tracks from an Objection Modifier session you're allowed to read.
• Export a PDF and download it through a signed link.
• Attach source files up to 50 MB; text files are read automatically, other files take a note.
• Save client contacts and pick from meetings you can access as inputs.

In the app: /pitch

1. 01Capture what they said.
2. 02Reframe it with guided questions and talk tracks.
3. 03Close on a committed next step.

• Three stages, Capture, Reframe and Close, take you from what they said to a committed next step.
• Objections are sorted into eight types, such as price, timing, authority and trust, each with a coaching hint.
• Draft builds talk tracks, questions, a follow-up e-mail, a one-pager and a commitment map from built-in templates.
• Built-in playbooks for question-based selling, closing, enterprise procurement, conflict resolution and gone-quiet follow-ups.
• Start a session from a recorded meeting's objection quotes, competitor mentions and next-step clarity.
• Park a session and pick it up later, stage intact.
• Practice between calls: 15 coaching rules, 5 session templates and a 56-card flash deck across six industries.

In the app: /objections

1. 01Pick a lane and a document kind.
2. 02Describe the job, or upload a prototype.
3. 03Preview, restyle and mark it ready.

• Ten document kinds, from proposals and change orders to NDAs and statements of work.
• 16 built-in templates across manufacturing, construction and agreements.
• Describe the job and Claude fills in the parties, sections, line items and notices.
• Upload a PDF or Word prototype up to 25 MB and draft from its text.
• Agreements are set to a governing US state, any of the 50 plus DC, with a not-legal-advice disclaimer.
• Choose from 20 visual themes and switch a document's theme in the editor.
• A live HTML preview, with Draft, Ready and Archived status.
• Start from a template without any AI at all.

In the app: /docs

1. 01Upload a file.
2. 02Edit its title and author, add page notes and regenerate the PDF.
3. 03Send it to a meeting's minutes or a pitch.

• Upload any file up to 50 MB. PDFs get a page count, their metadata and the text from their text layer.
• Edit the title, author, subject and keywords, add per-page notes, and regenerate the PDF.
• Preview pages and download through a signed link.
• Import a document's extracted text into a Plan Room meeting's minutes.
• Mark a document Ready and Pitch offers it as source material.

In the app: /folio

1. 01Pick a template.
2. 02Attach your references, then let Claude draft the pages from them.
3. 03Generate a branded PDF and download it to share.

• Seven page types, from cover and leadership letter to wins, events and calls to action.
• Four issue templates: standard company, department pulse, all-hands digest or a blank canvas.
• AI draft writes the pages from your references and issue details.
• Generate a multi-page branded PDF, then download it or rebuild it from a saved snapshot.
• Edit and reorder pages with a live preview.
• Admins set the brand colours and logo that Dispatch issues are built with.

In the app: /dispatch

1. 01Pick a design, or describe one and let Claude style it.
2. 02Publish and assign it to the org, a department or a person.
3. 03Members install it from My Signature and can share a QR business card.

• 103 email-safe signature designs across 8 industry families and 6 showcase packs.
• Lock blocks like the logo and disclaimer in a template, and employees can't change them in their own signature.
• Generate a signature theme from a short description; Claude returns design tokens only, validated to keep the HTML email-safe.
• Assign a design to the whole org, a department or one person. The most specific wins.
• Install your way: rich HTML for Gmail, a PNG for Outlook, a .htm file or a hosted image link.
• Publishing a template re-renders the hosted signature image of every user it applies to.
• Each member gets a digital business card with a QR code and Save contact, and can switch it off or get a new link.
• Printable badges in four sizes with a barcode or QR code, up to six per sheet.

In the app: /signatures

1. 01An employee files a request in the portal: one quick form in Simple mode, or a request type in Advanced mode.
2. 02In Advanced mode, the first routing rule that matches can set the queue, assign an agent or change the priority.
3. 03Agents work it from their workspace; if a target is missed, the assignee or the queue leads are notified.

• Simple mode is one quick request form. Advanced mode adds request types with smart forms, routing rules and SLA policies. Admins choose the mode in settings.
• In My requests, employees filter by Open, Pending you or Resolved, reply and attach files, reopen within 7 days of resolution, and rate the result from 1 to 5 stars.
• Switch on help-article suggestions and the request form lists up to five matching articles as people type. "This solved my problem" closes it without a ticket.
• With suggestions on, requesters can ask Claude for a short answer written only from your matching articles, with citations.
• Routing rules (Advanced): the first match on request type, category, department, channel, keywords or priority wins, then assigns by round robin, least loaded, skill or a named agent.
• SLA policies (Advanced) set first-response and resolution targets per priority, can count business hours only (your time zone, weekly hours and holidays), and pause while a ticket waits on the requester.
• Escalation steps fire at a set percentage of the resolution target and can notify, reassign or raise the priority.
• Agents work from one workspace: My queues, Assigned to me, Unassigned and Breaching soon views, live SLA badges, bulk assign and status changes, and keyboard shortcuts.

In the app: /service-desk

1. 01Import assets from CSV or add them one at a time.
2. 02Organize them by category and filter by status.
3. 03Edits are recorded field by field, and Service Desk agents link assets to tickets.

• Register assets with tag, serial, make and model, purchase date and cost, warranty expiry and a 1-10 criticality score, then filter by status and category.
• Every edit records old and new values across 14 tracked fields, and the History tab shows the latest 20.
• Bulk-import assets from a CSV file using a downloadable template. Rows that fail are reported individually.
• Organize assets in a parent-and-child category tree.
• Service Desk agents link these assets to tickets and see who has held each item.

In the app: /premise/core

1. 01Add a facility with its code, type and address.
2. 02Add its contacts by role and its rooms.
3. 03Link it to the visitor location where people check in.

• Keep a facility directory with name, code, type, status, address, timezone and area, searchable and filterable.
• Store each site's contacts by role (manager, security, maintenance, emergency) with a primary contact flag.
• Link each facility to its visitor check-in location, one to one.
• Track the rooms in each facility, with capacity summary counts.

In the app: /premise/grid

1. 01An employee reports the issue with a category, priority, facility and exact spot.
2. 02Your team filters the queue by status, category and priority, and discusses each request in its comment thread.
3. 03Once the request is resolved, the person who reported it rates the fix from 1 to 5 stars.

• Every signed-in employee can report a facility issue with a category, priority, facility and exact spot. Each request gets its own SR number.
• Work the queue with status, category and priority filters, and discuss each request in its comment thread.
• Once a request is resolved, the person who reported it rates the fix from 1 to 5 stars.
• From a meeting's action list, turn an action item into a facility request prefilled with the action and meeting title.

In the app: /premise/spark

1. 01Raise a work order with type, priority, facility and schedule.
2. 02Move it through the workflow and log the parts used.
3. 03Complete it with a resolution; overdue orders show on the dashboard.

• Raise work orders by type (corrective, preventive, emergency or inspection) with priority, facility, estimated hours and a schedule. Each gets a WO number.
• Work orders move through an enforced workflow from Open to Closed, and completing one stamps the time and the resolution.
• Log the parts used on each work order, and parts cost and total cost (labor plus parts) roll up automatically.
• The maintenance dashboard counts work by status and priority, flags overdue orders and tracks average completion hours.

In the app: /premise/forge

1. 01Add your parts with unit cost and minimum stock, and add your vendors.
2. 02Raise a purchase order and move it to Ordered.
3. 03Receive the lines; stock goes up with a movement record.

• Keep a parts catalogue with part number, category, unit cost and minimum stock, plus your total inventory value.
• The inventory dashboard lists the parts at or below their minimum stock, lowest first.
• Purchase orders follow a fixed status flow, from Draft through Submitted, Approved and Ordered to Received.
• Receive PO lines, partial receipts included, and stock goes up with a movement record. Over-receiving is blocked.
• Track vendors with contact details, per-vendor part pricing and lead times.

In the app: /premise/cache

1. 01Report the fault with category, severity and location.
2. 02Record the root cause and resolve it; time to resolve is calculated for you.
3. 03Add prevention actions and watch repeat categories in analytics.

• Report a fault with its category, severity and location. Each fault gets its own FLT number.
• Record the root cause with a 5 Whys chain, contributing factors and findings.
• Resolve with a resolution type, cost and labor hours, and time to resolve is calculated automatically.
• Add prevention actions with due dates and tick them off as they're done.
• Fault analytics show the top 5 repeat categories, average time to resolve and a 12-month created-versus-resolved trend.

In the app: /premise/trace

1. 01Add your meters and your emission factors.
2. 02Log meter readings and waste as they come in.
3. 03Open the monthly dashboard and carbon report.

• Track electricity, gas, water, solar and diesel meters.
• Log a meter reading and consumption is worked out from the previous reading. Each meter shows a consumption trend of its last 12 readings.
• A monthly carbon report splits emissions into Scope 1, 2 and 3 using the emission factors you set.
• Log waste by type, disposal method, weight and cost, and the dashboard shows your monthly diversion rate.

In the app: /premise/cycle

1. 01Deleting or sharing a recording, raising an emergency alert or changing a Premise record writes an entry.
2. 02The log lists entries newest first, with time, user, action, resource and IP address.
3. 03Company admins filter by resource, expand entries and export the rows on screen.

• The Audit Log lists recorded actions newest first, with time, user, action, resource and IP address.
• Expand any entry to see its full details and the browser that made the request.
• Recording deletions, purges and share decisions, emergency alerts, Premise changes, Service Desk channel changes and super-admin overrides all land in the log.
• Filter by resource, such as recordings, Note Taker, Premise requests, work orders, faults and assets, and export the rows on screen to CSV.

In the app: /audit

1. 01Open Settings and pick a tab; each tab has its own link.
2. 02Company admins set the kiosk logo and the visitor welcome e-mail under Organization.
3. 03Each person chooses their meeting e-mails under Notifications.

• Optional: after check-in, visitors can receive a welcome e-mail with your message, website and facility contacts.
• Put your logo on the kiosk: import it from your website, paste a URL, or upload PNG, JPEG, WebP, SVG, GIF or ICO.
• Each person sets their own meeting e-mails: every e-mail type On, Off or the organization default, plus digest time, time zone, and weekday-only or daily digests.
• Profile, Organization, Notifications, Security, Meeting Recording and Intelligence settings live in one page, and each tab has its own link.

In the app: /settings

1. 01Invite a teammate by e-mail with a role.
2. 02They accept from the e-mail link within 72 hours.
3. 03Change a member's role from their row; the last Company Admin can't be demoted.

• Invite people by e-mail with a role: Company Admin, Manager, Receptionist, Host, Reporting, Security or Kiosk. Each invite is single-use and expires in 72 hours.
• Track sent invitations (pending, accepted, cancelled or expired) and resend or cancel any of them.
• Change a member's role from their row, and the last Company Admin can never be demoted.
• See every member's role, MFA status, last login and location scope in one table.

In the app: /users

1. 01An admin signs in and grants the permissions Kahrbon needs.
2. 02Kahrbon generates the Teams PowerShell, checks the policy and syncs your directory.
3. 03Test a real meeting to see who matches your directory; health checks keep running daily.

• A guided wizard connects Microsoft 365 in nine steps or Google Workspace in five. Leave and resume any time; cancelling never touches an existing connection.
• For Microsoft Teams, the wizard writes the PowerShell your admin needs, filled in with your verified tenant.
• Test a real meeting: Kahrbon reports whether it can find it, read its transcript and attendance, and how many participants match your directory. It never guesses an ambiguous name.
• Kahrbon re-checks your connected workspace every day, and Check now re-runs the checks whenever you want.
• Directory sync filters out shared mailboxes, room accounts, guests and disabled accounts by default, supports domain include and exclude lists, and logs every sync.
• The wizard refuses a Microsoft tenant or Google domain that's already connected to another Kahrbon organization, and refuses personal Gmail accounts.
• Invite synced people as Kahrbon users, or add them to a location, straight from the Directory Users tab.

In the app: /settings/integrations

1. 01Sign up and your 15-day trial starts.
2. 02Choose a plan and upgrade through Stripe Checkout.
3. 03Manage your card and invoices in the Stripe Customer Portal.

• New organizations start with a 15-day trial and get e-mail reminders 7, 3 and 1 days before it ends.
• Your plan card shows the subscription status, the trial end date and the current billing period, and warns you if a payment failed.
• Usage meters track active locations, visitors this month and team members against your plan, turning amber at 70% and red at 90%.
• Upgrade opens Stripe Checkout, and Manage Billing opens the Stripe Customer Portal for cards, invoices and cancellation.

In the app: /settings/billing

1. 01Open Company Profile and fill in your slug, tagline, colors and logo.
2. 02Saving the profile also updates your organization's brand colors and logo.
3. 03Preview the page and copy the link to share.

• Publish a branded company page with your logo, tagline, description, a website button and your brand color.
• Search engines and link previews get a page title, a description from your profile, and your logo as the preview image.
• Saving the company profile also updates your organization's brand colors and logo.
• Pick your link: Kahrbon keeps the slug unique, and Preview and Copy URL are one click away. Unpublish with a single toggle.

In the app: /profiles/company

1. 01Open Kahrbon Profile; your page is created from your account.
2. 02Add your title, headline and bio, then save.
3. 03Copy your public link, or switch Published off to hide the page.

• Every teammate gets a personal public page, created on their first visit from their account details.
• Add a title, headline and bio, and the page wears your company's brand colors.
• Each personal page gets a search title and description built from your name, title, company and bio, with your company logo or avatar as the preview image.
• Turn Published off to hide your page. Pages of deactivated accounts stop showing too.

In the app: /profiles

1. 01Sign in with your password, or skip it with a passkey.
2. 02After the 48-hour grace period, sign-ins from untrusted devices need a 6-digit e-mailed code, or your authenticator code if you use one.
3. 03Sign-ins and failures are logged, and too many failures lock the account.

• Sign-in never reveals which e-mails have accounts: a missing account and a wrong password get the same answer in the same time.
• After a 48-hour grace period, a sign-in from an untrusted device needs a 6-digit code sent by e-mail, unless the account uses an authenticator app.
• Add an authenticator app by scanning a QR code and confirming one code. The secret is stored encrypted with AES-256-GCM.
• Sign in with a passkey instead of a password. A passkey counts as your second factor, so no code is needed.
• By default, five failed sign-ins on one account within 10 minutes lock it automatically until an admin unlocks it.
• In Login Activity, admins review sign-ins, failed attempts and automatic account locks, each with its IP address.
• Sessions use 15-minute access tokens and rotating refresh tokens. Reusing an old refresh token signs out every session.
• Integration OAuth tokens and authenticator-app secrets are stored encrypted with AES-256-GCM.

In the app: /settings?tab=security