Drop the audit log straight into your support UI
Mint a short-lived embed token server-side, drop the `<RecalledFeed />` React component into your support tool, and give your agents the last 25 actions of the customer without switching tabs.
Every time a support agent picks up a ticket, they alt-tab: Zendesk, Stripe, your admin panel, Segment, Sentry. By the time they have the full story the customer is already annoyed. Most of what they need is 'the last 25 things this user did', which is exactly what an audit log is for, if the audit log had a UI good enough to embed.
Call POST /v1/embed/token on your back end to mint a short-lived, scoped token for the customer the agent is looking at. Render the `<RecalledFeed />` React component inside your support UI with that token. Your agents see every action the user took, filtered to that user only, with action, time, IP, and targets. No new dashboard to learn, no new login.
// Inside your admin back-office, render the
// React component from @recalled/sdk/react:
<RecalledFeed
token={embedToken}
actor={customer.id}
limit={25}
/>Why support teams use Recalled
- Embed token with actor scope
Mint a token scoped to a single actor so agents only see the customer they are helping. Short TTL, no secret leaks.
- React component on npm
`@recalled/sdk/react` exports `RecalledFeed`. One import, one prop, done. No schema to design.
- Zero-context-switch
Audit log lives inside your existing support UI. Agents stay in their tool, customers get a faster answer.
- Filterable by action type
Show only billing events, only logins, only errors, depending on the ticket category. All server-side.
Related use cases
Query every event by actor id to rebuild a minute-by-minute timeline of what a user did. Perfect for support investigations, bug reports, and replaying the context of a complaint.
Log every sensitive action taken by a staff member from your back-office: suspensions, refunds, impersonations, role changes. Answer 'who did this and when' before anyone has to ask.
Your next audit log is 2 minutes away
Stop hacking on your own logs table. Drop in Recalled, send your first event, move on.