Insights & updates from our experts
The view in the ‘Inbound’ Email’ section of the Settings console is used by Xurrent account administrators to see which email messages were sent to the Xurrent account of their organization. In this view, they can see how Xurrent processed these messages (e.g. whether a new request was generated for an inbound email or whether the body of the email was used to add a note to an existing task). Administrators can also see which emails did not get processed by the Xurrent Mail API and why that was the case.
To make it easier for administrators to find specific emails, two columns have been added to the ‘Inbound Email’ view. The new columns are:
- Record Type – This column shows the record type icon of the record that was created or updated by the Xurrent Mail API after the email was received.
- ID – This column shows the unique number of the record that was created or updated by the Xurrent Mail API after the email was received.

Having these two extra columns available in the view makes it possible to sort the view by record type or enter a record ID in the Search box above the view to find the email that caused a specific record to be generated or updated.
Note that the column ‘Created’ has been renamed to ‘Received’ to make the view just a little more intuitive.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














