Questions? +40 763 659 291

Version of 11 November 2026

Guarantee and terms

These are the terms of every Casework contract. Your quote adds your prices, your dates, your scope and the AI model your setup uses (clause 10).

These terms are offered by Sensigo Software SRL, Ploiești, Romania. Full company details are at the end of this page.

  1. 1.Our 3 guarantees
  2. 2.What we do not guarantee
  3. 3.The setup
  4. 4.What you pay each month
  5. 5.What the service plan covers
  6. 6.How long the contract runs
  7. 7.Your data
  8. 8.Who is responsible for what
  9. 9.If we ever stop
  10. 10.The rest

1. Our 3 guarantees

1.1 It Passes Your Test, or You Don’t Pay

You pay the last part of the setup fee only when your setup passes your test (clause 3.2). You get back every dollar you paid for setup if your setup does not pass in time, as clause 3.3 says.

Your contract names the AI model your setup uses. Before we change that model, or upgrade our own software, we run your test again on your own tickets, the way clause 3.2 describes. We show you both scores, before and after. If the new score is lower, a change we chose to make does not go live.

A test is a sample, and a problem can still show up after a change goes live. After every change we choose to make, we keep scoring your real tickets against your rulebook, the same way as in your test. We compare your real tickets’ score in the 14 days after the change with the 14 days before it. If the score after is lower, we undo the change. You pay no AI fee from the day the change went live until the day we undo it. If the change was to our own software, you pay neither the plan nor the AI fee for that time.

Some changes are forced on us, such as moving off a model its maker retires, or a security fix. We do not choose them, so this guarantee does not cover them. They go live even if the score drops. We expect a newer model to do at least as well as the one it replaces. We cannot promise it. We still run your test and show you both scores. A security fix that cannot wait goes live first. We run your test within 7 days of the day it goes live. If the score does drop, we work to bring it back at no extra charge. That work is covered by your service plan (clause 5.1).

This guarantee does not cover a change you asked for to your rules or templates (clause 5.2). If one of those lowers your score, we look at your rules with you.

1.2 The Nothing-You-Didn’t-Approve Guarantee

Our system builds every reply and every draft from a template you approved, filled in with live details, except answers written by AI that you ask for (below). It writes no sentences of its own into them. Every ticket leaves an evidence record you can read.

You pay no service plan and no AI fee for any month in which our system writes a sentence you did not approve into a reply or a draft.

A sentence you did not approve is a sentence that is not in one of your approved templates. It counts when our system wrote it into a reply to your customer, or into a draft for your team. The details we fill in from your store, your helpdesk and your carriers are part of the template. They include a name, an order number, a date, a tracking link and a delivery status. They are not sentences of their own. A draft your team edits and sends is your team’s reply.

The brief our system adds when it sends a ticket to your team (clause 4.2) is a note for your team. It is neither a reply nor a draft, so this guarantee does not cover it.

The proof is the ticket’s evidence record. It shows the template used and the reply as our system wrote it, so anyone can compare the reply with the template. If you find a reply or a draft with a sentence you did not approve, show us the ticket within 60 days of that month’s invoice. You pay no service plan and no AI fee for that month if the ticket’s evidence record shows such a sentence.

A reply that used the wrong template, or filled in an order detail other than the one your helpdesk, Shopify or a carrier gave us, is a defect. It does not count as a sentence you did not approve. We fix defects at no charge, and your test measures them (clause 3.2).

You may ask us for answers written by AI rather than taken from a template, such as answers about your products drawn from your product pages. Before we build them, we tell you in writing whether this guarantee covers them.

1.3 The Never-Left-Alone Guarantee

Message the person who built your setup on WhatsApp, any day from 11:00 to 23:00 Central European time (CET, or CEST in summer), weekends included. You get a human answer within the hour.

An answer is a reply from a person that answers your question, or says exactly what happens next and when. An automatic acknowledgement is not an answer. A message sent outside those hours starts the clock at 11:00. Time outside those hours does not count.

No answer within the hour? Call the number in your contract. If you still have no answer by 23:00 on the day the hour ran out, that month’s service plan is free.

When the person who built your setup is away, we tell you in advance who answers instead. An absence we did not tell you about does not stop the clock.

The line is for questions about your service and your setup. A change you ask for is quoted first (clause 5.2). A defect is fixed at no charge (clause 5.1).

1.4 How the money reaches you

When a guarantee pays out, the amount comes off your next invoice. You never fill in a claim. We refund the amount within 15 days if you have left and there is no next invoice. The 15 days count from the day you leave or the day you show us the ticket, whichever is later.

In any month, the guarantees never give back more than that month’s service plan and AI fee. This cap does not reduce the setup refund in clause 3.3. A guarantee paying out takes nothing else away. Any defect is still fixed at no charge. You can still leave whenever you want. And you can still claim for a loss, within the limit in clause 8. What a guarantee paid for an event counts toward any claim for a loss from that same event.

2. What we do not guarantee

We do not promise a percentage. How many of your tickets our system answers depends on your rules and your tickets. Your report estimates that number from your real tickets, before you sign. It does not promise what our system will do. Until then, any number we show you, our estimate included, comes from other stores’ tickets.

3. The setup

3.1 How you pay for it

We quote the setup fee with your report. It covers the stores, languages and kinds of ticket in your quote. You pay it in 3 parts:

  1. $2,000 reserves your start date. That is the day we begin work on your rulebook, within 4 weeks of your deposit, sooner when a slot is free.
  2. Half the setup fee when you approve your rulebook and we start building. The $2,000 counts toward that half.
  3. The rest only when your setup passes your test.

No plan and no AI fee while we build.

3.2 Your test

We run the test on your own tickets, by your own rules. It is measured on at least 300 tickets from the last 2 rounds of drafts, each one answered or sent to your team. Spam, automatic messages, messages with nothing new and tickets already closed are not counted.

A reply is right when it is the one your rulebook prescribes for that ticket, filled with the right order details, and true to the order and the parcel. Sending a ticket to your team is right when your rulebook says a person should handle it.

Your setup passes when at least 90 in 100 are right, and 3 more things hold:

  • no run failed;
  • every ticket got a reply, went to your team, or was set aside for one of the reasons above;
  • no reply has a blank where an order detail belongs.

Our rulebook check scores each ticket. Each verdict names the exact rule, so you can check the verdict against your rulebook in one step. Your reviewer reads the same tickets. We use the reviewer’s verdicts to measure how often our check is right, and we report that with the result. Our rulebook check’s verdicts decide whether your setup passes. We read the rule a verdict names with your reviewer, whenever your reviewer disagrees with that verdict. If the rule’s words support the verdict, it stands. If they do not, we correct the verdict. A rule that is missing or worded other than you meant is a change. We fix it with you, as clause 3.4 says.

How many tickets our system answers on its own is not part of the test. You set that number, by choosing which kinds of ticket we answer for you.

3.3 If it does not pass in time

Your quote gives the date your setup should pass by. If it has not passed by then, we keep working at no charge, on the scope in your quote. We do this for up to half the time the build was quoted for. A build quoted at 8 weeks gets up to 4 more.

You get back every dollar you paid for setup, and the contract ends, if:

  • we tell you your setup cannot pass on the rulebook you approved;
  • that extra time ends and it still has not passed (or, if we both agree in writing, we carry on); or
  • we cannot give you a start date within 4 weeks of your deposit, or we miss the start date we gave you.

We pay it within 15 days.

Your part includes approving the rulebook, reading drafts, and choosing which kinds of ticket we answer for you. If your part takes longer than agreed, the clock waits for you. Your delay never triggers a refund. We may end the contract with written notice if your part is more than 60 days late in total. Nothing you paid for setup then comes back.

If you change your mind, nothing you paid for setup comes back. That includes the $2,000, once your start date is confirmed.

3.4 Changes during the build

We build to the rulebook you approved, and finish the build before taking changes. Changes then come out of a change budget worth 10% of your setup fee. Your setup statement shows the budget, what you have used and what is left.

A small change, such as one rule or one template, costs a flat amount set in your quote. We take it from the budget without asking. We price a larger change first, and take it from the budget only with your OK. Once the budget is used up, we quote each change. The budget is for the setup. Once your setup passes its test, we quote every change (clause 5.2), and what is left of the budget is not paid back.

A defect is never a change. If the build does not do what your approved rulebook says, we fix it at no charge.

A change your setup cannot pass its test without is the one exception. We make it first and tell you. You pay for it outside the budget.

4. What you pay each month

Your monthly bill starts the day your setup passes its test. It has 2 parts: the service plan and the AI fee.

4.1 The service plan

$400 a month at 3,000 tickets. Above that, the plan grows by $150 for every 1,000 tickets, worked out to the ticket. At 5,000 tickets, the plan is $700. We count your tickets from your helpdesk and use your median month. That is the middle of the 12 months before your build, when you line them up from quietest to busiest. So a single busy month does not raise your plan. The plan is fixed for each contract year. We count it again at each anniversary, the same way. It is never less than $400.

4.2 The AI fee

For each billable message. The price per message falls as your month’s count grows:

  • Messages 1 to 2,500 of the month $0.16 each
  • Messages 2,501 to 5,000 of the month $0.15 each
  • Messages 5,001 to 7,500 of the month $0.14 each
  • From message 7,501 on $0.13 each

Each price applies only to the messages in its own range. So a busier month never makes your first messages cost more.

We bill a message from your customer when our system reads it in full and then does one of 2 things:

  • it sends a reply from your approved templates, or drafts one for your team;
  • it sends the ticket to your team with a brief attached: what the customer wants, and the order and parcel facts we found.

4.3 What costs nothing

These are printed on your invoice at $0.00:

  • spam, automatic notifications and out-of-office replies;
  • messages with nothing new from your customer;
  • tickets your team closed before our system reached them;
  • the 7 kinds of ticket we hand straight to your team: legal threats, payment problems, invoice requests, anyone asking for a person, returned parcels, wholesale enquiries and sales pitches.

There is no charge per user, and nothing is paid in advance.

4.4 Your invoice

We send your invoice after each month, for that month, in US dollars. It also shows what you paid per ticket. Prices exclude VAT and any other tax on the sale, which are added where the law requires them. A month is a calendar month. The first and the last month are billed only for the days they cover.

When you sign, you save a card with our payment provider. We charge the card the day the invoice is issued. That is the way we prefer. You can pay by bank transfer instead, within 7 days. The transfer’s fees are yours, so the full amount has to arrive.

Every billed message has its evidence record. Question any line within 60 days. If we cannot show you a record that makes it billable, we credit it. If you tell us to delete a ticket’s data, we keep its number, date and price, and its line stays billed. A card payment you reverse with your bank counts as unpaid.

Above 10,000 tickets a month, we quote: same structure, negotiated rates.

4.5 If a payment fails

If a card charge fails, we tell you and try again. If it has not gone through within 3 days, we pause the service until it does. A bank transfer that has not arrived within 7 days pauses the service the next day, until it arrives. While it is paused, nothing is sent and no AI fee is billed. Your service plan is still billed. Your tickets wait in your helpdesk for your team, as they did before us.

5. What the service plan covers

5.1 Included

  • Running your setup on our servers, and watching it.
  • Keeping your setup correct when the helpdesk, Shopify and carriers named in your quote change how they work, as long as they still give our system what your setup needs. Moving to another helpdesk is a change (clause 5.2).
  • Fixing defects, at no charge, always. A defect is a fault in our software or your setup that stops your setup doing what your approved rulebook says. A reply that is wrong because your helpdesk, Shopify or a carrier gave us wrong details is not a defect.
  • The upgrades we must make to keep it running, such as a model its maker retires or a security fix.
  • A monthly report. It shows:
    • the tickets your rules do not decide yet, the rule that would cover each, and how many more tickets that rule would answer;
    • how many customers asked for their money back, how many got an offer and how many never did, where the offers stopped, and how much money stayed;
    • anything we noticed in your store that needs fixing.
  • Your rulebook and templates, always current, on your own download page, with a line in your report whenever either changes.
  • The WhatsApp line (clause 1.3).

5.2 Quoted first

Any change you ask for to your rules, your templates or your setup. That means a new rule, a new kind of ticket, a new store, a language or a channel. We quote each change on its own, and make it only with your OK in writing. A WhatsApp message counts as writing. Nothing is prepaid. We may change how we run the service as long as your setup still does what your rulebook says. Fixing a defect needs no quote and no OK.

5.3 Optional upgrades

A newer AI model, or a new version of our own software, may change how your setup behaves. We offer each one with a quote. It goes live only after it passes your test again (clause 3.2). We show you both scores first, as clause 1.1 says. If the new score is lower, it goes live only if you still want it. You may say no and stay on your version. If you stay more than 1 major version of our software behind, we may change your plan’s price at the next anniversary.

5.4 When something stops

If your helpdesk, Shopify or a carrier stops working, our system waits. Nothing is sent and no AI fee is billed for tickets it cannot handle, and your tickets stay in your helpdesk for your team. If our own system stops, the same holds, and fixing it is part of your plan.

6. How long the contract runs

6.1 The first year

The contract runs 12 months, counted from the day your setup passes its test. For those months your prices are fixed, and we cannot end the contract except under clause 6.4.

6.2 After that

Then the contract carries on month to month. From then on, we can also end it, with 30 days’ written notice. We count your plan again at each anniversary (clause 4.1).

6.3 You can leave at any time

You can end the contract whenever you want, by written notice. It ends on the day we receive your notice, or on a later day you name. You pay for what we did up to that day, and nothing after it. Leaving does not refund what you paid for setup, except as clause 3.3 says.

6.4 When we may end it

In the first 12 months, we may end the contract only in 2 cases:

  • an invoice stays unpaid 30 days after we paused the service;
  • you break these terms and do not put it right within 30 days of our written notice.

After the first 12 months, we may also end it with notice (clause 6.2). Clause 9 applies when we withdraw the service from you for any reason other than those in clause 6.4. Ending the contract under clause 6.2 is such a withdrawal. A pause (clauses 4.5 and 8.1) or an outage (clause 5.4) is not a withdrawal.

6.5 Prices

Your plan and your rates are fixed for each contract year. There is no automatic yearly increase. Counting your plan again at an anniversary, by the rule in clause 4.1, is not a price change. A price change can only start at an anniversary, after 60 days’ written notice.

6.6 Changes to these terms

Every version of these terms carries its date, and the version you signed is the one that applies to you. A new version applies to you only if you agree to it in writing, or from your next anniversary after 60 days’ written notice. A change the law requires applies when the law says. We tell you about it in writing, before it applies when we can. The changes our data processing agreement lets us make (its clauses 5 and 6) apply as that agreement says.

7. Your data

7.1 The estimate

You answer questions about your store. It uses none of your tickets.

7.2 Your report

Before you send anything, we sign a mutual NDA. You send your tickets in one of 2 ways: as a file you export yourself, or by giving us view-only access to your helpdesk, which you can remove at any time. We use up to 500 of them for your report. We open no others, even where your helpdesk shows them, except to count their messages as NDA clause 4.5 says. We delete them with the tickets we use. We use your tickets for your report and your quote only, and never to train any AI. We delete them 7 days after we send your report, or the same day if you ask. If we send no report, we delete them within 14 days of receiving them. We stop using any view-only access you gave us once we send your report, or once we tell you we will send none. Removing it is up to you, and we remind you when we send the report.

7.3 While you are a client

Your store’s data is yours. We use it only to run your setup, on your instructions, and for the counts in clause 7.6. In the words of the GDPR, you are the controller and we are your processor. Our data processing agreement is part of these terms.

Your setup runs separately from every other client’s, on servers we rent from Hetzner in Germany. If you prefer the US, we run it on Hetzner’s servers there, at no extra charge.

The AI model your setup uses comes from Anthropic. Anthropic’s commercial terms say: “Anthropic may not train models on Customer Content from Services.” We never use your data to train any AI model either.

The data processing agreement lists the companies that handle your customers’ data for us (its clause 6). We tell you 30 days before we add one, so you can object, or leave (clause 6.3).

If your data is ever exposed, we tell you within 48 hours of finding out: what happened, what it touched, and what we are doing about it.

7.4 What is yours

Your rulebook, your templates, your evidence records and your data are yours. Our software, the workflow we build for you, our methods and the way we write a rulebook stay ours. Paying for setup does not transfer them. We may use the same kind of rule for other clients, without your store’s details.

Your current rulebook and templates are always on your download page, and you can ask for a copy of your evidence records at any time.

7.5 When the contract ends

Within 30 days of the end, we send you a copy of your evidence records, your rulebook and your templates, and we delete your data. We keep the evidence records behind any invoice you can still question, until you no longer can (clauses 1.2 and 4.4). Then we delete them. We keep each billed ticket’s number, date and price until its invoice line can no longer be questioned (data processing agreement clause 8.1). We keep your contact details, your signed quote and our invoices as our privacy notice says (section 6). We keep a fingerprint of the copy we send you. A copy that does not match that fingerprint is not the copy we sent.

7.6 Our own numbers

We never name you as a client, or quote your numbers, without your written OK. We may count across all our clients, where no store, customer or order can be identified.

8. Who is responsible for what

8.1 What we need from you

Your policies are yours to decide. We write them into your rulebook, and you approve it.

Tell us before a policy changes. Until we change the rule (clause 5.2), our system follows the rule you approved.

Keep our access to your helpdesk and your Shopify store working. While it is broken, our system waits (clause 5.4).

Your policies, templates and data must be lawful. You may not use the service to break the law or the usage rules of the AI model’s maker. We may pause the service at once if you do, or if a law or an authority requires a pause. We tell you why, unless a law or an authority forbids it. We restart it once the reason is gone.

8.2 Who answers for what

Replies go out in your name and under your rules. So toward your customers, you are responsible for them, the same as for anything your team sends. That is why our system sends only replies built from templates you approved. Toward you, we run your setup with a professional’s care, within the guarantees in clause 1 and the limit below. A single wrong reply is at most a defect we fix (clause 5.1). On its own, it is not a breach of these terms.

Each of us is liable to the other for no more than 3 times your monthly service plan, for all claims together. The plan that counts is the one at the time of the claim. Until the service starts, it is the plan in your signed quote. Before you have a quote, it is the smallest plan, $400 a month. After the contract ends, it is the plan of its last month. That limit does not reduce what our guarantees pay. It does not limit the fees you owe us. And it does not apply where the law allows no limit. Neither of us is liable for indirect losses, such as lost profit.

9. If we ever stop

If Sensigo ceases trading, becomes insolvent, or withdraws the service, from you or from everyone, we deliver within 30 days of our notice, or of the day the service stops, whichever comes first:

  • your workflow: its code, its configuration and its settings;
  • your current rulebook and templates;
  • the notes to install it and run it;
  • a copy of your evidence records.

You may run it on your own servers, for your own stores, for as long as you like. You may not resell it, license it to others, publish it, or offer it to others as a service. The software your workflow runs on is open source, so no one can take that software away from you. You bring your own hosting and your own account with the AI model’s maker.

We keep this package ready from the day your setup passes its test. It is released in those 3 cases only: not when you end the contract, not when we end it under clause 6.4 over an unpaid invoice or a breach, not in a dispute, and not on request.

10. The rest

These terms, your signed quote, our data processing agreement and the NDA are the whole contract. Your quote adds your prices, your dates, your scope and your model. It may also improve these terms for you. Such an improvement holds until an anniversary. From then, we may change it with the notice in clause 6.6, like any other term. Your quote never takes away a guarantee (clause 1), a right over your data (clause 7) or clause 9.

Each of us keeps what we learn about the other’s business confidential, as clauses 2, 3 and 5 of the NDA say. That lasts during the contract and for 3 years after it. Trade secrets stay confidential as long as the law protects them.

Notices are in writing, by email: to the address in your quote, and to hey@casework.run. A WhatsApp message is not a notice. An email notice counts as received the next working day after it is sent, unless it bounces. Either of us may change its address by notice.

Neither of us may pass this contract to another company without the other’s written OK, unless that company takes over the business it covers. Clauses 1.2, 1.4, 3.3, 4.4, 6.3, 7.4 to 7.6, 8, 9 and 10 still apply after the contract ends. Either of us may ask a court to stop a breach without first waiting out the 30 days below.

Neither of us answers for a failure caused by something outside its control that it could not avoid, such as an outage at Hetzner, Cloudflare, Anthropic, WhatsApp, your helpdesk, Shopify or a carrier. The times in these terms wait for as long as that cause lasts. Such a cause never excuses a payment.

The contract is governed by Romanian law. If we disagree, we first try to settle it between us, for 30 days from the day either of us raises it in writing. After that, a claim goes to the courts where the other side is based. If we ever bring a claim against you, we bring it in your courts. You bring yours in ours. The contract is written in English. If a court sets one clause aside, the rest still stand.

Romanian law asks you to accept some clauses expressly, in writing (article 1203 of the Civil Code). Your quote lists them, and you accept them there with a second signature. They are:

  • the 60 days in clauses 1.2 and 4.4;
  • the cap in clause 1.4;
  • your setup payments in clauses 3.3 and 6.3, and our ending in clause 3.3;
  • the pause in clauses 4.5 and 8.1;
  • month to month and our ending in clauses 6.2 and 6.4;
  • changes in clause 6.6;
  • price changes in clauses 5.3 and 6.5;
  • the limits in clause 8.2;
  • the package’s limits in clause 9;
  • the law and the courts in clause 10;
  • clauses 3, 6, 7 and 12 of the data processing agreement.

Company details

Sensigo Software SRL
Str. Ion Maiorescu nr. 8, bl. 33T1, sc. A, et. 5, ap. 16
100067 Ploiești, Prahova, Romania

Fiscal code (CUI) 41144887
Trade register J29/1849/2019
EU VAT (intra‑community) RO46302856

hey@casework.run
+40 763 659 291