Connect Customer Thermometer

Customer Thermometer is a one-click customer satisfaction product. Your client clicks one of four colored icons in an email or an email signature, and that click is the response — no form, no login, no survey page. It also calculates Net Promoter Score. Most MSPs fire a thermometer when a ticket closes and read the results back against the technician and the client.

Connecting Customer Thermometer to StackJack gives your AI assistant a family of ct_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

• Read the feedback — survey responses with the recipient detail attached, and the free-text comments people left with them
• Report the numbers — Happiness Factor, Net Promoter Score, Temperature Rating, response rate, and a response count you can break down by color
• Find the plumbing — your thermometers and your recipient lists, with the IDs everything else needs, plus how many sends you have left
• Survey a client (on Pro plans) — send a thermometer to one person, for example when a ticket closes
• Keep the data straight (on Pro plans) — add a recipient to a list, bring historical responses in from another survey product, remove a response, and unsubscribe an address

How StackJack authenticates to Customer Thermometer

Customer Thermometer gives you a single API key. You paste it into StackJack and that is the whole setup — no client ID, no second secret, nothing to renew on a schedule and no web address to enter.

Use the sub-API key, not the Super API key

Customer Thermometer shows you two keys on the same page and they are not interchangeable in practice:

• The sub-API key is the one to use. Customer Thermometer describes it as only for talking to its API, and StackJack sends it in a request header where it stays out of web addresses and server logs.
• The Super API key gives full access to the whole account and is designed to travel inside the web address itself, which is where it ends up in proxy logs and error messages. StackJack never sends a key that way, so there is no reason to paste this one in.

Steps

1. Open API Information in Customer Thermometer. Sign in, open the menu at the top right, choose Automations, then API Information. You need to be an owner, or have global admin rights, to see this page.
2. Copy the sub-API key. Treat it as a password: anyone holding it can read every response in the account and send surveys from it.
3. Paste it into StackJack. Open Connectors, choose Customer Thermometer, and paste the key. There is nothing else to enter.
4. Run a Test Connection. StackJack checks the key by asking Customer Thermometer how many sends you have left — a question that reads no customer data and changes nothing.

If you ever think the key has been exposed, Customer Thermometer replaces it on request. There is no self-service rotation, so plan a short gap: the connector stops working the moment the old key is retired and starts again as soon as you paste the new one in.

What to know before your AI uses this connector

Everything is account-wide, because Customer Thermometer has no idea who your clients are

This is the most important thing about this connector. Customer Thermometer has one account per subscription, one set of thermometers, lists and blasts inside it, and one key that sees all of it. Your individual client companies do not exist in it as a concept. They exist only as data — a company name written on each recipient, plus whatever separation you built yourself out of different recipient lists and different blasts.

So an unfiltered satisfaction figure covers every client you survey, and reporting it as one client's score is simply wrong. Two ways to narrow it:

• Filter by blast, which works if each client's surveys go out as their own blast. This is the cleanest option and it is worth organizing for.
• Filter on the company name in the results. Your assistant can do this after the fact, but only if the company name was set when the survey was sent — so set it on every send.

If you run several separate Customer Thermometer accounts, add one connection per account instead. See Several customers below.

Four tools change something real

Read tools change nothing. Four of the five write tools do something you cannot take back, and each is marked destructive:

• Sending a survey emails a real person at your client and uses one of your send credits. It cannot be recalled.
• Logging a response writes satisfaction data that looks exactly like a genuine one. It moves every score the account reports, and it can fire your email and webhook notifications on the way in. It exists to bring history in from another survey product — it is not a way to record something a client told you on the phone.
• Deleting a response moves it to a bin Customer Thermometer empties on its own after 30 days. There is no way to restore it through the connector, only inside the product and only within that window.
• Unsubscribing an address stops every future survey to that person, across every thermometer and every list. Customer Thermometer documents no way to reverse it, so treat it as permanent.

Adding a recipient to a list is the one write that is not destructive: nothing is sent, nothing is deleted, and no notification fires.

Whether your AI application asks you to confirm before running a destructive tool depends on that application's own settings — see Destructive tools and confirmation. Review that setting before you let an assistant near the four above.

Sending without naming a blast makes a mess that cannot be cleaned up

If you send a survey and do not name an existing blast, Customer Thermometer creates a brand-new blast containing that one person. Send to twenty people that way and you have twenty single-person blasts, every per-blast report becomes meaningless, and there is no way to merge or remove them through the connector. Name a blast, or send against a recipient list.

Check your send credits before a bulk send

When the account has no send allowance left, Customer Thermometer accepts the request, sends nothing, and reports it as a success. StackJack recognizes that reply and reports it to your assistant as a failed send instead, so a survey is never reported as sent when it was not. It is still worth asking for the remaining send quota before a bulk send, so you find out before you are halfway through a list.

The results come back as XML, not as the usual structured data

Four of the reads — responses, comments, thermometers and recipient lists — come back from Customer Thermometer as XML documents, and the score tools come back as a single bare number. Customer Thermometer offers no alternative format, and StackJack passes the reply through exactly as it arrives rather than reshaping it. Assistants generally read both fine; it is worth knowing because these replies look different from every other connector's.

There is no paging, so narrow by date

There are no pages here. Each list read returns the most recent responses, newest first, with a size you can ask for, and the way to reach further back is to move the date window rather than to ask for more. Dates use the plain year-month-day form.

Plans and limits

Read tools are available on the Free tier. Sending, logging, adding, deleting and unsubscribing are Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated Customer Thermometer tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Customer Thermometer publishes no rate limit, so StackJack paces requests conservatively and backs off on its own if it is throttled, which usually makes a large report slower rather than failed. Pacing smooths a burst; it does not guarantee that every call arrives. Retries are bounded, so a wide enough read can still come back throttled or time out. Narrow the read, honour any retry delay the vendor sends, and check whether a write landed before repeating it — see Retrying a failed or timed-out write.

Several customers

If you hold more than one Customer Thermometer account, add one connection per account from the connector's card, name each one after the account, and your AI names it on each call. Omit the name and the call runs against your default connection. Pin an endpoint to one connection when an AI should never reach past a single account. See Several connections of one connector.

Note that this only separates whole accounts. Inside one account there is still no client separation — see the account-wide warning above.

Troubleshooting

"Customer Thermometer rejected the API key" — the key is wrong, was replaced, or is the wrong one of the two. Re-read the sub-API key from Automations, then API Information, and paste it again. Remember you need owner or global admin rights to see that page at all.

"Customer Thermometer did not send the survey" — the account could not send it, almost always because the send allowance is used up. Nothing was sent, nobody was emailed, and no response was recorded, so the survey can be sent again once there is allowance. Check the remaining send quota and top up or upgrade in Customer Thermometer.

A score covers the wrong clients — the read was not filtered. Customer Thermometer has no concept of your individual clients, so a score with no blast filter and no date range covers everyone you survey. Ask for it by blast, or ask your assistant to filter on the company name.

Responses are missing from a report — check the date window and the size you asked for before assuming the data is gone. There is no paging, so a report that looks short is usually a window that was too narrow or a size that cut the list off.

Nothing works at all and the key is definitely right — confirm the Customer Thermometer account itself is active and that the key was issued from the account that holds the thermometers you are asking about.

Customer Thermometer tools

ct_ · 15 tools · Free 10 · Pro 5

Responses & Comments

Scores & Aggregates

Account Discovery

Survey Dispatch

Response & Recipient Management