Apps › Extra Tools

Helpdesk & Ticket Management for Community

A support desk for Odoo: tickets by mail and on the customer portal, service targets counted in working hours, and a missed target given to somebody by name.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

The ticket pipeline of the demo: New, In Progress and Waiting on Customer, each card with its reference, customer, priority, tags and the next deadline
The ticket pipeline of the demo: New, In Progress and Waiting on Customer, each card with its reference, customer, priority, tags and the next deadline
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsOdoo onlyno Enterprise module
Price149 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.2.3bambooforge_helpdesk

110 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.

How you use it

How the desk works

Flow 01

Set up a team

For the team leader, once.

  1. Helpdesk > Configuration > Teams: the leader, the agents, who may read the tickets.
  2. Type the mail alias and choose the working hours.
  3. Tick the receipt by mail and the rating request, or leave them off.
  4. On the Service Targets tab: what, within how many working hours, for which tickets.
A team form on the demo: leader, agents, mail alias, working hours, and the receipt by mail ticked
Flow 02

Work a ticket

For the agent.

  1. Helpdesk > Tickets opens on the open tickets, by stage.
  2. Assign to me, then answer in the chatter: a note is internal and is not an answer.
  3. Waiting for the customer? Move it to Waiting on Customer: the clock stops.
  4. Close, with a reason when the stage asks for one.
A ticket on the demo: customer, team, assignee, type, priority and tags, with the buttons Assign to me, Close, Merge, Canned reply and Suggest a reply
Flow 03

Keep the promise

For the team leader.

  1. The Service Targets tab lists each target, its deadline, when it stopped and whether it was met.
  2. A missed target turns the ticket red and gives an activity to somebody by name.
  3. Helpdesk > Reporting > Tickets: by team and target, by week and stage.
The Service Targets tab of a ticket on the demo: first reply and resolution targets with deadline, time reached, lateness and status
Flow 04

Answer faster

For the agent.

  1. Canned reply: an answer written once, filled in for this ticket, edited before it goes.
  2. Its macro moves, tags or closes the ticket after sending.
  3. Suggest a reply: the last answer given on a similar solved ticket, as a draft.
The Canned response window on a ticket of the demo: the response chosen, what it does after, and the text filled in for this customer
Flow 05

The customer's side

For the customer, on the portal.

  1. Support Tickets lists their tickets and, unless private, their company's.
  2. A ticket shows the conversation without internal notes, and a box to answer.
  3. The contact named on it can close it; New ticket opens another.
A ticket on the demo's customer portal: the reference, the subject, the status, the conversation and the box to answer

Price and where to buy

149 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:

Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.