One WhatsApp number doesn't scale. One dashboard does.

Multiple numbers and multiple agents working together, with department queues, automatic routing, an after-hours bot, bulk campaigns and live supervision — and nobody has to hand their phone to a coworker.

Cloud or on your own server Multi-company API and webhooks
WppManager · Waiting queue
WppManager waiting queue, split by department

The problem

WhatsApp became the main channel — and it's still handled like a personal phone

Messages nobody saw, customers who told their story three times, an agent who went on vacation with the conversation on their phone. None of this is a lack of effort: it's a lack of tools.

“Who's handling this customer?”
Department queues with a live counter and wait time.
“He already told the other agent.”
Transfers carry the history along — the customer repeats nothing.
“It came in at 10 p.m. and nobody answered.”
Self-service bot and automatic after-hours message.
“How's the team doing today?”
Live monitor, agent ranking and satisfaction survey.

What's inside

Customer service, automation and campaigns in one place

Conversation hub

Multiple open conversations, text, images, video, audio, PDFs and stickers, several files at once. Shared view by department, mentions when a customer calls an agent by name, logged calls and a "replied from phone" badge.

Queues and routing

Queues by department and automatic distribution to the least busy agent. Agents pick up and reply in a pop-up without leaving the queue, and chats in the wrong department move to the right queue in bulk.

Transfers with history

Hand the conversation to another agent or another number, with a reason, accept or decline, real-time notification and a full log.

Self-service bot

The flow is shown as a flowchart: each step is a block and the connectors show where each option leads. Our team builds and tunes it; you follow and test it. Runs 24/7.

Bulk campaigns

Text, images, video or PDFs with variables. Scheduled, recurring ("every Monday at 8 a.m.") or as a sequence, with sent, delivered, read and replied reports per person.

Monitoring and supervision

Instances, agents and conversations live. Productivity ranking, auditable history and a 1-to-5-star satisfaction survey.

Tidy contacts

CSV import with column mapping, tags, duplicate detection and merging, and creating a contact straight from the conversation.

AI that helps, not invents

An agent with its own knowledge base, reply suggestions when the agent asks for them, profile and urgency reading, a summary for opening a ticket and classification of campaign replies. When the answer isn't in the base, it hands off to a person.

API, webhooks and PWA

Per-company API token to send messages and check results, webhooks, and installation as a phone app with push notifications. Chats, queue, supervision, calendar and bot all work on a phone.

A channel that drops and comes back on its own

When a number's connection drops, the system tries to reconnect on its own, at spaced intervals. Only when it gives up does the alert appear — and it blocks anyone working on that number. The worst case isn't the channel going down: it's an agent spending the afternoon replying without knowing nothing is going out. And the manager gets a WhatsApp alert when the queue stalls or a number goes down.

Supervision

You see the team at work, not yesterday's report

Each open conversation is a card, showing who's handling it, which department and how long the customer has been waiting — with the latest messages right there, no need to open it. It's the entire operation on one screen, as it happens. When the wait goes past what's acceptable, the card turns red: you don't have to look for the problem, it shows up.

  • Filter by agent, by channel or by who has been waiting the longest.
  • From the card itself you can transfer the conversation or take it over.
  • The Overview tab sums up the day: conversations, queue, SLA, average time and the timeline with each agent's status — the same status that drives routing.
  • Productivity ranking and a complete, auditable history of closed conversations.
  • Nudge: one click sends a note to the agent, which pops up on their screen with a sound; a badge shows whether they've seen it.
  • Counters for customer waiting, waiting on the customer and stalled for over 24 hours: no chat sits forgotten holding a slot.
/admin/supervisao
Real-time conversations tab in WppManager supervision: counters for customer waiting, waiting on the customer and stalled for over 24 hours, filters by agent and channel, and open chats as cards with time stalled and the latest messages
Bot

We build your bot. You see the design and test it.

The flow is shown as a flowchart: each step is a block colored by what it does — menu, transfer, AI agent, action — and arrows show where each customer choice leads. Our team builds and tunes the flow with you; in the dashboard you follow the design, the list of steps and how each one performs.

  • Action blocks talk to CdAdm and deliver the document in the chat.
  • AI agent blocks answer from the company's knowledge base.
  • Transfer blocks choose the receiving department.
  • Input and condition blocks ask something and change the path based on the answer — the city decides whether the appointment is in person or online.
  • Switch between flowchart and list view when the flow gets large.

And you can test it before customers see it. The Test button opens a chat with the flow right there, just as a customer would talk to it — nothing is sent to anyone. If something isn't the way you want, we adjust it before it goes live, instead of you finding the mistake with a real customer.

A clinic's bot flow as a flowchart, with menu, input, condition, transfer and action blocks linked by arrows; next to it, the test panel shows the bot replying with the menu to book, reschedule or cancel an appointment
Bot flow · flowchart and live test
Bot Monitor: counters for conversations in progress, abandoned, handled by the bot, transferred and closed, and the list showing where each conversation stopped
Bot Monitor · where each conversation stopped
AI agent

An AI that would rather hand off to a human than make up an answer

You enter your company's information into a knowledge base — hours, payment methods, policies, FAQs. Each block is indexed when saved, and the agent answers from there.

If the information isn't in the knowledge base, the AI doesn't improvise: it hands off to an agent. That's a design choice, not a side effect — and it's what separates a useful assistant from one that makes up prices and deadlines on behalf of your company.

  • The AI reads the whole conversation, not just the last few messages.
  • After N replies without resolution (you set the number), it hands off to a person instead of insisting.
  • The Bot Monitor shows what was resolved and what was transferred, and where in the flow each conversation stopped.
  • More than one AI provider configured, to reduce outages.
Appointment window in the WppManager calendar: an 80-minute first consultation, confirmed, Tuesday at 9:00, with source WhatsApp (bot); below, the rescheduling block with a new date, a new time, a notice that no slots are free that day, and the buttons to cancel, mark as no-show and mark as completed
Calendar · the appointment the bot booked, open in the dashboard
Calendar

The bot books on WhatsApp — and you stay in charge from the dashboard

Notice the small line in the screenshot: source: WhatsApp (bot). Nobody at the clinic typed that time. The client chatted on her usual WhatsApp — no app, no portal, no password — picked "first consultation", and the appointment was created confirmed, taking the 80 minutes that service lasts rather than a generic one-hour block.

From the same screen, the front desk handles the rest: reschedule, cancel, and record whether the patient was a no-show or the appointment was completed — which is what turns no-shows into numbers instead of memories.

  • When you change the date, the dashboard immediately shows which times are open that day — including "no free slots this day" when that's the case. It's the same math the bot uses: the schedule, minus blocked times, minus what's already booked.
  • "Fit it in anyway" ignores the schedule, blocks and booked slots. The system warns that it doesn't fit, but you make the call.
  • One calendar per professional, not one for the whole company: each with their own schedule, their own services and their own Google Calendar — the appointment shows up there automatically.
  • Booked directly in Google? That slot drops out of what the bot offers — the two sides sync both ways.
  • Minimum notice, maximum booking window and buffer between appointments are your rules. The bot's messages are edited in the dashboard, not in code.
  • Attendance confirmation: the bot asks whether the customer is coming, as far ahead as you choose, and a no frees the slot right away.
  • Services with variations ("haircut" → men's, kids'…) and who provides each one.

Free slots are calculated inside WppManager itself, not in Google. That's why the answer is instant — and why booking keeps working even if the Google API is down.

/admin/campanhas
WppManager campaigns screen
Campaigns

Sending with control — not with crossed fingers

Hourly limit, interval between messages, automatic text variations and batch-by-batch tracking. You see who received it, who read it, who replied and who stayed silent.

  • Select by tag, by group expanded into members, or by CSV.
  • Variables such as {{nome}} and {{empresa}} in the message.
  • Duplicate a campaign and export the results to CSV.
  • Person-by-person report, with errors in plain language ("Number has no WhatsApp", "channel disconnected").

And the system works to keep your number from being restricted. Anyone who has sent in bulk knows the risk isn't the message failing to go out — it's WhatsApp restricting the number afterward. That's why the safeguards aren't optional settings hidden on an advanced screen:

  • New numbers start slow. The daily cap rises with the number of days connected, instead of the first send going to your entire list.
  • Automatic brake. If messages start failing in a row, the campaign pauses itself and alerts you — instead of pushing on until the number is restricted.
  • Resend only to those who failed. Without touching those who already received it, which is exactly what turns a resend into spam.
  • Preview of who will receive it, with the option to remove contacts before sending — and an explicit warning when you choose to send to everyone again.
Recurring and sequences

The campaign that repeats itself, and the one that delivers one piece a day

Recurring: "every Monday at 8 a.m.", "on the 1st of every month", "every 15 days". Each round becomes a campaign with its own report, and with tags the list is live: whoever joined the group this week gets it, whoever left stops getting it. Nothing goes out on holidays or outside the number's business hours.

Sequence: each contact gets the content for their day. Someone who joined today gets day 1 and someone who joined a month ago gets day 30, in the same send. Use it for courses, follow-ups, onboarding and after-sales, and you can offer a free sample: when the person buys, they pick up where they left off.

/admin/recorrencias
New recurring campaign screen: message, channel, frequency, weekday, time, option to skip holidays and audience by tag

Real screens

The dashboard, actually running

Screenshots from the demo company: fictitious conversations, contacts and phone numbers. Click to enlarge.

Integration

Conversations that don't die in the chat

WppManager isn't an island. It asks CdAdm who's on the line, returns the document in the chat and logs the record in ScWork — without anyone typing anything twice.

How WppManager exchanges data with CdAdm and ScWork WppManager asks CdAdm who the number on the line belongs to and gets back the bank slip (boleto), invoice, PIX (Brazilian instant payment), pending items, owner payout and the VIP Area link. To ScWork it sends the lead with the suggested product, the ticket and the time spent on the conversation; and it receives campaign sends from ScWork. CdAdm also sends bank slips, owner payouts and invoices in bulk through WppManager, and the delivered and read confirmation flows back to the CdAdm grid. Below, the conversation with the customer on WhatsApp. CdAdm leases · finance portfolio · owner payouts WppManager bot · queue · service campaigns · supervision your company's WhatsApp ScWork CRM · help desk tasks · campaigns whose number is this? boleto · invoice · PIX pending items · payout · VIP Area lead · ticket · time WhatsApp campaign boleto · payout · invoice sent in bulk, through WppManager delivered · read flows back to the CdAdm grid Your customer on their usual WhatsApp The customer asks for a copy of the bill at 10 p.m. on a Sunday — and gets it with nobody on the other end. The next month, billing goes out in bulk — and the grid shows who read it.

How it works under the hood: the platform connects your numbers by QR code or pairing code, just like WhatsApp Web. Talk to us about volume and usage policy before planning large sends — we explain the limits frankly instead of promising unlimited sending.

Want to see it with your own numbers?

Build the scenario with us — how many numbers, how many agents — and get a firm quote, with no fine print. No lock-in contract and no cancellation fee, as with everything we sell.

Prefer to read it at your own pace or show it to your business partner? Download the PDF overview (in Portuguese) (8 pages, 1.4 MB).