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

Go from record to record without a trip back to the list

Get started

Install a TAF package, set it up, and give it to your users.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case. Our support team answers by email.

Open a support case

Our support team answers by email

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

We write these pages for Salesforce admins.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Change log

What changed in each release

Compatibility

Editions and seasonal releases

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

Contacts with the email contactsamplesign@gmail.com appear after Send Signature Request

This article tells you what to check, and how to fix the problem.

Last updated 12 Oct 2026

The short version

Simple Signature makes a temporary Contact for the preview, then deletes it as the user who sent the request. If that user cannot delete Contacts, the Contact stays. Give the user Delete on Contacts, or delete these Contacts each night with a Flow.

What to do

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.

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

Use this when your users must not delete Contacts. The Flow runs as an automated user.

  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 contactsamplesign@gmail.com, and Account ID Is Null True.
  6. Save the Flow, for example as Delete Simple Signature preview Contacts. Click Activate.

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 contactsamplesign@gmail.com. Tick the Contacts. Click Delete.

To check, send a signature request as one of these users. Search Contacts for contactsamplesign@gmail.com. With Fix 1, no new Contact shows. With Fix 2, it 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 into it. Our support team answers by email.