Overnight, asks came in by chat, email and the request form.
Inbox and formsBuild what customers ask for.
Every ask lands on one record, counted, with the people who made it.
1
Mobile appUnder reviewSupport chats, SMS
ACUMHO2352$610K2
Bulk importIn progressSupport, Sales
SOPIVA1247$540K3
Public API accessPlannedEmail, calls, forms
NWGXIN838$720K4
Dashboard customizationUnder reviewSuccess QBRs
STDUWA1529$480KRollupAsks counts every linked ask. ARR asking adds up the accounts behind them.
Sample workspace
Feedback, straight from the source.
- Logged by Stella
Can we pull our records into Snowflake?
- Filed by an agent
Any public API yet?
- Logged on the call
API access came up twice in our QBR.
- Logged by Stella
We need the API before renewal.
- Logged by Stella
Webhooks when a record changes?
- Creates the request
Scoped API keys per workspace
- 212 asks from last year's spreadsheetImported
One request, end to end.
A record, linked to every account and person that asked.
- Your own fields
- Linked accounts and people
- Source conversation
- Status and severity
Ten tickets, one line on what they want.
- AI summary
- Auto-filled fields
- Search by meaning
- Approve before it writes
Sort by how many asked, or by the money behind it.
- Count of asks
- ARR rollup
- RICE or ICE formula
- A board per team
Set it to Shipped and the next steps run.
- Status workflows
- Owner notified
- Release-note sequence
- Weekly digest
Who to ask. Who to tell.
- See who asked most.Every ask is linked to a person and an account, so sort by asks and the list writes itself.
- Ask them before you build.Enroll them in an interview sequence with your booking link or a short form.
- Tell them the day it ships.The same list gets the release note.
Plan it where the asks live.
A day on the Product team.
Her triage view is sorted by asks, each request summed up.
Views and AI fieldsOn a Globex call, Stella logs the ask. One approval.
StellaShe groups the backlog by quarter and specs it with engineering.
Board views and docsThe API pull request merges. The synced table already shows it.
GitHub syncShe sets it to Shipped. The 16 people who asked get the release note.
Workflows and sequencesProduct feedback, plainly.
Is this a feature-voting portal?
No. A request is a record in the same workspace as your customers, linked to the accounts and conversations it came from, so there's no separate voting board to keep in sync.
Where do requests come from?
Email, SMS, chat, calls and Slack land in one inbox, where Stella logs the ask with one approval or a conversation agent files it. A feedback form creates the request directly, and an old backlog imports from CSV.
How do I prioritize by more than a count?
A rollup sums the ARR of every account asking, and a formula can score RICE or ICE from your own inputs, rollup included. Save the sort as a view and the whole team triages the same list.
Can I reach the people who asked?
Yes. Every ask is linked to a person and an account, so select them in the list and enroll them in a sequence: an interview invite before you build, a release note when it ships.
Does it sync with engineering's tools?
GitHub issues and pull requests sync into tables you can link to requests, and Slack threads arrive in the inbox. Stripe and HubSpot sync onto the same accounts.
Does it tell customers when something ships?
Most of the way. A workflow runs when a request is set to Shipped and notifies the owner, and the people who asked are already linked. Sending to them is a sequence you enroll them in; Custral doesn't email customers on its own.
Let your customers shape the roadmap.
Requests, accounts and revenue in one workspace.
Plans from $39 a seat a month, billed annually. See pricing
One subscription instead ofYour whole feedback stack
Feedback toolFeedback objectRoadmap toolBoard and table viewsCRMAccounts and contactsNotetakerLive call notesTicket triageUnified inboxDocsDocs and whiteboardsDashboardsDashboardsSpreadsheetsTables and formulas