Pocket Isa docs

What Pocket Isa is

Pocket Isa tells your team which lead to work right now, what to do about it, and what to say. It runs on top of the CRM you already use, so nothing gets migrated and nothing gets replaced.

It answers three questions on every lead:

• Who should I work right now? Every lead gets a score out of 100 and the queue is ranked by expected revenue and urgency.
• What should I do? Each lead carries one recommended next action, with the reason behind it.
• What should I say? The Copilot drafts the email or text and sends it once you confirm.

Pocket Isa is not a CRM and does not try to be one. Keep Follow Up Boss, Real Geeks, or KW Command. Pocket Isa is the decision and execution layer on top.

The loop, in 4 steps

Everything in the product is one loop repeated: a lead arrives, it gets scored, it gets a next action, and the outcome teaches the system. Click through it below.

That is the whole product. Once the loop is running, the only thing that changes is how much of it you let Autopilot handle.

Quickstart: first 5 minutes

Zero to your first sent message. No CRM migration at any point.

1. Connect your leads. Open Connect in the sidebar and pick where your leads come from. Zapier is the fastest path and needs no code.
2. Open your top lead. Go to Dashboard. The queue is already ranked, so start at number one.
3. Tap Ask Copilot. Ask what to do and let it draft the message.
4. Send it. Review the draft, then confirm. Email sends immediately.
5. Log the outcome. Mark the call, text, or meeting result so future recommendations get sharper.

Short on time? Do steps 2, 3, and 4. That is the loop, and it works before your data is fully connected.

What is live today

Pocket Isa is in active beta. This table is the honest state of each channel so nothing surprises you mid workflow.

Calls are never automated, by design. Pocket Isa tells you who to call and what to open with, but a human always dials.

Plans and trial

Every new team starts with a 14-day trial after access is approved. Founding pricing is locked for life for the first 50 teams: Team at $199 per month and Growth at $399 per month, versus list pricing of $299 and $499.

• Team covers up to 10 agent seats. Growth covers up to 25 with higher AI fair-use limits and hands-on onboarding.
• Brokerage is custom, for rollouts across multiple teams.
• Teams already in the beta stay free through the beta and lock the founding rate the day it ends.

Your daily workflow

Open the app, work the queue top down, log what happened. That is the day.

1. Open Dashboard and start at the top of the priority queue.
2. For each lead, take the recommended action, or tap Ask Copilot if you want the reasoning or a draft.
3. Use the Execution Box to send the email, log the call, or log the text.
4. Move to the next lead. Do not cherry-pick. The order is already optimized for revenue and urgency.

The single highest-value habit is logging outcomes. Every logged result sharpens tomorrow's ranking for your whole team.

Reading the queue

Each card in the queue carries everything you need to act without opening the lead.

Rank on the left, score and temperature on the right, the next best action in the middle, and estimated commission with conversion likelihood at the bottom.

• Score (0 to 100) combines Speed, Engagement, Intent, Freshness, and Agent Activity. Open a lead to see the itemized breakdown.
• Temperature (Hot, Warm, Cold) is the fast visual read on the same score.
• Next best action is the one thing to do, already decided.
• Deal value and likelihood tell you what the lead is worth and how probable it is, which is why the order is what it is.
• Alerts at the top flag revenue going cold, so valuable quiet leads do not slip.

Working a lead

Open any lead and the recommended action sits at the top, above the record. Everything else on the page exists to justify it.

• Recommended Action is the single next move: call, email, or text.
• Why this matters shows conversion probability, estimated deal value, and expected timeline, so you can trust or overrule the call.
• Ask Copilot opens a chat that explains the reasoning and drafts what to say.
• Generate Call Playbook builds a personalized opener, likely objections, and questions from this lead's own history.

Always log outcomes. The system learns your team's real results, not generic averages.

Execution Box

One place to act on a lead, sitting directly under the recommended action.

• Email Live Sends from your connected email and logs automatically.
• Call Manual Dial from your phone, then log the result here.
• SMS Coming soon Unlocks automatically once Twilio is connected. Until then, generate the draft here and send it from your phone.

During beta only Email is automated. To get SMS ready, connect Twilio in Settings, then Integrations.

Copilot

The Copilot is a chat attached to every lead. It reads that lead's real history, answers in plain language, and can act for you once you confirm.

Things worth asking it:

• Why is this lead hot, or why is it cooling?
• What is the exact next step, and why that one?
• Write the follow-up email or text for me.
• What did we last talk about, and what did they care about?

It remembers the conversation per lead, so you can close the chat and pick up where you left off. Actions it can take on your confirmation: send the email, log a call, or update the lead.

Typical Copilot round trip is about 30 seconds: ask, read, confirm, done.

Autopilot

Autopilot sends follow-up emails for you so leads do not go cold while you are busy closing.

• Email only today. SMS automation needs Twilio. Calls are never automated.
• You must turn it on. An admin records consent before anything sends.
• You can pause or stop it at any time, per lead or across the board.
• Failsafes are built in. It pauses itself if negative replies spike.

Start in Suggest mode and read what it would have sent for a week. Move to Send once the drafts stop surprising you.

How Autopilot works → Guardrails, variants, and the learning loop in more depth.

Get help

Stuck on something, or found a screen that does not explain itself? Use the Feedback button in the top right of the app. We read every message during beta and usually reply the same day.

Managing leads

• Assign and reassign from any lead. Ownership can change at any time without losing history.
• The priority queue ranks automatically by conversion probability times deal value times urgency. Nobody hand-sorts anything.
• Revenue at risk surfaces deals slipping from no contact or a stalled stage, so you can intervene before they die.

Team and roles

• Invite users from Settings, then Team. They receive a secure invite link.
• Roles: Admin has full access, Manager sees the whole team, Agent sees assigned leads only.
• Deactivate rather than delete when someone leaves, so their history stays intact for reporting.

A seat is anyone who works leads in Pocket Isa, agents and ISAs alike. Team covers up to 10 seats and Growth up to 25. See pricing for what happens past that.

Performance tracking

Team Performance is per agent, sorted by what matters most, and filterable by 7, 30, or 90 days or all time. Every agent is a row, grouped into pipeline and conversion, speed and activity, then outcomes and quality. Click any row to open a drill-down with that agent's funnel, top leads, stale leads, and recent activity.

• Pipeline and conversion: assigned, open, qualified, won, lost, conversion rate, pipeline value.
• Speed and activity: average first response time, calls, emails, texts.
• Outcomes and quality: win rate, average deal size, and where leads stall.
• Overdue actions: the count you actually manage against week to week.

Use response time for coaching before you use win rate. Speed is the number an agent can change tomorrow.

Revenue Insights

Pipeline intelligence for the weekly review, not another vanity dashboard. Response time, stale leads, and hot leads missed sit up top as the numbers to act on. Below, leads by source and score distribution show where your good leads actually come from.

• Pipeline Health Score is one number summarizing risk and momentum.
• Weekly Closing List is the deals most likely to close this week.
• Lost Revenue Analysis shows where deals leak and why.
• Leads by source tells you which channels deserve more budget.

Autopilot controls

Autonomy levels

• Suggest proposes the next message. Your agent sends it.
• Draft and Wait writes and queues it. Your agent approves.
• Send delivers automatically inside the guardrails.

Monitoring

The Autopilot Activity screen answers one question: is this safe to run right now, and what should I change? When risk crosses the threshold, Autopilot says stop in plain language, gives the reasons, and lists what to change. Health Score and Autonomy Confidence show whether it has enough data to be trusted yet.

Consent and failsafes

• An admin must explicitly enable Autopilot. Consent is recorded before anything sends.
• It pauses itself if the negative reply rate spikes past your threshold.
• It caps how often any single lead can be contacted.
• It blocks sending outside business hours unless you override that.

When to enable or disable

• Enable when follow-ups are being missed or response time is slipping.
• Disable during a sensitive campaign or while you are testing new messaging by hand.

Best practices

Which method to use

Four ways to get leads in. Most teams are live within 48 hours and never write code. If you are on Real Geeks, use the native connector: it is the fastest and it brings your buyers' browsing activity with it.

Not sure? Use Zapier. It handles ongoing flow and you can still drop a CSV in for historical leads.

Real Geeks (native)

If your site runs on Real Geeks you do not need Zapier or a developer. Real Geeks posts leads straight to Pocket Isa, and unlike a CSV or a Zap it sends the buyer's browsing history along with the contact details.

Set it up

1. In Pocket Isa go to Settings, then Integrations. Under CRM connections pick Real Geeks, name it, and press Create. Copy the Webhook URL and Secret it shows you.
2. Sign in to leadrouter.realgeeks.com.
3. Click Configure Destinations and pick your site.
4. Choose Custom API, then paste in the Webhook URL and Secret.
5. Tick Active and save.

The connection reads "Waiting for the first lead" until Real Geeks sends one. After that it shows when the last lead arrived and how many have come in, so you can tell at a glance whether it is working.

What comes across

Contact details, source, timeframe and tags, plus whether Real Geeks has them down as a buyer or a seller and how urgent they rated them. On top of that we read the activity history, which is the part a CSV cannot give you:

• Properties viewed, including the address and asking price
• Favourites and saved searches
• Home valuation requests, with the estimated value
• Tour requests
• Which agent the lead was assigned to

All of it feeds the score, so someone who has viewed six homes and saved a search ranks above someone who filled in a form and left. Leads are scored on arrival, so they land in the right place in the queue rather than at the bottom.

Real Geeks sends a Potential Seller when someone runs a home valuation but never finishes signing up, so there is an address and no email or phone. We turn those away rather than creating a lead nobody can contact, and Real Geeks stops retrying them.

Other CRMs

Real Geeks is the only native connector today. Follow Up Boss, BoomTown, Sierra, Lofty and CINC come in through Zapier, CSV or the API, all covered below. They are listed in CRM connections but cannot be switched on yet.

Zapier setup

The fastest way to push leads from any tool into Pocket Isa. No code required. The three-step Zapier flow lives in Settings, then Integrations. The same screen is where you connect Twilio to unlock SMS.

1. In Settings, Integrations, REST API, create a key and copy it.
2. In Zapier, start a Zap with your lead source as the trigger (a form, Google Sheet, or your CRM).
3. Accept the Pocket Isa Zapier invite, then choose the Create / Update Lead action. Or use Webhooks by Zapier, POST with the details below.
4. Paste your API key, map the fields, and turn the Zap on.
5. Send a test lead and confirm it appears on your dashboard.

Your Integrations screen shows a live status: it says "Waiting for your first lead" until one arrives, then flips to connected.

CSV import

Best for a one-time upload of leads you already have. For ongoing flow, use Zapier instead. Pick the lead category, grab the sample file if you want the exact headers, then upload. Email is required because it is the deduplication key.

• email is required. It is the unique identifier used to detect duplicates.
• Download the sample file for your industry to get the headers right the first time.
• The auto-mapper handles 100+ header variations and processes in batches of 200 rows.

Do not upload the same file twice. Import can take a few minutes on larger files.

API overview

• Base URL: https://backend.rubyorbit.com/functions/v1
• Auth: send your key in the x-api-key header. Authorization: Bearer YOUR_API_KEY also works. Create keys in Settings, Integrations, REST API.
• Format: JSON in, JSON out.
• Rate limits: generous for normal use. Talk to us before a bulk backfill.

Quick test

curl -X POST https://backend.rubyorbit.com/functions/v1/api-leads-upsert \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"first_name":"Jane","email":"jane@example.com","source":"Website Form"}'

Full API reference → Every endpoint, field, and response shape in one place.

Core endpoints

POST /api-leads-upsert

Creates or updates a lead, matched by email. Use it for form submissions, leads coming from another system, and paid lead-gen delivery.

POST https://backend.rubyorbit.com/functions/v1/api-leads-upsert
Content-Type: application/json
x-api-key: YOUR_API_KEY

{
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane@example.com",
  "phone": "+15551234567",
  "source": "Website Form",
  "category": "real_estate",
  "tags": ["webform", "buyer"]
}

POST /api-timeline-add

Adds an activity to a lead's timeline: a call, email, text, meeting, or note. Use it to sync a dialer or push text replies back in.

POST https://backend.rubyorbit.com/functions/v1/api-timeline-add
Content-Type: application/json
x-api-key: YOUR_API_KEY

{
  "email": "jane@example.com",
  "event_type": "call",
  "event_title": "Discovery call",
  "event_body": "Discussed budget. Wants to see listings this week.",
  "source": "dialer"
}

Find the lead with lead_id or email. Set event_type to call, sms, email, meeting, or note (the default), and describe it with event_title and event_body. source and timestamp are optional.

Timeline activity feeds the score. A dialer sync is usually the single highest-value integration after lead intake.

Data mapping

Required

• email, a valid address. It is how an existing lead is matched, so a phone number on its own is not enough.

Optional

• first_name. If a new lead has none, the part of the email before the @ is used.
• last_name, phone, company_name, website
• source, tags[], notes
• assigned_agent, an agent's email or name. It matches an active agent on your team, or adds a new agent if none matches.

Industry fields

• Real estate: deal_value_min, deal_value_max, bedrooms, preferred_city, pre_approved
• SaaS and services: team_size, use_case, monthly_budget, current_tools

Unknown fields are ignored, not rejected. It is always safe to send extra context, and richer leads score more accurately.