One customer, every screen

Most teams keep the same customer in four places. A vote in the feedback tool, a ticket in the help desk, a row in the survey tool, an event in analytics. Each one knows a little. None of them knows it's the same person.

Harkly was built around one record.

Identify once

Your app tells Harkly who someone is, from the browser, React, or the Swift package in an iOS app:

Harkly.init({ publicKey: "hk_pub_…" });
Harkly.identify({ id: user.id, email: user.email, name: user.name, plan: "pro" });

To make identity tamper-proof, sign it on your server with the workspace's secret and pass the token instead; a bare public key can identify but can never change someone's email.

From then on, everything that person does lands on the same record: the posts they vote on and write, the conversations they start in the messenger or by email, the CSAT they leave, and any events you track. Turn on anonymous tracking and the votes they cast before signing in follow them too.

Why it matters

When a thread comes in, the person answering sees the customer's plan, their company, what they've asked for before and what they've been told. When a post ships, you know which of the voters are paying you. When an account looks unhappy, the evidence is in one place instead of four.

It also means one bill that counts people once. A customer who votes, emails support and uses your app is one identified customer, not three.