PYLO Docs
Contents

Home and My Board

Leads

Webinars

Resources

Settings: Integrations and automations

Settings: Billing

Settings: Data

Home and My Board

My Board

Your own monthly numbers, target and recent activity, plus a data profile of everything on record for you.

Read as Markdown

My Board is your personal dashboard: this calendar month's figures for your role, your monthly target and your latest activity. Only you and your workspace's admins can see it.

Who can open it

Every signed-in member can open My Board. Owners, admins and ops see the team version. Closers, setters and SDRs see their own. Roles with no board of their own, such as DM setters, see a short message pointing them to the Agency Dashboard.

Owners, admins and ops can also open a teammate's board from Team. You see it exactly as they do. Anyone else who tries to open another member's board lands on their own.

Closers, setters and SDRs who have not set a goal for the month are asked to set one before the board loads.

The four cards

RoleCards
CloserMy cash collected, My closes, My close rate, My commission
SetterMy sets, My show rate, My calls, My commission
SDRMy sets, My qualified rate, My calls, My commission
Owner, admin, opsTotal cash, Total closes, Team close rate, Total commission owed

What each card counts, for every role, is in What the figures mean, at the end of this page.

Each card shows the change against last month, or "No comparison yet" when there is nothing to compare with.

Chart, target and activity

The chart shows cash (sets for setters and SDRs) by week or by month. The Monthly target card compares this month's figure with your goal and the days left. Reps change it with Edit target. Owners set the team goal in account settings.

Recent activity lists your five latest events, filtered by All, EOD, Post-call or Payments. A call in the past with no post-call form shows as Missing. Closers and setters also see recent coaching feedback below.

Data profile

Switch to Data profile for your own full record, all time or this month: your figures as closer and as setter, your calls, end-of-day reports, payouts and competitions won.

Common questions

Why does my close rate not show 0%? A rate with nothing to divide by has no value, so with no live calls this month the card says so instead of showing 0%.

What the figures mean

Each explanation below is generated from PYLO's metric registry, the same source Ask PYLO and Claude quote from, so the docs and their answers always agree.

My board

Period, unless a figure says otherwise: Bucketed on the call's scheduled time, converted to Europe/London before the date is taken. Both ends of the period are included.

Live calls

Calls that took place. A no-show, a cancellation and a reschedule are the closed set that did not, and a close written with no call behind it is excluded by was_a_call.

  • Leaves out: No-shows, cancellations and reschedules: they did not take place. A close written with no call behind it (was_a_call false), such as a close made over DM. Voided calls (test, duplicate, spam or other) are left out of every count.
  • Shown to: owners, admins, ops, closers and setters.

Closes on live calls

Live calls that closed or took a deposit. Live-scoped on purpose, so it sits inside the live-call count it is quoted against.

  • Leaves out: Closes made over DM or recorded as a payment only: they were never live calls. Voided calls (test, duplicate, spam or other) are left out of every count.
  • Shown to: owners, admins, ops and closers.

Show rate

Live calls as a share of live calls plus no-shows. A cancelled or rescheduled call is in neither side.

  • Counts: Live calls, out of Live calls plus no-shows.
  • Leaves out: Cancelled calls are in neither side. Rescheduled calls are in neither side. A close written with no call behind it (was_a_call false) is not a live call. Voided calls (test, duplicate, spam or other) are left out of every count.
  • Shown to: setters.

Close rate

Closes as a share of live calls. A cancelled or rescheduled call is in neither side.

  • Counts: Closes on live calls, out of Live calls.
  • Leaves out: Cancelled, rescheduled and no-show calls are in neither side. Closes made over DM or recorded as a payment only are in neither side. Voided calls (test, duplicate, spam or other) are left out of every count.
  • Shown to: owners, admins, ops and closers.

Commission earned

Commission across all three tiers on every succeeded payment attributed to this member, net of refunds, whatever its verification status.

  • Shown to: owners, admins, ops, closers, setters and SDRs.

Commission on verified cash

The same three tiers counting only payments marked verified or grandfathered, and using the verified amount where one is recorded.

  • Shown to: owners, admins, ops, closers, setters and SDRs.

Triages attempted

Triages an SDR typed into their end-of-day form. Reported, not counted.

  • Shown to: SDRs.

Triages connected

Of those, the ones that connected. Reported, not counted.

  • Shown to: SDRs.

Qualified rate

Connected triages as a share of triages attempted. Both sides are the SDR's own tally from the same submissions and the same days.

  • Counts: Triages connected, out of Triages attempted.
  • Shown to: SDRs.

Cash collected

Succeeded payments attributed to one closer, paid inside the period, taking actual_amount where it is set and amount otherwise, with refunds netted as negative rows dated on the refund.

  • Shown to: closers.

Total cash

Succeeded payments for the workspace, paid inside the period, taking actual_amount where it is set and amount otherwise, with refunds netted as negative rows dated on the refund. Summed in TypeScript rather than by an RPC.

  • Shown to: owners, admins and ops.

Sets

Calls booked by one setter, counted on scheduled_at falling inside the period.

  • Shown to: setters.

Sets

Appointments an SDR typed into their end-of-day form, summed over the period. Reported, not counted.

  • Shown to: SDRs.

Calls

Dials an SDR typed into their end-of-day form, summed over the period. Reported, not counted.

  • Shown to: SDRs.

My performance

Cash collected

Succeeded payments attributed to one closer, paid inside the period, taking actual_amount where it is set and amount otherwise, with refunds netted as negative rows dated on the refund.

  • Shown to: closers.

Sets

Calls booked by one setter, counted on scheduled_at falling inside the period.

  • Shown to: setters.

Sets

Appointments an SDR typed into their end-of-day form, summed over the period. Reported, not counted.

  • Shown to: SDRs.

Team performance

Total cash

Succeeded payments for the workspace, paid inside the period, taking actual_amount where it is set and amount otherwise, with refunds netted as negative rows dated on the refund. Summed in TypeScript rather than by an RPC.

  • Shown to: owners, admins and ops.

Monthly target

Personal target

What one member is aiming for this month, against the figure their role is measured on: appointments set for an SDR, calls booked for a setter, closes for a closer. The unit follows the metric it targets, so a closer's secondary target is money and every other one is a count.

  • Shown to: closers, setters and SDRs.

Monthly cash goal

What the workspace set out to collect this month, in its own pricing currency. Zero means no goal has been set, not a goal of nothing.

  • Shown to: owners, admins and ops.

Cash collected

Succeeded payments attributed to one closer, paid inside the period, taking actual_amount where it is set and amount otherwise, with refunds netted as negative rows dated on the refund.

  • Shown to: closers.

Total cash

Succeeded payments for the workspace, paid inside the period, taking actual_amount where it is set and amount otherwise, with refunds netted as negative rows dated on the refund. Summed in TypeScript rather than by an RPC.

  • Shown to: owners, admins and ops.

Sets

Calls booked by one setter, counted on scheduled_at falling inside the period.

  • Shown to: setters.

Sets

Appointments an SDR typed into their end-of-day form, summed over the period. Reported, not counted.

  • Shown to: SDRs.

End-of-day reports

End-of-day reports filed

Distinct dates in the period on which this rep filed an end-of-day report. Two reports for one date count once, because the denominator counts days.

Days elapsed this month

Days of the current month up to and including today, in London. The denominator the rep's own Data profile compares their submissions against.

EOD compliance this month

Days this rep filed an end-of-day report this month as a share of the days of the month so far.

  • Counts: End-of-day reports filed, out of Days elapsed this month.