Omni-channel messaging for Alpine Portal — SMS, RCS, WhatsApp, wallet billing, and reporting. 3-month delivery at ₹16,00,000 fixed investment.
2026-06-22
SMS, RCS & WhatsApp module development for the Alpine Portal admin panel.
This proposal outlines the design, development, integration, testing, and deployment of an omni-channel messaging system within the existing Alpine Portal admin panel — delivered in 3 months at a fixed investment of ₹16,00,000.
A unified, scalable messaging platform for outbound customer communication at scale.
Manage SMS, RCS, and WhatsApp campaigns from one system — consistent UI, shared contact groups, and unified reporting across channels.
RCS and WhatsApp template creation with approval status tracking. Only approved templates available for campaign sending.
Unified wallet with channel-wise debit, pre-send cost estimation, insufficient-balance blocking, transaction ledger, and low-balance alerts.
Dedicated staging environment for API integration, webhook testing, wallet validation, and client UAT before production deployment.
1000xDev builds systems that scale with your business. We combine modern web development with intelligent architecture to deliver platforms that grow with you—without constant rewrites.
We specialize in fintech, enterprise SaaS, and communication platforms. From MVPs to complex integrations, we move fast and build right.
System Uptime
Ontime delivery
Users Served
Projects Delivered
Architecture & Integration
Owns technical direction, Alpine Portal integration patterns, provider API design, code reviews, and cross-module quality.
Product & Delivery
Drives requirements clarity, sprint planning, UAT coordination, and stakeholder communication throughout the 3-month engagement.
2.5 FTE
Backend and frontend implementation across SMS, RCS, WhatsApp, wallet, and admin panel modules.
2.5 FTE
Channel integrations, webhook handling, campaign workflows, and reporting features.
2.5 FTE
Wallet billing, transaction ledger, RBAC, and cross-module integration work.
Quality Assurance
Test planning, staging validation, webhook and delivery-status testing, regression suites, and UAT support before production rollout.
From booking platforms to enterprise communication SaaS, we craft digital experiences that scale across India and beyond.
Three channels, three gateways — integrated into the Alpine Portal admin panel.
Each channel connects to its designated provider. API credentials are stored securely on the backend; webhooks are validated where supported.
SMS sending, Unicode SMS, personalized campaigns, DLR handling, and reports. DLT template selection, Sender ID/route selection, and delivery receipt tracking.
RCS template management, campaign broadcasting, delivery tracking, and reports. Bot ID selection, rich card templates, and approval status sync.
Meta Embedded Signup, WABA/number onboarding, template management, campaign sending, webhook handling, and delivery/read receipts.
Single wallet balance per customer account. Channel-wise debit on send, configurable pricing, transaction ledger, low-balance alerts, and reconciliation.
The engagement covers SMS, RCS, and WhatsApp modules, a unified wallet and billing system, cross-channel reporting, admin panel integration, a dedicated staging environment, and production deployment support after UAT sign-off.
Integrated with msgn.mtalkz.com for outbound SMS campaigns with DLT compliance and delivery tracking.
Karix RCS integration for template management, campaign broadcasting, and delivery tracking.
Meta Cloud API and agreed wrapper APIs for WhatsApp Business onboarding, templates, campaigns, and webhooks.
Unified wallet across SMS, RCS, and WhatsApp — implemented after core channel workflows so debit logic maps accurately to actual campaign flows.
Campaign-wise and recipient-level reports across all three channels.
All modules integrated into the existing Alpine Portal with consistent UI and access controls.
Dedicated staging deployment for development, testing, webhook validation, and client UAT.
Production deployment support after successful staging UAT and written sign-off.
Items not included unless separately agreed.
How administrators create campaigns, manage templates, and track delivery across channels.
Compose → select DLT template → upload contacts → send or schedule → track DLR.
Select Sender ID, route, DLT template, and compose message.
Manual entry, contact group, or CSV/XLSX upload.
Estimated cost validated; blocked if insufficient balance.
Instant or scheduled send. DLR statuses in reports.
Select Bot ID → approved template → broadcast → delivery tracking.
Choose approved RCS template and Bot ID.
Add recipients, preview, and schedule or launch.
Channel-wise debit on message send.
Campaign and number-level status in reports.
Onboard WABA → create/approve template → send campaign → webhook receipts.
Approved WhatsApp template selected for campaign.
Upload contacts or select group; configure campaign.
Template-based send with wallet debit.
Delivery and read receipts captured in reports.
Create template → submit for approval → track status → use only approved templates.
Admin defines type, Bot ID, content, media, and suggested actions.
Template submitted and status synchronized from provider.
Only templates in approved state are enabled for campaigns.
Approved template becomes selectable in broadcast workflow.
Meta signup → WABA and number onboarding → channel mapping in Alpine.
Admin starts Meta Embedded Signup from Alpine Portal.
WABA setup and phone number onboarding completed.
Customer account mapped to WhatsApp assets and channel ID.
WhatsApp channel available for template and campaign operations.
Create template → approval tracking → campaign eligibility.
Admin sets category, language, and header/body/footer/buttons.
Template status tracked as pending, approved, or rejected.
Rejected/pending templates are blocked from campaign send.
Approved templates are enabled for campaign activity creation.
Estimate cost → validate balance → debit on send → ledger and reconciliation.
System calculates expected campaign cost from channel pricing rules.
Wallet balance checked before campaign launch.
On successful send, channel-wise debit and transaction ledger entry created.
Delivery outcomes drive reconciliation and refund rules where applicable.
Prevent campaign launch when funds are not available.
Admin attempts to send a campaign.
Wallet amount is below required estimated campaign cost.
Campaign execution is stopped before dispatch.
Low-balance message shown so top-up/credit action can be taken.
Build and verify in staging before production release.
Modules and configs released to dedicated staging environment.
API, webhook, delivery status, and wallet logic tested end-to-end.
Client performs UAT and confirms readiness in writing.
Approved build deployed to production with handover support.
Analyze campaign outcomes and export recipient-level data.
Admin opens SMS/RCS/WhatsApp campaign reporting dashboard.
Filter by campaign, date range, status, or channel.
Review campaign summary and recipient-level delivery logs.
Download CSV/XLSX for operational analysis and reconciliation.
These flows represent the primary field operator journeys. All data is cloud-resident; the application is online-only and requires an active connection to function.
Month 1: Discovery, Staging & SMS
Weeks 1–4Month 2: RCS, WhatsApp & Wallet Foundation
Weeks 5–8Month 3: Wallet, QA, UAT & Production
Weeks 9–12A parallelized 3-month execution plan to deliver SMS, RCS, WhatsApp, wallet, and reporting within the client's 3–4 month window. Team allocation per month is detailed below.
Discovery, staging environment, and SMS module live on staging
RCS and WhatsApp modules on staging; wallet debit and ledger foundation
Wallet completion, cross-channel QA, client UAT, and production rollout
This phased plan is priced at a significant discount compared to our standard Time & Materials rates, reflecting our commitment to the April 1st launch and partnership approach.
This phased plan is designed for a 2-month baseline delivery to meet the April 1st launch date. If the project extends beyond Month 2 due to dependencies (PRD changes, third-party API access delays, feedback delays, or approval delays), both parties will conduct a scope review and Month 3+ will be negotiated based on remaining work. See the Terms & Conditions section for full extension policy details.
Fixed-price engagement of ₹16,00,000 over 3 months with milestone-based payments.
Key components included in the engagement
Investment spread across two delivery stages with milestone-based payments
Discovery
Timely access to these items keeps the 3-month timeline on track.
Access to existing Alpine Portal codebase for development and integration
Staging and production server access for deployment
Existing database structure and documentation for data model integration
API credentials for mTalkz (msgn.mtalkz.com), Karix, and Meta Cloud API
Provider API documentation for development and testing
DLT-approved SMS templates and Sender IDs for SMS testing and production
RCS Bot IDs and Karix account access for RCS testing and production
Meta Business Manager access and WhatsApp Business Account access
Wallet pricing rules for all channels (debit and reconciliation logic)
UAT participants and timely feedback — critical for 3-month delivery
Written sign-off process and production deployment window agreed upfront
Operational controls and client responsibilities for a safe production rollout.
The solution is developed with security and operational controls. Regulatory and provider-side approvals remain the client's responsibility.
API credentials are never exposed on the frontend. Provider credentials are stored securely in backend environment configuration.
The following regulatory and provider-side approvals are handled by the MTalkz team:
A dedicated staging deployment enables safe validation before production.
The project is accepted once all criteria below are met on staging, with written UAT sign-off:
