Result Codes - Clean Suite for CRM: Salesforce#

Result Codes#

Melissa services return result codes with each processed record. Use these codes to decide whether your process can accept, review, or reject a record.

Read Result Codes#

A response can contain more than one comma-separated code. Each code describes a different part of the result.

For example, an address response can contain an address status code and a geocode status code. Review the complete returned code string before you change a record workflow.

Result Code Anatomy#

../../_images/result-code-anatomy.svg

Each code has a family and a number. Match a complete code, not a prefix.

A response can contain multiple comma-delimited, four-character codes. Check each code that the service returns. Do not infer a result from a code family alone.

Use Result Codes in Salesforce#

  1. Create output fields for the result code and the service outputs you need.

  2. Add those fields to the service Custom Mapping.

  3. Run a single-record action or a batch job.

  4. Review the output fields and Clean Suite Log entries.

  5. Use Salesforce Flow, reports, or list views to group records by code.

Code Families#

The first two characters identify a service or result category.

Prefix

Category

AC

Address change

AE

Address error

AS

Address status

AV

Address verification

CD

Presence of children

CM

SmartMover match status

CS

SmartMover change-of-address status

DA

Append results

DD

Date of death

DE

Domain error

DV

Domain verify

EE

Email error

ES

Email status

FE

Business or firm error

FS

Business or firm status

GD

Demographic gender

GE

General transmission error or geocode error

GS

Geocode status

GW

General transmission warning

ID

Household income

LD

Length of residence

MD

Marital status

NE

Name error

NS

Name status

PE

Phone error

PS

Phone status

RD

Own or rent

SE

Transmission service error

SG

Address suggestions

SP

Personator status

VR

Verify results

VS

Verify status

WD

Occupation

XS

Global Express Entry status

YC

Property change

YE

Property error

YS

Property status

Result Code Routing#

Use the complete result code string to select the record action.

../../_images/CleanSuite_ResultCodeRouting.png

Diagram flow

  1. Service response → Read all returned result codes

  2. Read all returned result codes → Apply the business rule for each code

  3. Apply the business rule for each code → Can the process accept the record?

  4. Can the process accept the record? → Accept the record (Yes)

  5. Can the process accept the record? → Does the record need review? (No)

  6. Does the record need review? → Route the record to review (Yes)

  7. Does the record need review? → Reject the record (No)

Process Records Safely#

A code is service output, not an automatic permission to overwrite data. Configure record updates and approval steps to match your business rules.

Review partial matches, multiple matches, unknown statuses, and errors before you replace user-entered contact data. Keep source values when your process requires audit history.

Troubleshoot Missing Results#

If result fields remain empty, check the Custom Mapping, field-level security, active license key, and Clean Suite Log. Confirm that the target user can read and edit the mapped output fields.

Result-Code Status Indicator#

Use the Result Code Status Indicator to show a configured result-code state on a Lightning page.

Service Coverage by Result Code Family#

Each Clean Suite service documents its result codes on its reference page. Use this table to navigate to the correct page for the code you need to understand.