The problem
Sentry has user ids. PostHog has person ids. Stripe has customer ids. Crisp has email addresses. The same company is four different strangers in four tools, and the question “who did this hit?” is answered by opening each and matching by hand.
So the customer email after an incident goes to everyone, or to no one. Neither is what the account paying €499 a month expects.
What Vesqo does
Vesqo makes one account per customer and attaches every source's record of them to it: the Stripe customer by id; the Sentry user, the PostHog group or person, the support contact and the CRM company by the domain of their email. From then on an error, a conversation, a payment and a deal about the same company land on the same page.
When a regression is written, the accounts behind the errors, the failed payments and the support threads in its window are listed on the signal, each with what they pay and a link to their page: what else happened to them this month, when they renew, what the CRM says.
The list is the write-up's audience. An automation can post it to Slack, or open a task to write to each one, in order of what they pay.
Example
Questions it answers
- Which customers were affected by this incident, and what do they pay?
- Who wrote to support about this, and are they paying customers?
- Which high-value customers encountered this error?
- Has Cortex been active since the fix?