Skip to main content
Product screenshot showing draft queues, review controls, and send states. Signature settings control what gets appended to emails sent through Ergo. Review them before a team rollout so generated drafts do not duplicate sign-offs or footers.

Who can use this

  • Users sending email through Ergo.
  • Admins and RevOps teams standardizing outbound email setup.

Before you start

  • Connect the sender’s email account.
  • Decide whether to import an existing Gmail signature or enter one manually.
  • Review whether your workspace uses a sent-with-Ergo footer or similar marker.

Steps

  • Open email signature settings.
  • Review the current signature.
  • Import from Gmail when available, or save a manual signature.
  • Remove the signature if it should not be appended.
  • Toggle sent-with-Ergo footer behavior if your workspace exposes that setting.
  • Send a test draft to confirm the final email renders correctly.

What to expect

  • Signature settings can include signature HTML, last updated time, Google token status, and sent-with-Ergo footer state.
  • Draft body and signature are separate. Avoid manually adding a second signature block to the body.
  • Import from Gmail depends on Google access.
  • Signature changes affect future sends; already-sent emails do not change.

Common issues

  • Gmail import fails because the Google grant is missing or expired.
  • A user adds a manual sign-off in the body and also has a saved signature.
  • The signature uses formatting that renders differently in the provider.
  • The footer setting is changed but old drafts still contain manually typed footer text.
Last modified on June 8, 2026