Organizations that provide services to consumers, students, or citizens, often use their website as a portal for answering questions or logging requests. Registering these people and their requests in 4me enables these organizations to apply 4me’s service management capabilities to these issues, allowing for easier communication, the possibility to assign requests to specialists within the organization, reporting, and more.
It was already possible for people to register themselves via 4me Self Service, with OpenID Connect or by sending an email to the right 4me email address, provided of course that this is allowed in the settings. Now it is also possible for a website to collect a user’s email address and other information and send that as an email to 4me, generating a person record if that customer is not yet known, and a new request.
To support this new functionality, a new parameter for sending email using the Mail API has been added to this API: the #from parameter. An option to allow for the use of this new parameter has been added to the ‘Email Policy’ section of the Settings console for Inbound Email.
Allow email parameter #from box in these settings expands this option. The
Senders field becomes visible, in which one or more email addresses that are allowed to send email with the #from email parameter can be entered. In the
Authentication token(s) field one or more authentication tokens must be entered. Inbound email with a #From parameter is rejected if the sender and / or authentication token is not registered in these settings.
The example below shows how these parameters can be used for inbound emails.