Agency playbook
Kommo agency playbook: add WhatsApp, AI, and calls for your clients (and bill for it)
Kommo implementation agencies can install Waply in each client’s Kommo account to deliver official WhatsApp Cloud API messaging, human WhatsApp calls with recording, call intelligence, and independent text/voice AI — then charge for setup, training, and ongoing optimization. Use the client’s own Kommo and Meta accounts (never shared agency credentials). Choose new number, Coexistence (messaging only), or migration before you promise calls. Upsell in layers: messaging → human calls + recording → text AI → Voice AI. Waply plans are USD 18 / 39 / 89; agency fees on top are yours to define — Waply does not publish a partner margin program on the site.
LatAm and global Kommo implementers already sell CRM rollout, pipelines, and WhatsApp inbox setup. Soft-word competitor pages often promise “official partner” packaging; what many clients still lack is Calling API, recording in the lead, and AI that is not limited to Kommo’s native agent. Waply’s /solutions/agencies/ page and agency-client-setup docs cover the product posture — this playbook is the SEO/AEO delivery guide for agencies that want to productize it.
Free 3-day trial with everything in Voice AI — run it on the client’s account.
Why Kommo agencies add Waply
Your clients already bought Kommo for conversational sales. They still ask for WhatsApp that feels complete: team inbox, human calls from the CRM, recordings and summaries on the lead, and AI that can text — or answer calls — without burning opaque native credits alone.
- Official Meta Cloud API only (no grey QR session connectors).
- Human WhatsApp calls on eligible platform-only numbers, with recording on Waply infrastructure (no automatic announcement).
- Independent AI on third-party models — not Kommo’s native AI agent — for text and Voice AI.
- Same clear public plans your client can verify on waply.online/pricing.
Soft-word: many LatAm implementer sites market “Kommo + WhatsApp Cloud API” packages. Treat those as market context, not as Waply partners or pricing benchmarks.
Client-owned accounts (non-negotiable)
Waply’s agency-client-setup docs are explicit: install with the client’s accounts and approvals, and hand over verification for the contracted scope. Do not replace their credentials with shared agency logins.
- Confirm the client controls Kommo, Meta Business Portfolio, the phone number, payment methods, and any BYOK AI keys.
- Install Waply with an authorized client admin present and document the onboarding path you chose.
- Test messaging, calls, AI, and billing against the purchased scope, then hand over support guidance.
If the agency owns the Meta asset “for convenience,” renewals, number quality, and offboarding become your liability. Keep ownership with the client from day one.
Number path: new, Coexistence, or migration
Before you quote “WhatsApp + calls,” lock the number strategy. Selling Calling API on a coexistence number creates a support ticket you cannot fix in product.
Agency decision table (Sept 2026)
| Path | Sell messaging? | Sell WhatsApp Calling API? | Agency note |
|---|---|---|---|
| New / platform-only number | Yes | Yes, if Meta eligibility + Calling enabled | Best when the client wants CRM calls, recording, Voice AI |
| Coexistence (Business app + Cloud API) | Yes (1:1 messaging sync) | No (Meta: Calling API not supported on coexistence-onboarded numbers) | Keep the phone app; do not promise CRM calls on that number |
| Migration from another BSP / prior Kommo path | Yes after cutover | Possible after a successful platform-only migrate (eligibility still applies) | Do not disconnect early; test send/receive before killing the old host |
- Outbound WhatsApp calls require prior permission from the contact (product rule).
- Recording lives on Waply infrastructure; Waply does not play an automatic recording announcement — clients remain responsible for local consent rules.
- Retention: Basic 90 days; AI 24/7 and Voice AI 365 days. Transcripts and summaries land on the Kommo lead timeline when call intelligence applies.
Upsell ladder: messaging → calls → text AI → Voice AI
Most agency deals start with “get WhatsApp working in Kommo.” Expand only when the number path and team process support the next layer.
Layer 1 — Official messaging (often Basic)
- Cloud API inbox in Kommo, templates, routing.
- Clarify Meta conversation pricing (separate from Waply) and use the calculator when the client asks “how much per message.”
Layer 2 — Human calls + recording (Basic+)
- Requires an eligible platform-only number — not coexistence.
- Sell QA, coaching, and dispute coverage: recording + timeline context.
- Point product deep-dives to the calls product page (and the call-recording guide once published on main).
Layer 3 — Text AI + call intelligence (AI 24/7)
- Independent message AI and call intelligence allowances — not Kommo native AI credits.
- Use the Waply vs Kommo AI guide when the client already pays for Kommo’s agent and wants a fair comparison.
Layer 4 — Voice AI on WhatsApp calls (Voice AI)
- Answer and qualify WhatsApp calls with Voice AI; log outcomes in Kommo.
- Honest limit: Voice AI cannot transfer to a human agent yet — design handoff via callback, message, or human take-back after the AI call ends.
Packaging and monetization (illustrative)
Waply publishes three public subscription plans. Agencies typically bill their own implementation and care fees on top. Soft-word only: the examples below are packaging ideas, not an official Waply partner price list.
Waply plans (USD, verified in packages/shared plans + waply.online/pricing)
| Plan | Monthly | Agency angle |
|---|---|---|
| Basic | USD 18 | Messaging + human calls/recording (90-day retention) — strong entry SKU |
| AI 24/7 | USD 39 | Text AI + call intelligence (365-day retention) — when the client wants automation without Voice AI yet |
| Voice AI | USD 89 | Managed/BYOK voice agents + higher call-intelligence allowance — premium delivery tier |
- Illustrative agency packaging (soft-word): one-time onboarding (number path + install + tests), a monthly optimization retainer, and optional training workshops — priced by your market, not by Waply.
- Meta message/call charges and BYOK model usage are billed separately when applicable — spell that out in the SOW.
- No fabricated reseller discount, revenue share, or “partner SKU” appears on Waply’s public docs as of this guide; if Fernando publishes one later, update this section.
3-day trial includes everything in Voice AI. Monthly allowances apply to every billing period. Six-month and yearly prices are charged as a single total (see pricing page).
Delivery checklist
Use this as the visible HowTo for a standard client launch. Adapt scope to the SOW; do not skip ownership checks.
- Sign scope: number path (new / coexistence / migration), plan tier, and whether calls/AI are in phase 1.
- Verify client admin access to Kommo + Meta; install Waply in the client’s Kommo account.
- Connect the WhatsApp number on the agreed path; wait until status is connected.
- Run acceptance tests: inbound/outbound messaging; human call + recording if in scope; AI behaviors if in scope.
- Train the client team, hand over docs/billing contacts, and schedule a 30-day optimization review.
Frequently asked questions
How do agencies install Waply for a client?
With an authorized client Kommo admin present: install Waply from the Kommo marketplace/install flow, connect WhatsApp on the agreed number path, configure the plan features in scope, and run messaging/calls/AI acceptance tests. Follow docs/agency-client-setup.
Should the agency or the client own the Meta and Kommo accounts?
The client. Waply’s agency docs say to use the client’s accounts and approvals and not to replace their credentials with shared agency credentials.
Can we keep Coexistence and still sell WhatsApp calls in the CRM?
You can sell Cloud API messaging with Coexistence. Meta does not enable WhatsApp Calling API on coexistence-onboarded numbers. For CRM calls, recording, or Voice AI on calls, plan an eligible platform-only number.
When should we upsell calls vs text AI vs Voice AI?
Calls/recording after the number is platform-only and the team will actually dial from Kommo. Text AI/call intelligence when message volume or coaching needs automation (AI 24/7). Voice AI when the client wants AI to answer WhatsApp calls — with the limit that transfer to a human is not available yet.
What are Waply’s plans?
Basic USD 18/month, AI 24/7 USD 39/month, Voice AI USD 89/month (verified in Waply plans source of truth). Meta and BYOK charges are separate when applicable. Free 3-day trial includes Voice AI.
Is there an official Waply partner or reseller program?
Not as a published partner margin or reseller SKU on waply.online as of this guide. Agencies use the same public plans and bill their own services. Soft-word any future program only after it is documented.
Does Voice AI transfer to a human agent?
Not yet. Design handoff via callback, WhatsApp message, or a human continuing after the AI call ends. See the Voice AI agent guide.
Where is the delivery checklist?
In the Delivery checklist section above and in docs/agency-client-setup. Cross-link connect-whatsapp-kommo and whatsapp-calls-kommo for number and calling deep-dives.
Productize WhatsApp for your Kommo clients
Own the number decision, install on the client’s accounts, and upsell calls and AI only when the path supports them. Waply gives you an official Cloud API stack with human calls, recording, and independent AI — with public plans your clients can verify. Start with a 3-day Voice AI trial on the client account.
Free 3-day trial with everything in Voice AI — run it on the client’s account.