Our comments follow. Our questions are rhetorical and meant as comments.
At 03:29 PM 9/28/00, you wrote:
>We plan on:
>
>- allowing RSPs to perform renewals from the client scripts
>- allowing RSPs to query our systems for names coming up for renewal in
>the next 60 days from the client scripts
Make this an input field, in case 90 days in advance is needed for some reason.
>- providing new views in the RWI, that show what names are coming up for
>renewal in 60 and 30 days, and allow single/bulk renewals from these screens
How about an input field rather than hard coded.
>- offering an "opt in" managed renewal service; once configured this
>service will automatically send email to the billing contact for all names
>that are coming up for renewal for any RSP. This message will be fully
>customizable by the RSP. It will send messages out at -60 and -30 days. A
>note will be appended to notes field for the name record to show that the
>email was sent
What if an RSP wants the first one sent at 90 days? What if the RSP wants
three or four renewal reminders? How about making the timing and the
number of instances user configurable.
>- providing an "opt in" daily service that emails a list of names that are
>due to expire in 60 and 30 days to the RSP
Ditto on timing and instances.
>At the renewal date, if the name has not been renewed, Tucows will send an
>email message to the admin and billing contacts, advising them that this
>is their final notice, and that if they do not renew the name within 15
>days, they risk losing it. This message will refer them to their RSP for
>renewal. RSPs will be allowed to manually stop this message from going out
>on a "per name" basis.
Why from Tucows? Why not from the RSP?
>The name will automatically be deleted at 29 days past renewal.
----
Don Brown - Dallas, Texas USA Internet Concepts, Inc.
[EMAIL PROTECTED] http://www.inetconcepts.net
PGP Key ID: 04C99A55 (972) 788-2364 Fax: (972) 788-5049
Providing Internet Solutions Worldwide - An eDataWeb Affiliate
----
