The AI is yours
The key, the model and the cap belong to your company. You set how much it can spend per day on the site — and you can switch the AI off without switching off the channel: the visitor then lands straight on the form.
New · Sales module The email that shows
The email that shows
where the conversation stands
Your team replies in Mesa, the agent desk. The lead gets an email put together on the spot: the state of the conversation at the top, the new message in the spotlight and the whole path, numbered. They reply to the email and the conversation carries on — no quote chain, no “see below”.
- The AI greets whoever arrives on your site
- The same Mesa as support
- Your own AI key, with a cap in R$
Sales comes in a plan like every other module: take it on its own or alongside Support and Projects — tickets and leads share one quota.
Sales · Berni Software
ERP integration — Interaction 4
Meeting set for Sep 24 at 3 p.m., with Ana
The new message
Ana, from Berni Software
Done, Marcos! I set it for Thursday at 3 p.m. and the invite is on its way. I will bring the migration case you asked for.
How we got here
- 1 Marcos · asked on the site whether the widget works in Delphi 7
- 2 Assistant · answered with the article from the knowledge base and offered to bring in the team
- 3 Marcos · asked for a call about the ERP integration
Reply Open the full conversation
Done with these emails? One click and we stop.
At the front door of your site Whoever arrives is welcomed,
Whoever arrives is welcomed,
not filed away
The bubble on your site opens with your assistant. It introduces itself, answers from your knowledge base and offers to bring in the team from the very first message.
Nothing before consent
No cookie, no IP, no browser fingerprint. Anything that identifies someone is stored only when the person hands it over, with the consent on record.
The queue in plain sight
Ask for a person and the visitor sees their place in the queue and how many people are ahead. Outside business hours, they find out right away.
Bots stay out
Proof of a human browser, invisible to real people, on the site widget and on the login code request. Whoever does not present the proof is refused: a direct call to our API, without the widget, stops at 403. If Cloudflare goes down, the request passes on purpose — we do not take your login down over a third party.
The conversation comes along
When they ask for the team, everything already said to the assistant arrives in Mesa with them. Nobody repeats the story — and every AI line is signed, so no one can paste in a promise it never made.
In your colors
Color, logo and name are your product’s. To the visitor, it is your site talking.
Possibilities Someone who only talked
Someone who only talked
tells a story too
Not every visitor wants to talk to a salesperson. What they asked the assistant becomes an anonymous record — the raw material for your next sales argument.
- Anonymous for real. No contact and no ID number: email, phone and CPF are stripped out of the text. From a work email, only the domain stays.
- What matters stays. Product, page, source campaign, the questions asked and how many times the AI offered the team.
- Short shelf life. It disappears on its own after 90 days.
- Split by intent. All, with contact, anonymous, turned into support, discarded.
Possibilities
01
Anonymous for real.
02
What matters stays.
03
Short shelf life.
04
Split by intent.
Ten people asking the same thing on the pricing page is a wording problem, not a salesperson problem.
How a lead is born Five ways in,
Five ways in,
no tedious form
The lead arrives ready: with the product, the source, the campaign and whatever the script decided.
- 1
Talking
After the first answer, the assistant asks for a name and a contact to carry on. If they agree, the lead is born right there.
- 2
Leave it, we call you
The visitor would rather be contacted later. They leave a contact with the consent and get on with their day.
- 3
I want to talk now
They ask for the team and join the Mesa queue, with the AI conversation attached.
- 4
It was support, it became a sale
Interest showed up in the middle of a ticket. One click moves it to Sales, and the customer notices nothing.
- 5
You record it
Came in through a referral, a trade show or a phone call? The team registers it on the Leads screen.
The script belongs to your product
- Up to six short questions, written by you, product by product
- Each answer decides the suggested plan, who takes it, the urgency and whether it is worth following up
- Simulate before publishing: see what the script would decide and what screening would say, without recording anything
- What the person answered stays on the record, in plain sight of whoever takes it
Screening Spam does not
Spam does not
wake your team up
Before any alert, whatever comes in goes through a sieve of rules — with no AI cost.
- Four kinds recognised. Spam, job applications, suppliers and competitors in disguise. Only high-certainty spam is archived silently; the other three land in Mesa with the Screening badge, for someone to decide.
- Nothing is deleted. What was turned away sits in Closed, with the reason. Got it wrong? One click brings it back as a lead.
- Doubt becomes a badge, not silence. A doubtful case enters Mesa with the Screening badge and no push — someone decides with one tap.
- The call is human. It is a lead, it was not a lead, it was a lead after all: the verdict of whoever is on it beats the rule.
Screening
4- Four kinds recognised.
- Nothing is deleted.
- Doubt becomes a badge, not silence.
- The call is human.
First reply The clock starts
The clock starts
when they write
Each product has its own first-reply target, by urgency. Miss it and bFocus does not email the team: it passes the turn on.
- 2 min
- for what is urgent
- 5 min
- for the normal
- 30 min
- for no rush
These times are the default and you adjust them per product. Miss it the first time and it goes to the next person in the rotation or the team is alerted again; miss it again and the area lead is called in.
- Closing means saying what comes next. Meeting set, call back, follow up, not interested or not a lead — with a date when that makes sense.
- Nothing is left hanging. What was agreed becomes the Next steps list, split into overdue, today and the coming days.
- The phone remembers. An alert 15 minutes before the appointment, on the phone of whoever is taking it.
- Did they write again? The lead reopens in the usual conversation, with the whole history attached.
On the same Mesa No second system,
No second system,
no second password
Leads and tickets live side by side in the Mesa your team already uses. What changes is what the screen asks for.
- One filter, two worlds. Everything, tickets or leads — with a Lead badge and a Screening badge in the queue.
- The right record beside it. Company, source, campaign, what the script decided and the visitor’s answers.
- Switch sides with one click. A ticket becomes a lead, a lead becomes a ticket, without losing the conversation.
- The company fills itself in. From a CNPJ or a work email, the legal name, industry, size, city and partners come from public sources — and what the person typed is never overwritten.
- On-call and rosters count the same. The sales queue uses the same on-call, the same presence and the same transfers as support.
On the same Mesa Leads Chamados
- lead One filter, two worlds.
- chamado The right record beside it.
- lead Switch sides with one click.
- chamado The company fills itself in.
The Leads screen Everything still open,
Everything still open,
with no side spreadsheet
The list lives next to Mesa. There is no funnel to drag: what moves a lead is what was agreed with them — and that is written on the record.
- Open
- Qualified
- Follow-up
- Closed
- Archived
- Mine
The record tells the whole story.
Contact, company, source and campaign, the script answers, what screening decided, the agreed next step and every conversation that person had.
Search and slices.
By name, contact, company or product — and “Mine” instantly separates yours from the team’s.
Manual entry, when the lead did not come from the site.
Referral, trade show, phone call: the team records it right there, with the same script and the same record.
Next steps in a single list.
Overdue, today and the coming days, mine or the team’s, with a reminder on the phone 15 minutes before the time.
Nothing is deleted.
Closing has a reason, archiving moves it out of the way without losing it, and whoever writes again reopens the same conversation.
Our biggest advantage Sales is not an island
Sales is not an island
— that is exactly why it works
Selling, supporting and delivering on the same base changes what each team sees. This is not an integration between systems: it is the same database, the same permissions and the same history.
-
The same Mesa and the same team.
Queue, on-call, presence, transfers and areas apply to leads and tickets alike. Having both modules adds a filter, not a second system.
-
The conversation switches sides, not addresses.
One click moves it from Sales to Support and back, with everything already said. The customer notices nothing, and a ticket that only existed because of it is cancelled with the reason.
-
The same record of people.
Whoever talks on your site becomes a person in the same registry support uses. If the contact already belongs to someone, the new person joins the possible-duplicates queue — nobody inherits someone else’s history by typing an email.
-
The same knowledge base.
The site assistant answers from the same per-product articles the support agent uses. You write once and it counts twice.
-
The same AI key, the same caps.
Site and support spend from your company’s account, with caps in reais per conversation, per user and per product — plus a separate cap just for what the AI answers on the site.
-
The ticket does not close before the delivery.
A ticket turned into a task stays locked until that task is done. When it is, Mesa gets the internal note and the nudge: reply to the customer and resolve it.
-
What you shipped becomes an answer.
Public release notes join the sources the AI searches. The site assistant and the support agent answer citing what has just gone out.
-
And the cycle closes.
The new customer’s ticket becomes a task in the sprint, the pull request links itself to that task and the release note tells everyone who has that product — with each acknowledgement on record.
That is why Sales was born inside bFocus, instead of being one more CRM to integrate later.
The right way Sell without pestering
Sell without pestering
and without stepping on the LGPD
Consent with the text and the date.
What the person read, in which language and where each piece of data came from stays on record — and it goes out in their data export.
One-click unsubscribe.
In the email footer and in Gmail itself. Whoever opts out receives nothing more from Sales.
A block list that keeps no contact.
We store only the fingerprint of the address, not the address.
Conversation page with no login.
The link in the email opens the whole conversation, numbered, with a reply box — and it expires.
What Sales does not do yet
Saying it now is cheaper for both of us than you finding out later.
- It does not issue proposals, quotes or contracts, and there is no e-signature.
- There is no deal value, revenue forecast, target or commission.
- There is no drag-and-drop pipeline: the lead moves by the next step your team agrees on.
- It does not run cadences, campaigns or mass sends.
- It does not capture leads through WhatsApp or the API, and it does not import a spreadsheet of leads.
- There is no sales dashboard, and the app does not show leads yet.
Questions about Sales
How do I sign up?
On the site, like any other module: on the pricing page you tick Sales (on its own or with Support and Projects), pick the size and subscribe. The 14-day trial includes all three, with no credit card. Tickets and leads share the same monthly quota.
Do I need AI to use it?
No. With no key on file, the bubble on your site opens straight on the form and the lead joins the queue all the same. With your key, the assistant answers first and you choose how much it can spend per day.
Does it work for teams already on Support?
It is the same Mesa, the same queue and the same on-call. Your team does not learn a new screen: it learns one more filter and one way of closing.
Is the visitor tracked?
No. Nothing that identifies anyone is stored before consent — no cookie, no IP, no browser fingerprint. Someone who only talks becomes an anonymous record that disappears after 90 days.
Do leads come in through WhatsApp?
Not yet. Today a lead is born in the widget on your site (by chatting, by leaving contact details or by asking for the team), in a ticket that becomes a lead, and in a manual entry. A reply by email continues an existing lead’s conversation — it does not create a new one. WhatsApp serves your customers, and that stays as it is.
Start with your site
The bubble that already answers questions starts bringing people in. Try 14 days with all three modules, no credit card.