Client management for home and field services
For trades and service companies such as plumbing, cleaning and cabinetry. Keep each customer, the steps of every job, the estimate and the paperwork in one place, and give your customer a portal to follow along and sign.
What a job looks like in Aqvori
From request to close-out
Draw your steps once: request, site visit, estimate, work order, close-out, or whatever yours are. Each job keeps its phase, its next steps and its full history, attached to the customer it belongs to.
Who has each job
Decide which team works each step and who approves. Next steps carry owners and due dates, and they land on each person's own list.
Estimates as documents
Keep your estimate with the job as a Word or PDF file, with every version kept, and send it for electronic signature.
Photos and paperwork
Customers upload files through the portal from a phone, iPhone photos included, and they stay with the job.
How your work maps to Aqvori
Customer records
Design the customer profile yourself in the Dossier Builder, with the fields you actually collect, such as the service address or access notes.
Workflow
Start from the Service Request template in Studio and add steps such as Site visit and Estimate, with no code. A validator checks it before you publish.
Client portal
Progress, documents, messages and tasks, each one a switch you control, in your branding.
How scheduling works today
- A Calendly booking can open a new job on its own, so a request made on your booking page lands in your workflow
- Each person connects their own mail and calendar, and an event on the Aqvori calendar can be linked to the customer
- The Service Request template has a Schedule step for agreeing the date and booking the people. A person works that step; Aqvori does not book crews for you
What Aqvori does not do today
- Aqvori does not invoice customers or collect payments. Those stay in your accounting tool.
- There is no dispatch board, route planning or technician GPS tracking.
- There is no line-item estimate builder, price book or parts inventory. An estimate is a document.
- There is no native phone app and no offline mode. Aqvori and the client portal run in a phone's web browser and need a connection.
- A request form on your own website does not open a job automatically. A Calendly booking does.
- The mail, calendar and storage path we publish today is Google. If you run on Microsoft 365, ask us on the demo call.
Is Aqvori field service software?
Not in the usual sense. It keeps the customer, the steps of the job, the documents and the portal together. If your day runs on dispatching crews and taking payment on site, a dedicated field service product will fit better.
Can a customer approve an estimate in the portal?
A customer can sign a document and message your team in the portal. The signature does not move the job by itself: someone on your team moves it on, and approval steps inside a workflow are decided by people on your team.
Can we call the work jobs?
Your steps, your fields and the names of your phases are all yours. The word the screens use for a piece of work comes from a set of word lists, and none of them says Job today. If that word matters to you, tell us on the demo call.
How does a job start?
By hand from the customer record, from a Calendly booking, or when a client, project or document is added. You pick the start when you draw the workflow.
Do our customers need to install anything?
No. The portal runs in a web browser, and they sign in to their own secure door.
Can we text our customers?
Yes, from your organization's own number, and only to people who opted in. Read our SMS and Messaging Policy.
Where do our files live?
In your organization's own Google Shared Drive, connected in your settings by an owner on your side.
Does the AI send anything to our customers?
No. Vori, the AI copilot, drafts and summarizes. Nothing reaches a customer until a person on your team sends it, and Vori runs on your organization's own AI account with the provider you choose.
See it on your own jobs.
Tell us how a job runs from the first call to close-out and we will sketch it as a workflow on the call.