Empavision / Support investigations
Trace the accounts, transactions and history behind a customer complaint. Review the evidence before approving a change.
The demo needs no account or API keys. Fictional data, with a guided report.
Sharetribe integration available today. See documented investigations
“My payment went through, but my account still says I need to subscribe.”
01 · Check the evidence
Compare the member profile, billing record and event history. See what is missing or uncertain.
02 · Review the proposed correction
Inspect the target record and the before-and-after values.
03 · Decide what happens
Approve a supported action or keep the diagnosis. An applied change has a receipt.
Evidence you can inspect
Approval before supported case actions
Receipts distinguish applied changes from suggestions
From real support work
Billing & access
A real investigation found an active subscription under a different billing customer. Two approved profile corrections were recorded and checked.
The customer’s final sign-in was not independently confirmed.
Explore a fictional version →Accounts & history
The history belonged to a second account. The investigation located the records and found no deletion events in the history it checked.
A diagnosis; no accounts were merged or records restored.
Explore a fictional version →Also documented: support impersonation in marketplace messages. Read the cases and their limits.
Inspect a sample report and simulate an approval. No account, credentials or live marketplace involved.
Use a Sharetribe test environment first if you prefer. We explain the permissions before you enter credentials. Stripe is optional.
Paste the complaint, review the evidence and decide what to do. Missing data stays visible as a limitation.
What we read
Users, listings, transactions, messages, reviews and bookings from Sharetribe; payments, refunds and subscriptions from Stripe. We keep a copy so answers come back in seconds.
Nothing is written without your click
Every refund, transaction step or changed field waits for your approval. Two optional background features, a “price dropped” marker on listings and a seller rating on profiles, stay off until you turn them on in Settings.
Every change has a receipt
Each change is recorded with what was there before. Field changes undo in one click. Refunds, cancellations and transaction steps cannot be undone, and the approval screen says so before you click.
Removing the key stops us
Delete the connection in Settings and we stop reading your marketplace within a minute.
Deleting the connection removes the copy
Deleting your marketplace connection deletes our copy of its data. Stripe payment history we already copied is kept unless you ask us to remove it. Disconnecting is not the same as deleting your Empavision account or every audit record.
Stripe: optional, and a key you can limit
Stripe is optional; without it, support cases say which billing facts they could not verify. When you connect it, a restricted key with read permissions (plus webhook endpoints, so we can set up the payment feed) is enough. We check what the key allows when you connect and name anything missing. A refund or cancellation needs the matching write permission on that key, and runs only when you approve it.
Sharetribe keys cannot be limited
A Sharetribe Integration API key always has full access to your marketplace. Sharetribe offers no read-only kind. So the limit lives in our product: the approval step above.
Empavision has been used in documented Sharetribe marketplace investigations. Sharetribe’s guide describes the integration. This listing is not a security certification or a guarantee of an investigation’s outcome.
Chat, marketplace records, reports, automations and extensions remain available. Explore all features.
Founding operator program: all Core features free until December 31, 2026. Program details.