DOMA MANTRA · SAMPLE ONLY — NOT A BILL
Like a utility bill: what you signed up for, what you used, and what it earned you in trust.
Sample Business — Sample Town · Sample Month · Plan: Sample Apartment — 2-bedroom (size, not usage)
All numbers on this page are SAMPLES. No real Postgres data, no real business, no settled price. Pricing is not settled anywhere on this page.
Rent is size. Usage is metered separately — a small apartment can use a lot of electricity. Same here: tokens, calls, and texts are counted by what actually happened.
| What happened | Count | Cost index | Index units |
|---|---|---|---|
| 🔥 Live call — hottest, a person + a person, live | 12 | 100 | 1,200 |
| 💬 Text — important, immediate, kept as record | 38 | 25 | 950 |
| ✅ Appointment confirmed — a person said yes, it counts | 21 | 40 | 840 |
| 💬 Chat answer — answered from your knowledge, with a source | 64 | 10 | 640 |
| 🎤 Voice recognition — speech heard and written down, minutes | 47 min | 8 / min | 376 |
| 🔔 General reminder — has value, not a person on the line | 53 | 5 | 265 |
| Rent — apartment size | 1 mo | — | Sample only |
Sample usage total: 4,271 index units — index units, not dollars. The dollar rate, if any, is not settled and is not shown here.
Every billed event on a real bill has a recording, a transcript, and a validity verdict behind it. Never bill an unproven event. That is the ledger rule — and this mockup shows the shape, not the proof.
Every case runs the same states, good outcome or bad. Nothing disappears. The ruling, and the reason, stay on the record.
Received → Heard → Verified → Ruled → Resolved → Recorded
Branches: No answer · Repeat contact · Flagged for review · Handed off warm
Heard the case, checked the record, ruled in favor, refund/credit started, confirmation promised. Outcome: good. Trust moves up — a promise made, and kept, in public.
Same person called 15 times about the same case. Heard every time, checked every time, ruled on the record — not in favor, with the reason stated plainly. Trust is on both sides: the business must keep its promises, and repeat contact is counted, not hidden.
Sample cases only. Not Jersey Mike's, not any real business, not any real Doma data. The pattern is the point: a complete cycle, with an outcome, either way.
Trust has two qualities: intentions (you mean it, and you keep it under pressure) and competence (you can actually do it). High in one and low in the other is low trust. The Index is built from commitments you make to your own customers — kept, verified, and scored over time.
Sample Trust Index movement this month: ↑ up — sample direction only, no score is claimed. A real score needs real data, in Postgres, over time.
What you signed up for shapes what is measured: your apartment size, your channels (chat / voice / text), and your promises. The report shows only what your plan includes — nothing extra, nothing hidden.
1 · Hang it off your website, hosted with us. We modernize your site and hang the interaction center off it. No activity, no usage charge — you paid for the modernization and the analysis, and the meter only runs when interactions actually happen. We keep the record, we send the utility bill, and we help you build the Trust Index from it.
2 · Buy the analysis, take it home. If you want it, you can buy the analysis itself — the interaction diagram, and the details of how it works for your business — and house it on your own side, for example in your own Hugging Face space, and run it there. You keep track of your own interaction score. We don't keep it. You own the diagram, you own the record, on your side.
Showcase wording only. Neither option is an offer, and no price is stated. Whether the full inner detail of the model is handed over, and what “buy the analysis” includes, is still to be ruled — this page shows the choice, not the terms.
No price configuration is settled. This is the shape of the strategy, for you to rule — what a tier is made of, before any number is put on it:
| Tier driver | Sample bands | Why it matters |
|---|---|---|
| Modernization (one time) | Small site / larger site / multi-location | The build + analysis, paid once, before any usage. |
| Apartment size | 1-bed / 2-bed / 3-bed | Rent is size — how big the business is, not how much it uses. |
| Number of calls / interactions | Low / steady / high volume | Metered usage, by cost index — live calls hottest, reminders lowest. |
| Fleet size | 1 truck / small crew / large fleet | Mission Control grows with vehicles, crews, and territories. |
| Channels | Chat only / chat + voice / chat + voice + text | More doors in, more to answer, route, and record. |
Sample bands only. No dollar price, no rate, and no band boundary is settled. The strategy itself — which drivers, in which order — is owed, and nothing here is quoted to anyone.
How many interactions, in which states, at which cost index — and what they earned in trust. Which questions come up again and again, which promises are kept, where people get stuck, and what to fix first. That is the gauge: not a pile of clicks, but a picture of how your customers are actually being served.
Prototype only. When real data lands in Postgres, this same shape fills with real numbers — same states, same ledger rule, same utility-bill clarity. Until then, it wows with the shape, and claims nothing real.
🎼 We are not the musician. We are the conductor. · Sample mockup — not a bill, not a score, not a price.