What we do
Tools
Industries
Department
How we workLet's talk →
Home/HappyFox/HappyFox Ticketing
HappyFox Help Desk

HappyFox Ticketing, Set Up in the Order Its Pieces Depend on Each Other

A ticket lands in HappyFox with no owner, the wrong priority and a due date nobody set. That isn't one setting to fix. Categories decide which team and which SLA a ticket belongs to, Smart Rules act on it without anyone clicking, and Canned Actions cover the reply plus the field changes an agent would otherwise make by hand. Build them out of order and the rules fire on tickets that were never sorted.

HappyFox ticketing, one layer at a time

Each layer reads the one before it, so it pays to build them in this order.

  1. 1

    Categories first

    Split incoming requests the way your teams already divide the work: billing, returns, technical, onboarding. Each category can carry its own SLA, canned actions and ticket templates, and agents get assigned to the categories they cover.

    Watch for: a catch-all "General" category. Tickets parked there skip every rule you wrote for the specific ones.

  2. 2

    SLA policies on top

    Set response and resolution targets per category, customer tier or channel. Smart Rules lean on these targets when they set due dates, send reminders and escalate a ticket that's running late.

    Watch for: targets counted around the clock when your team works weekdays. Smart Rules can schedule around working hours, so set those hours before the timers start.

  3. 3

    Smart Rules for what nobody should have to decide

    Match on category, priority, channel or customer type, then act: assign to an agent or team, change status, category or due date, email or text the customer, an agent or a third party, close or archive, escalate. A rule can also fire a webhook to an outside system.

    Watch for: two rules that each change a field the other one reads. Try a new rule on a handful of tickets before it runs on the whole queue.

  4. 4

    Canned Actions for what an agent decides

    One click adds a templated reply and changes status, priority or tags at the same time. Keep shared ones for answers the whole team gives, and let agents keep personal ones for their own habits.

Is this ticket a job for a Smart Rule or a Canned Action?

Smart Rule

The fields already say what to do

  • Fires the moment a ticket matches, whoever is on shift.
  • Right for routing, due dates, reminders and escalation.
  • Runs on every matching ticket, so a bad condition hits all of them.
Canned Action

Someone had to read it first

  • Reply and field changes in one click, after an agent looks.
  • Right when judgment is involved: a refund approved, a bug confirmed.
  • Shared across the team or kept personal.

If the right move depends on what the customer wrote, make it a Canned Action. If category, priority and customer type are enough to decide, make it a Smart Rule.

HappyFox queue trouble that starts in setup

Tickets breach their SLA while nobody owns them

How you'll know: The timer runs, but no Smart Rule assigns that category, so the ticket waits until someone happens to open it.

Fix: Give every category an assignment rule, even if it only goes to a team rather than a person.

Everything from the web form is urgent

How you'll know: The form lets customers pick their own priority, and they all pick the top one.

Fix: Let a Smart Rule set priority from category and customer type, and keep the customer's choice in a custom field as a hint.

Rules can't tell a paying customer from a lapsed one

How you'll know: Customer type was filled in once at import and hasn't changed since, so a cancelled account still gets the priority queue.

Fix: Feed that field from billing or the CRM so it changes when the account does. That's a connection outside HappyFox, and it's where n-frames comes in.

When a rule needs a fact HappyFox doesn't hold

Smart Rule conditions read the ticket and the customer details stored with it. Whether the invoice in that email is overdue, whether the order has left the warehouse, whether the account renews next week: none of that lives in HappyFox, so no condition can test it.

Going outward, a rule can fire a webhook. That covers the sending. Something still has to receive the call, look up the order or the invoice, do the work in that system, and write back what it did so the agent isn't guessing.

n-frames builds both halves: the job that keeps invoice status, plan or order state in the ticket and contact fields your rules already read, where HappyFox's API allows, and the receiver behind each webhook. The rules themselves stay in HappyFox, where your team can still edit them.

HappyFox tickets, rules and SLAs

What are HappyFox Smart Rules?

HappyFox's no-code automation for tickets. You set conditions such as category, priority, channel or customer type, and when a ticket matches, the rule acts: assigns it, changes its due date or status, sends a reminder, escalates it or calls a webhook.

Does HappyFox support SLA policies?

Yes. Categories can carry their own SLA requirements, and Smart Rules use those targets to set due dates, send reminders and escalate tickets that are overdue or about to be.

Can HappyFox route tickets automatically?

Yes. Tickets from email, chat, phone and other channels land in one queue, and Smart Rules assign them by category, priority or channel, so nobody sorts the inbox by hand first.

What are Canned Actions in HappyFox?

Saved one-click actions for agents. Each adds a templated reply and can change status, priority or tags in the same click. They can be shared with the team or kept personal.

Can a HappyFox Smart Rule check data outside HappyFox?

Not as a condition. Rules only test what's on the ticket and the customer record. To make a rule react to an overdue invoice or a shipped order, that fact has to be written onto the ticket first, and n-frames builds the connection that keeps it there.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.