Provide the technician and crew roster, identity mappings, service categories and certifications, customer locations and time zones, recurring agreements, working windows, parts and opening stock evidence, customer price policy, estimate limits, required completion evidence, communication permissions and scoped connector access.
Implementation
Configure the service operation around its real appointments and controls.
Implementation phases
- Prepare the operational modelYour team
- Configure assignments and workTeam and ERP.ai
- Configure decisions and billingTeam and ERP.ai
- Rehearse exceptionsTeam and ERP.ai
- Release and observeTeam and ERP.ai
Phase 1 · Your team
Prepare the operational model
Your team: provide the technician and crew roster, identity mappings, service categories and certifications, customer locations and time zones, recurring agreements, working windows, parts and opening stock evidence, customer price policy, estimate limits, required completion evidence, communication permissions and scoped connector access.
Phase 2 · Team and ERP.ai
Configure assignments and work
Test skill expiry, crew capacity, customer windows, travel assumptions, access notes and supported mobile behavior with representative visits.
Phase 3 · Team and ERP.ai
Configure decisions and billing
Set independent estimate limits, customer signature evidence, required collection policy and effective tax inputs. Reconcile payment and AR request outcomes.
Phase 4 · Team and ERP.ai
Rehearse exceptions
Exercise duplicate intake, offline replay, reassignment, insufficient stock, rejection, cancellation, refund and uncertain connector outcomes.
Phase 5 · Team and ERP.ai
Release and observe
Release the reviewed configuration, reconcile open work and assign owners for dispatch, mobile, inventory and billing exceptions.
Use Proto to propose changes on a reviewable branch. Test scheduling, signature applicability, stock balance effects and integration reconciliation against existing records before release. Version changed rules for future work; preserve accepted appointments, signed scope and posted transaction history.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.