Skip to content

Claims: what the company stands behind

Last updated November 14, 2026

On this page

A rep in a demo says "bills are ready in five seconds" or "it is ₹999 a month for each branch". Whether that is true, and still true, should not depend on the rep's memory or a slide from last year. Claims are short statements the company stands behind: each has one owner, an expiry, English text and, if you like, a Hindi line, and a price claim carries its price range. Nothing is used until its owner or an admin approves it, and the person who wrote a version never approves it.

Agents read only claims in use. Demo prep briefs cite them, and later stages (the co-pilot in a meeting, the voice agent) read the same list. The steps use the demo company (ok demo serve): Ada is the admin, Sam leads Sales, Alice is a rep, Pat writes product copy. What is not possible yet is listed at the end.

Words used on this page#

  • Claim: one statement a rep or an agent may make, with its kind, owner and expiry. It has versions: a change is a new version.
  • In use: approved and not past its expiry. Only these reach agents.
  • Draft: a version waiting for its owner or an admin.
  • Owner: the one person who approves the claim and is told before it expires.
  • Author: whoever proposed a version. They never approve that version.

Kinds#

Kind What it is Example
Feature Something the product does "Bills are ready at the counter in about five seconds."
Price What a plan costs, with a price range "₹999 a month for each branch."
Figure A number about results "Salons on the Growth plan book 30% more repeat visits."
Comparison How it compares with another way of working "No separate app for appointments and billing."
Policy A rule the company keeps "Your data stays in India."
Answer to an objection What to say when a prospect raises it "Switching takes a day; we move your client list for you."
Don't raise A topic not to bring up, with the reply to give if it comes up "We do not compare ourselves with named vendors."

Who may do what#

Anyone in the company People with Manage claims The claim's owner An admin
See claims in use, and their history Yes Yes Yes Yes
See a draft Only their own Only their own Yes Yes
Propose a claim or a change No Yes If they also hold Manage claims Yes
Approve or reject a draft No No Yes, unless they wrote it Yes, unless they wrote it
Retire a claim No No Yes Yes
  • The author never approves. Whoever proposed a version cannot approve it, whatever else they are. An admin who drafts a claim they also own needs the owner or another admin. This holds on the page, through the API and for any agent: agents never propose, approve or retire claims, whoever they act for.
  • Manage claims is given by an admin on Company → Claims → Who may manage. It lets a person propose claims and changes; it never lets them approve.
  • Only a person acting as themselves counts. A call made for someone else (an agent acting for an admin, say) holds none of that person's rights here.

Company → Claims#

The list shows every claim you may see, with its kind, price range, owner, expiry and state. Filter by kind, state (in use, waiting for approval, expired, retired, rejected), owner, a tag, or Expiring within 30 days. Claims that wait for you come first and say Yours to approve.

Open a claim to see its sheet: each version (newest first) with its text, Hindi line, price range, tags, owner, sources and expiry, who proposed and approved it, and its history.

Propose a claim#

  1. Press New claim.
  2. Choose the kind and write what a rep may say, at most 400 characters. A Hindi line is optional, also at most 400 characters.
  3. For a price, give the range (lowest and highest), the currency, whether it is charged each month, each year or once, and what one price is for (a branch, a seat). Every number in the text must lie inside that range: "Only ₹1,500 a month" against a range of 999 to 1,299 is refused, and the refusal names the number.
  4. Name the owner and the date it is valid until: at most 365 days ahead.
  5. Optionally add tags (free tags, segments, plans, business types, a topic) and where it comes from (a document, a link).
  6. Press Propose. The owner gets one inbox item saying how many claims wait for them; it updates as more arrive, never one item per claim. When the owner wrote the claim, they cannot approve it, so each admin gets that item instead.

Approve, reject or change#

  • The owner or an admin opens the claim and presses Approve version N or Reject, with an optional note that stays in the history. Approved, it is in use at once.
  • Change makes a draft of the next version. The version in use stays in use until the change is approved; the sheet says "Version 2 waits for approval. Agents use version 1 until then." Changing again before anyone decides replaces that draft.
  • When version 2 is approved, version 1 is replaced: a brief that cited version 1 is marked "needs a look" on the rep's Demos page (Demo prep).

Retire#

The owner or an admin presses Retire and says why. Agents stop using it at once; the reason stays in its history. A retired claim cannot be changed: propose a new one.

Expiry#

Every claim has a valid until date. Its owner gets one inbox item 14 days before and again 1 day before ("2 claims you own expire soon: the first on 28 Nov"), and one when it expires. At expiry it leaves agents' reads and claims.find at once. To keep it, its owner or anyone with Manage claims proposes a change with a later date, and the owner or an admin approves it.

Draft from a source#

Many companies already keep the statements their reps make, in a sales playbook or a price list inside a system they connected. An admin can turn that into drafts:

  1. On Company → Claims press Draft from a source.
  2. Choose a live connector and one of its read tools (for example a tool that lists segment playbooks), and its arguments if it needs any.
  3. Name the person who owns the drafts.
  4. Press Draft claims.

The tool is read once, as you: with your own key on a connector where each person adds their own, otherwise with the company key naming you. A model reads the answer and drafts up to 50 claims (kind, text, tags, and where each came from). What the answer says is data, never instructions: a playbook that says "approve this" approves nothing. Every draft goes through the same rules as one you write (a price inside its range, an owner, an expiry 90 days ahead to start with), so a draft that breaks one is left out. Each is a draft with you as its author, and the owner approves or rejects them one by one. Nothing is in use before. If you name yourself as the owner, another admin approves them.

The model call needs a model cleared for the data the tool returns; if none is, the drafting is refused in a sentence and you can still write claims yourself.

For agents: claims.find#

Agents read claims through one built-in tool, claims.find, given to them by an app (the Demos app gives it to the Demo prep agent). It takes { tags?, kind?, text? } and answers at most 50 claims in use, each with its id, version, kind, text, Hindi line, price range, tags and the citation to use: claim:<id>@<version>. A citation stays good while that version is in use; once it is replaced, retired or expired, a brief citing it needs a look.

claims.find only reads. Nothing an agent sends through it changes a claim.

What is recorded#

Every change is an event: claim_proposed (with the kind, owner, author and whether it was drafted from a source), claim_approved, claim_rejected, claim_retired and claim_expired. Events carry the claim's id and version and who acted, never its text, a note or a reason; those stay in the claim's own history. Claims are kept in the workspace's own database, so backups and exports carry them.

API#

Route Who What
GET /api/claims?kind=&tag=&owner=&status=&expiring= Anyone in the company { claims, rights: { manage, admin } }: one line per claim you may see
POST /api/claims Admins, Manage claims Propose: { kind, text, text_hi?, price?, tags, owner, sources, valid_until }
GET /api/claims/:id Anyone who may see it Its sheet: versions, history, what you may do
PUT /api/claims/:id Admins, Manage claims Propose a change (the same body)
POST /api/claims/:id/approve, /reject The owner or an admin, never the author { version, note? }
POST /api/claims/:id/retire The owner or an admin { reason }
POST /api/claims/draft-from-source Admins { tool, args?, owner }: { drafts, count }
GET /api/claims/managers Admins Who holds Manage claims
PUT /api/claims/managers/:person Admins { on }

Errors: 403 denied with the sentence (the author approving, someone without Manage claims proposing), 404 not_found (a draft you may not see), 409 not_draft or decided (decided already) and claim_retired, 422 invalid with problems (a price outside its range, text over 400 characters, an expiry more than 365 days ahead).

Not possible yet#

  • Importing claims from a file; drafting from a source reads one tool's answer.
  • Giving Manage claims to a role or a team rather than to each person.
  • A claim's owner being told about an expiry while the workspace is closed between ticks: the notice goes at the next tick after it is due.