For customer support
Crash and error monitoring for support teams
Look up the customer, see what went wrong, hand engineering a ticket with proof. No more asking a customer which phone they have.
Plans: Comments and users affected on every plan · user lookup, the journey and tickets on Growth and above · See pricing
u_48213
What went wrong
- Crash NullPointerException in CheckoutActivity
- Failed API call POST /v1/orders · 502
What you get
- Find the customerPaste the ID from your help desk: their user ID or the install ID, or their email if a workspace owner or admin has turned on email lookup. Matches are exact, never near-misses, over the last 90 days.Growth and above
- See what went wrong for themTheir recent crashes, errors and failed API calls, with the device, OS and app version, so you know it's real before you escalate.Growth and above
- What they did firstThe user journey shows their latest session in order: the failed calls and errors before the crash, plus screens and events with product analytics on.Growth and above
- A ticket with this contextCreate a Jira, Linear, GitHub Issues, Asana or ClickUp ticket from the customer's profile. It carries this customer's steps and device, not just the issue's latest event.Growth and above
- Is it just them?Every issue shows how many users it hit, so you can tell a customer whether it's a known problem and whether the team is already on it.Every plan
- Loop in engineering on the issueComment with what the customer reported and @mention the developer. They're notified in the dashboard and by email, and the activity timeline shows who picked it up.Every plan
Workflow
From "it crashed" to a ticket engineering can act on
Four steps from the customer's message to an issue someone owns, without a single screenshot pasted into chat.
- 1
Look up the customer
Search by the user ID from your help desk or the install ID from a log. Email search is optional: a workspace owner or admin turns it on. Choose Support when you sign up and Codeskop opens on this search.
Growth and above - 2
See what went wrong
Open their profile: recent crashes, errors and failed API calls, and the journey of their latest session.
Growth and above - 3
Hand engineering a ticket with proof
Create the ticket from the profile. It includes the stack trace, the customer's steps and device, and links back to the issue.
Growth and above - 4
Follow it to the fix
@mention the developer on the issue and watch the status move to Completed, so you can tell the customer when the fix ships.
Every plan
Frequently asked questions
Which plan do support teams need?
User lookup, the user journey and tickets are on Growth and above. Comments, @mentions and users affected on every issue are on every plan, including Free.
Can I find a customer by email?
Yes, once a workspace owner or admin turns on email lookup in Settings, and if your app sends an email trait with identify(). Codeskop matches a keyed hash of the address, never the address itself, so it only finds people identified since lookup was turned on. If your app uses the email as the user ID, searching for it works either way.
What if the customer never signed in?
Search by their install ID, for example from a log or a support form. Codeskop returns the anonymous install and any signed-in users on that device.
Do support agents need to read stack traces?
No. They see what happened in plain terms (crash, error or failed call, device, app version and when), and the ticket carries the stack trace for the developer.
Is this session replay?
No. Codeskop doesn't record video, screenshots or taps. The journey is a timeline built from the events the SDK already sends.
Do support agents take up a seat?
Everyone on the team is a member: Free includes up to 5, Starter up to 15, and Growth and above unlimited. Seats aren't billed.
Know what broke. Fix it faster.
Bring your whole team into the same issues.
Set up in minutes. Free plan for up to 5 team members, no credit card required.