Consistent call outcomes

Call disposition codes for a home-service office

A call disposition is a label for the result of an interaction. NiCE's documentation distinguishes call dispositions from the separate tags and notes that can accompany them. A disposition tells your office what happened; the supporting record explains the details.

Compare plans Read the guide

01 / Consistent call outcomes

Before you choose the next step

For a home-service business, “answered” rarely supplies enough information. A person might answer an estimate request, confirm an existing appointment, take a message for a scheduler or explain that the requested work is outside the service area. Those calls need different next steps.

02 / Consistent call outcomes

Separate connection, reason and outcome

Use three fields rather than asking one label to carry the whole story:

A fourth field records any next action, its owner and the agreed follow-up window. Applying a label does not perform that action. “Follow-up required” is useful only when someone can find and accept the work.

03 / Consistent call outcomes

Start with an evidence-based codebook

The following is an illustrative office codebook, not a built-in Revo feature or an industry standard. Choose one primary business outcome for the principal request. If a call contains separate requests, keep secondary request records rather than forcing several incompatible outcomes into one field.

What to check

Appointment confirmed: Use only when an authorized scheduling step succeeded and the appointment details were confirmed. Save the booking reference and the agreed details. A preferred date alone does not qualify.
Office question answered: Use when the requested information was supplied from an approved source and no action remains for that question. Record the topic and source. This label does not mean a repair was completed.
Follow-up required: Use when the principal request still needs a callback, a decision or another person's action. Record the owner, reason and approved window. An attempted transfer without an accepted handoff belongs here when work remains.
Outside service scope: Use when a documented service, location or other business rule prevents accepting the requested work. Record the applicable rule. If the facts are incomplete, choose review instead of guessing.
Request withdrawn: Use when the customer explicitly says they no longer want to proceed. Record that statement's context. Silence or a missed callback is not evidence of withdrawal.
Non-service contact: Use for a verified wrong number, supplier inquiry or another call outside the customer-service workflow. Record an appropriate subtype. A hidden caller ID alone is not evidence of spam.
Needs review: Use when the result cannot be supported confidently. Record the missing fact and the person who will resolve it. Keep this visible instead of assigning an optimistic result to make a report look complete.

04 / Consistent call outcomes

Work through two ordinary examples

An HVAC caller asks for a Tuesday visit. The office collects the address and preferred time, but a scheduler still needs to check availability. Record the reason as a new appointment request and the outcome as follow-up required. Name the scheduler or queue responsible for the decision. Do not classify the call as a confirmed appointment.

A plumbing customer asks which date is already booked. The office checks the authorized appointment record, gives the date and confirms that this answers the question. Office question answered may be appropriate. The underlying job remains scheduled, not completed. These examples are fictional and illustrate classification only.

05 / Consistent call outcomes

Keep the codebook stable and review exceptions

Write a short definition, required evidence and next action for each code. Give the codebook a version date. When the meaning changes, document the transition so old and new reports remain interpretable. HubSpot, for example, restricts editing saved outcomes because changing them can affect reporting data; that is a product-specific reminder to plan taxonomy changes carefully.

Review a sample together before rollout. If two team members assign different outcomes to the same example, improve the definition. Examine needs-review records and follow-up records with no owner. Retain an explicit missing value when information is absent; missing is different from unsuccessful.

For reporting, distinguish call counts from unique customer requests. Three calls about one estimate are three interactions, not three new leads. Link related records to the same request where your office's approved tools allow it.

06 / Consistent call outcomes

Questions to settle before adopting a tool

Can your existing system store the code, evidence and next action separately? Can your team export the definitions alongside the results? Who corrects an inaccurate outcome, and can they preserve why it changed? Check those details in the specific product and plan being considered. This guide does not establish that Revo assigns dispositions, creates tasks or updates a CRM automatically.

Common questions

Make the next step clear.

Resolve the details that matter to your team and callers.

Is a call disposition the same as a call summary?

No. A disposition is a standardized result label. A summary contains the context needed to understand the conversation. Keep the code short and retain supporting details in the associated record.

Should a successful transfer count as a resolved request?

Only if the actual request was resolved under your definition. Reaching another person and completing the customer's task are different events. Record the handoff separately when further work remains.

How many codes should a small office use?

Use enough to distinguish different decisions and next actions. Add a code when it changes how the office works or reports, rather than creating a separate label for every possible sentence a caller might say.

Sources and current terms

A useful disposition has a clear definition, supporting evidence and an owner for anything unfinished.

Review Revo’s current features and plans for the workflow your business needs.

Compare plans