Use case
Customer management (CRM)
Every interaction tied to a client record — jobs, invoices, files, notes, history.
The problem
Customer context is scattered across inboxes, spreadsheets, and people's memories. Service teams need one client record for contact details, addresses, work history, files, estimates, invoices, payment status, communication, and follow-up so the next person can help the customer without asking the same questions again. Clean customer records also make repeat service, billing, booking, and reporting much easier to manage as the company grows.
How it works
- Step 01
One client record
Contact + billing + type + status.
- Step 02
Every job links back
Work items, estimates, invoices, reports, files.
- Step 03
Activity timeline
Open the client → see chronological history.
What it includes
Structured records
Type-aware (individual / company) with billing address.
Status pipeline
Active / inactive / archived.
Permission-aware
Worker / manager visibility differs by role.
Why teams use it
- End spreadsheet sprawl.
- Surface job history on every interaction.
- Keep billing data clean for invoicing.
Modules involved
Frequently asked
Can I import existing customers?
Yes — paste a CSV into the migration center.
Do customers see their record?
Not unless you explicitly share a portal link.
Can two clients share a contact?
Yes — contact details are on the client row.
What about merge / dedup?
Teams can keep records clean with search, filters, activity history, and controlled client updates.
Can workers edit client records?
Role-gated — workers see, manager+ edits.
Is there a client portal?
Yes. BisHub supports client-facing portal and sharing workflows for service-business records.
See it in your account
Sign up free; activate the right modules; start in minutes.