Klarnow

Big ideas.
Plain English.

The Klarnow Dictionary. Understand the words, see what they mean for your business and put them to work.

60 terms to explore

Activation

In Klarnow's campaign language, an activation is a planned audience experience that leads to a useful action and measurable follow-through. It may happen at an event, through a partnership or within a digital journey. Attendance, attention, registrations and completed customer actions should be measured separately rather than bundled into one success claim.

See the business example for Activation

After-hours call handling

After-hours call handling defines what happens when someone calls outside the hours your team normally works. It may provide approved information, capture a message or follow an agreed escalation route. Being able to answer a call outside opening hours does not mean the business can deliver the requested service immediately.

See the business example for After-hours call handling

AGI

Artificial general intelligence, usually shortened to AGI, refers to the idea of AI with broad, general capability across many kinds of cognitive work. Definitions and proposed thresholds vary. It is not a useful substitute for specifying what a particular business tool can do, what information it uses and how its output will be checked.

See the business example for AGI

AI agent

An AI agent is a software system that uses information, instructions and permitted tools to work towards a defined objective. Its practical usefulness depends on the task boundaries, quality of context and actions it can genuinely perform. An agent's suggestion is not proof that a task has been executed, and access to one tool does not imply access to every system.

See the business example for AI agent

AI receptionist

An AI receptionist is software that handles a telephone conversation using the business information and instructions it has been given. It can ask why someone is calling, collect useful details and prepare a handover. Its ability to book, transfer or update another tool depends on the connections and permissions actually configured.

See the business example for AI receptionist

API integration

An API integration lets software exchange information or request actions through an interface provided by another system. The connection has to respect authentication, permissions and the receiving system's rules. Having API documentation or credentials is not proof of a working integration; the specific action, response and failure behaviour need to be tested.

See the business example for API integration

Appointment confirmation

An appointment confirmation tells a customer that the agreed booking has been accepted. It should make the date, time, location or joining method and any relevant conditions clear. The message must reflect the actual booking record. A successful email send by itself does not prove the calendar entry or service allocation exists.

See the business example for Appointment confirmation

Attribution

Attribution is the method used to connect a customer action with the marketing or referral touchpoints that preceded it. Different methods can assign credit differently, and missing data can limit what is known. A recorded source is useful evidence about a journey, but it is not necessarily proof that one campaign caused the sale.

See the business example for Attribution

Booking request

A booking request expresses a customer's preferred appointment, table or service time. It is not a confirmed booking until availability and the business's acceptance conditions have been checked. Systems should preserve that distinction in the record and in the message the customer receives, especially where a person still needs to approve the request.

See the business example for Booking request

Build Now

Build Now is the Klarnow stage where a clear business requirement becomes something usable. That might be a customer journey, website, receptionist configuration, workflow or operating document. The scope should follow the problem and include an acceptance standard, rather than expanding simply because more features or tools could be added.

See the business example for Build Now

Business knowledge base

A business knowledge base is an organised collection of information that people or software can use when doing work. For a receptionist it might include services, hours, locations, common questions and escalation rules. Information needs a clear owner and a review process so old prices or policies do not silently become current answers.

See the business example for Business knowledge base

Call forwarding

Call forwarding sends an incoming call from one telephone number to another destination. Depending on the provider and phone service, it may apply to all calls or only unanswered and busy calls. It is different from moving ownership of a number to a new provider. Available settings and charges need checking with your provider.

See the business example for Call forwarding

Call routing

Call routing is the set of rules that determines where an incoming call or captured enquiry goes. A route might depend on the reason for calling, opening hours, location or responsible team. Routing can result in a transfer, a message or a callback task; those outcomes should not be described as if they were the same.

See the business example for Call routing

Call summary

A call summary is a concise account of the useful information from a conversation. It should identify the caller's reason, the facts they supplied, anything still uncertain and the agreed next action. It is shorter than a transcript and should not turn a request, estimate or unconfirmed statement into a completed action.

See the business example for Call summary

Call transcription

Call transcription converts spoken conversation into written text. A transcript can help someone review what was said, but names, numbers and specialist words may be captured incorrectly. It is a source to check, not an automatic guarantee of accuracy. A business should decide who needs access and how the record will be handled.

See the business example for Call transcription

Call transfer

A call transfer moves an active telephone conversation to another person or destination. A successful transfer means the receiving side actually joins or accepts the call. Asking a colleague to call back later is a different action. Any transfer feature needs a valid destination, availability rules and a tested failure path.

See the business example for Call transfer

Catering enquiry

A catering enquiry is a request for food service for an event, group or occasion. Before a meaningful proposal can be prepared, the business normally needs the event date, location, guest count, service style and other relevant requirements. Recording the enquiry does not confirm availability, a final menu or a price.

See the business example for Catering enquiry

ChatGPT

ChatGPT is OpenAI's conversational AI assistant. A business can use it to draft, explain, analyse and organise material. In a working process, it needs a clear task and suitable context, and its output needs checking. A conversation or generated plan is not evidence that an external business action has been completed.

See the business example for ChatGPT

Clarity Review

A Clarity Review is a human review used in Klarnow's diagnosis process to understand fit and decide the next appropriate step. It should examine the information already supplied, clarify uncertainties and distinguish an immediate product need from a wider business-system problem. It is not a promise that every enquiry will need a large project.

See the business example for Clarity Review

Clear Now

Clear Now is Klarnow's principle of understanding the actual business problem before choosing what to build. It means separating symptoms from causes, gathering relevant evidence and naming the next useful decision. Clarity is not a long strategy document by default; it is enough shared understanding to make a responsible commercial move.

See the business example for Clear Now

Constraint

A constraint is a limiting condition that holds back a process or result. It might be capacity, missing information, slow approvals, poor routing or limited demand. The visible symptom is not always the constraint itself. Finding it requires looking at where work waits and what prevents the next useful step from happening.

See the business example for Constraint

Conversion

A conversion is a defined action that matters to a business, such as a qualified enquiry, confirmed booking or completed purchase. The action must be named before results are counted. A button click, submitted form and paid order are different events, even when they happen within the same customer journey.

See the business example for Conversion

CRM

CRM stands for customer relationship management. It describes the practice, and often the software, used to organise customer details, conversations, opportunities and next actions. A contact list is one part of it. A useful CRM also helps the team understand what has happened, who owns the relationship and what should happen next.

See the business example for CRM

Customer onboarding

Customer onboarding is the process that moves a customer from an agreed purchase or engagement into a working relationship. It confirms scope, responsibilities, required information, access and the first useful milestone. Sending a welcome message is only one step; the business still needs to know whether the customer can actually begin.

See the business example for Customer onboarding

Decision rights

Decision rights define who may make a decision or take an action, and when approval is required. They apply to people as well as automated systems. Clear boundaries distinguish collecting information, making a recommendation and committing the business to a price, booking, refund or other obligation. Those activities should not share an assumed permission.

See the business example for Decision rights

Definition of done

A definition of done states the observable conditions that must be met before a task is considered complete. It describes the result, required checks, evidence and any approval needed. Activity is not the same as completion: writing code, sending a message or uploading a file may be progress without satisfying the agreed outcome.

See the business example for Definition of done

Diagnosis

In Klarnow's business work, diagnosis means investigating what is preventing the desired commercial or operating result. It combines the founder's description with evidence about customers, tools, delivery and constraints. It should lead to a responsible recommendation, including when to simplify, delay or avoid work, rather than automatically recommending the largest possible installation.

See the business example for Diagnosis

Follow-up

Follow-up is the next relevant contact or action after an enquiry, conversation or purchase. It can answer a missing question, confirm a decision or move agreed work forward. Good follow-up has a reason, owner and timing. Repeated messages without context or regard for the person's preferences are not a useful process.

See the business example for Follow-up

Human handover

A human handover passes a conversation, decision or task from an automated process to a responsible person. It should include the context needed to continue, the reason for escalation and the next action. Depending on the setup, that can be a live transfer or a recorded callback request. The distinction matters to the caller.

See the business example for Human handover

Klarnow Call

Klarnow Call is Klarnow's AI receptionist offer for business telephone enquiries. The customer journey centres on preparing business information, reviewing call rules and testing the handover before relying on it for customer calls. Current plan details belong on the pricing and product pages; wider business-system installations are scoped separately.

See the business example for Klarnow Call

Klarnow Studio

Klarnow Studio is Klarnow's bespoke strategy, creative and implementation arm. It covers scoped work such as brand, websites, content, campaigns and custom delivery. A Studio engagement should name the customer problem, outputs, responsibilities and acceptance criteria. It is distinct from assuming every creative service is included in a Klarnow Call subscription.

See the business example for Klarnow Studio

Klarnow World

Klarnow World describes the company-specific operating environment within Klarnow's planned management architecture. The idea is to connect business context, people, tools and next actions around one organisation. It is not presented here as a separate subscription or proof that all of a company's systems have already been connected.

See the business example for Klarnow World

Launch Now

Launch Now is the Klarnow stage where tested work is introduced to its intended audience with a clear route for use, support and feedback. Publishing a page is one part of launching it. The team also needs to know how customers will find it, what action they should take and how the outcome will be reviewed.

See the business example for Launch Now

Lead capture

Lead capture is the process of recording an enquiry so the business can respond. Useful details usually include the person's contact route, what they need, relevant timing and how the enquiry arrived. Capturing a lead does not establish that it is a good fit, that the person has agreed to marketing or that a sale has occurred.

See the business example for Lead capture

Lead qualification

Lead qualification checks whether an enquiry matches the business's offer and delivery capacity. It can consider the need, location, timing, budget and information required for the next conversation. It should use relevant business criteria, make uncertainty visible and leave important judgements to the appropriate person rather than treating a score as a final decision.

See the business example for Lead qualification

Logos

Logos is the name used for the intelligence and coordination layer being developed within Klarnow. Its intended role is to interpret business context and help organise authorised work. It is not a separate customer-facing product on this website, and the name should not be used to imply that unverified integrations or autonomous actions are already available.

See the business example for Logos

Missed call

A missed call is an incoming telephone call that does not reach an answer on the intended route. It might happen because the line is busy, the team is unavailable or the business is closed. A call log shows an attempt to make contact; it does not prove that the caller became a lost sale.

See the business example for Missed call

Mission

A mission is Klarnow's term for a bounded unit of work with a clear outcome, owner and evidence of completion. It should explain what success looks like, what information is required and which decisions are outside scope. A mission is more useful than an open-ended instruction to improve something without defining the finish.

See the business example for Mission

Online ordering

Online ordering lets a customer select products or services and submit an order through a digital journey. A complete flow needs clear availability, prices, fulfilment details and an accurate confirmation. Payment, order acceptance and fulfilment are separate events, and the business should know which of them has happened at each stage.

See the business example for Online ordering

Operate

Operate describes the ongoing work of running and improving a system after it has been built. It includes maintaining business information, checking incoming work, handling exceptions and reviewing results. A delivered system still needs ownership; it does not become self-maintaining simply because some of its steps are automated or supported by AI.

See the business example for Operate

Prompt

A prompt is the instruction and context given to an AI system for a task. A useful business prompt states the intended outcome, the facts it may rely on, the constraints and the format of the answer. Longer is not automatically better. Missing or contradictory source information should be resolved rather than disguised by elaborate instructions.

See the business example for Prompt

Proof

Proof is evidence that supports a specific claim about work or an outcome. A screenshot can show that a page exists; a completed test can show how one journey behaved; a verified customer record can support a commercial result. Each proves something different. The evidence should match the claim without quietly stretching beyond what was observed.

See the business example for Proof

Property viewing

A property viewing is an arranged opportunity to inspect a property, usually after a prospective buyer or tenant expresses interest. A request needs enough information to identify the property and coordinate availability. Capturing preferences and contact details does not confirm a viewing or establish that the property is suitable for the person.

See the business example for Property viewing

Quote request

A quote request asks a business to price a defined piece of work. The initial conversation often lacks the information needed for a reliable offer, so the next step may be a site visit, clarification or assessment. An indicative estimate and an agreed quotation should be labelled clearly rather than used interchangeably.

See the business example for Quote request

Repeat purchase

A repeat purchase happens when a customer buys again after an earlier completed purchase. It is different from an email open, repeat website visit or second enquiry. Businesses can measure it over a defined period, but the calculation should state which customers and orders are included so the result is meaningful.

See the business example for Repeat purchase

Response time

Response time measures how long it takes to respond after an enquiry or request arrives. Be clear about the start and finish: an automatic acknowledgement, a useful human reply and a resolved issue are different milestones. Measuring them separately shows whether people are merely being notified or actually receiving the help they need.

See the business example for Response time

Route

A route is the agreed path that a customer, signal or task follows to reach its next stage and owner. It includes decision points and exceptions, not just the normal sequence. A clear route states what information travels with the work and what should happen if the usual destination is unavailable or the criteria are not met.

See the business example for Route

Sales pipeline

A sales pipeline groups active opportunities by the stage they have actually reached. Stages might include new enquiry, fit checked, proposal sent and decision pending. Each stage needs a clear entry condition. Moving a card should represent evidence of progress, not a team's hope that the prospect is closer to paying.

See the business example for Sales pipeline

Search intent

Search intent is the task someone is trying to complete when they search. They may want a definition, instructions, a comparison or a service they can buy. A phrase alone does not reveal the whole situation. Useful research checks the wording, available evidence and the kind of answer that would genuinely help the person.

See the business example for Search intent

SEO

Search engine optimisation, or SEO, is the work of making useful website content discoverable and understandable in search. It includes clear answers, accessible pages, descriptive titles and meaningful internal links. Technical setup supports that work, but it cannot guarantee that a page will be indexed, ranked or chosen for a particular search result.

See the business example for SEO

Signal

In Klarnow's operating language, a signal is an event or piece of information that may require a business response. It could be a new enquiry, purchase, booking request, approval or delivery change. A signal becomes useful when its meaning, source and required next action are clear enough for the right person or workflow to handle it.

See the business example for Signal

Single source of truth

A single source of truth is the agreed authoritative record for a particular piece of information. It does not require every tool to be replaced by one application. It means the team knows which record governs the customer status, price, task or decision, and how any copies are kept consistent with that record.

See the business example for Single source of truth

Smart Management System

Smart Management System is the name used for Klarnow's business management platform in development. The intended direction brings customer context, opportunities, work and next actions into a connected operating experience. It should not be confused with a claim that every planned module or integration is available to every customer today.

See the business example for Smart Management System

SOP

A standard operating procedure, or SOP, explains how to complete a repeatable task to an agreed standard. It should identify the trigger, required information, responsible role, steps, checks and definition of done. It also needs an exception route, because a real process must explain what to do when the normal steps cannot be completed.

See the business example for SOP

Structured data

Structured data is a machine-readable description of information on a page. Schema.org provides types such as DefinedTerm for a glossary entry, and JSON-LD is one way to express them. The markup should agree with what visitors can read. It does not replace useful content or guarantee enhanced search results or AI recommendations.

See the business example for Structured data

Table booking

A table booking reserves restaurant capacity for a particular party and time once the restaurant accepts it. The booking record should include the details needed to manage the visit and any questions requiring staff attention. Taking an enquiry over the phone is different from checking live capacity and reserving a table in the restaurant's system.

See the business example for Table booking

Test call

A test call is a controlled call used to check how a configured phone journey behaves. It should cover an expected request and important exceptions, then verify the resulting record and handover. Hearing a greeting is not enough to prove the full journey works, and a successful test does not guarantee every future call will behave identically.

See the business example for Test call

UTM parameters

UTM parameters are labels added to a URL to describe a campaign source, medium or other campaign detail. Analytics tools can use them to group incoming visits when tracking is available and allowed. They do not identify every influence on a customer, and the labels are only useful if the team names them consistently.

See the business example for UTM parameters

Webhook

A webhook is a message one system sends to another when an event occurs. It can tell a workflow that something changed, such as a payment status or booking update. The receiving system still needs to validate the message, handle duplicate deliveries and decide what action is appropriate. Receiving an event is not the same as completing the work.

See the business example for Webhook

Workflow automation

Workflow automation uses software to carry out defined steps when a particular event occurs. A workflow needs a trigger, conditions, actions and a way to handle failures. It may use fixed rules, AI or both. Automating a step does not remove the need to decide who owns the result or who reviews exceptions.

See the business example for Workflow automation

Understand it.
Then put it to work.

Use a practical guide to prepare your receptionist, organise enquiries or document a repeatable process.

Explore the Academy