← All guides

Queries: questions that aren't repairs yet

Recording a customer question that is not yet a repair, answering it, and converting it to a repair if needed.


A query is a customer question or problem that has not yet become a repair, and may never need one. It gives you a record of the conversation without booking in a product.

Switching queries on

On the Queries tab in Settings, Enable Queries adds a Query stage to the front of your pipeline. You can give queries your own Display Name, such as Enquiry, and RepairStep uses that word throughout. You also keep a list of Close Reasons, so resolved queries can be counted by outcome.

Logging a query

Choose the query from the Add menu on the Repairs page. The form asks for the customer, the product, the question, and the channel it came through. The channel decides how the conversation is captured: a phone call gives you a field for the call notes, an in-person visit gives you notes from the meeting, and an email or text gives you a reminder to log the message afterwards. These notes are internal and are never shown to the customer.

Working a query

A query has its own page, like a repair, with a short Query Progress rail, the Conversation, and the Add menu for emails, calls and notes. It ends in one of two ways:

  • Resolve Query: choose a close reason and add a note if needed. A resolved query can be reopened later.
  • Convert to Repair: the dialog asks Where does this repair go?, lets you fill in anything the query did not capture, and the query becomes a repair with its conversation intact.

Where queries appear

Open queries have their own Queue view on the Repairs page and a count on the dashboard. Insights has a tab for them, showing volume, outcomes and close reasons over time. Queries use the default branding theme and do not ask about warranty; that is assessed once there is a repair.