Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify and geocode Salesforce addresses

Highlighter

Colors, renames or hides Salesforce fields

List Browse

Browse Salesforce records without list clicking

Get started

Install, configure and roll out a TAF package.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article per task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case and a person reads it.

Open a support case

The fastest route to an answer

Give us access

Let us sign in and see the problem

Support home

Guides, release notes and the case form

Troubleshooting

Search by the error text you see

Documentation

Written for admins, not for developers.

Implementation guides

Guides for all four apps are ready.

How-to articles

One task per article

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo
Simple Signature · Troubleshooting

Contacts named [email protected] appear after Send Signature Request

What to check, and how to fix it.

Last updated 12 Oct 2026

What you see

Each time a user clicks Send Signature Request, a new Contact appears with the email address [email protected]. The Contact has no Account. Over time, many of these Contacts pile up.

Why it happens

To show the document preview before the request goes out, Simple Signature makes a temporary Contact. After the request is made, Simple Signature deletes that Contact. It deletes it as the user who sent the request.

When that user has no Delete permission on Contacts, the delete fails, and the temporary Contact stays.

What to do

Pick one of these two fixes.

Fix 1: give these users Delete permission on Contacts

  1. Open Setup. In the Quick Find box, type Users. Click Users. Click a user who sends signature requests. Note the profile and the permission sets.
  2. In the Quick Find box, type Permission Sets, or Profiles if you set object access on profiles. Click the one that gives the user access to Contacts.
  3. Click Object Settings. Click Contacts. Click Edit.
  4. Under Object Permissions, tick Delete. Click Save.

Simple Signature now deletes the temporary Contact after each request.

Fix 2: delete the temporary Contacts every night with a Flow

Use this when your users must not delete Contacts.

  1. Open Setup. In the Quick Find box, type Flows. Click Flows. Click New Flow.
  2. Click Schedule-Triggered Flow. Click Create.
  3. Set the schedule: a start date, a time at night, and Frequency Daily.
  4. Add a Delete Records element. Set How to Find Records to Delete to Specify conditions. Set Object to Contact.
  5. Add the conditions: Email Equals [email protected], and Account ID Is Null True.
  6. Save the Flow with a name, for example Delete Simple Signature preview Contacts. Click Activate.

The Flow runs as an automated user, so it can delete the Contacts even when your users cannot.

Remove the Contacts that already exist

Fix 2 removes them on its first run. With Fix 1, delete them once yourself. Open Setup. In the Quick Find box, type Mass Delete Records. Click Mass Delete Contacts. Search for Email equals [email protected]. Tick the Contacts. Click Delete.

How to check it worked

  1. Send a signature request as one of these users.
  2. Search Contacts for [email protected]. With Fix 1, no new Contact shows. With Fix 2, the Contact is gone after the next nightly run.

Applies to

Simple Signature 5.8.x. This fix comes from a solved support case.

Was this helpful?

Related

Support

Still stuck?

Open a case and paste the exact error text. A person reads every case.