Advanced Settings
The Configuration → Advanced page is where your number gets connected to WhatsApp, where you shape how the AI represents your business, and where the project-level controls that shouldn't be touched casually live. The sections below follow the page from top to bottom, so you can read this with the screen open next to you.
Most cards are admin-only: everyone on the team can look, but only project admins can save.
WhatsApp Provider
The first card decides how your number reaches Remo. There are two tiles:
| Provider | What It Means |
|---|---|
| Meta Cloud API | The official WhatsApp Business connection, and the way every new project connects. Set up in minutes with the Connect WhatsApp button. |
| WAHA | The original QR-code connection. It is now legacy — the tile is hidden on new projects and can't be chosen. Projects already running on WAHA keep working. |
Connecting With Meta
Choosing Meta Cloud API reveals a Connect WhatsApp button that opens Meta's own popup window. In roughly ten minutes you sign in with your Meta account, accept the terms, pick or create your business portfolio and WhatsApp Business Account, add and verify your number, and grant Remo access. Nothing is typed into Remo — the whole exchange happens inside Meta's window.
The default is Coexistence: your number stays live in the WhatsApp Business app on the phone while the bot also answers, so your team can keep using the handset exactly as before. The full walkthrough is in Connecting With Coexistence.
Right after a successful connection, and only once, Remo imports up to 180 days of previous conversations with their original timestamps, plus the phone's contacts. Imported history never triggers the bot — nobody gets messaged because their old conversation was pulled in.
A successful signup is confirmed by a short on-screen message and nothing more — there's no permanent "connected as +54 11…" badge on the page yet. Send a message to the number from your own phone if you want to be certain it's live.
If You're Still on WAHA
WAHA is deprecated: it still sends and receives, it keeps its QR screen (see WAHA Setup), and nothing breaks — but it isn't offered to new projects and it isn't gaining new capabilities. You can move to Meta whenever you're ready.
Switching provider preserves the credentials and sessions you already have, but you'll need to reconnect on the new side afterwards. A confirmation dialog spells out what to expect before anything changes.
Connection Details
The second card changes depending on which provider is active — WAHA connection on a QR project, Meta Cloud API credentials on a Meta one. You only ever see one of them.
WAHA Connection
When WAHA is the active provider, this card shows:
- Connection status — Connected or Not connected
- Connect with QR / Reconnect — generates a fresh QR code to scan from the phone whose number is being managed
- Disconnect — ends the WAHA session (handled by support in some builds)
If the session drops — the phone loses internet, say — Reconnect brings up a new QR.
Meta Cloud API Credentials
When Meta Cloud API is active, this card holds the technical values behind the connection. On a project connected with Connect WhatsApp you should never need to open it: the assisted signup fills it in for you.
Filling it in by hand is the legacy, assisted route — kept for connections made before Embedded Signup existed, or ones your Remo account manager sets up with you (the older step-by-step lives in Setting Up the WhatsApp Business API). The form holds the values Meta issues for your account: the access token, the verification token Meta echoes back when registering, and the identifiers for your business and your WhatsApp Business Account. There is nothing to invent here; if a value is missing, ask your account manager rather than guessing.
Two settings on the same card are ordinary configuration rather than credentials:
- Words per minute (TTS) — the pace used to simulate a natural speaking rhythm for voice replies
- Include scheduled meetings in AI system prompt — when on, the client's upcoming meetings are added to every prompt, so the bot doesn't offer an appointment they already have. It makes each reply slightly more expensive.
Once every value is present, the card shows Configured. From here you can also generate the default WhatsApp template set for every supported language in one click.
Members and agents see these values masked. Only project admins can edit them.
AI Service Credentials
The AI service credentials card holds the setup for the voice and AI services that power the assistant. This is business-level plumbing: an admin configures it once together with your Remo account manager, and there is nothing here for you to obtain, paste, or maintain day to day.
It is also not where you change how the bot behaves. Tone, knowledge, and what the bot is allowed to do live in AI System Prompts, Project Characteristics, and Routes & Capabilities. Think of this card as the power supply, not the steering wheel.
If the assistant has stopped replying and everything else on the page looks correct, this is the card to ask your account manager about.
Voice Agent
The Voice agent card turns on the spoken side of the assistant — voice notes, and outbound AI phone calls when a client asks to be called — behind an Enable voice calls toggle.
Like the card above it, this is business-level setup arranged with your Remo account manager, and editing it is admin-only. Once it's live, a client who sends a voice note can be answered with a voice note, and a client who asks to be phoned can be phoned.
Both directions cost credits on top of the usual reply, so keep an eye on Credits & Usage for the first few weeks. What the bot actually does with voice — and with photos, documents, and reactions — is covered in Voice Notes & AI Phone Calls.
AI System Prompts
The AI's voice, focus, and guardrails come from the prompts you write here. Each prompt is plain text — placeholders like the client name, the agent's name, and your business hours are injected automatically. You don't need to insert variables manually; just write the prompts naturally.
There are four prompt slots:
| Slot | What It Controls |
|---|---|
| Main system prompt | The AI's overall role, voice, and core knowledge about your business |
| Behavior prompt | Rules of engagement: what to focus on, what to avoid, how to handle edge cases |
| First-message prompt | How the bot greets a client the very first time they message — your chance to make a strong first impression |
| Follow-up prompt | How the bot phrases automated re-engagement messages |
Click Edit on any slot to open the prompt editor. The editor shows a character count and saves on click. Show more / Show less lets you preview a longer prompt without leaving the page.
Together with your project characteristics and your product catalog, these prompts are what genuinely shapes the answers a client receives.
The quality of these prompts is the single biggest lever you have over the bot's output. Be specific: company name, tone, what to recommend, what to redirect to a human. Short, vague prompts produce short, vague bots.
Routes & Capabilities
Routes & capabilities decides which actions the assistant is allowed to offer a client. Six toggles:
- Products & pricing — needs at least one product in your catalog
- Project images — needs at least one project photo
- Project PDFs — needs at least one project PDF
- Masterplans & floor plans — needs a masterplan file, or any project PDF
- Locations — needs at least one enabled address with a real value in it
- Meeting scheduling — controls the self-serve booking link; when it's off, booking requests are handed to a human agent instead
The rule worth memorising: a route is offered only when it is enabled here and has data behind it. A toggle on its own conjures nothing — an empty route hides itself and shows a No data badge, which is why the bot never promises a brochure that doesn't exist.
Editing routes is admin-only. The full explanation, including how to work out why the bot won't offer something you expected, is on Routes & Capabilities.
Project Characteristics
Characteristics are short, structured facts the AI can reference at any time — opening hours, locations, perks, parking, dress code, and so on.
In this card you can:
- Edit the project name (also shown in the topbar and project switcher)
- Edit the project description — a short summary the AI uses as background context
- Add characteristics — each is a
Titleplus aDescription(e.g., Office hours · Mon–Fri 9am–6pm) - Delete characteristics that are no longer accurate
Characteristics are easier to maintain than long prompts and are great for facts that change occasionally (phone numbers, rates, dates).
Campaign Detector
Campaign detection tags each new conversation with the marketing source that brought it in — Meta Ads, Google Analytics, or any keyword you configure.
- Enable campaign detection — a toggle that is not currently functional; detection is driven by the campaigns you sync below, not by this switch
- Meta Ads — connect your Meta Ads account and ad account ID, then click Sync Meta campaigns now
- Google Analytics — upload the service account file downloaded from Google Cloud
- Detected campaigns — the list of campaigns Remo has matched against incoming chats
Tagged conversations show their source in the chat list, and the analytics dashboard breaks performance down by campaign so you know which channel is actually generating leads.
The campaign detector labels the conversations that arrive; it never sends anything. Remo has no broadcast or blast feature at all — every outbound message is a reply, an automated follow-up, or something your team sends by hand.
Consolidate Clients
If your project has child projects that share a family, the Move all clients here action consolidates every client across the family into the current project. Use this when you've decided to merge several phases or sub-brands into a single workspace.
The action runs immediately and cannot be undone from the UI, so a confirmation dialog asks you to acknowledge before continuing.
High-Priority Alerts
High-priority alerts is where you define what "something is wrong" looks like for this project — a dead connection, a conversation nobody answered, a credit balance running down — and how loudly Remo should say so. Each alert has its own threshold, its own cooldown, and its own mix of push, email, and WhatsApp; Test fire proves the plumbing works before you need it, and Recent firings tells you whether an alert is a blip or a pattern. Alerts reach every member of the project, and nothing fires until you switch it on. The card is admin-only, and all ten alerts — plus advice on which two or three to start with — are covered on High-Priority Alerts.
Danger Zone
This card contains irreversible actions, gated behind a confirmation step where you have to type the project name to proceed.
Delete Project
Deleting a project permanently removes:
- Every chat and message
- Every contact
- The product catalog
- All training files and master plans
- Scheduling configuration
- Every team member and their assignments
This cannot be undone. If you're not sure, contact your account manager before clicking through.