Sender IDs and message templates in the ERP

The DLT registration details section of SMS Configuration shows how the networks know your school: the organisation, its sender IDs, the approved message texts and any recent refusals. It is also where you send JPRAXC new sender IDs and message texts to register, including ones your school already has approved on DLT.

Before you start#

• JPRAXC SMS must be active for the school. See Get JPRAXC SMS and complete the setup.
• Anyone who can view Communication can read this section. Only a school administrator can send details to JPRAXC.

Read your registration#

1. Open General Settings › SMS Configuration.
2. Scroll to DLT registration details. Select Refresh to read the latest from JPRAXC.
3. The numbered steps at the top show where the school stands in the registration.
4. Under Principal entity you see the DLT platform, the organisation's name and type, its Registration status, the Principal Entity ID, the Telemarketer chain status, and the PAN and GSTIN (partly hidden).
5. Sender IDs (headers) lists each sender ID with its Type, its Header ID and the Platform's answer.
6. Registered message texts (content templates) lists each message with its Sender ID, the Approved text (and how many variables it has), its Template ID and the Platform's answer.

The Platform's answer is shown as a coloured label:

If the Telemarketer chain line asks you to add a telemarketer on the platform, sign in to your school's DLT portal and add the telemarketer ID shown there.

Send JPRAXC new details#

Use the form Send JPRAXC the registration details at the end of the section. Fill in only what applies; anything already registered is left as it is.

1. Organisation (only if it is not registered yet, or to give an existing PE ID):
   • Choose the DLT platform and Entity type.
   • Type the Legal name (exactly as on PAN), the PAN and the GSTIN (if registered).
   • If the school is already registered on DLT, type its Principal Entity ID (if already registered). JPRAXC verifies it before it counts.
   • Add the Authorised signatory, Signatory mobile and Signatory email.
2. Under Sender IDs wanted, type up to two six-letter headers:
   • Service header for fees, attendance, results and notices.
   • Transactional header (OTP) only if the school sends sign-in codes.
3. Under Message texts to register, each automatic message the ERP sends by SMS is already listed with the ERP's own wording, with {#var#} where the ERP fills in a name, an amount or a date.
   • Change the words if you like, but keep the school name and the {#var#} marks.
   • Choose the Type for each.
   • Tick Register this one for each text you want registered. The common ones are ticked for you.
   • Select Add another text for a message of your own.
4. Select Send to JPRAXC.

The ERP confirms Sent to JPRAXC. The answers appear here as the platform gives them. If anything could not be taken, the message starts Sent to JPRAXC, except: and names the header or text with the reason.

Use sender IDs and templates your school already has#

If your school registered on DLT earlier and already has approved headers and templates:

1. Type the Principal Entity ID (if already registered).
2. Type your approved header in Service header (and Transactional header (OTP) if you have one).
3. Under Message texts to register, type each approved text exactly as it was approved, with its {#var#} marks, and tick Register this one.
4. Select Send to JPRAXC.
5. Add JPRAXC to your telemarketer chain on your DLT portal if the Telemarketer chain line asks you to.

JPRAXC checks the details and records the Template IDs. They then appear in the tables above.

Good to know#

• The ERP matches each automatic message (fee reminder, receipt, absence and so on) to the template registered for it. If you later reword that message in the ERP, register the new wording here first; a wording that no longer matches is refused.
• Each {#var#} can hold up to 30 characters.
• Keep the school's name in every text. The platform expects the sender to be named.

Troubleshooting#