DocumentationProduct features

Product

A complete feedback loop, not another ticket queue.

Heardock connects the moment a user has something to say with the context your team needs to act — and gives the user a way to hear back.

In-product capture

A focused native form keeps users in your app. Four clear categories and a 2,000-character message are enough to capture the story without ticket-system overhead.

Automatic context

App version, build, platform, OS, device, locale, and screen arrive with the note. Add your own route and metadata when your product needs more detail.

One shared inbox

Read feedback from every project in one place. Filter by app, scan categories and context, then open a thread when you are ready to respond.

Replies that stay connected

Reply from the Heardock thread. The user sees team messages in their app’s feedback center, without creating an account or handing over an email address.

Offline by default

Network failures do not erase what a user wrote. Mobile SDKs save the note locally and retry with idempotency keys, so retries do not create duplicates.

Built for your product

Use light or dark themes, customize accents and copy, and choose English or Simplified Chinese. Partial localization overrides fall back cleanly.

The feedback loop

From a thought to a useful conversation.

  1. 1

    A user writes in your product

    They choose Bug, Idea, Question, or Praise and describe what happened. There is no mandatory email field and no separate support portal to find.

  2. 2

    Heardock attaches the useful details

    The SDK adds technical context and sends the note with a publishable project key. If the network is unavailable, mobile clients keep a local copy for retry.

  3. 3

    Your team reads and replies

    The note appears in the project inbox with its context. Open the detail view to reply; the response becomes part of the same read-only thread in the app.

Privacy by design

Collect the problem, not the person.

Heardock starts with the minimum information needed to make feedback useful. You decide whether to add identity or product-specific metadata.

Safe client keys

Publishable keys identify a project and are designed to ship in client code.

No identity by default

User ID, email, and name are only attached when your app explicitly identifies a user.

Configurable context

Device, locale, and screen collection can be controlled through SDK options.