PebblePebble
Product
PricingCustomers
Pebble + Intercom

Agentic support for your hardest technical tickets

Pebble resolves the 30% of tickets that are too complex for Fin: the ones that need real investigation, not a knowledge-base answer.

Pebble digs through your logs, database, and code, then posts the root cause as an internal note in Intercom before your team even opens the ticket. It even drafts the customer reply, ready to review and send.

View in Intercom
The Intercom inbox with the Note tab active: a Pebble internal note with what's happening, the root cause, and a suggested reply ready to send

It works the ticket like your best support engineer

When Pebble picks up a conversation it reads the thread, then investigates the systems where the answers live: your codebase, Sentry, Datadog, GCP and AWS logs, a read-only database connection, past tickets, docs, and Slack history.

How it works in three steps

Step 1. Ticket comes in from your customer. Pebble gets to work, investigating across your systems.

The Intercom inbox: a new customer conversation, with Pebble already investigating across code, logs, and database

Human-approved by default: nothing goes to a customer until your rep sends it

Pebble writes internal notes, tags, and engineering tickets. It only sends customer-facing replies if you explicitly turn on auto-respond, and even then every reply has to clear Pebble's own quality bar first.

When Pebble can't resolve something, it says so: an internal note with what it found and what it needs, or a filed ticket. It does not guess to a customer.

The response mode setting: internal notes only is the checked default; auto-respond is optional, with Pebble's guardrails listed: factual, self-contained, high confidence with fallback to an internal note, no promised ETAs or future actions, and an audit note on every auto-reply

When it's really a bug, engineering gets the ticket with the investigation attached

Pebble files the Linear or Jira ticket, investigation attached, and opens a GitHub PR ready to review. Engineering starts from a proposed fix, not a one-line escalation.

A Linear ticket filed by Pebble: root cause, cited evidence, and a ready PR with passing checks and a Review PR button

How is Pebble different from Fin?

Fin answers questions. Pebble investigates problems.

Fin resolves the questions your knowledge base already answers. Pebble works the problems it can't: investigating your code, logs, and database, and posting what it finds for your rep to approve. Run both, and an Intercom rule splits the queue with a tag. Run Pebble alone, and it works exactly the same way: tag in, no Fin required.

You decide which conversations Pebble touches

Pebble does not barge into every conversation:

Tag a conversation.Add the pebble tag (yours to configure) and Pebble goes to work. Build an Intercom rule to tag whole categories automatically.
Mention @Pebble.An @Pebble in an internal note pulls it into any conversation, tagged or not.
Use the sidebar.The Pebble panel in the inbox has two buttons: Investigate and Create Eng Ticket.
Auto-triage is there if you want it.Optional: Pebble investigates every new conversation automatically and posts its findings as a note. Off by default, and most teams scope with a tag instead.
Pebble settings: trigger tag, dedicated Pebble teammate, and response mode with internal notes only as the default

Setup: install, connect your sources, tag a conversation

  1. Install from the Intercom App Store and approve access
  2. Optionally add the sidebar app, pick your trigger tag, and create a dedicated “Pebble” teammate for clean note attribution
  3. Connect investigation sources: GitHub for code, Sentry, Datadog, CloudWatch or GCP for logs, a read-only database, your issue tracker
  4. Tag your first conversation

Tag one conversation to see what it does. The more sources connected, the deeper the investigations.

96%
issue close rate
1 in 3
technical tickets resolved without a code change
< 5 min
to root cause
< 25 min
to a fix ready to review

Common questions

See it on your next technical ticket.

Install, tag one conversation, and the root cause lands as an internal note your rep can act on.

View in Intercom