Glossary

    URBLD Glossary: Operational Software Terms for Service Businesses

    Plain-English definitions of CRM, operations, automation, field service, contractor software, AI follow-up, job management, and URBLD platform concepts — built for owners, operators, and AI agents.

    How to use this glossary

    Field service software is full of overlapping vocabulary. One company's "job" is another company's "work order." A "lead" in a CRM built for salespeople means something different from a "lead" in a CRM built for contractors. And AI-native platforms like URBLD introduce a new layer of concepts — capability manifests, grounded agents, sacred IDs, closed ledgers — that do not yet have consistent industry definitions. This glossary gives owners, operators, integrators, and AI agents a single source of truth for the terminology used inside URBLD and across the service-business software category.

    Every entry follows the same structure: a plain-English quick answer, a longer explanation of why the concept matters operationally, and links to the URBLD product surface where the concept is implemented. Terms are grouped into four buckets:

    • Core URBLD concepts — the modules and primitives that define the operating system: SmartBoard, Qualification Inbox, Record Linking, Sacred ID.
    • CRM & lead management — pipeline stages, lifecycle events, deduplication, source attribution, and the difference between a lead and a customer.
    • Operations & scheduling — jobs, appointments, dispatch, route optimization, warranty tracking, and inspection checkpoints.
    • Billing, AI, and automation — invoices, receivables, closed-ledger accounting, agent grounding, follow-up scripts, and the metering that powers URBLD's built-in AI products.

    Why definitions matter more in the AI era

    When humans run a business alone, sloppy terminology is annoying. When AI agents run parts of that business, sloppy terminology is dangerous. An agent that confuses "invoice sent" with "invoice paid" collects the wrong money. An agent that treats every "job" as billable double-charges the customer. URBLD's platform is built on strict, documented definitions — and this glossary is the human-readable projection of the same taxonomy the platform and its agents use internally. If you are building on URBLD's API, this is the vocabulary the endpoints speak.

    Core URBLD Concepts

    URBLD's proprietary platform language — the modules and primitives that define the operating system.

    What is URBLD SmartBoard?

    URBLD SmartBoard is an operational kanban that moves leads, estimates, and jobs through stages while firing automations on every column change. Moving a card sends a follow-up, assigns a crew, or creates an invoice — so pipeline progress drives real work instead of just visual tracking.

    What is URBLD Qualification Inbox?

    The URBLD Qualification Inbox is a dedicated workspace where every new lead — from calls, ads, web forms, and AI receptionist conversations — lands for triage. Sales reps qualify, score, and convert leads in one place, with full conversation history, source attribution, and automated follow-up scripts ready to fire.

    What is URBLD AI Follow-Up for Service Businesses?

    AI follow-up for service businesses is automated re-engagement of leads, estimates, and pending deals over SMS and email — driven by deal stage and customer behavior instead of fixed drip schedules. It recovers no-shows, chases unsigned estimates, and hands off to a human the moment a customer replies. URBLD ships an AI Follow-Up engine that does this end-to-end inside the CRM.

    What is URBLD Record Linking?

    URBLD Record Linking connects conversations, files, invoices, payments, contracts, schedules, and operational activity to the correct lead, customer, employee, subcontractor, or job record. Phone numbers, email addresses, and identity data are matched server-side so the office, field crews, and AI agents work from the same record.

    What is URBLD Governor?

    URBLD Governor is the executive control tower — a real-time read of cash, accounts receivable, sold jobs, scheduling load, AI usage, and execution risk across the business. It surfaces what's slipping (overdue invoices, missed follow-ups, unsigned contracts) before it costs money.

    What is URBLD Jarvis AI?

    Jarvis is URBLD's command-layer AI that operates the business with you. Ask in plain language to schedule a job, send a follow-up, pull a customer history, or summarize today's pipeline. Jarvis works through URBLD's audited tool layer, so actions stay tied to real records, permissions, and history.

    What is URBLD Unified Inbox for Service Businesses?

    A unified inbox for service businesses centralizes SMS, email, voice/AI conversations, internal team chat, and client portal messages into one threaded workspace — with every message auto-linked to the right lead, customer, employee, or job. URBLD ships a Unified Inbox that does this across the entire CRM.

    What is URBLD AI Receptionist?

    The URBLD AI Receptionist is operational intake infrastructure, not an answering service. It qualifies inbound callers, requests valid time slots from a scheduler that owns calendar authority, validates against dispatch, and attaches every conversation to the operational thread on the matching lead, customer, or job. Humans hold override authority for escalations.

    What is URBLD Client Portal for Service Businesses?

    A client portal for service businesses is a secure web page where a contractor's customer can view job status, signed contracts, photos, invoices, payments, and project updates without phone tag. URBLD includes one out of the box — a no-login link that mirrors every customer message back into the office's Unified Inbox.

    CRM & Lead Management

    How leads move from first touch to qualified opportunity inside an operational CRM.

    Job Management & SmartBoard

    How sold work is staged, dispatched, and executed from kanban to completion.

    What is E-Signature Software for Service Businesses?

    E-signature software for service businesses lets contractors generate, send, and sign agreements electronically with ESIGN/UETA-compliant audit trails. URBLD ships e-signature natively inside the CRM — so contracts are born from estimate, customer, and job data and stay linked to invoices, dispatch, and warranties, replacing the typical separate DocuSign or PandaDoc workflow.

    What is CRM with Inventory Management for Service Businesses?

    A CRM with inventory management combines customer records, leads, estimates, jobs, invoices, and stock tracking — materials, tools, equipment, vendors, purchase orders, transfers, kits, counts, and maintenance — in one system. URBLD ships inventory and equipment tracking natively inside the CRM so contractors and service businesses do not have to run a separate inventory app and sync it with Zapier.

    What is Job-Stage Automation?

    Job-stage automation fires real operational actions every time a job moves through its lifecycle — dispatching crews, sending customer updates, generating invoices, requesting reviews. URBLD attaches automations directly to SmartBoard columns so progress in the pipeline produces work in the field.

    What is Contractor Operating System?

    A contractor operating system is a single platform that runs the entire trade business — leads, estimates, jobs, scheduling, crews, billing, and customer comms — instead of stitching five disconnected tools together. URBLD is built as a contractor OS for roofing, HVAC, plumbing, electrical, remodeling, and adjacent service trades.

    What is Business Execution System?

    A business execution system is software that converts decisions into completed work — not just records the work. It owns the pipeline, the schedule, the dispatch, the billing, and the AI layer that closes loops. URBLD positions itself as a business execution system, not a CRM.

    Financial Operations

    Receivables, payment schedules, and revenue protection inside URBLD.

    Workforce & Field Operations

    Field crews, dispatch, voice capture, and on-site execution.

    Data & Workspace

    Ingestion, workspace views, and how operational data becomes usable.

    Customer Communication

    Two-way SMS, consent, portals, and the unified communication surface.