A low score should reach your team the same day.

Build a rule from an answer's score, category (such as detractor or promoter) or sentiment. Combine conditions with "all of" or "any of". Score and category rules apply to one campaign. Sentiment rules can cover every campaign.

• Score 6 or lower on your customer NPS survey.
• A negative comment on any survey.
• A promoter answer, so your team can say thanks.

Every alert has a delivery record: pending, delivered or failed, with the number of attempts and the last error. If the destination is briefly down, Pulseri makes up to five attempts over about 20 minutes. If it rejects the message for good, such as a deleted webhook, you see the failure straight away. Each rule alerts at most once per answer, so a busy day will not flood your channel.

Pulseri can call your system when a new answer or person arrives or a campaign changes. Each call carries an X-Pulseri-Timestamp header, a unique X-Pulseri-Delivery id and an X-Pulseri-Signature header, an HMAC-SHA256 signature of the timestamp and the body. Trust only calls that match and are less than five minutes old.

import { createHmac, timingSafeEqual } from 'node:crypto'

function isFromPulseri(rawBody, timestamp, header, secret) {
  if (Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false
  const expected = 'sha256=' + createHmac('sha256', secret).update(`${timestamp}.${rawBody}`).digest('hex')
  const a = Buffer.from(expected)
  const b = Buffer.from(header ?? '')
  return a.length === b.length && timingSafeEqual(a, b)
}

Your system can also start a survey by sending Pulseri an event, with a service account key or the signed generic webhook.

Low scores that warn of churn are one use for these alerts. The customer churn guide shows a rule to copy.

See the API and assistants