Understand working with contact registration requests

When a shopper submits the required information for the contact registration request, an Administrator sees the new registration request in the Contact Requests area of the Accounts page, and can view, search, and work with contact registration requests there.

A Delegated Administrator can perform the same functions using the Contact Registration Requests widget on the store.

Both Contact Requests and Account Requests menu items appear as sub-items under Registration Requests in the Accounts navigation page in the administration user interface. Anyone with the Administrator and/or Account Manager Role can view, update, accept, and reject registration requests.

Note: The Contact Requests tab always appears in the user interface. The Account Requests tab will not appear if Account Registration is disabled in Settings and there are no account registration requests with a status of New, Review, More Info Needed, or Rejected.

After the initial submission of the required details by the shopper, the contact registration request is reviewed from the merchant side by the administrator (or delegated administrator). At this point, the administrator (or delegated administrator) may also request from the shopper additional details such as credit checks and more. Upon receipt of all the requested information, the administrator (or delegated administrator) then either approve or reject the registration request. If the request is approved, the new contact with the account is activated and can then begin transacting business.

Work with the contact registration request list

The information in the new contact registration request list can be looked at by both Administrators and Delegated Administrators. The information that follows describes the differences in the information that is available to each separate Role.

Via the administration user interface, the new contact registration request list for Administrators in the Contact Requests area of the Accounts page provides the following information in a list divided into the following:

Column Head	Description
Request ID	Request ID generated by the system. This provides a link that opens the request details.
Requested Account ID	Account ID that the requester provided
Requested Account Name	Account Name that the requester provided
Email Address	Email address that the requester provided
Last Name	Last name that the requester provided
First Name	First name that the requester provided
Originating Site	Site on which the request originated (Site name - or, if name is unavailable, Site ID)
Request Date	Date when the request was received. (No timestamp is provided)
Status	Displays Status icon (for statuses of “Rejected” and “More Info Needed”) The Status of a request can be either New (the request is new and has not been viewed), Review (the request has been viewed or changed and needs to be acted upon), More Info Needed (the request has been viewed and an action needs to be taken to collect more account or shopper information before the request is approved or rejected), or Rejected (the contact registration request has been rejected and no contact has been activated). The status is the same regardless of which Admin is viewing it.

You can also do the following with the new contact registration request list:

Filter the list by status. The default view of the list is to show all statuses.
Use a typeahead search box. The placeholder text in the box is “Search for registration request.” When you type a string, the list is filtered to records containing that string in the Company field.
Sort the list by the following:
- Email address: A-Z or Z-A
- First name: A-Z or Z-A
- Last name: A-Z or Z-A
- Request date: Newest or Oldest
- Request ID: A-Z or Z-A
- Requested account name: A-Z or Z-A

The default sort order is by Request date: Newest.

Look at other pages of the list as the list is paginated as the list grows longer.

Column Head	Description
Request ID	Request ID generated by the system. This provides a link that opens the request details.
Email Address	Email address that the requester provided
Last Name	Last name that the requester provided
First Name	First name that the requester provided
Originating Site	Site on which the request originated (Site name - or, if name is unavailable, Site ID)
Request Date	Date when the request was received. (No timestamp is provided)
Status	Displays Status icon (for statuses of “Rejected” and “More Info Needed”) The Status of a request can be either New (the request is new and has not been viewed), Review (the request has been viewed or changed and needs to be acted upon), More Info Needed (the request has been viewed and an action needs to be taken to collect more account or shopper information before the request is approved or rejected), or Rejected (the contact registration request has been rejected and no contact has been activated). The status is the same regardless of which Admin is viewing it.

The Delegated Administrator can also do the following with the information that they are allowed to view:

Filter the list by status. The default view of the list is to show all statuses.
Use a typeahead search box. The placeholder text in the box is “Search for registration request.” When you type a string, the list is filtered to records containing that string in the Company field.
Sort the list by the following:
- Email address: A-Z or Z-A
- First name: A-Z or Z-A
- Last name: A-Z or Z-A
- Request date: Newest or Oldest
- Request ID: A-Z or Z-A

The default sort order is by Request date: Newest.

Look at other pages of the list as the list is paginated as the list grows longer.

Search for a specific registration request

As an Administrator in the Contact Request list view, you have access to Advanced Search in the administrator user interface via a typeahead search box.

Note: This functionality is not available for Delegated Administrators in the store’s Registration Requests widget.

The placeholder text is “Filter contact requests.” When you type a string, the Contact Request list is filtered to records containing that string in the Last Name field.

You can also use an Advanced Search control (same as found in the accounts, contacts, and contact registration user interfaces to search for contact registration requests by creating expressions like the following:

<property 1> contains <value 1>
 <property 2> contains <value 2>
...
<property 5> contains <value 5>

You can also specify “Match Any” or “Match All.”

The properties available for this type of search must be:

Of type string OR
A custom string property of a contact registration request, account, or profile OR
Queryable static string properties that include:
- Last Name
- Email Address
- First Name
- Contact Registration Request Property ID
- Request ID
- Requested Account ID
- Requested Account Name
- Approver Comments
- Notes from the Requester

Also, the Advanced Search control feature presents you with dropdown lists of two groups of properties with the headers Contact and Request.

The group and the order of the properties for each header are as follows:

Under the Contact header:
- The Contact static properties listed above, in alphabetical order
- Any Contact dynamic properties, in alphabetical order
Under the Request header:
- The Request static properties listed above, in alphabetical order
- Any Request custom properties, in alphabetical order

When you use the extended search control, keep in mind the following:

The first row is populated with the “Last Name” property.
The “contains” operator is not shown; it is implicit.
Multiple terms with the same property are supported.
“Match All” is the default.
When an extended search is in effect, the text, “Advanced Search Results Shown” appears in the search box.
After you perform an extended search, the next time you open the Extended Search control, the criteria from your last search is displayed. This is true even if you have performed simple searches since performing the extended search. The criteria persist until you perform another extended search.
The Extended Search control allows at most 5 criteria.

You cannot search for registration requests via store APIs.

View and edit contact registration request details

Contact registration request details be looked at and/or edited by both Administrators and Delegated Administrators. Administrators use the Contact Requests area of the Accounts page in the administrator’s user interface to view, search, and work with contact registration requests. A Delegated Administrator can perform the same functions using the Contact Registration Requests widget on the store.

The information that follows describes the differences in the information that is available for viewing and editing for each separate Role.

To look at and/or edit an actual new or existing contact registration request as an Administrator, click the Request ID (which is a link) of the request found in the Contacts Requests area of the Accounts page. When you do that you see a detail view that combines the following information:

Data received from the requester
All custom contact self-registration request properties
Selected static contact (profile) properties
All custom contact (profile) properties

Each request displays two tabs of information: Request and Contact. Some of the fields on the tabs can be viewed and some can be edited. The following contains more details on the information found on each tab:

Request tab containing the following fields:
- Status – A dropdown list that can be used to change the status of the requests. The choices are New, Accept, Reject, More Info Needed, and Review.

The dropdown shows New when the request is first opened. Once the status changes, the New status is removed from the dropdown. If the profile has been deleted, the Status can only be changed to Reject.

This field is Editable except if the Status is Rejected it becomes read-only. Also, if the contact has been deleted, the Status can only be changed to Rejected.

Request ID - Read-only.
Request Date - Read-only in the user interface but editable via API.
Site Where Request Originated - URL, Read-only in the user interface but editable via API.
Notes from the requester - Read-only in the user interface but editable via API.
Rejection comments - Read-only in the user interface but editable via API. Displayed only if the request was rejected.
Any custom properties that exist – Editable unless the Status is Rejected.
Contact tab containing the following fields:

Note: This tab is grayed out if the profile has been deleted. This would occur either via the Agent API (for GDPR reasons) or because the request was rejected and the contact was new.

First Name – Read only. For an existing contact, the First Name stored in Commerce takes precedence over the submitted First Name and is displayed here.
Last Name – Read only. For an existing contact, the Last Name stored in Commerce takes precedence over the submitted Last Name and is displayed here.
Email/Login ID – Read-only.
Requested Account ID - Read-only in the user interface but editable via API.
Requested Account Name - Read-only in the user interface but editable via API.
Account Name - Accessed via the picker. Editable unless the status is Rejected. This is the name of the account to which the contact will actually be added. This name will be pre-populated in the field with the requested account if the system identified the account.
Any custom properties that exist – Editable unless the Status is Rejected. If the email address is that of an existing contact, the existing contact’s property values take precedence over the submitted values and are the ones displayed.

If you click Cancel, any changes you have made are discarded. The Save button applies changes made in all tabs.

Note: The previous fields described list fields that are displayed in the administration interface. The following fields can be edited only in the REST API:

approverComments (listed above as Rejection Comments, but the field is also editable by API on an approved request)
approvedBy
approvedSource

As a Delegated Administrator, you can look at and/or edit the following information in a contact request that you are working on. Each request displays two tabs of information: Request and Contact. Some of the fields on the tabs can be viewed and some can be edited. The following contains more details on the information found on each tab:

Request tab containing the following fields:
- Status – A dropdown list that can be used to change the status of the requests. The choices are New, Accept, Reject, More Info Needed, and Review.

This field is Editable except if the Status is Rejected it becomes read-only. Also, if the contact has been deleted, the Status can only be changed to Rejected.

Request ID - Read-only.
Request Date - Read-only in the user interface but editable via API.
Site Where Request Originated - URL, Read-only in the user interface but editable via API.
Notes from the requester - Read-only in the user interface but editable via API.
Rejection comments - Read-only in the user interface but editable via API. Displayed only if the request was rejected.
Contact tab containing the following fields:

Note: This tab is grayed out if the profile was deleted. This would occur either via the Agent API (for GDPR reasons) or because the request was rejected and the contact was new.

First Name – Read only. For an existing contact, the First Name stored in Commerce takes precedence over the submitted First Name and is displayed here.
Last Name – Read only. For an existing contact, the Last Name stored in Commerce takes precedence over the submitted Last Name and is displayed here.
Email/Login ID – Read-only.

If you click Cancel, any changes you have made are discarded. The Save button applies changes made in all tabs.

Note: The previous fields described list fields that are displayed in the Delegated Administrator user interface. The following fields are editable via API:

approverComments (listed above as Rejection Comments, but the field is also editable by API on an approved request)
approvedBy
approvedSource