We're looking to offer a passwordless website login via an emailed token. The REST API has a SendCredentials method for generating a credentials email, but the recommendation from Tessitura has been to set email frequency to every 5 minutes. From a UX perspective, a 5 minute wait time (or even the minimum 1 minute) is too long for a purchase path login.
One option to speed this up would be to have the website use its own SMTP server to send a token email instead of TPS. We are able to use CRM/WebLogins/{loginId}/LoginCredentials to retrieve a generated token. However, we found that it stays null until calling SendCredentials, which attempts to send its own email. So we have two questions:
Hi Susan, we don't appear to have support@iwave.com in the website, so the only thing I can think is that there might be someone's address from iWave has an autoforward rule or alias has come into play. I will contact you offline with names of folks we have with iWave so we can do some cleanup.
Best,
ToddTessitura Network