A ticketing system everyone in your organization can use

A ticketing system is where people ask for what they need, and where the team that handles it sees each job through to the end. In fam., every request becomes a ticket that everyone involved can open, with its priority, its deadline and the people on it.

Most organizations start with an email address, a phone number and a group chat. Something breaks, someone writes, and someone else replies "I'll have a look". A week later nobody remembers whether it was done, and you're the one who gets asked.

Anyone can ask, and it costs you nothing

Requester seats are free and unlimited, so you can open fam. to the whole organization on the first day without counting heads.

The form is short. People start from a location, an asset or the request itself, and fam. asks only for what's missing. They attach a photo if it helps, and they're done.

Your admins build the list of requests, so it uses your organization's own words. Work that isn't tied to a place has a home too: access to an IT system, a new user account or a parking permit can be a form under General location.

A request can also come with a short checklist for the person creating it. They answer it first, so the team gets the answers with the job, and nobody calls back to ask which floor it was.

Requests go straight to whoever's on

For each request at each location, your admins choose who handles it in business hours and who handles it out of hours, each with a budget. A new ticket goes straight there, and nobody has to sort an inbox first.

A ticket can go to an organization, a team or a person. It also shows the office operator or team handling it and the field operator or team doing the work on site, so whoever opens it sees who's on it right now.

The ticket's priority sets the deadlines for acceptance, first attendance and resolution. Click the priority and you'll see when each one falls and whether it was met. Urgent tickets nobody has picked up yet have a page of their own, so you'll know where the morning starts.

The person who asked sees every step

The operator accepts the ticket, schedules it, checks in on arrival and checks out when the work is done, and each step goes on the ticket's timeline. The person who created the ticket watches it from the start, so every step reaches them in the app and by email. They can turn either one off. Our work order software page follows the same job from the operator's side, through the checklist at check-out to what it cost.

Everything they've asked for is under Requested by you. When the work is done, the ticket waits under To rate. Rating takes a few seconds, with stars and a line on why, and after a few months you'll see which work is done well and where it isn't.

The conversation stays on the ticket

Comments, photos and costs are on the ticket, so nobody digs through a mailbox to find them. When you need someone to look at something, nudge them. Only the people you pick will see it, and it leaves no trace on the ticket.

Anyone who can see a ticket can watch it and get its updates in the app, by email or both. A team that works in several languages reads the same ticket too: fam. is available in ten languages, and anyone can translate a ticket into more than 130, comments included.

If the same team also plans maintenance and looks after your assets, our CAFM software page shows how that works in fam.

How much does a ticketing system cost?

With fam., you pay for the people who run the system and the people who do the work: Admins and Operators each have a paid seat on the Operations plan. Requester seats are free for as many people as you have.

There's no setup fee and no lock-in, and you can cancel at the end of any billing period. You'll find the numbers on the pricing page.