Separate workspaces
Each company and each leader workspace has its own data, settings, languages and keys. Nothing from one customer is ever copied into another.
Security
OneBot is built so that each person sees only what their role allows, the history cannot be quietly changed, and payment for your plan never depends on a key stored on our servers.
Each company and each leader workspace has its own data, settings, languages and keys. Nothing from one customer is ever copied into another.
Members see only their own cases, leaders their team, admins the organisation. Enforced in the database with row-level security.
Two-factor sign-in, account approval and team roles in the CRM.
Recorded chat messages cannot be edited or deleted, so the conversation history can be trusted.
API keys are hashed or encrypted and never sent to the browser. The site runs under a strict Content-Security-Policy.
Block visitors from countries where you do not operate, and publish your own risk text.
OneBot's own payment system receives your plan payments without holding the keys that could move the money.
The server only derives and watches payment addresses. It cannot move funds. Keys stay offline with the owner.
Your plan is extended only from confirmed on-chain transfers, never from anything a browser sends.
A daily reconciliation compares every payment in our books with the blockchain and alerts on any difference.
If a paid period ends without payment, your public site pauses and visitors see a neutral page that does not mention payment. Nothing is deleted. Your team can still sign in to see the billing screen, and the service switches back on by itself within a minute of the payment confirming. Data is deleted 90 days after the period ends, after several warnings.
A 30-minute demo on a live instance, then a 60-day company pilot or a 14-day leader trial.
Questions? Ask the assistant.
Hello. I am OneBot's AI assistant. Ask me anything about the product, plans or billing.