Overview
Assigned to you
Since your last visit
Your engine
Conversion funnel
Recent Activity
Broadcast
Send an approved template to an audience via your WhatsApp Cloud API. Respects opt-out and your daily send cap (Settings → Spend & Budget). First time? Read the first-campaign guide →
Compose
Broadcasts
Contacts
Synced Contacts Explorer
In-page sync explorer with cursor streaming and scope-aware filters.
Recent Activity
Social
Pages & QR
Assets
Page Assets
View-link Actions
Discovery
Find a Collaborator
Enter another operator's collaboration WhatsApp number to find and invite them to your workspace.
Invites Received
My Workspace Members
Operators you have invited into your workspace.
Workspaces I Belong To
Workspaces where another operator has invited you.
Shared Contacts
Contacts that appear in both your network and a workspace member's network. Coordinate to avoid doubling up.
Activity Log
Trust & Credibility
Operator-reviewed trust signals and evidence-backed contact readiness for your synced contacts.
Portfolio
Projects, sites, matters: all your operational entities in one view.
Deals Pipeline
Visual sales pipeline linked directly to your WhatsApp conversations.
Connect
Import contacts from Google, Outlook, iCloud, or any file — they merge into your unified contact graph with names, emails, and provenance tracking.
Your sources
Add a source
- Phone normalization — country codes standardized, formatting stripped
- Deduplication — same phone from multiple sources merges into one contact (names, emails enriched)
- Source provenance — each contact tracks which source(s) it came from (badges in explorer)
- Contacts Explorer — imported contacts appear immediately with filtering, scoring, and segmentation
A small Google Apps Script runs in your Google account, reads your contacts via the People API, and pushes them here. No passwords stored — the script has native access.
- Click Generate Script below — it includes your API key
- Open script.google.com → New Project
- Click + next to "Services" → find People API → Add
- Delete placeholder code, paste the generated script
- Click Run → authorize when prompted
- Optional: Triggers (clock icon) → Add → Time-driven → Day timer for auto-sync
Recent activity
Connections & System Health
Manage active WhatsApp line status, messaging limits, and channel diagnostics.
Meta daily broadcast limits and account warmup status.
Continue normal sending pace.
Sync Meta Product Catalog for in-chat commerce.
Connection Details & Advanced Credentials ▾ Phone Number IDs, WABA IDs & System Tokens
For existing BSP migrations or Meta Business Manager setups holding permanent system user tokens.
whatsapp_business_messaging and whatsapp_business_management.
Developers
Named, scoped, independently revocable credentials for your integrations.
Each key works as a Bearer token on /api/v1/*.
Full OpenAPI 3.0 spec available at
/api/v1/openapi.json.
Authenticate with Authorization: Bearer uni_key_...
Settings
Authenticates your own backend against this workspace. Treat it like a password.
Replies to a contact's first-ever message.
Replies outside your business hours.
Reply when an inbound message matches a specific word or phrase.
Answers automatically, with no review, using your Business context — and only when the answer is fully covered by it. Anything else is left for a human; nothing is invented. Runs last, after any greeting, away or keyword rule has had its turn. Edit your Business context →
Turning this off hides that a message was read — customers still see delivered (grey ticks). It also disables the typing indicator, because Meta marks a message read as part of showing it.
Two rules about timing, not about content. Both start out following whatever this deployment was set up with, and either can be changed back to that at any time.
The ✨ button in your inbox drafts a reply for you to review — it never sends on its own. Tell it what your business is and it can answer real questions; leave this blank and every draft can only say a colleague will follow up.
This reads the same business profile customers see when they tap your name in WhatsApp — including its website. Fill or edit that profile → The richer it is, the better your drafts and the more a new contact trusts you.
Shows a translation alongside any inbound message that isn't in your language, and translates your replies into theirs. The original text is always what's kept in the thread and what a keyword rule matches against.
Assign specific numbers to a teammate (e.g. Sales, Support) — leave unassigned to give access to all numbers. You, the account owner, are always an admin.
+ Add a teammate
Automatically assign incoming conversations to available team members. Needs at least one teammate.
The WhatsApp number other operators use to find and invite you to workspace collaboration. Separate from your main WA session — use a number you designate for teaming. Leave it empty to stay undiscoverable.
Track conversation volume by billable category, and cap sends so a campaign can't blow your budget.
Meta's optimized marketing send path — it can reach a contact Meta has capped for regular marketing messages. Klaros cannot enroll your WhatsApp Business Account into it: that's a manual, irreversible step you take directly with Meta (App Dashboard, or during Embedded Signup). This only checks and shows the current status.
A complete export — contacts, conversations, messages, templates, sequences and configuration. Use it to migrate to your own self-deployed instance, or as a backup.
Requests permanent deletion of this account and all its data. Our team reviews every request and confirms with you before anything is removed.
Global Audit Log
A chronological record of automated system decisions, intelligence routing, and platform configuration changes.
Templates
WhatsApp message templates submitted to your Meta WABA for approval — required for business-initiated messages (outside the 24h window) and broadcasts.
Approval status
Template library
Ready-made templates for the scenarios every business hits — each locked to its honest Meta category and written to pass review. Personalize once (we remember it), tap the ones that fit, and watch the preview become your message before anything is submitted.
Generate with AI
Describe what you want to say and AI will draft 3 compliant template variants. Pick one, tweak it, then submit below.
Create & submit for approval
Flows
In-chat forms — booking, lead capture, feedback, support. A customer fills them out right inside WhatsApp; sent like any message from the Inbox.
Status
Flow library
Ready-made in-chat forms for booking, lead capture, feedback, and support. Personalize once, tap the ones that fit, and watch the preview update — nothing is created until you deploy.
Build a custom flow
Paste Flow JSON from Meta's own Flow Builder if the library doesn't cover what you need.
Meetings
Scheduled customer calls and outcomes. Proposed directly from the inbox via interactive buttons or parsed from free-text times.
Events
Run events on WhatsApp: a page people share, passes, reminders, the door, and what comes after.
Organisations and people
Set these up once and pick them on any event. Anything added while creating an event appears here too.
Organisations
Each keeps its own name, logo and colour for the events it runs. A joint event counts for every host.
People
Coordinators, volunteers, speakers, partners and observers. One person can work with several organisations in several roles. Nobody here needs a login.
Venues and regions
A registered venue puts a map link on every pass. Its region is what reports roll up by.
What attendees get, automatically
Cohorts
A cohort is a slice of the attendee list you can message in one go, or hand to a nurture sequence. Both go through the campaign queue, so consent, opt-outs and the spend cap all still apply.
Registration
What attendees receive
Every message this event sends, in the words people will read, in the order they get them.
For your team
Messages to co-organisers and task owners. These settings apply to all your events.
Team, tasks and activity
People
Run-sheet
What everyone did
Staff follow-ups
Registrants are credited to whoever owns them, check-ins to whoever scanned the pass, and needs to whoever sat down and recorded one.
Door
Arrivals as they happen, and who has not come yet. The scanner runs on a volunteer's phone and keeps working with no signal.
Results
Reports
The funnel from registered to arrived to asked-for-something, what they asked for, and what the event cost in messages.
Site visits
Geo-stamped check-ins. Ask someone where they are from the inbox; the reply lands here, measured against the site they were expected at.
Attendance
Pins received
Sites
A pin inside a site's radius reads as on site. Keep the radius generous: phone GPS is routinely 50-100m out, and a tight radius reports honest arrivals as off site.
Shift asks
Sends the check-in prompt automatically at a set time on chosen days. WhatsApp only allows a freeform prompt inside an open 24-hour window, so an ask to someone who hasn't messaged recently is recorded as skipped rather than sent.
Media
Files stored for your number — images, documents and other media you can attach to messages. Products moved to their own tab →
Stored media
Products
What you sell, what it costs, and where customers can buy it.
Commerce
Every cart a customer sends, and every payment request you send back, in one place — instead of a chat bubble no one can act on. Manage your products, prices & stock →
| Contact | Items | Total | Status | Received |
|---|---|---|---|---|
| Loading… | ||||
Maintenance plans, memberships, rentals and repairs — what customers still have with you after the sale.
Last 30 days. Read top to bottom: each row is a stage, and the gap to the next is who did not get there.
Last 30 days. Asked, paid and lost are separate on purpose: "asked 400, paid 2" and "asked 2, paid 2" are different situations, and a single conversion rate hides which one you have.
Connect your own Razorpay account and Klaros can generate a payment link per order for you. The money settles into your account. We never hold it, never route it, and take no cut, because we are not in the payment path at all. Leave this disconnected and everything still works: you paste your own link per order.
Add this webhook URL in Razorpay (events: payment_link.paid, payment.failed) and paste the secret you set there. Without it an order stays "Payment requested" even after your customer has paid.
Connect to see itWhatsApp's payment-request message (India, order_details) carries a payment link per order. With a gateway connected above, Klaros generates it. Without one, paste your own into the composer. This setting controls the abandoned-cart reminder.
Outside the 24-hour window, a customer who has opted in sees the products they left, straight from your catalogue. Everyone else gets a short plain reminder.
Savings
Behavior
Behavior-triggered WhatsApp, from your own backend: fire a milestone with one API call when a customer does something — places an order, completes KYC, finishes onboarding — and the matching rule sends the next-step template from your own number at Meta's raw price.
Milestone → template
One send per contact per rule; opted-out and suppressed contacts are never messaged.
Built-in milestone: opted_in fires automatically the first time a contact opts in — no API call needed. Define a rule on it (a delay of 30–60 min works well, so it lands after the instant welcome + cadence question) to start a welcome journey.
Integration snippet
curl -X POST https://YOUR-DEPLOYMENT/api/v1/milestones \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone":"919876543210","milestone":"order_placed","meta":{"orderId":"ORD-1042"}}'
Recent activity
Sequences
Automated follow-up sequences — time-based drips or reply-driven interactive flows.
Your sequences
Team
Add users to this workspace, set their role and team, and issue each a desktop key. You (the owner) see all data; each user sees only what they sync.
Add a user
Users
Costs
What Meta billed your WhatsApp account — straight from Meta, with zero Klaros markup.
What zero-markup saved you
Spend trend
—
Your ratecard
Your mix
Cost playbook
What each outcome costs
Where the spend goes
Where your messages land
What the assistant costs to run
Where chats and sales came from
Each sale counts once, for the most recent ad or link the person came through before buying, however long the conversation took.
Spend is Meta-authoritative (from Meta's conversation analytics), shown in your WhatsApp billing currency — Klaros never adds a markup. "Markup avoided" is an estimate against a typical reseller markup, not a Meta charge.
Services
Done-for-you services — we do the work, you approve the results.
Extensions
Activate a vertical pack to unlock operational intelligence: structured capture, portfolio tracking, silence detection, and auto-generated digests for your industry.
AI Sources
What the assistant reads before it answers. Connect your own content so replies come from it.
Compliance
Consent records, evidence export, and right-to-erasure — your audit surface.
Lookup & record
Consent evidence
Exports every opted-in contact with their consent evidence — the proof you'd show in an audit.



Occasions