The arrangement,
in language you can read.

What this covers

These terms describe how Kasper is provided and what each side is responsible for. They apply to whoever signs up for a workspace and to everybody they invite into it.

They are written to be read. The last four sections are the ones that are genuinely legal questions rather than descriptions of the product — what is warranted, how liability is limited, who answers a claim, and which law applies — and they are drafted here so the shape of the arrangement is visible before you meet it in a contract. Where a figure, a country or a court belongs, this page leaves the gap where you can see it rather than filling it with something that only looks settled. Ask us for the signed agreement before you commit to anything; it is not something we hide behind a click-through.

The service

Kasper answers conversations on the channels you connect, using the agents you configure and the knowledge you supply. What the agent says is shaped by the rules you write and bounded by the knowledge you give it; it answers from that and refuses outside it.

You keep control of the agent. You can change its rules, its voice, its knowledge and what it is allowed to do at any time, and you can turn it off without anybody having to re-point a number.

We improve the product continuously. Changes that affect how your agents behave are versioned — live conversations always use the version you published — and anything that would change a published version is your action, not ours.

Your account and your people

You are responsible for who you invite into your workspace and for the roles you give them. Roles decide what a person can see and do, and we enforce them on every request rather than in the interface.

Keep credentials to yourself and use two-factor authentication where the account matters. Tell us if you think an account has been reached by somebody who should not have it, and we will help you work out what was touched from the audit log.

Your data stays yours

The conversations, transcripts, recordings, tickets and knowledge in your workspace are yours. We process them to run the service and to give you what comes out of a call; we do not use them to train models, and we do not sell them.

You can export your data and you can delete it. Retention periods for recordings and transcripts are yours to set, and deletion runs automatically when they expire.

What we do with data, and which third parties are involved in carrying it, is set out on the privacy and security pages, and in the sub-processor schedule attached to your agreement.

What you are responsible for

You decide what your agent says, and you are responsible for it being accurate, lawful and appropriate for the people who will hear it. The knowledge you upload is the answer the agent gives; an out-of-date price list produces an out-of-date price.

You are responsible for telling your callers what you are legally required to tell them — that a call may be recorded, and anything your regulator requires about automated systems. The rules differ by country and by sector and we cannot make that judgement for you.

Do not use Kasper to place unsolicited outbound calls or messages, to impersonate somebody, or for anything unlawful where you or your callers are. That is the shortest version, and it is the one that matters.

Plans, usage and payment

Plans are billed monthly in advance and include a stated number of voice minutes. Usage past the included bundle is billed per minute at the rate on your quote; Enterprise runs on dedicated capacity agreed separately.

You can move between plans. Moving up takes effect immediately and is prorated; moving down takes effect at your next billing date, so you keep what you have paid for.

We will not change your price during a paid term. If pricing changes for a renewal we will tell you before the renewal, not with it.

Availability and support

We aim to keep the service running and we will tell you when it is not. Where an availability commitment is part of your plan it is written into your agreement with the numbers in it, because a commitment without a number is not one.

Support runs on the channel your plan includes. Anything that stops calls being answered is treated as urgent regardless of plan — that is not a paid tier, it is what the product is for.

Ending the arrangement

You can cancel at the end of any billing period, from inside the product, without having to ask anybody. Your workspace stays reachable until the period you have paid for ends, and you can export everything before it does.

We can end an account for non-payment or for use that breaks the rules above, and we will tell you why and give you a chance to fix it first unless it is causing active harm.

After an account closes, data is deleted on the schedule in your agreement. Ask us and we will delete it sooner.

What we promise, and what we cannot

We promise to provide the service with reasonable care and skill, to run it on the controls the security page describes, and to tell you when it is not working rather than wait for you to find out.

We do not promise that an agent’s answer is correct. It answers from the knowledge you give it, it refuses outside that, and it can still mishear a name on a bad line or read back a document you have not updated. That is a property of speech and of language models rather than a defect we are excusing, and it is why every call leaves you a recording, a transcript and a summary to check instead of asking you to take the outcome on trust.

We do not promise the service is never interrupted. Where an availability figure is part of your plan it is written into your agreement with a number in it, because a commitment without a number is not one.

The formal disclaimers a software agreement carries — which warranties are excluded, and which of the ones a country’s law implies may be excluded at all — differ by country and are exactly what counsel is for. They are not on this page, and their absence is not their exclusion: nothing written here is a disclaimer and nothing here should be read as one.

Where responsibility sits, and where it stops

We are responsible for running the service — keeping it available, keeping workspaces apart, protecting what is inside them, and telling you when something has gone wrong. Where our own failure causes you loss, that is ours, and the security page sets out the controls we hold ourselves to.

What we are not responsible for is what your agent says. It answers from the knowledge you upload and the rules you write, so an out-of-date price list produces an out-of-date price, and a caller acting on it is acting on your content. The same goes for what you send out: the number, the list and the consent behind an outbound call are yours.

Between those two sits a limit — a ceiling on what either of us can be made to pay, and an exclusion of the indirect losses agreements of this kind normally exclude: profit that was not made, business that went elsewhere, an opportunity that did not happen. The figure is not set. Writing one here would make it the most consequential number on this website, decided by whoever last edited a page, so the ceiling is a commercial decision taken with legal advice and it belongs in your agreement.

If somebody brings a claim

Two kinds of claim can come out of a product like this one, and they arrive from opposite directions.

The first is about a conversation — a caller who was told something wrong, a regulator asking why an automated system answered without saying so, a call recorded where a warning was owed first. Those come out of the knowledge, the rules and the disclosures you control, so they are yours to answer, and we will help you reconstruct exactly what happened from the recording, the transcript and the audit log.

The second is about the system itself — that the software infringes somebody’s rights, or that we handled data in a way we said we would not. Those are ours. We are not asking a customer to carry a defect in our own product, and wording that tried to would be worth arguing about before you signed it.

Turning that division into an obligation — who defends a claim, who pays, what notice is owed, and what happens when one claim touches both halves — is drafting, and it is a lawyer’s. It is not written here, because a paragraph copied from a template would look exactly like a paragraph somebody had thought about.

Which law applies, and where a dispute is heard

This matters more here than for most software, because the product crosses borders by design. The company is registered in one country, your workspace may be run from another, and the callers whose voices the agent hears are usually somewhere else again. Two questions follow: which country’s law reads this arrangement, and where a disagreement about it is settled.

Neither is answered on this page, and the gap is deliberate rather than an oversight. Naming a country and a court has consequences for you as much as for us — how far you would have to travel to argue, and which consumer and data-protection rules sit underneath whatever we agree. That is being decided with legal advice, and it will reach the agreement you sign before it reaches this page.

One thing does not wait for it. Whichever law ends up reading this contract, what you owe your own callers — about recording, about disclosure, about their personal data — belongs to the places those callers are, and that is what the responsibilities section above asks of you. We are not in a position to advise you on it, and this page is not the document that would.