Task, Ticket or Opportunity? Choosing the Right Record Type

A guide to CRM record types: the difference between tasks, tickets, opportunities and appointments, the decision rule and reporting impact.

“The customer asked for a price list.” Is that a task, a support ticket or a sales opportunity? If three teams give three answers, three months later no report adds up — because the same work is being counted in three places.

Four types, four different questions

Task

Question: “who will do what?” A defined, finite piece of work for one person. Short-lived, closed when complete.

Support ticket

Question: “has the customer’s problem been solved?” It comes from a customer, has a number, stays open until resolved and is subject to an SLA.

Opportunity

Question: “will this sale happen?” It carries a revenue expectation, has stages and closes as won or lost.

Appointment

Question: “when are we meeting?” It occupies calendar space with a time range and participants.

The decision rule

Three questions end the confusion — ask them in order:

  1. Does it occupy calendar space? If yes, it is an appointment. Something happening at a set time with set people is not a task.
  2. Did it come from a customer and does it need resolving? If yes, it is a ticket. If a customer is waiting on the outcome and a time commitment applies, it should not be opened as a task.
  3. Is there a revenue expectation? If yes, it is an opportunity. If you need stage tracking and a value, a task will not do.
  4. If none of those, it is a task. Tasks are where everything outside the other three belongs — that is the catch-all category.

Nested cases

In real life these are not independent; they nest, and that is normal:

  • A ticket can contain several tasks: “check the logs”, “apply the patch”, “inform the customer”.
  • An opportunity can contain follow-up tasks and an appointment (a demo).
  • An appointment produces a task afterwards: “send the quote”.
  • A ticket can turn into an opportunity: once their problem is solved, the customer asks about an extra module.

What matters is getting the hierarchy right: whichever is the parent, the others attach to it. A task under a ticket kept somewhere separate leaves both looking incomplete.

The cost of choosing wrongly

  1. Reporting breaks. Customer problems not opened as tickets understate ticket volume, and the capacity plan comes out wrong.
  2. SLAs do not run. A customer problem opened as a task has no clock; the delay is invisible.
  3. The pipeline is incomplete. Potential business not opened as an opportunity never appears in the forecast.
  4. Customer history fragments. When the same topic is recorded under different types, the whole story is not visible on the customer record.

How to standardise it

  • Write the rule and keep it to one page. A three-question decision flow gets used more than a long document.
  • Set the defaults correctly. Everything arriving through customer channels (email, WhatsApp, web forms) should open a ticket automatically, so nobody has to decide.
  • Make conversion easy. When the wrong type was chosen, one click should convert it and preserve the history. Deleting and reopening loses the history.
  • Teach it to new staff in week one. The habit sets in the first days.

Frequently asked questions

Which type should internal requests (IT, HR) use?

If a time commitment and resolution tracking apply, ticket logic fits; if it is simply “please do this”, a task is enough. What matters is being able to separate internal and external requests in reporting.

When should an opportunity be opened?

When there is a concrete revenue expectation and a counterpart. Opening one for every interested person inflates the pipeline and ruins the forecast; opening after qualification is healthier.

Can’t we work with a single record type?

It works briefly in a small team, but the first report exposes it: different work needs different measures. Tickets are measured on resolution time and opportunities on win rate; the two cannot be compared in one list.

Next step: to see how record types link to each other, request a demo.