Skip to main content

Look up one person's setup and history

When a rep queries their pay, the fastest route is usually not the payout — it is their participant page, which shows everything Lokom believes about them on one screen.

Where to start: Organization → Participants, then click the person.

Goal​

Answer "is this person set up correctly" without opening five screens.

The header​

Their name, email, and two chips: Team · Role, and their Pipedrive identity. Below that, "Picked by <who> on <date>" and "Last validated <date>".

Identity & lifecycle — is Lokom looking at the right person?​

Three blocks:

  • Pipedrive linkage — the matched Pipedrive user's name, email and id. Watch for a flag like Email changed in Pipedrive: the person's address moved and the link may now be pointing at a stale record.
  • Lokom user — whether this participant is Linked to a Lokom user, and which one. If this is empty, they can sign in but will see nothing on My Payouts. → Link a user to the right participant
  • Provenance — when they were added.

Two actions sit at the top: Re-match Pipedrive user (use it after an email change or a bad auto-match) and More actions.

Role history — which plan applied, and when​

Plans attach to roles, so a rep who changed roles mid-year was paid by different plans across the year. This section makes that legible: a Current entry ("Currently on <team> as <role> · Since <date>") and every previous assignment with its date range.

This is the first thing to check when an old payout looks wrong. A March statement was produced by whatever role they held in March.

Edit role changes the assignment.

Compensation — their OTE and OTV​

Two figures:

  • OTE — on-target earnings.
  • OTV — on-target variable, with the variable share shown beneath (e.g. 30% variable).

Each says where it came from — "Inherited from <role>" with a link. Edit override sets a personal figure that departs from the role default.

Watch for: an override is invisible from the role page. If one rep on a shared role has unexpected numbers, look here before you suspect the plan.

Commissions summary — the last few periods​

A small table of Period / Quota / Earned / Attainment, stamped "As of <date>", with links to Open Quota Manager and Open Commissions.

A — under Quota means no quota was found for that period, which is enough on its own to explain a missing quota bonus. → Set up quotas

Recent attribution activity — the live feed​

Marked Live. Each row is one attribution: the deal, the event that attributed it, the period it landed in, the amount, and how long ago. Every row links to the deal in Pipedrive.

The event column is the useful part. You will see values like Won time, Close time, Local close date, Local won date and Add time — these are the date fields Lokom attributed on. When someone insists a deal belongs in a different month, this row tells you which date put it where it is.

View all attribution → opens Deal Review filtered to this person. → Check and exclude deals

The five-check routine​

When a rep queries their pay, walk this page top to bottom:

  1. Pipedrive linkage — right person?
  2. Lokom user — linked, if they log in?
  3. Role history — which role held in the period they are asking about?
  4. Compensation — any personal override?
  5. Attribution activity — did their deals land in the period they expect?

Four of the five most common payout disputes are answered before you open a plan.

Common mistakes​

  • Checking the current role for a historical question. Use Role history.
  • Missing an OTE override. It looks like a plan bug and is not.
  • Ignoring "Email changed in Pipedrive". It quietly breaks the link between the deal owner and the participant.