Normally, when someone replies to an email notification from Xurrent about a request, problem, release, change, change task, project or project task, the reply gets added as a note to the record for which the notification was generated. From now on, though, Xurrent first checks whether this record reached its final status more than 28 days ago. If that is the case, rather than adding the reply to this record, Xurrent’s Mail API will generate a new request with a note containing the body of the reply email.
This was already the case for email that is not a reply to a notification generated by Xurrent, but which has the ID of an existing record in its Subject field. This adjustment therefore brings the processing of replies to Xurrent notifications in line with the processing of inbound email that is not a reply to a Xurrent notification.
More details about inbound mail processing can be found in Xurrent’s developer documentation.
Xurrent named a Market Leader in Research In Action’s Vendor Selection Matrix™ for IT & Enterprise Service Management Solutions
Xurrent earns #1 rankings in customer satisfaction, price vs value, and recommendation index in Research In Action's global ITSM/ESM Vendor Selection Matrix report.
Managing risks and delivering successful AI-driven outcomes at the Service Desk
Discover how IT leaders can navigate AI risks and achieve successful outcomes at the service desk. Learn strategies for cost control, robust security, and minimizing AI hallucinations to deliver measurable ROI. Download the Gartner report for deeper insights.