WhatsApp setup
Connect WhatsApp Business Cloud (Meta) so AdoxERP can send document PDFs from your company’s number — phone number ID, WABA ID, app ID, and access token.
AdoxERP can send a document PDF (quotation, invoice, purchase document, and similar) to a customer’s WhatsApp number. An administrator saves this company’s WhatsApp Business Cloud (Meta) keys under Settings → Integrations → WhatsApp, then staff use WhatsApp on the document.
You do not enter Twilio credentials. Twilio is an Adox platform backup used only when this company has no Cloud keys. Adox never uses another company’s WhatsApp account.
Cloud keys are a tenant setting (your company only). Secrets are encrypted and are not shown when you reopen the page. Leave the access token blank on later saves to keep the stored value.
Before you configure the account
- Turn on WhatsApp for the company (business settings — Enable WhatsApp and Send invoice)
- Add a WhatsApp or phone number on the customer (WhatsApp first, then phone)
- Go to Settings → Integrations → WhatsApp and paste the Cloud API fields from the table below
- Set a test recipient in E.164 format (for example
+9665xxxxxxx), then Save and Send test
On a document, WhatsApp appears when those settings are on and your role can view that document type.
If you skip Cloud keys, send still works when Adox has enabled the backup sender. Recipients on a Twilio sandbox (backup only) must join that sandbox first.
WhatsApp Business Cloud (Meta)
Use Meta if your company has a WhatsApp Business Account (WABA) in Meta Business Suite. These are the only keys AdoxERP collects from the business.
Where to log in
| What | URL |
|---|---|
| Meta for Developers (apps) | https://developers.facebook.com/apps/ |
| Cloud API get started | WhatsApp Cloud API — Get started |
| WhatsApp Manager | https://business.facebook.com/wa/manage/home |
Fields in AdoxERP and where they come from
Open your Meta app → add the WhatsApp product if needed → API Setup.
| Field in AdoxERP | Example | Where to get it |
|---|---|---|
| Phone number ID | 123456789012345 | API Setup — From phone number → Phone number ID (digits, not the +966 display number) |
| WABA ID | 123456789012345 | API Setup — WhatsApp Business Account ID, or WhatsApp Manager |
| App ID | 123456789012345 | App Settings → Basic → App ID |
| Access token | Temporary token or a system-user token | API Setup Temporary access token, or Business Settings → System users → generate token with whatsapp_business_messaging. Temporary tokens expire — use a durable token for production |
| Verify token | A string you choose | You invent this if you later connect a webhook. Store the same value in AdoxERP. Not required just to send a test PDF |
| Test recipient | +9665xxxxxxx | A number allowed to receive from this WABA (test numbers in API Setup, or a real customer once the number is live) |
Meta’s send URL (for your IT team, not pasted into AdoxERP) is:
https://graph.facebook.com/v21.0/<PHONE_NUMBER_ID>/messages
AdoxERP calls this for you. You only paste the IDs and token into Integrations → WhatsApp.
Phone numbers on the document
The WhatsApp dialog prefills in this order:
- Customer WhatsApp
- Customer secondary WhatsApp
- Customer phone
Use E.164 (+ then country code, no spaces): +9665xxxxxxx, +9715xxxxxxx.
Sending from a document
- Open the document (sale, quotation, purchase, and other mapped types)
- Click WhatsApp
- Confirm the number and optional caption
- Send — AdoxERP attaches the same PDF used for Email
Business-initiated WhatsApp messages outside the 24-hour customer-care window usually need an approved template on the Cloud number. This AdoxERP action sends a session-style document message. New WABA numbers often fail until the recipient is a listed test number or the number is live.
What to do next
- Email (SMTP) setup
- Managing customers
- Print templates — customize A4 Print / PDF layout
- Sales invoices