On Page Navigation

Managed Frappe Helpdesk for Support Teams Ticket Queues Real SLAs

Frappe Helpdesk is a capable support desk that will sit there doing very little if the email intake is wrong and the SLA policies never match a ticket. We set the intake up properly and migrate what you already have, then answer the requests that follow. One monthly figure.

A Cascadia engineer reviewing a Frappe Helpdesk configuration
A Cascadia engineer reviewing a Frappe Helpdesk configuration

Where a support desk usually goes wrong

Installing Helpdesk is the easy part

A support desk fails in specific, boring ways. Mail that arrives and never becomes a ticket. An SLA policy that quietly skips the one priority you actually care about, because its condition matched and its priority table did not. We own that class of detail for the life of the subscription. Where you need more than one Frappe app, we cover the rest of the app range on the same terms.

Concretely, the inbound mail path is tested rather than assumed, including what happens to replies and to autoresponders. SLA policies are written against your real priorities and then checked by firing them. Ticket types, teams and assignment rules match how your people are actually organised rather than how an org chart says they are. The customer portal says what you want it to say. And when volume or team shape changes, the configuration changes with it instead of staying as it was on day one.

Subscription versus a one-off rollout

A managed desk vs a project that ends

The usual way to get Frappe Helpdesk is a fixed-scope project. Somebody configures it against what you described in a kickoff call, trains whoever is in the room that week, invoices, and leaves. That holds up until your first real Monday. Where you want several Frappe apps handled this way rather than one, our all-apps subscription covers the set.

Your SLAs get revisited

A project sets the response targets you guessed at before you had any data. Six months in, that guess is wrong in at least one place. We change it inside the subscription rather than pricing a variation.

Somebody watches the intake

Email intake breaks quietly. A mailbox password rotates or a folder mapping resets after a migration, and tickets stop appearing while mail carries on arriving. That is something to monitor rather than something to configure once.

No change order for a ticket type

Under project billing, a new ticket type or one extra field waits for a quote and then waits for approval. Small changes stop being worth asking for, and the desk gradually stops matching the work.

Agents keep getting trained

Implementation training happens once, for the agents you happened to have that week. Support turnover being what it is, the person answering your customers in month eight was never in the room.

Releases have an owner

Frappe Helpdesk carries on shipping after your project closes. With nobody tracking releases against your customizations, an upgrade is either postponed indefinitely or applied on a Friday and discovered on a Monday.

Nobody relearns your setup

Bring a contractor in for the next change and the first days go on reading your configuration. We already know why your Urgent policy has the schedule it has, because we argued about it with you.

Who this service fits

Who this is for, and who it is not

This suits a support team that has settled on Frappe and wants the desk run properly rather than stood up and abandoned. It is the wrong buy for a two person operation answering a handful of emails a week. At that size the honest recommendation is Managed Zoho Desk, which costs less and asks less of you, and we would rather sell you that than oversell this.

How the work runs

From first call to a desk your agents trust

Nothing goes live on day one. We agree what a ticket is and who owns it, build against that on a test site, then move your real mailbox across once it behaves the way you were told it would.

1

We define priorities and targets

The first sessions are about your commitments rather than the software. What counts as Urgent. What you have promised in writing. Which hours you genuinely cover, as opposed to the hours on the website. These are decisions your side has to make, and they are the ones your customers will hold you to.

2

We configure and test against real tickets

Everything gets built on a test site first: ticket types, the policy set with its holiday list, routing, the portal, the first knowledge base articles. Then we raise tickets on purpose at awkward times, because a clock you have not watched cross a weekend is a clock you are guessing about.

3

We migrate, launch and keep going

Your mailbox moves across, agents are trained by role, and the request queue opens. The first weeks get watched closely. The difference between the desk you designed and the desk you actually have shows up in about ten days.

Transparent pricing for a managed support desk

Pricing

Managed Frappe Helpdesk - Standard

Standalone Service

$800.00
/per month, per instance
One active request at a time

DETAILS

A monthly subscription covering implementation, configuration, migration, agent training and the request queue afterwards. One active request at a time.

Managed Frappe Helpdesk - Priority

Standalone Service

$1,600.00
/per month, per instance
Two active requests at a time

DETAILS

Everything in Standard at double the capacity. Two requests run in parallel, turnaround is faster, and a configuration review happens every quarter.

Testimonials

Here's what others had to say

What the subscription actually covers

Everything included in Managed Frappe Helpdesk

This is the icon that represents an included managed service.Cascadia Web Services logo

Tickets and the Intake Path

Every ticket arrives from somewhere, and the somewhere decides how much context an agent starts with. Email, the customer portal, a call an agent logs by hand. We set the intake routes you actually want, agree what a ticket must carry before it can be worked, and switch off the paths nobody monitors. An unwatched intake channel is worse than no channel, because a customer has already used it and is waiting.
This is the icon that represents an included managed service.Cascadia Web Services logo

Email to Ticket

The mailbox your customers already write to, turned into tickets with the thread attached. This is the part that quietly fails on self-installs. Frappe Helpdesk needs the incoming Email Account carrying an IMAP folder mapping, with Folder Name set to INBOX and Append To set to HD Ticket. Miss that mapping and mail arrives in the account perfectly while no ticket is ever created, and nothing anywhere reports a fault. We set it, then pull a test message through and confirm a customer reply threads back onto the same ticket instead of opening a second one.
This is the icon that represents an included managed service.Cascadia Web Services logo

Ticket Types, Priorities and Statuses

Priority drives your SLA clocks, so it is a configuration decision rather than a label. Low, Medium, High and Urgent each carry their own response and resolution targets. Statuses matter as much. Resolved and Closed fulfil an SLA, while Replied pauses the resolution timer until the customer writes back. We define the set your team will actually use and explain what each one does to the clock before anybody starts clicking them.
This is the icon that represents an included managed service.Cascadia Web Services logo

SLA Policies

Response and resolution targets per priority, with conditions deciding which policy a ticket gets. The mechanism catches people out. A policy applies only when its condition matches the ticket and its priority table lists that ticket's priority, so a policy scoped to a team that never mentions Urgent will skip an urgent ticket in silence and the next policy is tried instead. Rank decides the order, lower first, and a rank of zero means unranked and is applied last. We build the policy set and rank it deliberately, then test it against tickets we raise on purpose.
This is the icon that represents an included managed service.Cascadia Web Services logo

Working Hours and Holiday Lists

SLA clocks only advance inside the hours you define, and they pause on any date in the linked Holiday List. A ticket arriving at five in the evening against a four hour target is not late at nine that night. It is due mid morning tomorrow. Weekends go in as recurring holidays rather than typed one date at a time. We configure this against your real cover and write down what happens to something that lands on Friday afternoon.
This is the icon that represents an included managed service.Cascadia Web Services logo

Assignment Rules

Rules that put a new ticket on a named agent by condition, so nothing sits waiting for a volunteer. Round robin spreads evenly. Load based hands the next one to whoever is carrying least. We also agree what should happen to a ticket that arrives outside cover, because the honest answer is usually a queue somebody checks first thing rather than an agent who is asleep.
This is the icon that represents an included managed service.Cascadia Web Services logo

Agents, Teams and Availability

Teams group agents by the work they handle, which is what makes conditional routing possible in the first place. Availability status tells the rest of the desk who is actually at a keyboard, which matters more than any dashboard when a ticket is twenty minutes from breaching. We map your teams onto how you really cover a day, including the part where one person covers two things on Fridays.
This is the icon that represents an included managed service.Cascadia Web Services logo

Customers and Contacts

A contact is a person. A customer is the organization paying you. Holding them apart is what lets an agent see every ticket that account has ever raised rather than just this one. Domain matching attaches an inbound email to the right customer without anybody choosing from a list. Settling this before migration saves the hours nobody budgets for merging duplicates afterwards.
This is the icon that represents an included managed service.Cascadia Web Services logo

Customer Portal

Where your customers raise a ticket, watch it move, and read what you have already published. It carries your name and your branding rather than looking like somebody's software. We think hard about the fields the portal form asks for, because a form asking too much gets abandoned and a form asking too little produces a ticket your agent has to answer with a question.
This is the icon that represents an included managed service.Cascadia Web Services logo

Knowledge Base

Articles organised into categories, published to the portal, searchable before anybody opens a ticket. The value shows up as tickets that never arrive, which makes it the hardest part of a desk to measure and one of the most worthwhile. We seed it from the answers your team is already retyping every week, found by reading your existing mailbox rather than by guessing.
This is the icon that represents an included managed service.Cascadia Web Services logo

Saved Replies

The paragraph your team writes forty times a month, stored once and kept accurate. Agents insert and adjust rather than composing from nothing, so tone stays consistent and the technically correct detail stays correct.
This is the icon that represents an included managed service.Cascadia Web Services logo

Views and the Agent Home Page

Filtered and sorted views saved per role, so an agent opens the desk and sees their own work rather than everybody's. The agent home page puts whatever is closest to breaching in front of the person who can fix it. Most of what makes a helpdesk feel calm rather than frantic is this, and it takes an afternoon rather than a project.
This is the icon that represents an included managed service.Cascadia Web Services logo

Custom Fields, Dependencies and Actions

The fields your support actually needs, with field dependency so choosing a category narrows the next question instead of showing thirty irrelevant options. Custom actions put a button on the ticket for the thing your agent does next, whether that is raising an issue against a build or pulling a record from another system.
This is the icon that represents an included managed service.Cascadia Web Services logo

Notifications and Email Preferences

Who gets told what, and when. Notification settings decide what reaches an agent. Email preferences control what your customer receives on each ticket event. We tune this down rather than up, because a desk that emails everybody about everything trains everybody to ignore it, and that is the failure mode that costs you a breach.
This is the icon that represents an included managed service.Cascadia Web Services logo

Outside Working Hours Banner

A banner on the portal telling a customer they have arrived outside your cover and when somebody will be back. Small feature, disproportionate effect. Expectations set at the moment a ticket is raised are the cheapest support you will ever provide.
This is the icon that represents an included managed service.Cascadia Web Services logo

Telephony with Twilio or Exotel

Either provider connects for inbound and outbound calling, with the call logged against the ticket automatically and recordings attached where your provider retains them. Numbers and agent mapping are configuration work, and we do it with your provider console open alongside rather than handing you a documentation link.
This is the icon that represents an included managed service.Cascadia Web Services logo

ERPNext Connection

Where you run ERPNext, an agent can see the customer's orders and invoices while answering, so a support conversation stops being blind to whether that account is three weeks late paying. Both applications sit on the same framework, so this is configuration rather than an integration project with a middleware bill attached to it.
This is the icon that represents an included managed service.Cascadia Web Services logo

Internal Notes and Bulk Reply

Comments are internal and invisible to the customer, which is where the actual diagnosis happens and where a handover between two agents survives. Bulk reply sends one response across many tickets at once, which is exactly what you want on the morning an outage has produced sixty of them all saying the same thing.
This is the icon that represents an included managed service.Cascadia Web Services logo

Data Migration

Open tickets, contacts, customers and whatever closed history is worth keeping, brought across from Zendesk, Freshdesk or a shared mailbox. Everything loads into a test site first and we reconcile counts with you before production sees any of it. We will also tell you which of your closed conversations are not worth migrating, because moving dead data costs real money and buys nothing.
This is the icon that represents an included managed service.Cascadia Web Services logo

Ongoing Support and Review

Requests come through the subscription: a new ticket type, a changed SLA schedule, a routing rule, a report, an article nobody has written yet. Production problems go to the front of the queue. Once a quarter we check whether the configuration still matches how you support people, because support processes drift faster than anybody remembers to update the system.

Questions support teams ask before signing

Frequently asked questions
Do we need ERPNext to run Frappe Helpdesk?
No. Frappe Helpdesk runs perfectly well on its own and plenty of teams use it that way, usually because their billing lives somewhere they are happy with. What you give up is context. An agent answering a question about a late delivery cannot see the order that produced it. Where you already run ERPNext, both sit on the same framework and that view becomes configuration rather than an integration.
How long does an implementation take?
Three to six weeks for most rollouts. What sets the pace is not the software, it is your side settling on priority definitions and SLA targets, and since your customers will hold you to those, they are worth arguing about properly. One mailbox, one queue and no migration can be answering tickets inside a fortnight.
We are on Zoho Desk. Should we move?
Quite possibly not. Zoho Desk is a capable product, and if it is doing the job while nobody on your team is fighting it, staying put is the right answer. The reasons to move are real but narrow: you want the data on infrastructure you control, you need the desk in the same database as an ERP you already run, or Zoho's edition ladder is charging you an upgrade for one feature. Where none of that applies, Managed Zoho Desk is the cheaper and better fit and we would rather sell you that.
What does the price include?
Everything up to and including the day you go live, then the request queue afterwards. That covers configuration, migration, agent training and the changes you will want in month three. One flat monthly figure. Hosting is billed separately.
Is hosting included?
No, it is priced separately. Managed Frappe Cloud is our hosting service and the two land on a single invoice when you take both. If somebody else hosts you, we work inside that environment and agree upgrade windows with whoever runs it.
What is the difference between Standard and Priority?
One active request at a time on Standard. Priority runs two in parallel with faster turnaround and adds a quarterly review session. Production problems jump the queue on either tier, so Priority buys throughput rather than urgency. Most clients take it during the build and drop to Standard once the desk has settled.
Email is arriving but no tickets are being created. Can you fix that?
Yes, and this is the most common self-install problem we see. Mail lands in the Email Account correctly and no ticket ever appears, with no error logged anywhere to point at. The cause is almost always the IMAP folder mapping on the incoming account, where Folder Name has to read INBOX and Append To has to be set to HD Ticket. We configure the mapping and pull emails manually to confirm, then send a real message in from outside and watch the ticket appear.
Why does a ticket show no SLA at all?
That is a normal state rather than a fault. A ticket ends up without one when nothing matched it. A policy applies only if its condition matches and its priority table lists the ticket's priority, so a policy scoped to a team that never mentions Urgent will pass over an urgent ticket entirely. A ticket can also lose an SLA later, when its priority changes to one the policy does not cover or when the condition stops matching. Any breach that already happened is kept, so the ticket still reads Failed.
Our resolution timers look frozen. What is happening?
Check the status first. Replied pauses the resolution timer by design, so a queue full of tickets waiting on customers will look stopped, and that is correct behaviour rather than a bug. After that, look at working hours and the holiday list, because the clock only advances inside the hours you configured. A ticket raised on Saturday afternoon does not start counting until Monday morning where weekends sit in the holiday list.
Can you migrate from Zendesk or Freshdesk?
Yes. Their exports behave differently enough from each other to be worth naming, and a shared mailbox is its own kind of project again. The work is deciding what comes across rather than the import itself. Open tickets and active contacts always. Four year old closed conversations rarely, whatever the export happens to contain. We load into a test site, reconcile counts with you, and only then touch production.
Can customers raise tickets without an account?
Yes, and it is worth deciding deliberately rather than accepting a default. Email intake needs no account at all, which is the lowest friction path available and also the one that hands you the least structured information. The portal can require a login or accept a ticket from a contact it has never seen. We usually run both and let the customer pick.
Does it handle phone calls?
Twilio and Exotel both connect, giving click to call from the ticket and an automatic call log written against it. Recordings attach where your provider keeps them. The provider account stays in your name, so call charges never route through us and you can change provider without asking our permission.
Do you write our knowledge base for us?
We seed it and you own it. The first batch comes out of your existing mailbox, because the answers your team already retypes every week are exactly the articles worth publishing first. After that, adding an article is a request like any other and it goes in the queue.
Is there a minimum term?
None, and no setup fee either. It bills monthly and ends on thirty days notice. Where a migration is unusually large we price that piece on its own, and you hear about it before you subscribe rather than after.
Who owns the system if we stop working with you?
You do. Frappe Helpdesk is open source, the site is yours, and every SLA policy and published article we build lives inside it. So does the documentation. Nothing of ours sits in the middle waiting to stop working when the invoices do.
​Contact

Ask Us Anything

We’d love to hear from you!