You can put a Simplesat survey in the emails a Trengo automation rule sends, such as the email that goes out when a ticket closes. The survey works without connecting Trengo.
When you connect Trengo, each response also shows up in Trengo. It goes on its ticket as an internal note, in ticket fields and as labels. In Simplesat, each response gets its ticket, customer and agent from Trengo.
What the Trengo integrations do
You switch each integration on separately with Activate integration. None of them has settings.
Integration | Listed under | What it does | Where it shows |
Update contact custom fields after receiving a Simplesat rating | Survey integrations | Writes the rating and sentiment to custom fields on the Trengo contact | The contact in Trengo |
Pull ticket details | Ticket integrations | Adds the ticket, its contact and its assigned agent to the response | The response, in Simplesat |
Add an internal note to a ticket after receiving a Simplesat rating | Ticket integrations | Adds the response to the ticket as an internal note | The ticket |
Update ticket custom fields after receiving a Simplesat rating | Ticket integrations | Writes the rating, sentiment and comment to custom fields on the ticket | The ticket |
Update ticket labels | Ticket integrations | Labels the ticket with the rating and sentiment | The ticket |
The ticket integrations run on responses to every survey set to External email embed with the Trengo option, as described in Send surveys from Trengo below.
Tip: Switch on Pull ticket details whenever you use the Trengo survey. It replaces the made-up customer email from the survey link with the email of the ticket's real contact. Update contact custom fields after receiving a Simplesat rating also uses it to find the Trengo contact.
Before you start
The Trengo integrations are available on every Simplesat plan. To connect Trengo and switch integrations on, you need the Manage integrations permission. Owner and Admin have it by default.
If your security team asks what a connected tool can read and write, send them Integration security, permissions and data flow.
Connect Trengo
In Trengo, open the developer settings at app.trengo.com/admin/developers/rest and create an API key.
Copy the key now. Trengo shows it only once.
In Simplesat, on the Integrations page, open Trengo and click Authenticate.
Paste the key into API Key and click Authenticate.
When the page shows Authenticated with Trengo, click Activate integration on each integration you want.
Before you rely on an integration, test it with a real ticket. Testing an integration end to end shows how.
Send surveys from Trengo
Create or open the survey and choose External email embed.
Under Choose where to add your survey, choose Trengo.
On Publish, click Generate embed code.
Choose HTML and click Copy survey.
In Trengo, open the automation rule that should send the survey, or create one. For example, use a rule that sends an email when a ticket closes.
In the rule's email, switch to code view and paste the HTML where the survey should appear. Switch back to check the preview, then save the rule.
To test it, close a ticket with yourself as the contact and answer the survey from the email.
When Trengo sends the email, it fills in the placeholders in the survey links. That's how each response knows its ticket, agent and company:
What the link carries | Trengo placeholder |
Ticket ID |
|
Team member first name |
|
Team member last name |
|
Team member ID |
|
Company |
|
Customer email |
|
The customer email is made up. It's the Trengo profile name followed by @email.com, which isn't a real address. Pull ticket details replaces it with the email of the ticket's contact, at least five minutes after the response arrives. Without Pull ticket details, responses keep the made-up address.
Placeholders and merge fields explains how placeholders work in every tool.
Feedback in Trengo
Simplesat writes to Trengo at least five minutes after a response arrives. It writes again whenever the response changes, for example when the customer answers another question later. Writing feedback back, and mapping the fields explains the timing.
Add an internal note to a ticket after receiving a Simplesat rating
This adds the response to its ticket as an internal note, with every question and answer. If the response changes, a second note is added.
Update ticket custom fields after receiving a Simplesat rating
This writes these custom fields on the ticket:
Simplesat rating: the metric ratingSimplesat sentiment: the sentimentSimplesat comment: the customer's comment on the metric question
If the fields don't exist in Trengo, the integration creates them the first time it runs. Simplesat rating is a number field and the other two are text fields. It finds the fields by name, so don't rename them.
Update ticket labels
This adds two labels to the ticket, one for the rating and one for the sentiment. The rating label is simplesat_ followed by the metric, an underscore and the rating. For example: simplesat_csat_4, simplesat_nps_9, simplesat_ces_6 or simplesat_5-star_5. The sentiment label is simplesat_sentiment_positive, simplesat_sentiment_neutral or simplesat_sentiment_negative.
If the labels don't exist in Trengo, the integration creates the whole set the first time it runs.
When the rating changes, it removes the ticket's earlier Simplesat labels and adds the new ones. 5-star rating labels are the exception. They stay on, so a ticket whose 5-star rating changes ends up with two rating labels.
Heads up: An NPS rating of 2 and a CES rating of 3 get only the sentiment label. That's because the labels the integration creates for them are named simplesat_nps_ and simplesat_CES_3. To fix this, create a Trengo label named simplesat_nps_2. If Trengo shows a label named simplesat_CES_3, rename it to simplesat_ces_3.
Update contact custom fields after receiving a Simplesat rating
This writes the rating to a custom field on the Trengo contact. The field depends on the survey's metric: Latest CSAT, Latest CES, Latest NPS or Latest 5-star. It writes the sentiment to Latest sentiment.
If the fields don't exist in Trengo, the integration creates them the first time it runs. Latest sentiment is a text field and the rating fields are number fields. It finds the fields by name, so don't rename them.
It doesn't write to the contact when a response first arrives, because the response isn't linked to its Trengo contact yet. Once Pull ticket details has made that link, the integration writes the next time the response changes, for example when the customer answers another question. So a response that never changes never reaches the contact fields, even if the customer has answered your surveys before.
Keep Pull ticket details on. Nothing else links a response to its contact.
Ticket, customer and agent details in Simplesat
Each response starts with the ticket ID, agent and company that Trengo filled into the survey link. Attribution: linking feedback to tickets, customers and agents explains how Simplesat connects them.
Pull ticket details reads the ticket at least five minutes after the response arrives, and again when the response changes. It replaces the response's details with these from Trengo:
The ticket's subject.
The ticket's channel and team, as the ticket fields
channelandteam, and a link to the ticket in Trengo, asurl.The ticket's contact as the customer, with their name, email and Trengo contact ID. The contact's profile name becomes the company, and a link to the contact in Trengo becomes the customer attribute
URL.The agent assigned to the ticket, as a team member with the role Assignee, with their name, email and Trengo user ID.
Change the Trengo account or API key
To use a new API key, or to connect a different Trengo account:
Click Revoke access.
Click Authenticate and paste the new key.
Any integration that was on before switches back on by itself. Check that each one you use shows Deactivate integration. If one is still off, click Activate integration.
Responses that arrive between Revoke access and Authenticate aren't written to Trengo, so do the steps in one go. Survey code that's already in your Trengo rules keeps working.
Heads up: If the API key is deleted in Trengo, the integrations stop working, but the page still shows Authenticated with Trengo. Create a new key and reconnect with the steps above.
Troubleshooting
My Trengo responses show a customer email ending in @email.com
The Trengo survey link fills in the customer email as the Trengo profile name followed by @email.com. Pull ticket details replaces it with the email of the ticket's contact, at least five minutes after the response arrives. Switch it on, and new responses get the real contact.
Feedback doesn't show up on my Trengo tickets
Check each of these:
The survey is set to External email embed with the Trengo option, and the survey code in your Trengo rule includes
[ticket.id].At least five minutes have passed since the response arrived.
Each integration you want shows as active. If you've reconnected Trengo, any that were on before switch back on by themselves. Click Activate integration on any that's still off.
If none of these explains it, contact us and include the response's link.
Some of my tickets get a sentiment label but no rating label
An NPS rating of 2 and a CES rating of 3 get no rating label. That's because the labels the integration creates for them are named simplesat_nps_ and simplesat_CES_3. Create a Trengo label named simplesat_nps_2. If Trengo shows a label named simplesat_CES_3, rename it to simplesat_ces_3. Responses that arrive after that get both labels.
My ticket has two Simplesat rating labels
When a 5-star rating changes, the earlier 5-star label stays on the ticket and the new one is added. Remove the earlier label in Trengo.
The Latest CSAT and other contact fields stay empty in Trengo
The contact fields update only when a response changes after it arrives, for example when the customer answers another question. If a customer answers once and the response never changes, the fields stay empty.
Update contact custom fields after receiving a Simplesat rating writes to the Trengo contact that Pull ticket details links to the response, so switch on Pull ticket details too. The integration also finds the fields by name. Check that Latest sentiment, Latest CSAT, Latest CES, Latest NPS and Latest 5-star haven't been renamed.
My Trengo integrations stopped working, but the page still says Authenticated with Trengo
Simplesat doesn't check the connection again after you connect. If the API key is deleted in Trengo, the integrations fail and the page still shows Authenticated with Trengo. Create a new key in Trengo. Then click Revoke access, click Authenticate and paste the key. Any integration that was on before switches back on by itself. Check that each one you use shows Deactivate integration, and click Activate integration on any that's still off. Integration error messages and what they mean explains what the page can tell you.
FAQ
Do I need to connect Trengo to send surveys?
No. The survey works in your Trengo rules on its own. But without a connection you can't use Pull ticket details, so responses keep the made-up customer email from the survey link.
Can I choose which surveys the Trengo integrations run on?
No. The Trengo integrations have no settings. The ticket integrations run on every survey set to External email embed with the Trengo option.
What do the simplesat_ labels on my Trengo tickets mean?
They come from Update ticket labels. The rating label names the metric and the rating, so simplesat_nps_9 is an NPS rating of 9. The sentiment label shows the response's sentiment. A new rating replaces both labels, except 5-star rating labels, which stay on.