|
The Netbillingsystem automatically sends emails to
your customers on your behalf. There are two steps to setting up
these automatic emails. You create the emails to be sent (or use the
pre-set emails supplied by the Netbilling system), and you must choose
when those emails are sent.
Since
the system delivers pre-set emails to you automatically, you can skip to choosing which emails are sent when. This is
done by visiting WEBSITE EMAILS, and associating emails with the events that
send them. (For more information about WEBSITE EMAILS, click the arrow to
the left of WEBSITE EMAILS in the menu.)
If you
would prefer not to use the Netbilling supplied emails in your WEBSITE EMAILS,
you can create your own. You can either copy an existing email and edit it, or
create your own from scratch. In either case, you begin by going to EMAIL EDITOR
in the setup area. Once you have created a new email (or copied one) you can
choose to edit it. This will bring up a screen where you can control the contents
of the email.
Most
of the process of creating your own
email requires no special work; it's like typing a normal email. But, if you want to
put something in an email that is different for each email (such as the name of
your customer) you can't just type that information in, you must instead insert an email
field.
Email
field are placed in an email where you want information to be
pulled from your database to customize the email. For example, if
you want the name of your company to appear in the email, you would
insert the variable ${COMPANY_NAME} into the email. The email system
would then grab whatever you configured as your company name in the
Contact Info section of your Netbilling gateway account.
There are four data sources
from which the email manager can capture information. Not all data
sources are available for all emails, so use only the data sources
that make sens for the kind of email you are making. The four
data sources are ACCOUNT, TRANSACTION, SITE, and
SUBSCRIPTION/MEMBERSHIP.
For example, if you are creating an email to
welcome a new member to your subscription site, it might make sense
to use all four data sources. The user has just paid
(TRANSACTION) to be a member (MEMBERSHIP) of your (ACCOUNT) website
(SITE).
On the other hand, if you are creating an email
to act as a receipt for a product purchase, then ACCOUNT and
TRANSACTION information may be appropriate, but MEMBERSHIP and SITE
information would not be available.
If you are unsure what data sources to use, copy
an existing email, or visit the WEBSITE EMAILS screen. Both
these places can help you to learn which data sources are
appropriate for the kind of email you are making.
ACCOUNT
This information is always available to all your emails.
This
is the specific information about your Netbilling account that you have
entered into various parts of your configuration like your company
name, address, and telephone numbers. This information is static and
is always available to the email
manager. While you could just type your contact information directly
in an email, it is smarter to use these fields
so that ALL your emails will automatically be updated
if you change your contact information later.
TRANSACTION
This information is only available in emails that are a result of a transaction, such as
a transaction receipt or a subscription signup.
This is the information that comes through the system for a given
individual transaction. This would include items like the credit
card number, the card holder's first and last name, and their
billing address among others. This information is specific to
a single transaction and once that transaction is finished, the
information is no longer available to the email manager.
SITE
This information is only available to emails that are associated with a SITE. This
means most transactions can use this information - but in certain places (such as the
Virtual Terminal) you can choose to omit the SITE. If you do, this information will not
be available.
This is information that comes from your WEBSITE CONFIG screen and
includes information such
as the site tag, the name of the site, the webmaster's email
or the url of the site. This information is static and is always
available to the email manager.
MEMBERSHIP
This information is only available to emails that are associated with a
Subscription or Membership.
This is information that specific to a membership, but not part
of the transaction data.
This would include the username, password, length of membership,
and expiration date. This data is pulled from a single membership
signup, and then is no longer available to email manager.
Below, we have listed all the information that is available in
the different data sources for you to create your own, completely
original email. Just remember, that when you create a completely
original email template that you choose the data sources that
you choose make sense for the email you have chosen. For example,
if you are not using the subscription features, avoid the membership
fields.
(a) primarily intended for end users
(b) primarily intended for agents
ACCOUNT DATA SOURCES
ACCOUNT FIELDS
| Name |
Description |
Example |
| ${ACCOUNT_ID} |
The ID number of the merchant | 123456789012 |
| ${AGENT_ID} |
The ID number of the merchant's agent | 234567890123 |
| ${AGENT_COMPANY_NAME} |
The name of the merchant's agent | 3rd National
Bank |
| ${COMPANY_NAME} |
The everyday name of the merchant's company | John's BBQ
Sauce |
| ${COMPANY_LEGAL_NAME} |
The legal name of the merchant's company | John Wilson,
Inc. |
| ${COMPANY_DBA_NAME} |
Another name of the merchant's company | John's BBQ
Sauce |
| ${COMPANY_PHONE} |
The merchant's phone number | 888-888-8888 |
| ${COMPANY_FAX} |
The merchant's fax number | 888-888-8877 |
| ${COMPANY_STREET} |
The merchant's street address
| 888 E. Eighth
St. #8 |
| ${COMPANY_CITY} |
The merchant's city | Eightville |
| ${COMPANY_STATE} |
The merchant's state | AZ |
| ${COMPANY_ZIP} |
The merchant's ZIP number | 12345-6789 |
| ${COMPANY_COUNTRY} |
The merchant's country | USA |
| ${CONTACT_NAME} |
The name of the merchant's primary contact | John
Botsford |
| ${CONTACT_EMAIL} |
The email of the merchant's primary contact | john@johnsbbq.com |
| ${CONTACT_PHONE} |
The phone of the merchant's primary contact | 888-888-8889 |
| ${TECHNICAL_NAME} |
The name of the merchant's technical contact | Sue
Jones |
| ${TECHNICAL_EMAIL} |
The email of the merchant's technical contact | sue@johnsbbq.com |
| ${TECHNICAL_PHONE} |
The phone of the merchant's technical contact | 888-888-8899 |
| ${FINANCIAL_NAME} |
The name of the merchant's financial contact | Chris
Smith |
| ${FINANCIAL_EMAIL} |
The email of the merchant's financial contact | chris@johnsbbq.com |
| ${FINANCIAL_PHONE} |
The phone of the merchant's financial
contact | 888-888-8999 |
TRANSACTION FIELDS
| Name |
Description |
Example |
| ${TRANS_ID} |
The ID number of the transaction | 456789012345 |
| ${ACCOUNT_ID} |
The ID number of the merchant | 123456789012 |
| ${SITE_TAG} |
The TAG (brief nickname) of the SITE | BBQ1 |
| ${AMOUNT} |
The amount of the transaction | 25 |
| ${FANCY_AMOUNT} |
The above item, formatted nicely | 25.00 |
| ${AUTH_CODE} |
The authorization code returned when the transaction was run | 999999 |
| ${ISSUE_DATE} |
The date the transaction was issued | 2001-01-20
14:33:08 |
| ${FANCY_ISSUE_DATE} |
The above item, formatted nicely | WED
2001-JAN-20 14:33:08 |
| ${AUTH_DATE} |
The date the transaction was authorized | 2001-01-20
14:33:08 |
| ${FANCY_AUTH_DATE} |
The above item, formatted nicely | WED
2001-JAN-20 14:33:08 |
| ${CAP_DATE} |
The date the transaction was captured | 2001-01-22
15:25:11 |
| ${FANCY_CAP_DATE} |
The above item, formatted nicely | FRI
2001-JAN-22 15:25:11 |
| ${AUTH_MSG} |
The authorization message returned when the transaction was run | Captured |
| ${AVS_RESULT} |
The AVS result code returned when the transaction was run | Z |
| ${AVS_RESULT_MSG} |
The AVS result message returned when the transaction was run | 5-digit ZIP
Code matches, address does not |
| ${CVV2_RESULT} |
The CVV2 result code returned when the transaction was run | M |
| ${CVV2_RESULT_MSG} |
The CVV2 result message returned when the transaction was run | CVV2 match |
| ${BILL_STREET} |
The street address entered for the transaction | 1212 E.
Green |
| ${BILL_CITY} |
The address city entered for the transaction | Bensenville |
| ${BILL_STATE} |
The address state entered for the transaction | IL |
| ${BILL_ZIP} |
The address ZIP entered for the transaction | 60614 |
| ${BILL_COUNTRY} |
The address country entered for the transaction | USA |
| ${CARD_ISSUER} |
The issuer of the credit card (VISA, MasterCard, etc.) | VISA |
| ${BILL_NAME1} |
The first name of the cardholder | Sam |
| ${BILL_NAME2} |
The last name of the cardholder | Brown |
| ${CARD_NUMBER_XXX} |
The obfuscated card number | xxxxxxxxxxxx1111 |
| ${CARD_EXPIRE} |
The expiration date of the card | 0304 |
| ${CUSTOMER_EMAIL} |
The email of the cardholser | samb123@email.com |
| ${CUSTOMER_PHONE} |
The phone number of the cardholder | 932-932-9322 |
| ${DESCRIPTION} |
The description fo the product | 6 bottles bbq
sauce - mild |
| ${MISC_INFO} |
The miscellaneous information supplied with the transaction | I love your
stuff - send me a catalog |
| ${REMOTE_ADDR} |
The IP address that delivered the transaction | 123.11.22.33 |
| ${REMOTE_HOST} |
The web (.com sytle) address that delivered the
transaction | http://www.email.com> |
SITE FIELDS
| Name |
Description |
Example |
| ${SITE_ID} |
The ID number of the site | 567890123456 |
| ${ACCOUNT_ID} |
The ID number of the merchant | 123456789012 |
| ${SITE_TAG} |
The TAG (brief nickname) of the SITE | BBQ1 |
| ${SITE_NAME} |
The NAME of the site | John's BBQ
Heaven |
| ${SITE_URL} |
The web address of the site | http://www.johnsbbq.com |
| ${MEMBER_URL} |
The web address of the membership area of the site (if it
exists) | hhtp://www.johnsbbq.com/members/ |
| ${WEBMASTER_NAME} |
The name of the webmaster | Sue
Jones |
| ${WEBMASTER_PHONE} |
The phone number of the webmaster | 888-888-8899 |
| ${WEBMASTER_EMAIL} |
The email address of the webmaster | sue@johnsbbq.com |
| ${REFRESH_DATE} |
The time when memberships are refreshed daily | 2001-04-01
0:55:30 |
| ${FANCY_REFRESH_DATE} |
The above item, formatted nicely | MON
2001-APR-10 0:55:30 |
| ${GRACE_DAYS} |
The grace period of an expired membership | 5 |
SUBSCRIPTION/MEMBERSHIP FIELDS
| Name |
Description |
Example |
| ${MEMBER_ID} |
The ID number of the member | 890123456789 |
| ${ACCOUNT_ID} |
The ID number of the merchant | 12345679012 |
| ${SITE_TAG} |
The TAG (brief nickname) of the SITE | BBQ1 |
| ${SIGNUP_CHARGE_ID} |
The ID of the recurring transaction | 012345678901 |
| ${SIGNUP_DATE} |
The date of the member signed up | 2001-01-20
14:33:08 |
| ${FANCY_SIGNUP_DATE} |
The above item, formatted nicely | WED
2001-JAN-20 14:33:08 |
| ${EXPIRE_DATE} |
The expiration date of the member | 2001-02-20
14:33:08 |
| ${FANCY_EXPIRE_DATE} |
The above item, formatted nicely | THU
2001-FEB-20 14:33:08 |
| ${LOGIN_NAME} |
The login name of the member | willy1 |
| ${PASS_WORD} |
The password of the member | wonthe2 |
| ${REAL_NAME1} |
The first name of the member | Bill |
| ${REAL_NAME2} |
The last name of the member | White |
| ${EMAIL_ADDRESS} |
The email address of the member | bill@white.net |
| ${STATUS} |
The member's current status | ACTIVE |
| ${REBILLING_SETUP_DATE} |
The date rebillings were set up | 2001-01-20
14:33:08 |
| ${FANCY_REBILLING_SETUP_DATE} |
The above item, formatted nicely | WED
2001-JAN-20 14:33:08 |
| ${REBILLING_DUE_DATE} |
The date the next rebilling will occur | 2001-02-20
14:33:08 |
| ${FANCY_REBILLING_DUE_DATE} |
The above item, formatted nicely | THU
2001-FEB-20 14:33:08 |
| ${AMOUNT_EXPR} |
The amount the member was charged | 12.50 |
| ${NEXT_AMOUNT_EXPR} |
The amount the member will be charged at the next
rebilling | 2.50 |
© Copyright Netbilling, inc.
|