WhatsApp in the Mesa desk
The customer writes to your company's WhatsApp and the conversation lands in Mesa, in the same queue as the widget, chat and email. It works for one-to-one chats and for the customer's group, through our partner bZapper.
Integrations It talks to what
It talks to what
your company already uses
No "universal connector" that never quite works. There are only a few integrations, all maintained by us, and each one solves a concrete part of the day: your customer's WhatsApp, email, your product, the code and the alert.
- WhatsApp in the same Mesa queue
- Scoped keys you can revoke
- Step-by-step guide in the app
What already connects Seven points of contact,
Seven points of contact,
all maintained by us
Each one with a guide in the app and a state that is actually checked.
An inbound address per company, the customer reply landing in the same ticket, and outgoing email with your company name as the sender and your own footer.
Widgets on your site and in your app
The support widget and the release notes widget run on your site and, with the native packages, inside your app — iOS, Android, Flutter, React Native, .NET, Delphi, Lazarus, Java and Python. Your page says who is there, from which company, for which product and, if you want, that person’s role in the product.
API and SDKs
Customers, people, contacts, extra identifiers, products, knowledge base and release notes through the API, with scoped keys and batch loads. You read and test your AI agents with the same key. Open-source SDKs in Node, Python, PHP, .NET, Java, Go and Ruby.
GitHub
The link belongs to the organization, not to one person. The pull request attaches to the task by its key in the branch, the title or the body; a branch created from the task starts out linked. The PR status shows up on the card.
Error capture from your system
With the Monitoring add-on, nine packages send your system’s errors here — browser, Node, Python, PHP, .NET, Java, Go, React Native and Flutter. The error arrives grouped and scrubbed, becomes a task in Projects and shows up on the ticket of whoever hit it. The repository can be on GitHub, GitLab, Bitbucket, Azure DevOps or Gitea, so the investigation can read the code of the version that broke.
Push notification
In your apps, push goes out through the credential of your own Firebase project — it arrives as your notification, not ours.
An integration that does not exist does not show up on this page.
WhatsApp in Mesa Customers write where they already are,
Customers write where they already are,
your team answers in Mesa
WhatsApp is one more path into the same queue. The conversation gets a protocol number, a deadline, history in the customer dossier and the same service as every other channel.
- One-to-one chats and the customer's group: in the group, your company's AI asks before it registers anything, naming everyone tagged in the message — unless someone tags the assistant with @ or asks for a person from your team, and then it goes straight ahead
- "No, thanks" and nothing is created. With no answer, the question expires quietly after 30 minutes
- With a "yes", the AI uses what the message already brought — the text, the screenshot, the person tagged — and asks at most two questions
- "Open a ticket for @John" registers it right away, already assigned. Automatic assignment only happens when the owner is unambiguous, and the tags become names in the ticket, not numbers
- Unknown number? The assistant asks for the email on file and sends a code to that address — whoever types the code proves they are the customer
- The phone says who the person is. Someone linked to a single company goes straight through; someone who moves between several picks which one they are writing for, the latest one first — the company is what decides the product, the assistant and the knowledge base that answer
- On arrival and after the product menu, the message already carries the queue position. Whoever writes while waiting gets "You're still in the queue — position N", at most every 10 minutes
- The assistant answers first and hands over to the right person, with a summary of what was said
- At the end, the customer gives a score from 1 to 5, which goes to the ticket
- Your team replies from Mesa, with the agent's name at the top of the message
Through our partner bZapper
WhatsApp in Mesa works through bZapper, our WhatsApp partner. We enable the channel for your company; you sign up for the WhatsApp account and plan on bZapper itself, right from the bFocus connection screen.
Meet bZapper How you connect it Guided inside the app,
Guided inside the app,
not through a support ticket
The Integrations Hub walks you through each one and checks the real state: whether the key has been used, whether the email arrived, whether the channel is on.
- Each integration has its own guide, with what to copy and where to paste it
- The state is actually verified, not ticked off by hand by you
- Separate keys: the public one goes in the browser, the server one stays in your backend
- The secret key never goes to the browser. When your front end needs the data, your company’s backend is the one that calls the API
- Immediate revocation and a record of the last use of each key
- The widget can declare the role of whoever is there (role), alongside the product: a role that does not exist is created and linked, and the SDKs sync the roles on every deploy. It is a statement that guides the AI agent and targets internal release notes, never a permission — what the person gets to see is still decided by bFocus
- Support mailboxes that forward to bFocus, with the sender checked
- A record of who created each key and connection
Verified identity
For the widgets and the SDKs, your server signs who the user is and which company they belong to. The signature lasts 7 days; with verified identity on, a session without a signature does not get in — and a widget created today starts with it already on.
Questions about integrations
Do you charge per integration?
No. bFocus has no activation fee and no per-connector charge. The one separate bill is WhatsApp, which works through our partner bZapper: you sign up for the number's plan there (bzapper.com.br).
Does WhatsApp have its own queue and rules?
No. A WhatsApp conversation enters the same Mesa queue, with the same assistant, the same deadline and the same closing as the chat on your site. Your team does not learn a new screen.
Do I need a developer to connect this?
For email, WhatsApp and the widget on your site, no: you copy an address, scan a QR code or paste one line. GitHub, push, the API and verified identity do need someone from tech.
What if I use another tool that is not listed here?
The API keeps customers, contacts and products in step with your system, and the specification is generated from the code itself. If an operation is missing, write to us: the list of what is missing guides what we build.
Did the Teams integration ship?
The meetings module is turned off and has no date. We would rather say that than keep a button that does nothing.
Connect what you already use
Create your account and turn on the first integration today — the guide in the app does the rest.