Per-contact, per-channel, per-purpose consent receipts (channel + purpose + timestamp + Ed25519 signature) stored in the audit hash chain. Required for full DPDPA 2023 §6 compliance for promotional sends. A contact's email opt-in does NOT cover WhatsApp promotional sends — each channel needs an independent receipt. AiSensy / WATI / WebEngage leave DPDPA compliance entirely to the customer; tapestree will store receipts natively. The view is roadmap — DPDPA consent capture at opt-in form level is a live control; the structured per-contact log with DSR export is post-v2.

Extend ERP-native journey triggers beyond the 4 live event types (invoice overdue, deal created, contract renewal, trial sign-up) to the full behavioral signal catalog: page-visit score changes, product usage drops, GLI-anomaly, payroll variance, sentiment shifts from WA replies. The current 4 ERP triggers are live MVP. The full behavioral catalog requires a dedicated signal-processing pipeline and is a post-v2 capability. Klaviyo has ecommerce-only triggers; tapestree's ERP + comms data advantage grows with the catalog.

Generate campaign copy in all 23 supported platform locales (en, hi, ta, ar, ur, fr, es, ja, ko, zh-Hans, zh-Hant, and 12 Indian scripts) from a single English brief via Gemma 4 26B model-router. MVP delivers en/hi/ta samples for UI preview. Full 23-locale production generation with ICU MessageFormat enforcement, per-locale compliance review, and RTL (ar/ur) template rendering requires the multilingual-catalog pipeline to be complete. Braze ContentCards charges ₹50k+/mo for comparable multilingual AI; tapestree will bundle this. ADR 3NNN required before build begins.

Distinguish campaigns that originated a deal from those that accelerated close velocity — using a causal inference model on deal timeline + marketing touch sequence. Per-deal granular ₹ attribution from GL-posted revenue (not just CRM deals). Journey-level totals (₹ 38L, ₹ 14L, etc.) are ERP-closed-loop today; per-deal decomposition with causal ML is post-v2. Marketo Measure (Adobe) is the benchmark; tapestree's ERP-closed-loop data makes the causal signal stronger than any standalone attribution tool.

Run 3, 4, or more simultaneous message variants across WA and email — statistical multi-arm bandit auto-selects the winner and pauses underperformers mid-send. Braze and MoEngage lead here at enterprise pricing; tapestree delivers this at SMB scale once the campaign volume supports significance thresholds.

Describe your campaign in a single brief — "re-engage hospitality CFOs who haven't opened in 60 days with a WA-first journey and hand off MQLs to Aanya" — and tapAdvisor constructs the full journey, drafts copy in selected locales, assigns segments, and schedules. Benchmark: Braze BrazeAI Operator (Apr 2026, $50k+/yr). tapestree equivalent at SMB price via model-router ai.reason.* + Temporal workflow.

Surface contacts at elevated churn probability — incorporating billing arrears, CRM inactivity, product usage signal, and NPS trend — into an auto-updating high-risk segment that triggers a re-engagement journey automatically. Klaviyo recovers 12–18% more at-risk customers vs time-based triggers; tapestree's signal is richer because it includes GL and payroll data.

Upload your highest-value closed-deal profiles to Meta Ads and Google Ads lookalike APIs to expand into new audiences that mirror your best customers — without leaving tapestree's campaign console. Braze and Salesforce Marketing Cloud offer this at enterprise; requires Meta Ads API integration separate from the WhatsApp channel.

Extend campaign reach to tapestree's Flutter mobile app (in-app push) and web shell (web push) — triggered from the same journey builder that runs WA/email/SMS today. MoEngage and Braze treat these as core channels. The notification-service is wired; the marketing-side campaign trigger is not yet exposed.

Full TRAI DLT entity registration wizard, sender header management, template pre-approval tracking, DND suppression list management, and 2025 opt-out suffix enforcement — as a guided in-app workflow. Currently a status panel showing existing DLT data; the full registration-and-management flow is post-v2.

Track partner-sourced leads, referral codes, and affiliate commission tiers from campaign click through to GL-posted revenue — extending the attribution model to the partner channel. Overlaps with CRM partner module; scope-change ADR required before any build begins.