Module overview

Pick the areas that match how you operate

FullVue is modular. Enable Field, Counter, Accounting, Rentals, Email, and more when they fit how you operate—without buying a separate product for each department. Sales, jobs, field, invoicing, purchasing, and workforce tools share one permissioned system.

AI

Pain: Answers live in reports and tabs—owners spend Monday hunting instead of deciding.

Outcome: A permission-aware assistant that answers questions from your FullVue data, plus assist-tier polish and table explanations. Read and assist only—metered with AI credits, no silent edits.

  • Ask natural-language questions about jobs, sales, and operational data you can already see
  • Get answers grounded in FullVue—not a generic chatbot
  • Use assist-tier polish and table explain for everyday clarity
  • No write mode—it does not post invoices or rewrite jobs

Core

Pain: Job detail, labor, materials, and customer context live in different places.

Outcome: Core is the company hub—customers and vendors, jobs with costing, inventory, permissions, search, and settings—so every other module has a single source of truth. Invited customers can use the portal for jobs, quotes, invoices, and documents where you enable it.

  • Run jobs with tasks, materials, mileage, extras, and audit-ready states
  • Maintain customers, vendors, locations, and role-based access
  • Find records fast with global search and home dashboard widgets
  • Configure PDF templates, announcements, and onboarding for new teams

Field

Pain: Dispatch and field staff do not see the same schedule and job context.

Outcome: Field turns daily road sheets, schedules, mileage, and on-site closeout into operational truth—so office and crew stop arguing from different notes.

  • Capture daily field records tied to jobs
  • Schedule field work and track job mileage
  • Close out on site with photos and customer signature when configured
  • Keep working with offline-friendly field sync when signal drops

Invoicing

Pain: Billing drifts away from what crews logged on the job.

Outcome: Turn completed work into invoices and payments, including public pay-by-link so customers can pay by card after FoundTech Payments is set up.

  • Create and send invoices tied to jobs and sales
  • Record payments and track AR in the same system
  • Share pay links customers can open without a staff login
  • Keep billing documents on brand with templates

Sales

Pain: Opportunities die in inboxes and quotes never tie cleanly to executed jobs.

Outcome: Track pipeline work, build structured quotes, collect signatures on customer-facing quote links, and convert wins into jobs with estimates you can compare to actuals later.

  • Opportunity tracking with structured detail
  • Quote builders and customer-facing quote signing links
  • Convert accepted quotes into jobs for downstream billing

Accounting

Pain: Operators who need a real ledger still retype cash documents into a side system—or get sold a fake “sync.”

Outcome: An in-app general ledger—AR/AP, journals, bank reconciliation, budgets, and financial reports—with file-based bank import. Pair it with one-way QuickBooks Online push when your accountant lives in QBO.

  • Maintain chart of accounts, journals, and fiscal periods
  • Reconcile bank accounts and import CSV/OFX/QFX files
  • Run financial reports without exporting to a side spreadsheet first
  • Optional one-way QuickBooks Online push—not two-way sync, not live bank feeds

Purchasing

Pain: Parts orders outrun receiving and invoices rarely tie back to jobs.

Outcome: Formal POs, vendor records, bills, and inventory balances stay aligned so crews bill what they actually used.

  • Create purchase orders routed to vendors
  • Follow PO lifecycle from submitted through received
  • Match vendor bills and payments
  • Inventory counts tied into operational workflows
  • Units conversions between stocking and selling when sizes differ

To-Dos

Pain: Non-job tasks disappear into sticky notes.

Outcome: Shared execution lists with owners, statuses, and notes so operational follow-through stays visible.

  • Capture assignments outside formal jobs
  • Track progress with notes hand-offs between shifts

SDS

Pain: Compliance binders do not travel with crews.

Outcome: Central SDS library that stays searchable—especially valuable when hazardous materials documentation matters for audits or safety meetings.

  • Upload SDS revisions once
  • Search quickly when crews ask “which revision is current?”

Human Resources

Pain: Personnel notes scatter across email and folders.

Outcome: Structured HR records—benefits, pay bands, reviews, kudos, and corrective notes—with timelines people can act on.

  • Benefits enrollment snapshots per employee
  • Performance reviews tied to roles
  • Document coaching moments for accountability

Products

Pain: Serial numbers, BOM hints, and repair history live on paper.

Outcome: Product catalog entries linked into sales and support conversations so technicians quote parts confidently.

  • Structured specs per SKU or assembly
  • Faster lookups when diagnosing repeat repairs

Customer Support

Pain: Callbacks bounce between voicemail and spreadsheets.

Outcome: Tickets anchored to customers and installed products so resolutions capture labor and parts when billing applies.

  • Issue threads alongside catalog context
  • Track shipped parts or onsite labor for invoices

Production Meetings

Pain: Morning huddles never capture commitments.

Outcome: Standing agenda tooling before, during, and after meetings so production rhythms leave an audit trail.

  • Central place for notes and follow-ups tied to ops cadence

Assets

Pain: Fleet tools, shop equipment, laptops, and software licenses live in separate registers—or nowhere at all.

Outcome: One unified asset register for equipment, devices, components, and software—with assignments, costs, attachments, and links between records.

  • Shop and fleet equipment with assignments and utilization
  • Devices, components, and software in the same module
  • Configurable asset types and ties to Rentals when enabled

Rentals

Pain: Rental reservations and returns do not connect to the assets you bill or dispatch.

Outcome: Reservations, checkout, and returns tie to rentable asset types—aligned with jobs and customer visibility in the portal.

  • Rental reservations and checkout workflows
  • Returns tracking against rented assets
  • Connected to Assets categories you mark as rentable

Counter

Pain: Counter sales and memberships sit outside the job software your crews already use.

Outcome: Register-oriented dashboards, promotions, memberships, loyalty, punch cards, promo codes, fees, and stored value—alongside traditional sales and job permissions.

  • POS dashboard and register workflows
  • Promotions, memberships, loyalty, and stored value
  • Permissioned with the sales and job areas you already run

Tether

Pain: Decisions made in texts and email never tie back to jobs or customers.

Outcome: Team channels, DMs, customer chat for staff, and personal notes—coordination inside FullVue instead of another chat app.

  • Group channels and direct messages
  • Customer chat for service conversations
  • Voice notes with optional transcription

Planner

Pain: Personal calendars ignore the jobs, quotes, and todos already in your system.

Outcome: Time-blocking with reminders on a calendar layered on operational items—jobs, quotes, todos—so individuals see their day in context.

  • Personal schedule blocks with reminders
  • Layers for jobs, quotes, and todos
  • Complements Field schedules—not a replacement for dispatch

Email

Pain: Work lives in FullVue; the inbox lives in another tab—and context never meets.

Outcome: Employees connect Google, Microsoft, or IMAP mailboxes to read and send from FullVue—separate from company transactional document email.

  • Connect per-employee Google, Microsoft, or IMAP accounts
  • Work inbox and compose without leaving FullVue
  • Keep mailbox access distinct from Resend document senders
  • Reduce tab-hopping between CRM-ish work and the inbox

SMS

Pain: Job updates and review asks live in personal phones—or never go out at all.

Outcome: Consented job texts, opt-in handling, review invites, and an optional AI receptionist for unmatched inbound leads—texting as a module, not a side spreadsheet.

  • Text customers about jobs with consent-aware messaging
  • Manage opt-in and opt-out the right way
  • Optional AI receptionist for after-hours lead capture—not a full phone agent

Attendance

Pain: Clock punches and schedules are reconciled in spreadsheets after payroll is already wrong.

Outcome: A time clock plus staff scheduling that produces payroll-ready reports your bookkeeper or payroll provider runs with—and lets leadership compare punch time to job time.

  • Quick in/out punches from navigation
  • Week rosters, shift swaps, availability, and PTO accruals
  • Period hours generated from punches—export for your payroll provider
  • Aligns with Human Resources workflows

Need help sequencing modules?

Start a trial with Core plus the areas you leak margin—usually jobs and invoicing—then add purchasing, attendance, or Accounting as the data trusts the system.

Top