About
Build the platform once. Onboard by configuring it.
A clinic, a salon, a repair shop and a shop selling kurtas are all served by one schema and one code path. What differs between them is configuration — never a branch in the software, and never a custom deployment.
Why it is built this way
The rule everything else follows
Most software sold to small businesses starts as one business’s software and is generalised afterwards. It never quite works: the assumptions of the first customer are still in there, and the tenth customer gets an option that exists because somebody needed it in 2023.
This is built the other way round. There is no doctor, no stylist, no technician and no table anywhere in the domain — those words are banned from the code by a check that fails the build. What exists instead is capabilities, and a business switches on the ones it needs.
The practical consequence is the thing this whole website is about: a business we have never seen before is set up by answering questions, and taking one job rather than all of them is a real starting point rather than a trial.
Where it is up to
What is built, and what is early
This table is generated from the same registry that decides the badge next to every claim on this site, so it cannot say something different from the page you read it on.
- voice.inboundWorkingAny figure for answer time, accuracy, uptime or call quality. None is measured on a real carrier account in this repository.
- booking.schedulingWorkingThat the AI decides who is free. Duration, buffers, staff eligibility, resources and timezone belong to the booking engine, and the database refuses an overlap whatever a model proposed.
- voice.outboundWorkingThat customers are called automatically. A seller approves a batch before any number is dialled (packages/application/src/outbound-contact).
- voice.selectionWorkingMigration 0049 (voice catalogue) and ADR-0023: one resolution seam, the selection names the supplier that minted it, and what actually spoke is recorded.
- voice.languagesWorkingA count of languages. The list is provider-dependent and is not fixed in this repository.
- voice.hoursWorkingMigration 0037 (contact policy); the calling-hours screen; a customer’s own preference outranks the business default.
- whatsapp.outboundEarly accessThat live production WhatsApp is generally available. The transport is built and tested against Meta’s documented API; it has not been proven on a live business account in this repository.
- whatsapp.inboundEarly accessThat the AI replies to inbound WhatsApp messages on its own, or that there is a shared team inbox. Neither exists: an inbound message is recorded, and the product says so on its own Messages screen.
- orders.confirmationWorkingMigrations 0036 (confirmation snapshot) and 0045 (confirmation response); thirteen derived statuses on the confirmations board; approval precedes any contact.
- orders.approvalWorkingThe confirm-batch preflight runs the same gate the call itself faces, so the screen and the dialler cannot disagree. Importing never contacts anybody.
- orders.importWorkingpackages/application/src/csv-import.ts and csv-execute.ts: every row lands in exactly one bucket, the buckets add up to the file, and failures come back with the reason attached.
- shopifySetup requiredThat connecting a shop starts calling customers. An imported or webhook-delivered order waits for approval like every other one.
- telephony.numberSetup requiredThat a number is issued instantly in every country. Provisioning through a supplier API is proven against the mock; the first real supplier declares numberProvisioning: false until somebody has bought one on a real account.
- handoffWorkingADR-0010 and ADR-0011: routing evaluations are persisted and explainable, and a policy whose final step is not a task or a call-back is rejected when the blueprint compiles.
- knowledgeWorkingADR-0020 (Company Intelligence) and ADR-0018: PostgreSQL full-text retrieval behind a port, structured facts, versions and approval.
- automationsWorkingThat there is a drag-and-drop workflow builder. There is not, by decision (ADR-0013), and one is listed as post-launch.
- walletWorkingAuto-recharge. It is built (migration 0081: UPI Autopay / card e-mandate with a pre-debit notice) but has never collected against a live bank mandate, so it is not advertised until it has.
- tenancyWorkingAny certification — SOC 2, ISO 27001, HIPAA, or a compliance claim of any kind. None has been undertaken.
- pricingWorkingA plan or tier name — Starter, Growth, Business, Enterprise. A tier is a commercial commitment about what is bundled with what, and none has been approved. Also: auto-recharge, included minutes, or any bundle. There are none, by decision.
How we talk about it
No logos. No quotes. No numbers we made up.
We are not going to show you a wall of customer logos we do not have, or a testimonial nobody said. What is here instead is a set of decisions you can check inside the product on your first afternoon — before you have paid for anything, and without asking us.
- Every claim on this page is something the product does today
- Anything not yet proven on a live account is labelled early access
- No certification is claimed, because none has been undertaken
- Every figure of usage or performance is absent, because none has been measured
If you find something on this site that is not true of the product, tell us at info@capturo.in and we will change it.
Give your business an AI employee.
Start with one job. Add more when you need them. Nothing goes live until you say so.
Or talk to a person first.