Table of contents
Send messages
The messages institutions send with IO are always personal communications, as they are directed to a specific user.
The institution can query the back end with respect to the fiscal code it has available and to which it has something personal to communicate. If the fiscal code is present among the app users and if the service is active, the institution is authorized to proceed and send its communication.
If the institution sends a message via IO to the legal representatives of legal persons, no checks are performed of the correspondence of the fiscal code of the legal representative and the legal person.
Therefore it is not permitted to send mass communications to all IO users or to send messages to users who are not direct recipients of the provided services.
.png)
Types of messages
The messages that are sent on IO can be of different types and enriched depending on:
- The type of content to be conveyed: informative, regarding payments or due dates;
- How the content of the message is managed: static or from remote.
Content of messages
In general, the messages can be:
- informational messages: text messages that can concern an update related, for example, to a new available document or a request presented to the institution;
- messages that indicate a payment: messages that contain information about an amount due, with a reminder of the payment deadline and the “see notice” button to proceed with the payment. For these types of messages, the fields related to the payment_data (notice code, amount to be paid, due date) must be included;
- messages that indicate a deadline: messages that contain a deadline or a reminder (a reminder for the expiration date of a document to be renewed or the deadline for signing up for a service). For these types of messages, the due_date field must be used in the message payload.
With respect to the basic messages, it is possible to enrich the messages with some additional functions. If required, with additional integration it is possible to:
- Add attachments to messages
- Check at any time if the messages have been sent, received or read
- If there is a payment notice, the institution can check at any time if it was paid
- If the citizen provides consent, and the associated debt position has a due date, they can generate push notifications that remind the citizen that the message was read but the payment was not made.
Managing content
In addition to the categorizations previously described, messages can be identified in two types, according to the content management method provided by your institution:
- Traditional messages, i.e. messages whose content is invariable over time and defined at the time they are sent;
- Messages with remote content, i.e. messages whose content is not managed directly by IO but provided by your systems at the time of their use by the recipient. Messages with remote content are intended in particular for communications that send sensitive information.
You can find detailed information on remote content messages in the dedicated section of the IO Technical Guide.
Haven't completed onboarding yet and need help?
Write an email describing your problem or question to the address areariservata@assistenza.pagopa.it.
Tell us what you think
To report problems or give feedback, leave a comment in the GitHub space of the IO app