Communication
Email & SMS
Custom integration — assessment requiredDesign notifications with a clear sender and outcome.
Explore data & scopeCommunication · WhatsAppCustom integration — assessment required
Scope business messaging around a clear customer workflow.
Assess authorised WhatsApp business messaging for your operational needs. Registry entries do not establish a live SalesTOS WhatsApp sender. Account access, message permissions and provider requirements must be reviewed.
WhatsAppAuthorised source / destination
01
Approved recipient detailsSalesTOS → messaging service
02
Message requestSalesTOS → provider
03
Delivery outcomesProvider → SalesTOS
SalesTOSCandidate business communication
Record ownership and direction are defined below. No universal two-way sync is implied.
The operational need
Why connect these systems?
Teams need a defined sender rather than scattered personal accounts.
Customer communication must have an authorised purpose and recipient.
Message status should not be mistaken for payment or task completion.
Direction, ownership, prerequisites
What data can be exchanged?
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Approved recipient details | SalesTOS → messaging service | SalesTOS for selected contact | Candidate business communication | Assessment: access and appropriate recipient use |
| Message request | SalesTOS → provider | SalesTOS for request | Agreed operational notification | Assessment: account and message requirements |
| Delivery outcomes | Provider → SalesTOS | Provider | Potential communication history | Custom implementation required |
| Replies | Provider → SalesTOS | Provider for received message | Potential follow-up workflow | Separate routing and access assessment |
Connection design
How the connection works
Review the current Meta business account model and the chosen authorised provider. Establish sender access and the permitted message workflow before implementing API calls or callbacks. Personal-account automation is not offered.
Illustrative working scenario
From system context to a useful next action.
A business could request an approved visit reminder for an eligible customer. If implemented, the provider outcome would be recorded separately from the representative’s visit completion.
What happens to writeback?
A sent or read message does not mark an invoice paid, close a collection or complete a visit.
Before implementation
Setup requirements
- Business messaging account and provider
- Sender ownership and authorised access
- Message purpose, examples and recipient process
- Reply owner and status-retention requirements
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Operating the agreed scope
Reliability & access
A proposed connector must define callback verification, duplicate events and failed-message handling. No live WhatsApp delivery or automated retry capability is claimed for the current registry entry.
A clearer scope starts here
Questions, answered.
WhatsApp integration
Is a live WhatsApp connector ready?
No. This page offers assessment and clearly scoped implementation.
Can we automate personal accounts?
No. Scope an authorised business messaging setup.
Are all message types allowed?
The current provider rules and account permissions must be reviewed for the intended workflow.
Will delivery close a collection?
No. Communication outcomes and financial outcomes are separate records.
What should we prepare for a WhatsApp discussion?
Business messaging account and provider; Sender ownership and authorised access; Message purpose, examples and recipient process; Reply owner and status-retention requirements. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
How is WhatsApp integration scope confirmed?
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. A sent or read message does not mark an invoice paid, close a collection or complete a visit.
No matching questions. Clear your search or discuss your requirements with us.
Explore the adjacent workflow
Related integrations
ERP & Accounting
ERPNext
AvailableConnect employee identity and attendance events.
Explore data & scopeReporting & Data
Excel & CSV
File import supportedStart with an approved template and a reviewable import.
Explore data & scopeYour systems. A defined scope.
Discuss This Integration Discuss WhatsApp with SalesTOS.
Bring your business workflow and current setup. We’ll use them to assess the right data scope.