Official SDKs in 7 languages and a native widget on 9 platforms — Delphi 7 and Lazarus included.
Your team answers from the phone: an app for iPhone, iPad and Android, with on-call and notifications you can reply to — and the same desk on Mac and Windows, on the way.
Meet the team appTickets, chat and an AI agent running on your company’s own AI key, wired to the team’s projects — inside your site and your apps.
No credit card · account live in 5 minutes · unlimited users; live chat agents depend on the plan
bFocus assistant
AI agent · answers with a source
Here the AI runs on Berni Software’s key. In your bFocus, the key is yours.
Website visitor · Chat
AI handling itNo human deadline while the AI is handling it
AI summary
The AI is leading. If it transfers, the summary shows up here.
Padaria Estrela · Widget
AI handling itTeams, customers and products come with every contract. Users are unlimited on every plan (only the number of live chat agents varies by plan) — the price follows the volume of work, not the size of your team.
Your AI greets whoever arrives on the site, and the lead is born with your product’s script.
Every channel in a single queue, with the deadline in sight, live chat and an AI agent.
What support uncovers becomes planned work, without switching tools.
You subscribe to the modules you want — one, two or all three — and the price follows the combination and the size. Users are unlimited on every plan, and tickets and leads share the same quota. Monitoring is not a fourth module: it is an add-on that stacks on top of any of them.
An error tool pages you and stops there. Here the error does not become an alert: it becomes work — and it comes back as an answer to the customer who hit it. The path from "the system broke" to "we told the people it reached" stops being walked by hand, across three tools.
A brand-new error files a draft bug task in the agent’s project, with where it blew up, the stack trace, the numbers and a priority suggested by severity and by how many customers were hit. The same error again does not open a second task: it only gets a comment at the milestones — 10, 100, 1,000 occurrences, every 5 new customers. Nobody reads a task that turns into spam.
A ticket opened by someone who hit an error in the last 30 minutes — or by anyone at the same customer in the last 2 hours — is born with an internal note tying ticket, error, task and probable cause together. The agent stops asking "what did the screen say?", because they already know.
Finishing the task resolves the error. An event from a newer version reopens the task on its own — "it is back in X". And once the fix ships in a version, the team decides to tell the people who were hit: an email in your company’s brand for each of them, and a note on every linked ticket. Nothing goes out unless someone sends it.
Where to install it
What it costs
On its own, with no other module: the cheapest front door we have. On top of the plan you already have it costs even less — there the base of the contract is already paid for.
What Monitoring is not: an observability tool. There is no distributed tracing, no performance profiling, no response-time charting. The ground here is one thing only — errors that become work, and work that comes back as an answer to the customer.
Your team’s app is already on the Apple and Microsoft stores — Android is next: reply, transfer and close conversations from every company you support, in a single list.
Where it runs
Our biggest advantage is not any single module: it is what happens when sales, support and projects live in the same database, on the same record of people and the same AI.
Your assistant greets them, answers from your knowledge base and offers to bring in the team.
SalesConsented contact, product, source and what the script decided — with the first-reply clock already running.
SalesSupport that turned into a sale? A sale that turned into support? One click switches sides in the same Mesa, and the conversation comes along.
MesaThrough the widget on the site or inside the app, already identified by your server’s signature.
WidgetIt answers citing the article. With no source, it transfers with the summary and the details it gathered.
AI agentWith the Monitoring add-on switched on, your system’s error arrives before the ticket does — grouped, with the customers it hit, and already a draft bug task in the right project.
MonitoringThe ticket lands in the right project, and a theme that keeps coming back becomes backlog.
ProjectsThe task key in the branch name or in the PR connects GitHub to the work.
GitHubYour pipeline writes the release note through the API, per product and per version.
APIThe customer sees "New" inside the system they already use every day — and the report shows, customer by customer, who read it.
Release notesIn other tools, each of these steps lives in a different system — and your customer tells the story again in every one of them.
Your key, your model, your depth and your cap in reais. We never charge per resolution and we do not mark up tokens.
Your key
OpenAI, Anthropic, Google, DeepSeek, Mistral, xAI, DO Gradient or any compatible URL. The key belongs to your company, and it leaves whenever your company wants.
Your model
bFocus lists the models your key can reach and recommends one. Switching to a cheaper or a stronger one is a single click.
Your depth
Per product. Assisted suggests replies to the agent; autonomous talks to the customer and transfers when it has no source. Turning it off is a legitimate option.
Your limit
Per conversation, per user per day and per product per month, converted at the Central Bank PTAX rate and blocked before it overruns.
How the market charges
How bFocus does it
No exceptions: even semantic search in the knowledge base runs on your company’s key (OpenAI, Google, Mistral or DO Gradient). With a key that doesn’t build an index, such as Anthropic’s, search keeps working on words. Market prices checked in September 2026.
Two layers. In your customer’s app, the native widget. On your server, the SDKs that keep the records in sync: customer, people, who uses which product and each version’s release note go in under the id your system already uses — and repeating a call duplicates nothing.
In your customer’s app
On your server
<!-- before </body> --> <script> (function (w, d) { w.bFocusQueue = w.bFocusQueue || []; w.bFocus = w.bFocus || { init: function(o){ w.bFocusQueue.push(['init', o]); } }; var s = d.createElement('script'); s.async = true; s.src = 'https://widget.bfocus.com.br/v1/widget.js'; s.setAttribute('data-bf-key', 'bf_pk_…'); d.head.appendChild(s); })(window, document); bFocus.init({ user: { externalId: 'USR-123', name: 'João Silva' }, customer: { externalId: 'EMP-456', name: 'Empresa Ltda' }, userHash: '…' // signed on YOUR server }); </script>
Support widget — already live
# pubspec.yaml dependencies: bfocus_widget: ^0.1.0 import 'package:bfocus_widget/bfocus_widget.dart'; await BFocus.init(BFocusConfig( publishableKey: 'bf_pk_…', user: BFocusUser(externalId: u.id, name: u.nome), customer: BFocusCustomer(externalId: u.empresaId), userHashProvider: () => minhaApi.bfocusUserHash(), navigatorKey: navigatorKey, ));
bfocus_widget package 0.1.0 — on pub.dev
$ npm install @bfocus/sdk import { Bfocus } from "@bfocus/sdk"; const bf = new Bfocus({ apiKey: process.env.BFOCUS_API_KEY! }); // creates or updates by the id in YOUR system const cliente = await bf.customers.upsert("ERP 1042", { name: "Padaria Estrela", email: "[email protected]", });
@bfocus/sdk 0.2.5 — on npm
$ pip install bfocus import os from bfocus import Bfocus bf = Bfocus(os.environ["BFOCUS_API_KEY"]) cliente = bf.customers.upsert("ERP 1042", name="Padaria Estrela") print(cliente["id"])
bfocus package 0.2.5 — on PyPI
$ composer require bfocus/bfocus <?php require __DIR__ . '/vendor/autoload.php'; $bf = new \Bfocus\Bfocus(getenv('BFOCUS_API_KEY')); $cliente = $bf->customers->upsert('ERP 1042', [ 'name' => 'Padaria Estrela', ]);
bfocus/bfocus package 0.2.5 — on Packagist
Things a foreign help desk will not do for you.
Brazil’s consumer-service deadline (Decree 11,034) goes into the queue maths: the ticket heats up before the deadline is missed, not after.
The on-call roster flags a workday over 10 h, less than 11 h between shifts and weekly rest under 35 h.
The admin exports the data of anyone who uses the widget, and every export is recorded with who did it and when.
Caps are set in R$, converted at the Central Bank PTAX rate. No in-house credits, no account in dollars.
App, widget, emails and this site in all three languages, written to the same standard.
Your company name as the sender and your own footer. The customer replies to the email and the reply lands on the right ticket.
Sprints, Kanban with your own columns and recurring tasks — always with the ticket it came from one click away.
Sprint 24 · Product
8 tasks · 3 days left
BFO-142
Resend the invoice through the portal
BFO-145
Export report as XLSX
BFO-138
Filter the queue by product
BFO-131
Release note badge in the customer’s app
Identity signed by your server, roles and departments in the app, and a record of what was done and by whom.
Your server signs who the user is and which company they belong to, and the signature lasts 7 days. With verified identity turned on, an unsigned session does not get in — and a widget created today starts with it already on.
Publishable key in the browser, server key with scopes, IP allowlist and revocation at any time.
Approvals confirmed by code, release-note acknowledgment per customer and a history of what changed.
Pick the modules and the size: those two answers set the price. Users are unlimited on every plan, and there is a single quota — a ticket and a lead count the same. WhatsApp is contracted separately, with our partner bZapper, and the AI runs on your company’s key: neither is part of the monthly fee.
Monitoring adds on top of a plan with Projects, at your plan’s size: errors from your system arrive as work items on the board.
Chamados, chat ao vivo, Mesa e agente de IA
O lead nasce na porta do seu site, com a sua IA
Kanban, sprints, tarefas recorrentes e GitHub
includes Monitoring + R$ 23
Chamados, chat ao vivo, Mesa e agente de IA
O lead nasce na porta do seu site, com a sua IA
Kanban, sprints, tarefas recorrentes e GitHub
includes Monitoring + R$ 71
O lead nasce na porta do seu site, com a sua IA
Kanban, sprints, tarefas recorrentes e GitHub
includes Monitoring + R$ 199
Chamados, chat ao vivo, Mesa e agente de IA
Quem vende e atende, sem time de produto
Capta e entrega, sem suporte contínuo
includes Monitoring + R$ 23
Quem desenvolve e atende o que desenvolveu
includes Monitoring + R$ 23
Capta e entrega, sem suporte contínuo
includes Monitoring + R$ 71
Quem vende e atende, sem time de produto
Quem desenvolve e atende o que desenvolveu
includes Monitoring + R$ 71
Capta e entrega, sem suporte contínuo
includes Monitoring + R$ 199
Quem vende e atende, sem time de produto
Quem desenvolve e atende o que desenvolveu
includes Monitoring + R$ 199
Do lead ao release note, na mesma base
includes Monitoring + R$ 23
Do lead ao release note, na mesma base
includes Monitoring + R$ 71
Do lead ao release note, na mesma base
includes Monitoring + R$ 199
Pick at least one module to see the price.
Os três módulos, para conhecer sem prazo
Volume combinado, SLA contratual e implantação acompanhada
You do, straight to the provider. bFocus does not supply AI: your company brings its own key (OpenAI, Anthropic, Google, DeepSeek, Mistral, xAI and others), picks the model and sets spending caps in reais per conversation, per user and per product. We never charge per resolution and never mark up tokens.
No. Users are unlimited on every plan; what varies by plan is the number of live chat agents. The price follows the volume of work, not the size of your team.
Yes: 14 days with all three modules and no credit card. Live chat and WhatsApp are enabled by our team. When the trial ends you subscribe to a plan or move to the free one, as long as your account usage fits its limits. If you do neither, the account keeps working for 3 more days and is then suspended.
A ticket and a lead count the same, against one quota — that is why the plan says “tickets/leads per month”. It covers tickets opened on any channel (widget, chat, email, WhatsApp or phone) and leads born on your site or entered by your team. Replies and comments do not count, and a chat conversation becomes a single ticket. WhatsApp conversations count here, but the number’s plan is contracted separately, at bZapper.
Nothing coming from your customer is blocked: tickets through the widget, chat, email or WhatsApp always come in, and so do leads from your site. What stops above the quota is your team opening tickets manually inside the app, until you move up a plan or the month turns over. The month’s usage is shown in the subscription area.
On DigitalOcean infrastructure, with a managed database and backups. Processing follows the Brazilian data protection law (LGPD), and the security page details what is collected, for how long, and how to export or delete it.
Live account in 5 minutes. No credit card. Cancel whenever you want.