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

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.
• Multiple AI providers chained — if one goes down or runs out of quota, the next one takes over.

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.

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.

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.

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.