Queries
A Query in ServCraft is a support request or issue raised by or about a customer — similar to a helpdesk ticket. This section explains what Queries are, how they differ from Jobs, and how to use them effectively.
In This Section
| Article | What it covers |
|---|---|
| Webforms & Inbound Email | The two automated ways queries are created — embeddable webforms and email forwarding |
What Is a Query?
A Query is a record of a question, complaint, or service request. It's the starting point for tracking customer issues before — or instead of — creating a formal Job.
Think of it as the inbox for things that need follow-up. A query might turn into a job, or it might be resolved through a phone call or email without a technician ever going on-site.
Query vs Job
| Query | Job | |
|---|---|---|
| Purpose | Track a question, complaint, or request | Record field or workshop service work |
| Has technicians? | No — assigned to an internal employee | Yes — dispatched to field/workshop tech |
| Has scheduling? | No (has a follow-up date) | Yes — appointments on the scheduler |
| Billing? | Not directly billed | Can be invoiced |
| Becomes a job? | Yes — can be linked or converted | — |
| Created from? | Staff, webforms, inbound email | Staff, quote, customer request |
A common workflow: customer raises a query → staff assess → a Job is created and linked to the query → Job is completed → query is marked resolved.
Query Fields
| Field | What it is |
|---|---|
| Query Code | Auto-generated reference number (e.g., Q12345) |
| Customer | Which customer raised this query |
| Contact | Which contact at that customer |
| Location | Which customer location it relates to |
| Query Type | Category of the query (configurable — see Settings) |
| Status | Current state (configurable — see Settings) |
| Priority | Low, Medium, or High |
| Description | Full details of the issue or request |
| Reference | Optional external reference number |
| Follow-up Date | When a response or resolution is due |
| Assigned To | Internal employee responsible |
| Store | Which branch of the business handles it (if multi-store) |
| Source | How it arrived: Internal, Email, Webform, or the ServCraft API |
| Custom Fields | Business-specific fields configured in Settings |
Query Statuses
Query statuses are fully configurable by the business in Settings → Queries (Statuses tab). There are no fixed system statuses — each business sets up statuses that match their workflow. Separately from status, a query can be flagged as Draft (how webform and inbound-email queries arrive) and can be Closed or Archived.
Common status sets include:
- Open → In Progress → Waiting for Customer → Resolved
- New → Assigned → Pending → Closed
- Received → Acknowledged → Under Investigation → Resolved → Closed
Query Priority
Three built-in priority levels:
| Priority | Use when |
|---|---|
| Low | Non-urgent question or minor issue |
| Medium | Standard request requiring follow-up within normal SLA |
| High | Urgent issue — customer is blocked or experiencing significant disruption |
Query Types and Reasons
Both are configurable in Settings → Queries:
- Types — categories like "Technical Issue", "Billing Question", "Feature Request"
- Reasons — sub-classification within a type, useful for reporting (e.g., "Configuration Error", "User Training Needed")
How Queries Are Created
By Staff
Via Queries → New Query in the web app. The most common method.
A query can also be started from a customer, job, quote or invoice, for example with Options → Create Query on the customer page. The new query opens with that item's customer already filled in and locked. Only the contact and location can be changed. To use a different customer, start the query from Queries → New Query instead. Cancel on the new query returns to the page it was started from, or to the query list when there is no earlier page.
From a Webform
ServCraft supports embeddable webforms on the service business's website. When a customer fills in the form, a Query is automatically created in ServCraft.
From Inbound Email
Some configurations capture inbound emails as Queries — the email becomes the query description and is assigned to the configured inbox.
Linking Queries to Jobs
A query can link to one or more jobs:
From the Query: Query detail → Link Job — either link an existing job or create a new one.
Once linked:
- The query shows a "Jobs" tab listing all linked jobs
- The job shows the linked query in its detail
- Closing the job does not automatically close the query — staff close them separately
This allows complex issues (multiple site visits, multiple technicians) to be tracked under a single query.
The Query Detail Page
When you open a query, you see:
| Tab | What it shows |
|---|---|
| Query Details | All editable fields — the main form |
| Appointments | Scheduled appointments linked to this query |
| Jobs | Jobs linked to this query |
| Quotes | Quotes created from or linked to this query |
| Invoices | Invoices related to this query |
| Purchases | Purchase orders linked to this query |
| Summary | Status change history — a log of when status changed and who changed it |
| Attachments | Files attached to this query |
| Messages | Messages and notes — internal or customer-facing |
Tabs like Jobs, Quotes, Invoices, and Purchases only appear once linked items exist (and you have permission for that module).
Actions on a Query
| Action | What it does |
|---|---|
| Create Job | Creates a new Job and links it to this query |
| Link Job | Links an existing job |
| Create Quote | Creates a quote linked to this query |
| Create Invoice | Creates an invoice linked to this query |
| Create Purchase Order | Creates a purchase order linked to this query |
| New Query | Starts another query for the same customer |
| Open / Change Customer | Jumps to the linked customer, or re-links the query to a different customer (see below) |
| Archive | Archives the query — removes from active list but preserves all history |
| Close | Marks the query as resolved |
| Re-open | Re-opens a closed query |
Changing a Query's Customer
Change Customer on the query's options menu (shown to users with the Customer permission, next to Open Customer) opens a box headed "Change Customer for [query code]". It explains: "Changing the customer reassigns any related quotes and invoices still in draft. You cannot change the customer when there are related quotes or invoices that are approved or have linked payments."
Pick the new customer and a contact (both are required) and, if you want, a location, then click Change Customer. A message confirms "Customer change was successful". If the query has quotes or invoices that are already accepted, invoiced, approved or paid, the box is headed "Cannot Change Customer for [query code]" and gives the reason instead of letting you pick a customer.
Follow-up Date and Tracking
The Follow-up Date field is the key SLA tracking mechanism. It records when a response or resolution is due.
Queries approaching or past their follow-up date should be prioritised. Sort the query list by follow-up date to work through overdue items first.
There is no automated escalation notification built in — it's up to staff to monitor the query list and follow-up dates.
Query Settings
Settings → Queries (requires Super Admin access) has four tabs:
| Tab | What it configures |
|---|---|
| Settings | Field settings for the Query form — which fields (including custom fields) are shown, hidden, or required |
| Types | Create and manage query type categories |
| Statuses | Create and manage the workflow states |
| Reasons | Create and manage reason codes |
A separate "Query Show Inventory" option controls whether inventory/parts selection appears on queries.
Query Permissions
The Query permission controls access to the Queries module. A user without this permission cannot open the Queries section at all. Access to the query-related tabs on other pages (like the customer page) is gated by the same permission.
Managing query settings (types, statuses, reasons, field settings) additionally requires Super Admin access.
Triggers and Templates for Queries
Queries support the same trigger and template system as Jobs:
Settings → Templates → Triggers — choose the Query module. Three trigger rules are available for queries:
- Query Status Change sends a notification when a query moves to a chosen status, optionally for one priority only
- Query Employee Allocated sends a notification when a query is saved by an employee other than the one assigned to it, for example when a manager assigns it to a technician. It fires on every such save, whether or not the assignment changed. Choose Assigned Employees as the recipient to reach the technician who owns the query
- Email to Query Create sends a notification when an inbound email creates a new query (see Webforms & Inbound Email for the setup steps)
There is no trigger rule for query follow-up dates.
Settings → Templates — create email/SMS templates for query-related communications.
Common Scenarios
"A customer emailed us about an issue — how do we track it?"
Create a Query. Paste the email content into the Description. Set the customer, contact, priority, and follow-up date. Assign to the relevant employee.
"A query has turned into a site visit — how do we handle it?"
From the query, use Create Job. A new job is created and automatically linked. The query stays open until the issue is resolved; the job tracks the site work.
"How do I find all open queries assigned to me?"
Query list → filter by Employee (pick yourself) and leave the Closed Queries toggle off. Sort by follow-up date.
"Can ServCraft remind technicians about open queries?"
No. All three query trigger rules react to something happening to a query, and none of them fires because time has passed. The time-based reminder rules exist only for jobs, quotes and invoices. Nothing reminds anyone about an open query or a passed follow-up date.
"Can a customer see their query in the Customer Zone?"
The Customer Zone currently shows Jobs, Quotes, Invoices, and Appointments. Queries are not visible to end customers in the Customer Zone — they are internal records only.