Busy Accounting · Busy WhatsApp integration
Busy Accounting WhatsApp Integration
Choose which accounting documents to send and which account questions customers should be able to ask. An outbound invoice workflow and a customer-requested ledger menu need different triggers and permissions.
This guide describes workflows to scope with Whats91. Confirm the Busy version, enabled connector, sender and template eligibility, account access and plan terms before relying on any workflow. Sending a request does not activate an integration.
Illustrative workflow
Select the Busy record
Identify the company, customer, voucher or report and the fields needed for the task.
Map recipient and permission
Match the record to the intended recipient; decide who may request that account's information.
Prepare the message
Agree the trigger, template or reply format and any PDF attachment for the enabled setup.
Check the result
Handle rejected requests and delivery failures; route unresolved queries to the accounts team.
Outbound documents or an inbound menu?
Use an event or schedule for a business-initiated message. Use an authenticated account lookup for a customer question. A message accepted for sending is not proof that the recipient received or read it.
Document delivery
Scope invoice or receipt PDFs, recipient mapping, template variables, permission to contact and failure handling.
Customer requests
Scope balance, ledger or receipt options and the checks that bind a request to the correct customer account.
A menu built around accounting tasks
These are candidate menu actions, not a list enabled for every account. Confirm the source record and output for each option.
On a narrow screen, scroll the table horizontally to read every column.
| Action | Input to map | Output to scope |
|---|---|---|
| Check balance | Company and party ledger | Balance text with period or as-of context |
| Bill-by-bill ledger | Party, period and bill references | Debit/credit detail; PDF if configured |
| Last receipt | Selected receipt voucher | Receipt reference or PDF |
| Bilty status | Mapped transport record | Available bilty/dispatch fields |
| Download statement | Party and date range | Period statement PDF if configured |
| Talk to team | Unresolved question and routing context | Handoff to a designated accounts queue |
Separate data retrieval from messaging
The Busy API path explains the data contract. This page covers how an accounting record becomes a message or a menu reply. Agree whether the connector uses an event, polling or a snapshot; the freshness of a reply depends on that arrangement.
Choose the trigger and stop condition
Illustrative tasks include sending an invoice after an eligible entry, a receipt after reconciliation, an outstanding reminder on an agreed schedule, or a dispatch update when a mapped record changes. Stop reminders when the account is settled or disputed. A saved voucher alone does not confirm funds or delivery.
Reports and vouchers to discuss
Retain the distinction between a report over a period and a document for a transaction. Availability depends on the connector and your Busy data.
Reports
Outstanding/balance summary, bill-by-bill ledger, sales summary, stock and dispatch reports.
Vouchers
Sales invoice, receipt, payment voucher, credit/debit note and bilty/transport document.
Agree who can see each account
Confirm recipient verification, company/party access boundaries, credential handling, request logs and retention for the selected setup. Review messaging permission, template approval and opt-out handling. This workflow description does not certify controls or compliance.
Where this task fits
A distributor may need invoice and outstanding replies; a manufacturer may need dispatch documents; a transport business may need mapped bilty fields. These are hypothetical uses. They do not establish a customer result or support for every industry record.
Prepare a small integration scope
Bring the Busy version and export/connector access, company and party mappings, the intended WhatsApp number and an example document with private values removed. Agree the menu, recipient rules, test cases, exception owner and written launch terms. Setup time depends on those prerequisites.
Questions about Busy WhatsApp integration
Does this use WhatsApp Web automation?
The workflow discussed here uses the WhatsApp Business Platform path. Confirm the actual sender setup, enabled connector and permitted message formats for your account; the diagram does not establish approval or delivery.
Can a customer request a bill-by-bill ledger?
Scope a lookup using the authorized company, party and period. Confirm the available bill references, dates, debit/credit fields and PDF format with the connector before exposing the menu.
Does saving a receipt send it automatically?
Only an enabled and configured trigger could do that. Agree whether it runs on entry, synchronization or reconciled payment, and how failures and duplicate events are handled. No fixed delivery time is promised.
How do outbound templates and human handoff fit?
Check sender/template eligibility and permission to contact before outbound messaging. Define a human accounts destination for disputes, missing records and unsupported requests; unattended replies do not mean staffed support is available at all hours.
What data is stored?
Confirm the actual connector's storage, processing locations, logs, retention and provider responsibilities in the agreed setup. This guide does not establish a storage or privacy policy. Review the Privacy and Legal Center pages before sharing production data.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support and availability in your signed service agreement.
Discuss your Busy WhatsApp integration setup
An enquiry does not book an appointment or activate a product. Availability, setup, support and commercial terms need separate confirmation; binding commitments require a signed agreement.
Send an enquiry