Septic Website vs Field Service and Dispatch Software: What Should Own What?

Overview

A septic business can use a website/CRM and field-service software at the same time.

The clean architecture is simple:

the website owns the customer journey before service; field software owns the job after acceptance.

What the public website should own

Usually:

Current OneStudio features fit this layer.

• service pages;
• service areas;
• quote/service request;
• routine booking when appropriate;
• ordinary client/contact history;
• marketing source;
• reviews/media;
• public analytics.

What septic field-service software should own

Usually:

• accepted job;
• property/system record;
• truck;
• technician/crew;
• route;
• tank/service history;
• field notes;
• completion;
• disposal/waste record where required;
• operational invoice.

Keep the customer separate from the property

One client can own or manage:

The CRM relationship belongs to the person/company.

The operational job belongs to the service property.

• home;
• rental;
• commercial property;
• multiple sites.

Keep the public request separate from the field job

Customer:

Pump 1,000-gallon tank next week. Lid probably buried.

Field system may later contain:

Keep both.

The request preserves what the customer said.

The work order preserves what happened.

• verified tank size;
• lid location;
• truck assignment;
• route;
• arrival;
• actual service;
• disposal;
• completion.

Keep septic asset history specialist

A property record may eventually include:

Do not turn the ordinary CRM contact card into a septic system database.

• tank;
• size;
• location;
• lids/risers;
• prior service;
• pump;
• alarm;
• drainfield notes;
• photos.

Keep dispatch specialist

Truck routing can depend on:

A calendar slot is not the same as an optimized route.

• geography;
• truck capacity;
• disposal site;
• service duration;
• crew;
• emergency jobs;
• traffic;
• time windows.

Keep route changes out of the public promise

A homeowner may request Tuesday morning.

Operations may need to confirm:

Use booking confirmation or request-first rules where route capacity matters.

• route fit;
• crew;
• truck;
• access;
• disposal cycle.

Keep disposal/waste records specialist

Pumping operations may need records for:

OneStudio should not be positioned as the compliance record.

• gallons;
• truck;
• disposal;
• receiving site;
• manifests/tickets;
• local requirements.

Keep field proof attached to the job

Operational records can include:

Keep these with the field job.

Publish marketing images only after approval.

• before/after photos;
• access notes;
• tank condition observations;
• work performed;
• completion.

Keep invoice ownership clear

If field-service software owns:

it should usually own the operational invoice.

OneStudio payment status should not create a second invoice truth.

• performed service;
• additions;
• disposal;
• truck/crew;
• final amount;

Use one explicit handoff

Choose:

Septic service request accepted into field operations

Before handoff:

After handoff:

• website;
• request/booking;
• ordinary client/contact;
• marketing source.
• property;
• job;
• truck/crew;
• route;
• field notes;
• disposal;
• invoice.

Source-of-truth matrix

24 acceptance tests

1. Website and field software have explicit roles.
2. Client and property are separate.
3. Request and work order are separate.
4. Customer tank size remains historical.
5. Handoff has one explicit trigger.
6. Verified property has one owner.
7. Septic asset has one owner.
8. Service history has one owner.
9. Work order has one owner.
10. Truck assignment has one owner.
11. Crew has one owner.
12. Route has one owner.
13. Arrival/field status has one owner.
14. Field photos have one owner.
15. Work performed has one owner.
16. Gallons/disposal record has one owner where needed.
17. Completion has one owner.
18. Operational invoice has one owner.
19. Public CRM excludes route data.
20. Public CRM excludes compliance records.
21. Public booking is not assumed to be dispatch.
22. Customer messages have one stage owner.
23. Website URLs can survive field-software changes.
24. Staff can explain the boundary in one sentence.

Give the website the relationship and the field system the route

The public layer should make the company easy to find, understand and contact.

The field layer should make every property, truck and service job operationally traceable.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask