Broadcasts know your inbox. Flows know your catalog. Templates know your analytics. Click any card for the full breakdown — what it does, how it works, who it's for.
Kanban, SLA timers, routing rules, presence, internal notes, playbook macros, AI agents — built for teams that reply.
Multi-recipient one-time. Sent/delivered/opened/clicked tracked per contact.
Sheets, Docs, appointments, catalog, AI responder — describe it in English, AI builds the graph.
A/B variants, random assignment, AI copy generation. Start/pause/resume lifecycle, bulk delete drafts.
Standard, carousel, auth. AI generation. Multi-language. Approve/refresh status.
Levenshtein typo tolerance. Multi-language with auto-translate. Reply with text · template · flow · catalog.
5-step wizard. AI copy from brief. Targeting, scheduling, sync from Meta ad account.
OpenAI · Anthropic · Gemini · Mistral · ElevenLabs. RAG knowledge base from PDF/DOCX/URL.
Meta catalog sync. SPM / MPM / carousel. Custom domain, themed storefront, orders + payment links.
Slot picker via Calendar. Auto Meet link. Customer-tz conversion. Cancel/reschedule.
Embed an AI chatbot. Custom colors, greeting, linked assistant. Per-IP rate limit.
Single/multi choice, short/long text. Push to Meta Flows API. Submissions tracked.
Custom slugs · pre-filled message · per-link click analytics. Use anywhere.
Mix engines per workspace. Embedded signup, OAuth, or scan a QR.
OAuth, order webhooks, contact sync, Sheets/Docs/Forms/Calendar. Apps Script ingest.
Daily / weekly / monthly / cron. Pause/resume, retry failed, run-now.
Outbound dial. Inbound toast with accept/reject. WebRTC SDP. AI voicemail fallback. 3-way recording with transcript playback.
2FA · IP allowlist · lockout · WA guardrails · scam patterns · abuse filters · webhook signatures · device trust · audit log.
Most platforms ship features that never meet each other. A broadcast tool that can't see the inbox. Flows that don't know the catalog. Templates without analytics. We built features that share the same workspace — broadcasts read replies, flows enrol carts, analytics tag every send.
Tag a VIP in inbox · broadcasts respect it · flows route it · analytics segment it. One source of truth, twelve consumers.
Drop a payment node into a flow. Embed a template in a broadcast. Pipe an inbox reply to a webhook. No connectors. No middleware.
Whether you ship one feature or all twelve, your bill is the same shape. No upgrade nags. No per-agent fees. Ever.
A production WhatsApp system should prove the basics first: provider configuration, webhook delivery, inbox routing, template status, queue workers, and safe AI behavior before high-volume sending.
Still unsure? Email team@dptalkflow.com — a real human replies inside 4 hours.
Plan access depends on how the administrator configures packages. Core WhatsApp operations can be available on entry plans, while AI, calling, integrations, limits and provider options may vary by package.
Absolutely. Many customers start with just broadcasts + inbox. The other features sit dormant until you need them — no bloat in the UI, no nag emails.
AI features use the provider keys configured by the platform admin or the workspace. Review your selected AI provider terms before enabling AI for customer conversations.
All ship together on a single platform release. We deploy weekly. Every feature shares the same data layer, design system, and API.
Yes, but migration scope depends on your export files and provider access. Contacts and templates are usually easier than message history, automations and provider-specific metadata.
Create a test workspace, connect one number, send test messages, receive replies in the inbox, then enable automation and AI only after the base sending flow is stable.
Start with one connected number, verify your sending flow, then add automation and AI when your workspace is ready.