Your own business number
The number is registered to your organisation. Recipients see you, not a shared sender.
Exclusively for JPRAXC clients
Available on request
Your ERP’s notices, receipts and reminders delivered on WhatsApp, from a business number registered to your own organisation — not a shared one, and not a personal handset.
Your own business number · Approved templates · Notices, receipts and reminders · Delivery and read reporting · One API
WhatsApp API is sold only to organisations already running a JPRAXC product, so it connects to the ERP you already use rather than standing on its own.
The number is registered to your organisation. Recipients see you, not a shared sender.
Use approved message templates for supported notices. Changed wording may require another provider review before use.
Use supported ERP communication workflows for fee dues, attendance, holidays and events, with the required recipient permissions.
Send supported payment receipts to the registered family number through the configured communication workflow.
Track provider-reported sent, delivered, read and failed events where available. An accepted request is not proof of delivery.
A balance, a published rate and a spending cap, the same way the SMS account works.
Use the WhatsApp tools supported by your installed JPRAXC product. Confirm product and version compatibility during activation.
Permitted categories, daily ceilings and spending caps carried on your licence.
Each message keeps the rate version that priced it. A later rate change never rewrites an old charge.
The School ERP WhatsApp workspace keeps incoming replies and outgoing messages in one conversation, with replies available when messaging is permitted.
School ERP can fill message wording with saved details such as the recipient name, school name and date, keeping each notice relevant to the person receiving it.
School ERP communication permissions control who can view WhatsApp conversations and who can reply, so access follows each team member’s role.
Submit the request with your existing JPRAXC licence reference. WhatsApp API is exclusive to current clients.
Your business number is registered and verified, and your message templates are submitted for approval.
Buy a pack. The invoice is raised by JPRAXC Sales and the balance is credited once the payment is confirmed.
Your ERP sends through the same account, and every message is reported against the balance it came from.
The number, the templates and the balance belong to your organisation. JPRAXC operates the platform behind them.
Service outcomes
Prepare your setup
Identify the organisation-owned number to review during registration and verification.
Bring examples of the notices, reminders and receipts you need so template requirements can be reviewed.
School communication and company sales use their own account connections. The interface brings the work together without treating every organisation as one sender.
Keep eligible notices, fee reminders and receipts close to the school records that prompted them. Select the supported message type, check the recipient details and use an approved template when required.
Read incoming WhatsApp replies and outgoing messages in the School ERP workspace. Viewing and replying follow communication permissions; connecting the business account is an administrator task.
The JPRAXC Sales Portal has its own WhatsApp configuration and connection flow for the company’s business account. It is separate from a school’s account and number.
Review the connected account, templates and message outcomes before opening access to the team. Activation, available modules and billing depend on the agreed service and the installed product version.
An administrator signs in through the supported Meta connection flow and selects the organisation’s WhatsApp Business Account and business number. Number eligibility and account approval are checked during onboarding.
Confirm recipient permission, choose suitable templates and fill supported school or recipient details. Existing records are not a substitute for permission to contact someone.
Use incoming replies and provider-reported sent, delivered, read or failed events where available. API acceptance alone does not mean the person received or read the message.
Check the current quotation, service entitlement and billing arrangement before activation. Usage limits, provider charges and available features vary; this is not unlimited free messaging.
No. WhatsApp API delivers through WhatsApp to an eligible recipient number. ConnectX is the messaging workspace inside JPRAXC School ERP and its Parent and Staff apps. Choose the channel for the audience and message.
Ask for an eligibility check before changing anything. Do not delete an existing WhatsApp account as a preparation step. This JPRAXC connection currently targets the dedicated Cloud API number flow; keeping the same number active in the Business app is not promised.
Within the 24-hour customer service window opened by a user’s message, Meta permits replies without a template. Outside that window, an approved template is required. The recipient’s opt-out and Meta’s current messaging rules still apply.
No. Each organisation still needs its own eligible account and number, permissions, working connection and applicable template approval. A school’s setup is separate from JPRAXC’s own Sales Portal setup.
No. Recipient connectivity, account status and provider restrictions can affect delivery. A read event is shown only when it is reported; it is not a guarantee that a notice was understood or acted on.
Request activation against your existing JPRAXC licence. The team confirms supported features, setup requirements and pricing before enabling the service. Review the Terms, Privacy policy and the agreed order before paying.
Read our Privacy policy, Terms of service and Grievances, together with Meta’s WhatsApp Business Messaging Policy .
Already a JPRAXC client?
YOUR NEXT CHAPTER