Customer success and sales
Log what an account asked on a call, on their behalf, and tell them when it ships.
CSMs and sales log requests for customers from the dashboard, the API or Claude. The vote counts for the account; they hear back when it ships.
Set it up
Add the vote from the request page
They asked too: pick the person, set importance (nice to have, important, critical) and note what they said. They now follow the request.
Inbox → request → Who asked
Or from your CRM or support tool
File a request on behalf of a user, or add their vote with importance. externalId keeps it idempotent.
Settings → API
curl -s https://theyasked.me/api/public/v1/posts/audit-log/votes \ -H "Authorization: Bearer $KEY" -H 'content-type: application/json' \ -d '{ "userId": "u_1200", "importance": "critical" }'Or from Claude after the call
With write scopes, Claude can find the matching request and vote for the customer (vote_on_behalf), or log a new one (create_post).
Using theyasked, Dana at Atlas Freight asked for an audit log on today’s call. It blocks their SOC 2 audit. Add her vote as critical.Close the loop
When it ships, the changelog entry emails everyone who asked, including the people you added.
Changelog → New entry
What you learn
- Critical votes
- Severity that plain vote counts hide.
- Account briefs
- Everything one company asked, with MRR and renewal date.
- Revenue at stake
- Requests logged by CSMs count like any other vote.
Who it's for
- Customer success managers
- Before a QBR: what did this account ask, and what shipped.
- Account executives
- Log the blocker from the deal, not just a Slack message.
- Support leads
- Turn repeated tickets into one request with every customer on it.