The short answer: delegate repeatable work around customer records, routine booking, schedule communication, estimate follow-up, invoice delivery, recurring service events, reporting, and controlled data entry. Keep technical judgment, unusual pricing, payment authority, user administration, payroll, destructive actions, and final exception decisions with the appropriate manager.
This guide is about a human remote assistant. ServiceTitan also uses “Virtual Agent” for an AI product that can answer calls and book jobs. If you want automated call handling instead of a named office operator, review ServiceTitan's current Virtual Agent documentation.
Start with an individual account, not a shared login
ServiceTitan's current terms say authorized employees or contractors may use the platform, but users must keep credentials secure and paid authorized-user accounts cannot be shared. Give the assistant an individual user profile that fits your subscription and confirm the setup with your administrator or account contact. See the ServiceTitan Terms of Use.
Use role permissions as the starting point, not the finish line. ServiceTitan documents default office and field roles, lets administrators adjust Role Permissions, and notes that users must sign out and back in before changes apply. Review the current role overview and account configuration guide.
The five controls that make delegation workable
- One system owner. Name the person who approves the workflow, resolves exceptions, and reviews results.
- A written normal path. Define what the assistant can do without asking, including booking windows, follow-up cadence, templates, and status rules.
- A written exception path. List the conditions that stop the assistant and route the decision to dispatch, accounting, sales, or the owner.
- Task-level permissions. Grant only the access needed for the current lane. Add permissions after the workflow is stable.
- A visible QA rhythm. Review a sample, exception queue, or reconciliation report on a fixed cadence.
ServiceTitan describes role-based access control as a way to restrict access by role and privilege. The company still needs its own decision rules and oversight. See ServiceTitan's security controls overview.
Interactive ServiceTitan delegation and permission map
Use the map below to choose tasks for a first handoff. “Low” and “moderate” describe this worksheet, not a guarantee about your account. Your package, configuration, customer data, and policies may require tighter controls.
Original worksheet
Choose a controlled first lane
| Task | Risk | Authority | Stop or approval rule | QA check |
|---|---|---|---|---|
| low | Assistant flags only | Office manager reviews before any merge or deletion | Weekly duplicate queue | |
| low | Assistant owns | Escalate conflicting or identity-sensitive changes | Daily spot check | |
| low | Assistant owns | No interpretation of technical documents | Record and filename check | |
| low | Assistant owns | New tags require manager approval | Weekly tag audit | |
| moderate | Assistant owns within a decision tree | Ambiguous, safety, or technical calls escalate | Sample call audit | |
| moderate | Assistant owns | Outside service, capacity, or job-type rules escalates | Booked-job review | |
| low | Assistant owns | Use approved templates and channels | Delivery exception queue | |
| moderate | Assistant owns | Capacity conflicts or priority changes escalate | Schedule-change log | |
| low | Assistant owns | Dispatcher decides unusual assignments | Start-of-day review | |
| moderate | Assistant recommends | Dispatcher or owner approves field-impacting exceptions | Midday board review | |
| low | Assistant owns | Use factual notes without technical conclusions | End-of-day missing-note check | |
| low | Assistant owns | Filters and cadence are manager-approved | Saved-view check | |
| moderate | Assistant owns the follow-up | Pricing, scope, and discount questions escalate | Call and outcome sampling | |
| low | Assistant owns | Do not mark sold, dismissed, or lost outside policy | Open-opportunity audit | |
| moderate | Assistant flags missing information | Accounting owns corrections and posting | Reviewer signoff | |
| moderate | Assistant owns after approval | No edits to totals, taxes, or payment terms | Sent-status check | |
| low | Assistant owns | Payment disputes escalate | Bounce and dropped-email queue | |
| moderate | Assistant owns after approval | Accounting defines recipients and exclusions | Sent-list reconciliation | |
| moderate | Assistant owns within membership rules | Suspended, incomplete, or unusual records escalate | Recurring-event review | |
| moderate | Assistant prepares data | Accounting reconciles and approves payment | Month-end reconciliation |
Select three to five tasks from one connected workflow, then write the permissions and exception owner for each.
- No tasks selected yet.
What the 20 tasks look like in practice
Customer records and call handling
ServiceTitan's Customer and Location Records can hold contact information, service addresses, notes, tags, and related actions for office employees. Record maintenance is a reasonable lane when the assistant updates approved fields and flags possible duplicates instead of merging or deleting them. See the Customer and Location Records overview.
For calls, use a company decision tree. Routine dispositions can move. Technical diagnosis, safety questions, unusual policy requests, and anything that changes the company's promise should escalate.
Booking, rescheduling, and dispatch preparation
ServiceTitan's Call Booking screen supports lead capture and job booking. Its Dispatch Board supports assignment, dispatch, rescheduling, and communication. Routine work becomes delegable after the company defines service scope, job types, arrival windows, technician or crew rules, and who decides capacity conflicts. Review the Call Booking overview and Dispatch Board workflow.
The assistant can keep the board current, contact customers, log changes, and prepare exception lists. The dispatcher or owner retains decisions that displace committed work, require field judgment, or fall outside assignment rules.
Estimate follow-up
ServiceTitan's Opportunity and Estimate Follow Up report includes status, estimate age, follow-up dates, and follow-up counts that office employees can filter and sort. The assistant can run the saved view, contact customers on the approved cadence, log outcomes, and schedule the next attempt. Pricing, scope changes, discounts, financing guidance, and unusual objections return to sales or the owner. See the report guide.
Invoices, statements, and accounting preparation
Invoice delivery can be delegated after accounting approves the record. The assistant should not change totals, taxes, payment terms, or accounting treatment unless the assigned accounting role and company policy authorize it. See ServiceTitan's guides to emailing invoices and sending statements.
ServiceTitan has also published an accounts-payable playbook where a virtual assistant handles data entry while accounting reconciles and approves. That is the boundary in task 20: preparation can move, payment authority does not. See ServiceTitan's accounts payable guide.
Membership and recurring-service follow-up
The Recurring Service Events screen lets authorized office staff filter events, contact customers, log follow-ups, and book eligible events. An assistant can own that queue when membership status, booking fields, templates, and escalation rules are clear. Suspended memberships, incomplete setup, special requests, and revenue-recognition decisions return to the designated manager. See the recurring service event workflow.
ServiceTitan work that should stay owner-only or manager-approved
- User creation, role assignment, permission changes, and account administration.
- Pricebook changes, pricing exceptions, discounts outside policy, and sold-estimate changes.
- Collecting, editing, deleting, refunding, or applying payments unless accounting has approved that exact lane.
- Payroll settings, payroll adjustments, performance decisions, and compensation changes.
- Record deletion, merges, bulk dismissals, or other hard-to-reverse actions.
- Technical diagnosis, safety guidance, emergency classification, code questions, or licensed-trade judgment.
- Final dispatch decisions when capacity, skill, customer promise, or field safety is unclear.
A practical first 30 days
Week 1: map the full operating scope, identify decision owners, select one connected priority lane, and create the assistant's individual account with only the needed permissions.
Week 2: document the normal path, exceptions, templates, and QA check. Let the assistant observe examples before acting.
Week 3: move the approved work while the manager reviews the exception queue and a sample of completed records.
Week 4: tighten the SOP, remove unnecessary access, and decide whether the stable lane can expand.
This is how Early Bird approaches a software handoff. The full operating scope is mapped first, then one priority workflow is stabilized at a time around a dedicated, full-time executive assistant with ongoing Early Bird support. The service agreement includes confidentiality obligations, and assistants sign nondisclosure agreements. Access and approval rules still need to fit the client's systems.
Choose the model that matches the bottleneck
A human ServiceTitan assistant fits recurring office work that requires context, communication, follow-through, and coordination. Native automation or ServiceTitan's Virtual Agent may fit a narrow, configured interaction. A local dispatcher or accounting specialist may be better when the role requires continuous field judgment or specialized financial authority.
The question is not “Can a virtual assistant click this?” It is “Can this workflow be described, permissioned, reviewed, and escalated without putting an unqualified person in charge of the decision?”