Add Simplesat rating choices to the emails your helpdesk or email platform sends, or to your email signature. You can also generate a plain survey link to share.

The code shows the metric question (the question your metric rating comes from), and each rating choice is a link. CSAT and 5-Star choices appear as images or emojis, and NPS and CES choices appear as numbers.

When a customer clicks a choice, the survey opens on a Simplesat survey page, and the page saves that rating as soon as it opens. The page then shows the questions after the metric question and skips any placed before it. The rating counts even if the customer leaves without answering anything else.

The code in the email is fixed once you generate it, while the survey page and everything after the click update as soon as you change them.

You need the Manage surveys permission to choose a delivery method and save its settings. Owner and Admin have it.

The code goes out with every email built from the template you paste it into. Your sending tool decides which emails carry a survey and how often, so set that up there.

A survey has one delivery method, and Publish lists the delivery methods only while the survey has none. To move the survey to a different destination, remove its current delivery method and set it up again:

Customers can still respond to the survey while it has no delivery method.

If your sending tool is listed, select it. Simplesat adds that tool's merge fields to the links. A merge field is a placeholder your tool swaps for a real detail, such as the recipient's email address or the ticket ID, when it sends the message.

For Generic Embed, type your tool's merge fields into Rating placeholders for the customer, team member and ticket details you want in the links. The Placeholders for common helpdesks link next to the form lists merge fields for common tools. Use a fixed value only when it should be the same for every recipient.

On Configure, Generic Embed surveys get Capture customer information from anonymous surveys, which named destinations don't have:

If your destination is also a Simplesat integration, you can connect responses directly with its tickets. On Publish, under Connect responses directly with tickets, click Configure integrations. That opens the tool's integration page at its Configure integrations section, where you turn on the integrations you want.

Pick the output that suits where you're pasting it:

Visual is offered on Generic Embed and some named destinations. Where it isn't, the window opens on HTML.

A signature survey goes out with every email that person sends, and its links keep working in emails they've already sent.

Gmail and Outlook signatures have no merge fields, so use Generic Embed. Every recipient gets a link with the same details, and nothing in it says who the recipient is. Instead, the customer information question asks customers for their name and email on the survey page. For team member details, you can either:

Copy the Visual output, paste it into your Gmail or Outlook signature settings, and save the signature.

If your signature-management tool is listed as a destination, select it instead of Generic Embed. Its merge fields add each sender's details, so one code works for your whole team. Briskine, CodeTwo and Exclaimer also add the recipient's email address.

Link opens the survey from the beginning, and nothing is recorded until the customer answers. Use it when you want to share a link rather than rating choices, such as in a QR code or on an invoice.

Every destination except Intercom offers Link. For messages a listed tool sends, use that tool's destination so the tool can fill in its merge fields. For QR codes, PDFs or anywhere else that can't fill those fields, use Generic Embed. Unfilled merge fields can break the link or show up as literal text in the response.

On Generic Embed, if Rating placeholders is empty, responses come in with no customer or team member unless the customer answers the customer information question.

Direct email delivery and Web-embed surveys have no Link output. To get one, duplicate the survey and move the copy to Generic Embed:

Simplesat adds the survey and rating to each rating link. Customer, team member and ticket details come from your destination's merge fields or Rating placeholders.

You only need this if you're editing the links by hand.

On Generic Embed, the links look like this:

The first is the link behind each rating choice in Visual and HTML. The second is the Link output. From left to right, a link has these parts:

You can add fields of your own. Add &t_<name>=<value> to save a ticket field, or &tm_<name>=<value> to save a team member field, for example &t_priority=high. Add it to every rating link in the pasted code, or to the Link output. The value can be one of your tool's merge fields, which your tool fills in when it sends the email. That's how a helpdesk field such as a ticket's channel reaches Simplesat.

These fields show in the response's details, you can filter on them in Feedback, and they appear in exports. Only t_ fields can fill a {{ticket.<field>}} variable in a call-to-action button's link on the confirmation page.

Keep the rating, the survey token and source exactly as generated. If a link's source value isn't one Simplesat knows, the link records no rating. If you edit the ticket ID, use only letters, numbers, dots, hyphens and underscores.

Use your sending tool to change the sender name and address, subject, template, styling and text around the survey. Whether images appear depends on your tool and the customer's email client.

The rating block carries its own inline styles, so it can look different from the rest of the email. You set its look on Publish before you generate the code.

Pasted code doesn't update itself. If you change any of the following, generate the code again and replace every copy:

You don't need new code for changes to the questions after the metric question, their logic, the confirmation page and its call-to-action buttons, or the survey page's branding.

Each code belongs to one survey, so any other survey needs its own code, including a duplicate.

A rating is saved the moment the survey page opens from a rating link. That means software that opens and loads pages from emails, such as some mail security scanners, can leave a rating. If the link carries a customer email, the rating is recorded under that customer.

Every rating that arrives this way gets an automatic spam check, and ratings flagged as spam are kept out of your feedback. The check doesn't catch every automated click. These help:

For the full picture on spam checks, automated clicks and duplicates, see Anonymous, spam and duplicate feedback.

The link reached Simplesat but doesn't lead to an active survey. Possible causes:

Check Expiration settings on Configure:

That's expected. The click answered the metric question, so the page saved that rating and moved on to the next question. Questions placed before the metric question are skipped too. To start customers from the beginning, use the Link output.

If the saved rating isn't the one the customer clicked, check the link behind each choice in the pasted code.

The pasted code is the Link output, which carries no rating. Copy Visual or HTML from Copy your embed code instead.

On Generic Embed, the links carry only what was in Rating placeholders when you generated the code, even if your tool has its own destination. Fill the fields in, generate the code again, and replace it.

On a named destination, either your tool didn't fill its merge field when it sent the email, or the destination doesn't carry that field. To check the first, look at a link in a sent email. As for the second, signature tools carry no ticket ID, and Symprex, WiseStamp and Xink carry no customer email.

Simplesat doesn't save invalid email addresses. In a sent email, check the customer_email value in a rating link. It should contain the recipient's email address, not an unfilled merge field or another value.

The size limit comes from your tool. Every rating choice has its own full link, so the code grows with the number of choices, the text labels and the values in each link. To shorten it, use fewer rating choices, turn labels off or fill fewer fields. The Link output is a single URL.

Some email clients block images until the reader allows them. For CSAT and 5-Star, these settings on Publish help:

NPS and CES ratings are numbers, not images, and the Link output needs no images at all. Generate the code again after changing any of these.

Generate embed code is available only when the survey's delivery method is External email embed. If the survey uses another delivery method, open its three-dot menu, select Change delivery method, then select Remove current delivery method. Then choose External email embed on Publish. If you chose Intercom, use Send as an app or Send as text instead.

Open the survey's Publish tab. The heading shows its destination.

Yes. Use Generic Embed, put your mail tool's merge field for the recipient's address into Customer details → Email address, and paste the code into the email your tool sends. Or send the Link output.

Yes. On Configure, under Capture customer information from anonymous surveys, turn off Show question if customer info isn't already associated with the answer. Customers whose link already carries their email are never asked.

No. Unsubscribing stops the surveys Simplesat sends, and you're the one sending the survey in your signature.

No setting does that. Signature links normally carry no ticket ID, so each click is a new response. Suppression and unsubscribes apply only to surveys Simplesat sends.

No, there's no blocklist for an address or a domain. Every rating click gets the automatic spam check. On Generic Embed, Require the question and hide all anonymous responses also hides ratings that arrive with no email address.

No.