Times shown in
| User | Status | Focus today | Idle today | Break today | Total time | Login / start time | Last end tracking |
|---|
← back to team
Account
Deactivating blocks this person from signing in to the dashboard or extension — tracking history, screenshots, and leads are all kept, and reactivating restores access immediately. This is different from Delete below, which is permanent.
Active
Permanently deletes this user's login and all of their tracked time, screenshots, and leads. This cannot be undone.
Schedule & limits
Leave "Target leads" blank to disable — an agent with no target just gets hourly pay, exactly as before. Only leads marked accepted on the Leads tab count toward the target and bonus.
Each row pays a bonus once accepted leads exceed the target above by at least that many "extra" leads — e.g. 10 extra leads → 50, 20 extra leads → 150. Only the highest tier the agent qualifies for is paid (not stacked), on top of the base target bonus above.
Each row pays a flat monthly amount once accepted leads for the period reach that row's minimum — e.g. 0 leads → 300, 40 leads → 450, 50 leads → 550, 60 leads → 650. Only the highest tier reached is paid (not stacked). Include a 0-leads row so there's always a base salary — otherwise an agent below every tier's minimum shows no pay at all for the period.
Today (toward limit): —
Today's break: —
Leads today: —
This week (toward limit): —
Leads this month: —
00040812162024
View & edit timesheets
Select a user to see their daily timeline
0:00:00 productive
0:00:00 break
0:00:00 idle
— activity
12am6am12pm6pm12am
Productive
Break
Idle
| Project / Task | Status | Activity | Duration | Time | Shots |
|---|
Reports
Day/month boundaries are computed in each agent's own schedule timezone, not your browser's — an overnight
shift is split at that agent's local midnight, so hours land on the day they'd actually recognize.
or
Suspicious activity
Heuristic signals only, not proof of anything — a flag is worth a quick look (e.g. that day's screenshots),
not an automatic conclusion. Scanning goes minute-by-minute, so a week or two at a time is usually plenty;
very wide ranges will be slower.
Pick a range and hit Scan.
| User | Date | Type | Detail |
|---|
Leads
This is the analysis period for the insights below. Queue Review, Tickets Review, PrimeHome Buyers, and All Queue each have their own independent date filter on their own subtab — widening one of those no longer requires widening this range too.
Total submitted
—
Accepted
—
Pending
—
Rejected
—
Leads Queue Review
—
Leads Queue Review — PrimeHome Buyers
—
—
Status breakdown
Leads by day
Top campaigns
By agent (accepted leads)
Submit a lead
Not tied to a campaign/task — pick whichever form fits this lead. Built and maintained under Submission Forms Creator.
Your role has view-only access to Lead Submission — ask an Owner/Admin to grant it Edit access under Leads → User Types → Lead Submission to submit leads here.
Your role has view-only access to Submission Forms Creator — ask an Owner/Admin to grant it Edit access under Leads → User Types → Submission Forms Creator to build or change forms here.
New form
Field templates
A named, reusable snapshot of fields — save any form's current fields as one below (each form card has its own "Save as template" button), then apply a saved template to any form (including a brand-new one) from that same card. Duplicates are skipped, same as "Load from Default Template Final." A template named exactly "Default Template Final" is treated specially: its own Load from Default Template Final button on every form always keeps every one of its fields marked required.
Showing
—
Pending
—
Accepted
—
Rejected
—
Submissions
| User | Submitted at | Leads | Seller Name | Phone | Extra fields | Campaign Name | Type | Campaign Fit | Status | Rejected reason |
|---|
Leads submitted through the Ticket form (Submission Forms → Lead Submission). Accepting one asks which real campaign it belongs to, then sends it to that campaign's client for a Yes/No on their Tickets tab — a Yes brings it back here as a normal pending lead (recording required to Accept); a No rejects it directly. Rejecting here never reaches a client.
Showing
—
Awaiting staff review
—
Awaiting client (Yes/No)
—
Client said Yes — back for review
—
Rejected
—
Tickets
| User | Submitted at | Seller Name | Phone | Campaign Name (as submitted) | Stage | Status | Actions |
|---|
Send ticket to client for review
Pick which real campaign this ticket belongs to, and correct any details before sending. That campaign's client will see it on their Tickets tab (without Seller Name/Phone/Email) and answer Yes/No.
Submitted details
Showing
—
Disputes
—
Feedback
—
Open
—
Accepted
—
Rejected
—
Narrows what's already loaded by the date/user/status filters on Leads Dashboard above — doesn't fetch anything new. "Sent by" is whoever actually clicked Send, which can differ from the submitting agent shown in "User".
Showing
—
Not sent
—
Sent
—
Send failed
—
Sent to gyhomes
—
Sent to PrimeHome Buyers
—
Awaiting gyhomes decision
—
Sent volume by sender
Successful sends only, matching whatever's currently filtered above.
Leads — PrimeHome Buyers review
0 selected
| User | Submitted at | Seller Name | Phone | Campaign Name | Status | Rejected/Refund Reason | PrimeHome Buyers | Sent by | Actions |
|---|
Upload CSV / Excel
Columns match PrimeHome Buyers' own required + optional fields (both now required to send: Call recording link and Ping ID), plus Phone (used to find an existing lead to fill in) — the two fields deliberately left out of the agent's submission form and entered here instead, per PrimeHome Buyers' "Provider lead fields description". For both, paste a URL directly here, or leave blank and upload an actual file per-lead in Lead Reviewing instead — either way a URL is what's actually sent. A row whose phone matches an existing lead fills in that lead's details; a row with no match creates a brand-new lead (attributed to you as the importer) ready for review below.
A raw call-intake export (Timestamp / Seller Name / Phone Number / Property Address / Condition / Occupancy / Reason / Closing / Additional Notes / Call Recording, etc. — not this template's own headers) is auto-detected and converted on upload, no pre-processing needed. Conversion skips DNC-tagged and unreadable rows and leaves fields it has no real signal for blank rather than guessing — the preview below always shows exactly what will be imported before anything is saved.
A raw call-intake export (Timestamp / Seller Name / Phone Number / Property Address / Condition / Occupancy / Reason / Closing / Additional Notes / Call Recording, etc. — not this template's own headers) is auto-detected and converted on upload, no pre-processing needed. Conversion skips DNC-tagged and unreadable rows and leaves fields it has no real signal for blank rather than guessing — the preview below always shows exactly what will be imported before anything is saved.
Preview
Combines every lead (Leads Queue Review, PrimeHome Buyers, Tickets Review), every Dispute/Feedback thread, and every raw Client Submission (Client Qualification Form / Data Form) in one list — mainly for housekeeping and bulk cleanup. "Details" shows everything submitted on that record — the same full picture the client or the staff subtab it came from would see, not just the summary columns here. Delete is permanent and Owner/Admin only.
| Queue | Name / Contact | Phone | Campaign / Form | Submitted | Status | Details | Actions |
|---|
No records match these filters.
Available to claim
Sent back by a reviewer instead of Accept/Reject — claiming one is exclusive, so it disappears from this list for everyone else the moment you pick it up.
0 selected
| Seller Name | Phone | Campaign Name | Reason | Fields to confirm | Sent back |
|---|
Nothing waiting to be claimed.
My claimed call backs
0 selected
| Seller Name | Phone | Campaign Name | Reason | Fields to confirm | Claimed |
|---|
You haven't claimed any call backs.
User Management
Users
| User | Tasks assigned | Type | Status | Extension version | Created |
|---|---|---|---|---|---|
| Loading… | |||||
Task categories
Each category sets how idle detection behaves for tasks assigned to it. Standard is normal mouse/keyboard + tab-scoped detection. Dialer-exempt (e.g. Cold Calling, Sales) holds off idle while the agent is on a recognized dialer/CRM domain, same as before. Bounded grace (e.g. Backoffice) tolerates a set number of minutes of system idle — for work like downloading a call recording, uploading it, and editing it in a desktop spreadsheet app the extension can't see — before counting as idle like anyone else.
Tasks
Dialer / CRM domains
Users on these domains (or any subdomain of them) count as tracking, not idle, even with no mouse/keyboard activity — for softphone/dialer tools where they're on a call rather than typing. Changes here take effect for users within a few minutes, with no extension update or reload needed.
Extension version
After rolling out a new build to agents, raise this to that version to force everyone still on an older
one off it — a below-minimum extension is blocked from starting new sessions, and an already-running
session is stopped automatically within a minute. Leave blank (or set to 0.0.0)
to allow any version.
Activity scoring ceilings
The activity % shown per agent and stored on every sample is mouse/keyboard event counts scored against
these per-minute ceilings (100% = at or above the ceiling). The defaults (90 mouse, 60 keyboard) are
starting guesses, not measured — pull a range of real activity_samples for your
team (Reports tab, or query the table directly) and set these to what real, focused work actually looks
like for your agents' roles. Leave either blank to use the extension's built-in default for that channel.
Takes up to 5 minutes to apply to already-running sessions (cached client-side).
Add a user type
A user type controls which dashboard tabs an account can see, whether it can edit or only view
each of those tabs, and — separately — which users' data it's allowed to see at all. Owner and Admin are
protected and can't be edited or deleted here — both always see and edit everything. Creating, editing,
resetting passwords for, or deleting user accounts on the Dashboard tab is always Owner/Admin only — no
custom user type can be given that ability; custom user types can still be given view access to the
Dashboard tab to see the team list. The User Management tab (this one) additionally breaks down into
sections below — a user type can be given, say, Tasks but not User Types itself.
Check a tab to make it visible. For tabs with an "Edit" option, leave it unchecked to give this role read-only access to that tab.
Restricts the task dropdown in the extension to only these categories — e.g. a "Backoffice" user type only ever sees Backoffice tasks. Leave nothing checked for no restriction (this role sees every task, same as before). Owner/Admin are never restricted.
Restricts every tab above to just these users' data (Dashboard, Timesheets, Reports, Leads, Flags). Owner and Admin always see everyone regardless of this setting. Check as many of the first three as you like — they combine (e.g. "Only themselves" + "A specific user type" together). "All users" is exclusive since it already includes everyone.
| User Type | Dashboard tabs | User view scope |
|---|
GoHighLevel
Add a GoHighLevel location below to enable lead sync. Each location is authorized
separately — connecting one doesn't affect any others.
Opens GoHighLevel's own consent screen in a new tab — approve the install there,
then close that tab and come back here.
Simpler than the OAuth flow above, but one token per location — generate it from
that location's GHL settings under Private Integrations.
Which connected location above to send client-facing text notifications through (new ticket / new lead / dispute-feedback reply). Only needed if more than one location is connected — otherwise the single connection is used automatically.
Agent → GoHighLevel mapping
Match each Sales or Admin user to their GoHighLevel user ID so their calls are attributed to them for activity tracking. Find a user's ID in GHL under Settings → Team, or from a call log.
Loading…
Recent GoHighLevel calls
Live call activity received from GoHighLevel via webhook. Unmapped calls show the raw GHL user ID until you map that user above.
Loading…
GoHighLevel contact lookup
Look up a phone number's live conversation history and open opportunities directly from GoHighLevel. Requires the connected location's token to include the conversations.readonly and opportunities.readonly scopes -- if it was connected before those were added, disconnect and reconnect that location first.
ReadyMode
ReadyMode's Integrations team confirmed their API is lead-oriented only — Call Logs, Research Calls, and Agent/Productivity data isn't available via API. Two ways to get it in here instead: (1) automatically, via a ReadyMode Automated Task that emails a CSV on a schedule — see "Automated email imports" below; or (2) manually, by downloading a CSV from ReadyMode's Reports screen and pasting it into the boxes below. Note: ReadyMode's Productivity Report itself has no export option — use the Agent Report instead, which covers the same ground (Ready/Break time, calls made, etc.).
Lead-posting channels (campaigns)
Each ReadyMode Channel (Lead → Channels → + → Website → Configuration → Enable third-party lead posting) maps to one campaign/Lead File and has its own posting URL. Save one row per campaign here — the "Upload list for ReadyMode" tool below lets you pick which one to push into.
Agent → ReadyMode mapping
Match each Agent user to their ReadyMode username so their calls, research lookups, and productivity stats are attributed to them.
Loading…
Import ReadyMode reports (CSV)
Paste the CSV contents from each ReadyMode report's "Download CSV" button, then click Import. Safe to re-import — matching rows are updated, not duplicated.
Upload list for ReadyMode — dedupe check
Upload a raw property list (DealMachine, BatchLeads, or similar export — CSV or Excel) before loading it into ReadyMode's dialer. This checks every address against leads already known to iSpeedToLead (any PrimeHome Buyers submission, any status) and flags ones that would just come back "Duplicate address/phone number" if resubmitted, so agents aren't cold-calling a property already in the pipeline. Direct upload straight into ReadyMode isn't wired up yet — their inbound Channel/TPI API access is still pending from their Integrations team — so this produces a cleaned CSV for ReadyMode's own manual upload in the meantime.
Rows in file
0
Duplicate addresses
0
Clean — ready to upload
0
| Address (as uploaded) | Result | Matched iSpeedToLead lead |
|---|
Lead push history
Permanent record of every lead ever pushed to ReadyMode via the "Push clean list to ReadyMode" button above — who pushed it, when, and whether ReadyMode accepted it. Independent of ReadyMode's own optional email notifications.
Loading…
Campaign progress
Live per-campaign dialing progress, built from ReadyMode's own call-result webhook as calls actually happen — not a manual export. "Leads pushed" comes from our own push audit log above; a campaign whose leads were uploaded manually in ReadyMode (not through this dashboard) will show 0 pushed even while calls are happening, since we only know what we ourselves sent. ReadyMode's own file-level "Leads remaining/Health/Round" numbers still aren't available via their API — this is a different, always-current view built from the real-time call events instead.
Loading…
Automated email imports
Set up a ReadyMode Automated Task (Call Logs and/or Agent Report) to email its CSV to your Mailgun inbound address on a schedule, and Mailgun forwards it straight to the
readymode-email-import function — no manual pasting needed. Full setup steps are in READYMODE-INTEGRATION.md. This table shows every import attempt so you can tell at a glance whether an email arrived and parsed correctly.
Loading…
Gmail
Connect one shared Gmail inbox to send and read client email directly from the Chat widget's Email tab, the same way the SMS tab already works with GoHighLevel's numbers. Only one inbox is supported at a time — connecting a new one replaces the last.
Staff notifications — who gets notified
Which user types see each notification-center alert below (bell icon, top of the dashboard) when a client does something that needs staff attention. Leave every box checked for a kind to keep today's behavior — everyone sees it.
Loading…
Client notifications — activity, SMS & email
Turn each client-facing notification on/off and edit its wording — SMS goes out through the connected GoHighLevel number (see Client SMS location under Integrations), email goes out through Resend. Available placeholders:
{client_name} everywhere, plus {campaign} or {password} where noted. Turning a kind off skips BOTH the SMS and the email for it.
Loading…
Voice calling (WebRTC)
The 📞 call button in chat connects two agents' browsers directly (peer-to-peer), using free public STUN
servers by default — this works for most home/office networks but can fail to connect on stricter ones
(some corporate firewalls, certain mobile carriers). If calls start failing to connect for some agents,
add a TURN relay server.
Using Cloudflare? Cloudflare's TURN Token ID and API Token are NOT static credentials — don't paste them into the fields below (that won't work, and would expose a secret that can mint unlimited credentials). Instead, set them as secrets on the cloudflare-turn-credentials Supabase function (supabase secrets set CF_TURN_TOKEN_ID=... CF_TURN_API_TOKEN=...) and deploy it — calls will then auto-fetch short-lived TURN credentials with no fields to fill in here.
The fields below are for a different kind of TURN server: one that gives you a real static username/password (a self-hosted coturn, or another provider that issues long-lived credentials). They're only used as a fallback if the Cloudflare function above isn't set up. Leave blank to keep using STUN only (and Cloudflare, once configured). Both people still need dashboard.html open in a browser tab to call or receive a call — there's no ringing when the app is closed.
Using Cloudflare? Cloudflare's TURN Token ID and API Token are NOT static credentials — don't paste them into the fields below (that won't work, and would expose a secret that can mint unlimited credentials). Instead, set them as secrets on the cloudflare-turn-credentials Supabase function (supabase secrets set CF_TURN_TOKEN_ID=... CF_TURN_API_TOKEN=...) and deploy it — calls will then auto-fetch short-lived TURN credentials with no fields to fill in here.
The fields below are for a different kind of TURN server: one that gives you a real static username/password (a self-hosted coturn, or another provider that issues long-lived credentials). They're only used as a fallback if the Cloudflare function above isn't set up. Leave blank to keep using STUN only (and Cloudflare, once configured). Both people still need dashboard.html open in a browser tab to call or receive a call — there's no ringing when the app is closed.
Client Chat Routing
Clients get an AI assistant in their portal's chat button. It answers
simple questions itself, and routes anything else — or an explicit
"Connect me to..." request — to whichever team below matches. Every
staff member assigned to that team is notified and can see the
conversation waiting in their own "Client Chats" panel — whoever
clicks Accept first gets it assigned to them.
| Team | Description | Assigned to | |
|---|---|---|---|
| Loading… | |||
Add a team
Every one of these gets notified when a chat comes in for this team — first to hit Accept in Client Chats gets it.
Clients
Client accounts sign into a separate portal (not this dashboard) and can only ever see leads for the
campaigns granted to them below. They never appear in the Users list and can never be granted a dashboard role.
| Client | Company | Phone (SMS) | Campaign access | Status | Last login | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Campaigns
Campaign Name filters both Data Form and Client Qualification Form together — a Cold Caller package submission appears on both, so this keeps them in sync.
Total Submissions
—
This Week
—
This Month
—
Forms
—
Submissions by form
Submissions in the last 14 days
Most common answers
A quick read on market/criteria trends — the field(s) clients fill in most consistently, broken down by their most common values.
Niche List (Data order Form) and Skiptracing submissions, plus the data-pulling
fields of any Cold Caller package (Criteria + Data) Form submission — which also
appears on Client Qualification Form below, since that package covers both.
| Submitted | Form | Name | Phone | |
|---|---|---|---|---|
| Loading… | ||||
Caller only (Criteria) Form submissions, plus the criteria fields of any Cold
Caller package (Criteria + Data) Form submission — which also appears on Data
Form above, since that package covers both.
| Submitted | Form | Name | Phone | |
|---|---|---|---|---|
| Loading… | ||||
Campaigns created through the client portal's self-serve Create Campaign flow, with the dialer/data source/caller staffing choices made at signup — moved here from Campaign Guide, which clients see, since this is internal fulfillment info. A campaign only appears here once it's gone through the New Campaign flow (paid, or complimentary) — a plain form granted to a client, or an ordinary lead-submission form, is not the same thing. Package/Active Until/Status reflect that campaign's live subscription (Finance → Stripe Subscription) — pausing or canceling it from there, or it expiring on its own for a complimentary campaign, shows up here automatically. Use the Status/Package filters above (in place of Form, which doesn't apply here) to narrow the list.
| Submitted | Campaign Name | Client Details | Dialer | Data Source | Caller Staffing | Package | Active Until | Status | Accepted / Rejected | Accept Rate |
|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||||
Client edit requests
Campaign Resources
Add resource
Data Science
Properties Overview
Account-wide counts across every property synced from Cook and DuPage county open data (plus, as of v478,
GA/TN/AL/MS/FL/SC pre-foreclosure listings from Rubin Lublin, Hillsborough County FL, and Hutchens Law Firm). Does not include equity, mortgage, or
tax-delinquency counts — no free, reliable public-record source exists for any of those (see List Builder's
"Pull more data" card for why); a fabricated count would be worse than no card at all.
Data freshness
—
Orders waiting
—
Skip-trace hit rate
—
Delivered to clients
—
Orders waiting longest
Pending/processing Data Orders and Buy-a-List orders, oldest first. No SLA is configured anywhere in this
system — the 1d/3d/7d colouring is presentational, to make a queue that has quietly stopped moving obvious.
| Age | Type | Status | Client / email | Created |
|---|
Total Properties
—
Cook County
—
DuPage County
—
Absentee Owner
—
Corporate/Entity Owner
—
Inherited (Estate Sale)
—
Probate/Estate-Held
—
Building Code Lawsuit
—
Vacant Building
—
Pre-foreclosure (GA/TN/AL/MS/FL/SC)
—
Tired Landlord (3+ props)
—
Long-Term Owner (10+ yrs)
—
Multi-Family 2-4 / 5+
—
/
—
Excluded from Exports
—
Breakdown by county
| County | Total | Absentee | Corporate | Inherited | Probate | Lawsuit | Vacant | Tired LL | Long-Term | MFH 2-4 | MFH 5+ |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||||
Sync trend
Properties synced per day, by county — based on when each row was first pulled into this system, not a
historical snapshot of the signal counts above (no such history exists yet; this is the closest real trend
available today).
| Date |
|---|
| Loading… |
Field coverage
How many active properties actually carry each filterable field. A filter can only ever match within its
field's populated subset — so a low count here caps what the matching List Builder filter can possibly
return, no matter how the rest of the search is set up.
| Field | Populated | Coverage | Missing | Filters that depend on it |
|---|---|---|---|---|
| Loading… | ||||
Signal overlap
How many properties carry both of any two signals — the diagonal is each signal on its own. Combining
two signals with a near-zero cell will return almost nothing, which is exactly the trap that made
criteria-heavy order matching silently come back empty. Click any cell to open that combination in List Builder.
| Loading… |
Couldn't load overview stats.
Order readiness
What we can actually deliver against each open request, based on the geography the client asked for.
Motivated excludes plain absentee owners — that flag covers 55% of all properties and on its own
selects for nothing.
| Age | Client | Geography parsed | Properties | Motivated | Requested | Verdict |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Buy a list — fulfillment
Requests placed via the client portal's Skip Tracing → Buy a list tab. Upload the finished list to mark a request ready — it becomes downloadable in the client's portal immediately.
| Loading… |
Pull more data
Pulls directly from each county's own free open-data API — no vendor, no cost. Building characteristics (beds/sqft/year built) aren't available from Cook's pilot source; DuPage includes assessed value but not beds/sqft/year built either. Equity/mortgage is never available (not public record). Start with a small limit to check results before widening.
Full-county backfill (background)
A scheduled job pulls a small page of every Cook/DuPage township/county every 2 minutes, automatically, with no action needed here.
Loading…
Filter
Advanced filters
Property-characteristic fields below (Beds/Baths/Sqft/Year Built/Lot Sqft/Stories/Garage/Attic/Basement/Property
Use Type) are Cook County only -- DuPage's open-data source has no equivalent fields, so combining any of
these with DuPage selected will correctly return zero results.
Ownership
Property characteristics (Cook only)
Financial & sale info
Review
Results (0)
Address is always shown. Pick any of the other 43 available fields to add as columns.
Run a search to see matching properties.
Orders placed on proptechnologyai.com/skiptrace. Auto-refreshes every 10s while this sub-tab is open.
Fulfillment via Ninja Skip Tracing is manual (they're UI-only, no bulk API) — use each row's Export
button to send that order to Ninja, then Import to bring their results back. The customer is emailed
automatically the moment Import completes; the row's Email button is just a resend if needed.
Total Orders
—
In Progress
—
Completed
—
Needs Attention
—
Revenue
—
| Submitted | Records | Price | Status | Updated | Results | Actions | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Order readiness
What we can actually deliver against each open request, based on the geography the client asked for.
Motivated excludes plain absentee owners — that flag covers 55% of all properties and on its own
selects for nothing.
| Age | Client | Geography parsed | Properties | Motivated | Requested | Verdict |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Data Order Requests
No data order requests yet.
No tasks have been created yet — add one under User Management > Tasks and it'll show up here.
Calls
—
Texts
—
Appointments
—
Emails
—
Call Log
—
Agent Report
—
Productivity
—
Showing
—
Pending
—
Accepted
—
Rejected
—
Logged hours
—
Agents shown
—
Leads submitted
—
Accepted
—
Rejected
—
Sent PrimeHome Buyers
—
Sent gyhomes
—
Logged hours
—
Your account isn't granted access to any Activity reports. Ask an Owner/Admin to grant access under User Management → User Types.
| Start Time | End Time | Agent | Contact | Direction | Call Status | Disposition | Call Duration | Phone Number | Recording |
|---|
| Sent At | Client | Kind | Message | Sent By |
|---|
| Start Time | End Time | Timezone | Agent | Contact | Appointment Status | Appointment Title | Meeting Location |
|---|
Email activity tracking isn't available yet — GHL doesn't attribute inbound emails to a specific agent, so there's nothing to show here.
| Date | Agent | Contact | Campaign | Direction | Disposition | Duration | Phone |
|---|
| Date | Agent | Login ID | Shift Start | Shift End | Logged Time | Ready Time | Break + Lunch | Meeting Time | Talk Time | Calls Made |
|---|
| Date | Agent | Ready % | Talk % of Ready | Calls / Ready Hr | Calls / Logged Hr | Calls Made | Calls Connected |
|---|
| Submitted At | Agent | Task | Fields | Status | Actions |
|---|
| Agent | Role | Leads Submitted | Accepted | Rejected | Sent PrimeHome Buyers | Sent gyhomes | Logged Hours |
|---|
Select a message on the left, or click Compose to write a new one.
Your role doesn't have permission to email people directly.
| Time | Admin | Action | Details |
|---|
Import Weekly Transactions Report (xlsx)
Callers
—
Dialers
—
Data records
—
Acquisitions
—
Total profit
—
Profit by category
Data $0.05/record (10k/mo full-time · 7.5k/mo part-time) · Dialer $200/mo/unit · Caller + Acquisition split the remainder| Category | Units | Profit | % of total |
|---|
Weekly trend
| Week of | Callers | Dialers | Data records | Acquisitions | Total profit |
|---|
Transactions
⚠ highlighted = negative caller remainder
| Date | Customer | Product | Cadence | Amount | Callers | Dialers | Data | Acq | Caller $ | Dialer $ | Data $ | Acquisition $ |
|---|
Chat Logs
Owner/Admin oversight — every Communication post, DM, and group conversation company-wide, read-only.
Only visible here; nothing about viewing a conversation shows up to the people in it.
Campaign Subscriptions
Loading…
Pending campaign payments
Campaign requests submitted but not yet paid — nothing is created for these until payment completes.
| Campaign | Client | Tier | Dialer | Data | Requested | Payment Link | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Discount codes (campaign checkout)
Creates a real Stripe promotion code a client can enter at checkout when creating a paid campaign. One-time use per code (not recurring across renewals).
| Code | Discount | Redeemed | Status | Expires | |
|---|---|---|---|---|---|
| Loading… | |||||
One-time client charges
Charge a specific client a one-time amount (e.g. a setup fee) via Stripe. By default nothing is charged until the client pays it themselves from their own Billing tab or you send them a payment link — or use Charge now on a pending row below to debit their saved payment method directly. If a direct charge fails (declined card, no payment method on file, etc.), the reason is shown in the Status column so you know exactly why. Once a charge is paid, Partial refund in that same column issues a full or partial refund straight through Stripe, however it was originally paid.
| Client | Description | Category | Amount | Status | Created | Payment Link | Charge now / Refund | ||
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
Campaign pricing
Monthly campaign pricing used at checkout and for add-on changes (caller tiers, dialer, data). Editing here updates the single shared source every pricing calculation reads from — no code changes or redeploys needed. Existing subscriptions are not retroactively changed; a new price only applies to new checkouts and future add-on changes.
iSpeedToLead Postbacks
Postbacks received
—
Applied to a lead
—
Accepted
—
Rejected
—
Needs review
—
Needs reconciliation
—
Total Purchased ($)
—
Total Accepted ($)
—
Total Refunded ($)
—
| Received At | Phone | Agent | Raw Status | Mapped Status | Amount | Rejected Reason | Matched Via | Applied? | Reconciliation |
|---|
Skiptrace Credits
—
Credit History
| Date | Client | Type | Credits | Note |
|---|---|---|---|---|
| Loading… | ||||
Commission & Payroll Liability
What's owed to agents for the period below — basic pay plus any
lead bonus/extra-target bonus they've earned (same formula as
Reports -> Payroll, see Schedule cards for each agent's
target/rate setup). Compare this against the revenue shown
elsewhere in Finance for the same range to see real margin, not
just revenue.
Accepted leads (period)
—
Total commission owed
—
Total basic pay owed
—
Total payroll liability
—
| Agent | Accepted Leads | Target | Lead Bonus | Extra Bonus | Basic Pay | Total Owed |
|---|
Taxes
Import Bank Statement (CSV)
Or, in RelayFi: Accounts → Statements → Export → Email statements → send to the connected invoices inbox (Taxes → Invoice Archive shows which address) — then sync it in here. Links expire ~4 hours after RelayFi sends them, so sync soon after.
Total Spend
—
Total Deposits
—
Net
—
Total Deductible
—
Transactions shown
—
Spend by category
| Category | Amount | % of spend |
|---|
Monthly trend
| Month | Spend | Deposits | Net |
|---|
Transactions
| Date | Account | Payee | Description | Amount | Category | Transfer? | Deductible? |
|---|
Import invoices from Gmail
Connect one or more Gmail inboxes — they don't need to be the one used for client email, and you can connect more than one (e.g. a personal inbox some vendor bills go to, alongside the shared business one). Each connected inbox is scanned for invoice/receipt/bill emails carrying a PDF or image attachment, archiving every match below automatically. Every archived invoice is also forwarded to RelayFi's receipts inbox so it auto-attaches to the matching bank transaction there. Checks weekly on its own; use "Sync now" to check all connected inboxes immediately.
Loading…
Archive an invoice / receipt
Archived invoices
No invoices archived yet.
Stripe Income
Every charge, refund, and adjustment actually settled to this Stripe account in the selected range, straight from Stripe's own balance ledger — not reconstructed from this app's own billing tables, so it can't miss a payment path this app doesn't know about.
| Date | Type | Description | Amount | Fee | Net |
|---|---|---|---|---|---|
| Pick a date range and click Run report. | |||||
Link invoice to a bank transaction
Candidates within 10 days and 2 cents of this invoice's amount and date.
Choose a card to charge
+ New Campaign
Same fields the client fills in from their own portal's "+ New Campaign" button. Unless marked complimentary below, nothing is charged here — generate a payment link afterward from Finance → Stripe Pending Payment.
Campaign auto-cancels the day after this date unless extended.
Criteria answers (all required)
Convert to paid
Choose what the client will actually be billed for. This creates a pending payment request — use "Get link" under Finance → Stripe Pending Payment afterward to actually charge them.
Resume campaign
Choose what the client will be billed for going forward. This reuses the same campaign name, lead history, and Campaign Guide, and creates a pending payment request — use "Get link" under Finance → Stripe Pending Payment afterward to actually charge them.
Submit a candidate
Result: Not passed
Your submissions
| Candidate | Type | Interview | Start date | Submitted | Status | Reason |
|---|
You haven't submitted any candidates yet.
Candidate review
| Candidate | Mobile | Contact phone | Address | Type | Interview summary | Fit? | Checklist | Video | ID/Passport | Start date | Submitted by | Submitted | Status | Actions |
|---|
No candidates to review.
Welcome email settings
Sent automatically when a candidate is approved (unless unchecked in that modal). Placeholders:
{first_name} {full_name} {position} {email} {password} {meeting_datetime} {meeting_info} — the last two come from the Approve modal's own date/time picker and the onboarding meeting block below.
EGP 0 earned so far
EGP 1,500 per candidate you submitted, once they've been approved, given an employment start date, been active for at least 14 days since that date, and are still an active account. Only candidates approved with a recorded start date appear below.
My commission
| Candidate | Start date | Days employed | Account status | Commission status | Amount |
|---|
No approved candidates with a recorded start date yet.
Candidate history archive
Every candidate ever submitted, across every status — a permanent audit trail. Approve/Reject stay under Candidate Review; Edit here corrects a candidate's own details (name/email/mobile/etc.) and can replace their video/ID document — same permission as Candidate Review's own Edit.
| Candidate | Mobile | Contact phone | Address | Type | Interview summary | Fit? | Checklist | Video | ID/Passport | Start date | Submitted by | Submitted | Status | Reason | Reviewed by | Reviewed | Actions |
|---|
No candidate submissions match these filters.
Edit candidate —
Leave blank to keep the current video. Choosing a file replaces it.
Leave blank to keep the current document. Choosing a file replaces it.