[Customer Thermometer] List the free-text comments people left on their survey responses — the half of the feed a human actually wants to read, because a red score with a comment is actionable and a red score alone is a number. Returns an XML DOCUMENT verbatim, not JSON. Newest first; the vendor returns the most recent 200 when no limit is given. WHOLE-ACCOUNT, exactly like ct_list_responses: narrow with blastId or filter companyName yourself. No paging — move fromDate and toDate to reach further back.

[Customer Thermometer] List survey responses with the recipient data attached — the CSAT feed itself, and the tool to start from. Returns an XML DOCUMENT verbatim, not JSON: Customer Thermometer publishes no JSON format for this method, so parse the XML or read it as text. Newest first; the vendor returns the most recent 200 rows when no limit is given. WHOLE-ACCOUNT: Customer Thermometer has no concept of your individual clients, so this covers every client you survey — narrow with blastId if you organized a blast per client, or filter the companyName field in the response yourself. There is no paging of any kind, so reach further back by moving fromDate and toDate rather than asking for a bigger limit.

[Customer Thermometer] Count survey responses, optionally at one temperature. Returns a BARE INTEGER. This is the tool that gives the other scores a denominator — a happiness figure with no sample size behind it is not reportable — and counting by temperature (4 = red) is the fastest read on how many unhappy responses landed in a period. WHOLE-ACCOUNT unless you pass blastId. The vendor applies NO default limit here, so with no filter at all this counts every response the account holds.

[Customer Thermometer] Get the Happiness Factor as a percentage. Returns a BARE INTEGER — the digits and nothing else, with no sample size or period alongside, so pair it with ct_count_responses when you need to say what it was calculated from. WHOLE-ACCOUNT unless you pass blastId: Customer Thermometer has no concept of your individual clients, so an unfiltered figure mixes every client you survey and must not be reported as one client's score. The vendor applies a default limit of 100 most-recent responses when limit is omitted, which is a rolling window rather than a period — pass fromDate and toDate for a calendar month.

[Customer Thermometer] Get the Net Promoter Score. Returns a BARE INTEGER, and it MAY BE NEGATIVE — NPS runs from -100 to 100, so a leading minus sign is a real value and not an error. WHOLE-ACCOUNT unless you pass blastId. Unlike the happiness and temperature scores, the vendor applies NO default limit here: with no filter at all this is the account's lifetime NPS. The vendor also documents that limit should be combined with a blast or a date range rather than used on its own.

[Customer Thermometer] Get the survey response rate as a percentage. Returns a BARE INTEGER. This covers EMAIL Thermometer blasts only — surveys embedded in an email signature are excluded from the calculation at account level, so a low figure on an account that mostly uses embedded surveys is a measurement artifact rather than disengagement. WHOLE-ACCOUNT unless you pass blastId. The vendor applies a default limit of 100 most-recent sends when limit is omitted.

[Customer Thermometer] Get the Temperature Rating as a percentage — Customer Thermometer's weighted blend of the four icon choices, which is a different measure from the Happiness Factor rather than a restatement of it. Returns a BARE INTEGER. WHOLE-ACCOUNT unless you pass blastId. The vendor applies a default limit of 100 most-recent responses when limit is omitted; pass fromDate and toDate for a calendar period.

[Customer Thermometer] Get the number of survey sends left on the account. Returns a BARE INTEGER. Check it before a bulk send: ct_send_survey answers 0 and sends nothing once the allowance is gone, which reads as a success to anything that only checks for an error. Takes no parameters.

[Customer Thermometer] List the recipient lists in the account with their names and IDs. The second half of the plumbing: ct_send_survey and ct_add_recipient_to_list both need a list ID and this is the only place one comes from. Returns an XML DOCUMENT verbatim, not JSON. Takes no parameters and returns the whole account in one call. Worth reading before a reporting question too — because Customer Thermometer has no concept of your individual clients, a per-client list is usually how an MSP has organized them.

[Customer Thermometer] List the thermometers in the account with their names and IDs. Start here before sending anything: ct_send_survey needs a thermometer ID and this is the only place one comes from. Returns an XML DOCUMENT verbatim, not JSON — Customer Thermometer publishes no JSON format for this method. Takes no parameters and returns the whole account in one call; there is no paging and no filter.

[Customer Thermometer] SENDS A REAL EMAIL to a real person and spends one of the account's send credits. It cannot be recalled once sent, which is why it is marked destructive. Returns a BARE INTEGER — the blast ID the send landed in. When the account cannot send (most often the send allowance is used up) Customer Thermometer answers a bare 0 with a success status; StackJack reports that as an error instead of a result, so a value returned from this tool always means the email actually went out. Check ct_get_send_quota first when sending more than a handful. GET thermometerId from ct_list_thermometers and listId from ct_list_recipient_lists; both are required and cannot be guessed. IMPORTANT: leaving blastId empty makes Customer Thermometer create a brand-new blast for this one person — send to several people that way and the account fills with single-person blasts and every per-blast report becomes useless, with no API method to merge or delete them. Pass the blastId of an existing blast when sending to more than one recipient. The recipient is also appended to listId as a side effect.

[Customer Thermometer] Add one recipient to an existing recipient list. Additive and safe: nothing is sent, nothing is deleted, and no notification fires — which is why this is the one write here that is not marked destructive. Returns the email address as a BARE STRING. Get listId from ct_list_recipient_lists. Setting companyName is worth doing on every add, because it is the only field that ties later responses back to one of your client companies.

[Customer Thermometer] Delete one survey response from reporting. Destructive: the response leaves every score and every report immediately, and the row goes to a bin Customer Thermometer empties automatically after 30 days — there is no API method to restore it, so the only recovery is inside the product and only within that window. Returns a BARE INTEGER. Get the response ID from ct_list_responses.

[Customer Thermometer] Write a survey response directly into reporting, as if a real person had clicked. Destructive: the row is indistinguishable from a genuine response afterwards, it changes every score the account reports, and it CAN FIRE the account's email and webhook notifications on the way in. This exists to migrate historical responses in from another survey product — it is not a way to record satisfaction you were told about verbally, and using it that way corrupts the client's CSAT numbers. Returns a BARE INTEGER. Get thermometerId from ct_list_thermometers.

[Customer Thermometer] Add an email address to the account's unsubscribe list, which stops EVERY future survey to that person across every thermometer and every list. Destructive and effectively PERMANENT: Customer Thermometer documents no re-subscribe method, so once an address is suppressed there is no way to reverse it through this API. Do not use it to tidy a list — removing a client contact by mistake silently ends their CSAT history. Returns a BARE STRING. The optional notify flag emails the person to tell them they were unsubscribed.