Send an ERP document
Check: Document fields, authorised recipient and connector.
Plan for: Missing or stale data; failed document delivery.
Explore campaigns, ERP documents and customer request flows with Whats91. Start with one task: sending an invoice, answering a ledger request or routing a conversation to your team.
Confirm the features enabled for your account, integration prerequisites and written terms before launch. Meta's hosted messaging API does not establish Whats91's provider designation or host every connected ERP workflow.
A request sends an enquiry; it does not schedule an appointment or activate an account.
Explore invoice, ledger and reminder workflows for Busy Accounting.
Explore Busy integrationPrepare your audience, opt-ins and template review before sending.
Explore campaign workflowsMap a request to a reply, system lookup or human handoff.
Explore Flow BuilderUse Meta INR rates effective 1 October 2026; keep platform terms separate.
Open cost calculatorExplore the messaging and integration paths below. Confirm the enabled features, dependencies and permissions for your account.
Reach
Prepare the audience, message purpose and template. Review account conditions and delivery signals; response and conversion depend on your audience and offer.
Automate
Explore triggers, conditions and actions in Flow Builder. Confirm the available nodes, connected systems and permissions, then plan the exception path when a request needs a person.
Illustrative workflow with sample content. This is not a product screenshot, customer result or confirmation of account access.
Illustrative workflow with sample content. This is not a product screenshot, customer result or confirmation of account access.
Integrate
Explore how an ERP document or authorised customer request can move through a connector and a WhatsApp workflow. Confirm the source fields, sync schedule, hosting and failure handling for your setup.
Check: Document fields, authorised recipient and connector.
Plan for: Missing or stale data; failed document delivery.
Check: Trigger, permissions, lookup and reply.
Plan for: Unknown request; route to a human.
Check: Opt-in audience, template review and account conditions.
Plan for: Rejections, opt-outs and delivery failures.
Explore ERP, commerce and spreadsheet integrations alongside AI assistant paths. Confirm product support and account eligibility for the integration you need.
Explore product MCP access on the MCP page. Public website content is available through whats91.com/api/mcp — a read-only content catalogue, not an executable tool gateway.
The messaging API, your accounting system and any connector have separate dependencies. Confirm who runs each part.
Confirm your number, account eligibility and onboarding route. Verification, display name and template decisions depend on the provider review.
Identify the ERP or CRM fields, connector, hosting and permissions. Agree on setup work and schedule before changing a live system.
Test the intended reply, document or campaign path and its exceptions. Review the pilot before expanding to more recipients or actions.
For Developers
Building on a custom CRM? Define the events, field mapping, permissions and failure handling before wiring a webhook to your systems. The illustration shows a possible ledger-request path, not a live event stream.
Check the Graph API version, event types and enabled account features for your integration.
Confirm signature checks, credential handling, retries and failure logging for the receiving service.
Review the documented endpoint contract and changelog; confirm current limits and behaviour for the intended flow.
Illustrative workflow with sample content. This is not a product screenshot, customer result or confirmation of account access.
Text
Simple text inquiries
Interactive
Buttons & lists
Location
GPS coordinates
Media
Images & documents
Free Tools
Prepare message quantities, explore your own lead assumptions, or create a contact link and QR code. A calculator scenario is not a promised business result.
Effective 1 October 2026
Illustrative workflow with sample content. This is not a product screenshot, customer result or confirmation of account access. Illustrative October 2026 India budget: 1,000 Marketing deliveries at ₹0.8631 and 1,000 Utility deliveries at ₹0.1150; no prior monthly paid tier volume. Meta delivery subtotal ₹978.10. Platform fees and taxes are separate. Whats91 Coexistence platform subscription ₹699/month or ₹5,000/year, before 18% GST. Monthly billing has a ₹1,000 one-time setup fee; annual setup is included. Meta delivery charges are separate. Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate.
Review the published policies and confirm the controls that apply to your setup. This page does not certify compliance, residency or a particular security control.
Define how your team records opt-ins, handles opt-outs and limits each message to its intended purpose.
Review acceptable useConfirm processing roles, providers, locations, retention and the process for customer data-rights requests.
Read the privacy noticeAsk for the controls that apply to your service: credentials, access, logs, backup, incident reporting and recovery responsibilities.
Read the security statementAgree on the audience, baseline, measurement period and exceptions. Customer scale, campaign benchmarks and ROI figures are not established here.
Before the pilot
Record the opted-in audience and current response baseline.
What to compare
Compare delivered messages, available read signals, replies and useful actions for the same audience and period.
Before the pilot
Record how staff handle invoice and ledger requests today.
What to compare
Measure completed requests, exceptions and staff time after the agreed workflow is configured.
Before the pilot
Record the due accounts and existing follow-up process.
What to compare
Compare payment timing and manual follow-ups for the agreed cohort; account for other collection activity.
Outcomes depend on your data, audience, configuration and other business activity. Discuss a pilot scope.
Whats91 is a WhatsApp Cloud API platform for Indian businesses exploring campaigns, ERP document workflows and customer conversation automation. Confirm the features, integrations and plan scope available to your account before launch.
Meta hosts the WhatsApp Cloud API messaging service. An ERP integration can also depend on accounting software, a connector, customer systems and a chosen inbox. Confirm where each part runs, its permissions and what happens when it is offline.
Choose one workflow, such as an invoice PDF or ledger request. Confirm the Busy version, document fields, connector, data freshness, recipient permissions and exception handling. Ask for a demonstration of that scope before agreeing to rollout.
Map the customer request, required data, reply and human handoff. Confirm enabled triggers and actions, permissions, failures and the support process. An illustrated flow does not establish live access or unattended availability.
Confirm staffed support channels and hours in your written offer. A binding uptime percentage, response target or service credit applies only when stated in a signed order, proposal or enterprise SLA.
Review the privacy and security statements, then confirm your processing roles, providers, locations, retention, access controls and data-rights process. These pages and workflow illustrations do not certify compliance or a particular security control.
Effective 1 October 2026; original INR billing card, per delivered message. This future schedule is not the price for messages delivered before 1 October 2026. Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate. Use the cost calculator for category volumes, remaining Service allowance and confirmed free-entry exclusions.
Tell us the task, your accounting or CRM system and the exceptions your team handles. Confirm feasibility, account eligibility and written terms before rollout.
A demo request is an enquiry, not a scheduled appointment or account activation. Support hours and any SLA need written confirmation.