TicketHappy
Guide Sign in Start free trial

Setup guide

Everything you need to set up your help desk and run it day to day, from your first ten minutes to forwarding your support address and splitting the work between departments.

New here? The tutorials are the short version: eight walkthroughs for your first hour.

Getting started

The step-by-step setup panel

Owners and administrators get a Setup tab on the right of every page. It opens a step-by-step guide: bring in your old tickets, connect Jamf Pro or Intune, forward your support e-mail from Microsoft 365 or Google Workspace, set up single sign-on with Google, Microsoft, Okta or another provider, then departments, people, articles, service levels, branding and your plan. Each step explains what to do and opens the page it needs, and the guide stays open beside the page while you work, so you can explore during your trial and come back to it.

Do the steps in any order. Skip: we don't use this for anything you don't need, and Mark as done when you've finished one. Many tick themselves: importing tickets, the first forwarded e-mail, adding equipment, inviting people. When you're finished, choose I'm done with setup to put the panel away; Settings → Setup guide brings it back.

The checklist in brief

This takes most organizations about half an hour. You can stop at step 4 and come back to the rest.

  1. Sign up and pick a plan. Create your account, name your organization, and choose how many agents. Stripe asks for a card to start the 30-day free trial; nothing is charged until it ends, and you can cancel before then. Have a promotion code? Enter it on Stripe's page under Add promotion code.
  2. Check your settings. Under Organization → Settings, set your company name, the ticket prefix (tickets are numbered like TH-1, TH-2), your time zone and the default priority.
  3. Name your departments. You start with one department, called Support, which receives everything. Rename it (for example to I.T.) under Organization → Departments, and add others, such as H.R. or Facilities, if they run their own queues. To share a department's new tickets out among its agents in turn, tick Share new tickets out in turn in its settings; each team can follow that or choose its own. See Departments and teams.
  4. Invite your team. Under Organization → People, invite your agents and managers by email and choose their departments. Everyone else, the people raising tickets (staff, customers, students, parents), joins as a requester, which is free. See Adding agents and other people.
  5. Add ticket categories. Each department has its own categories (Hardware, Accounts, Payroll), set on the Departments page. A category can set a default priority and a default assignee.
  6. Set your service levels. Under Settings → Service levels, choose your working hours and how quickly you aim to reply to and resolve each priority. See Service levels.
  7. Connect your support email. Forward your existing address, such as [email protected], to TicketHappy so emails become tickets. See Tickets by email.
  8. Publish answers. Write a few knowledge-base articles and, if you like, switch on the public knowledge base with your logo and colors. See Knowledge base.
  9. Optional extras. Let people sign in with Google or Microsoft, add custom fields such as Room number, save canned responses and record your equipment in the inventory.

Who can do what

Each person has one role in your organization. The same person can have a different role in another organization.

RoleWhat they can doUses a seat
OwnerEverything, in every department: settings, billing, people and every ticket. There can be more than one (see below).Yes
AdministratorRuns their own departments' people, settings and tickets, invites people and manages billing.Yes
ManagerSees, assigns and edits every ticket in their departments; looks after their teams, categories and reports.Yes
Support agentSees their departments' queues, and assigns and works any ticket in them.Yes
RequesterRaises tickets with any department and follows their own. Never sees internal notes.No, free

Adding agents and other people

Invite someone

  1. Go to Organization → People.
  2. Under Invite someone, enter their email address and choose a role.
  3. For staff, tick the departments they'll work in.
  4. Click Send invitation. They get an email with a link that works once, for that address only, for 7 days. Outstanding invitations are listed on the same page, where you can revoke them.

If your plan has no free seats left, inviting a staff role is refused. Requesters never need a seat. Add seats under Billing to get more.

Change a role, or remove someone

On the People page, change someone's role from the list, or Deactivate them. A deactivated person can't sign in, and their open tickets go back to the queue. You can reactivate them later. Nothing is deleted, so their history stays on the tickets.

Let people join on their own

If everyone at your organization has an address like [email protected], verify that domain and new people can join automatically when they sign in. See Signing in with Google or Microsoft.

More than one owner

Your organization can have several owners, and they're all equal. Only an owner can change who the owners are, on the People page:

  • Make owner on someone who's already joined. People can't be invited straight in as an owner: invite them first, then make them one.
  • Remove as owner on another owner, or Step down on yourself. They become an administrator.
  • There's always at least one owner, so the last one can't step down. Make someone else an owner first.

Every owner gets an email whenever the owners change, and it's recorded in the audit log. If your only owner has left and nobody can sign in as an owner, contact TicketHappy support. Once we've checked with your organization, we can make someone else the owner.

Departments and teams

A department is a separate help desk inside your organization, such as I.T., H.R. or Facilities. Each has its own queue, people, ticket categories and email address. Departments can't see each other's tickets or staff. A team is a smaller queue inside a department, such as Devices or Network, and everyone in the department sees every team's tickets.

Add a department (owner)

  1. Go to Organization → Departments.
  2. Under Add a department, enter a name and, optionally, a short email name such as hr. Its address becomes [email protected].
  3. Open the department's Settings to choose whether it takes tickets by email and who may email it.
  4. Add people to it from its People list, or choose it when you invite them.

Teams and categories

Under each department, its managers can add teams and ticket categories. Put people in a team by clicking the team's name next to them. Anyone in a team gets a My teams view on the ticket list.

To give a ticket to a team, choose it under Team, just below Assignee on the ticket, and press Assign to team. To do several at once, tick them in the ticket list and use Assign to team…. Staff can also pick a team when they raise a ticket. A ticket can be in a team without being assigned to anyone yet.

Confidential departments (H.R. and the like)

Normally the owner sees every department's tickets. Tick Confidential in a department's settings and the owner stops seeing its tickets, notes and files anywhere: the ticket list, search, the dashboard, reports and Recently deleted. Its own people work exactly as before.

  • The owner still runs the department: its name, address, people, teams, categories and how long its tickets are kept.
  • The owner still sees a ticket they raised themselves there.
  • The organization export still includes its tickets.
  • If the owner is one of its people, they still see its tickets; remove yourself from its people to stop.
  • The owner can always look, by joining the department or turning Confidential off, but never quietly: either is recorded in the audit log and e-mailed to the department's administrators and managers.

The default department

Your main address ([email protected]), and any ticket raised without choosing a department, go to the default department. The owner can change which department that is.

Moving a ticket to the wrong department is easy to fix: anyone who can edit it can choose Move to department on the ticket page.

Tickets by email

Every organization and department has its own TicketHappy address. An email sent there becomes a ticket, and replying to any TicketHappy notification adds the reply to its ticket.

Your addresses

You'll find your exact addresses on the Dashboard, on Raise a ticket and on the Departments page. your-org is your organization's short name.

Forward your own support address

People are used to emailing an address like [email protected], so keep it and have it send a copy of everything to TicketHappy. Use one of these.

Google Workspace: a group (simplest)

  1. In Google Groups, create a group with the address people already use, such as [email protected] (or open the existing one).
  2. Under Group settings, let anyone on the web (or your organization) post, and allow members from outside your organization.
  3. Add your TicketHappy department address as a member. Keep any colleagues who should still get a copy.

Google Workspace: a routing rule (administrators)

  1. In the Admin console, open Apps → Google Workspace → Gmail → Routing.
  2. Add a Routing rule for messages to [email protected], and under Also deliver to add your TicketHappy address.
  3. Save. Mail now arrives in both places.
Gmail's own Forwarding setting (in a mailbox's settings) first sends a confirmation code to the new address, which TicketHappy can't show you yet. Use a group or a routing rule instead.

Microsoft 365

  1. In the Exchange admin center, open Mail flow → Rules and add a rule.
  2. Apply it when the message is sent to [email protected], and choose Bcc the message to (or Redirect the message to) your TicketHappy address.
  3. Save. If you forward from a mailbox's own settings instead, Microsoft blocks forwarding outside your organization by default; an administrator has to allow automatic external forwarding in the outbound spam policy.

Anything else

Any email service that can forward, redirect or copy incoming mail to another address works. Point it at your TicketHappy department address.

Who may email in

Each department chooses, in its settings on the Departments page:

  • Members only (the default): anyone in your organization, requesters included.
  • Members and anyone at your verified domains: plus people with an address at your verified domains who don't have an account yet.
  • Anyone: useful for HR, admissions or a customer-facing team, which hear from people outside the organization.

People without an account get updates by email and can reply to them. One outside address can open at most five tickets an hour, so an auto-responder can't flood your queue. Out-of-office replies and bounced emails are ignored.

Attachments and pictures

Attached files and pictures pasted into the email both reach the ticket, and pictures show on the ticket page. A logo in someone's email signature arrives as a picture too. Files that aren't allowed are removed, and the ticket says what was removed and why.

Replies and the sender's name

Notifications come from TicketHappy's address, or from your own once you set it up (below), with the ticket number in the subject, like [TH-42]. Each has its own reply address, so people just press reply. Tickets arrive within about five minutes of the email.

Send from your own address

Ticket emails can come from your own address, such as [email protected], instead of TicketHappy's. An administrator sets it up once.

  1. Forward your support address first. Make sure the address already forwards to your TicketHappy address (see Forward your own support address above).
  2. Enter your address. In Settings → E-mail → Send from your own address, type it and click Save. TicketHappy shows one DNS record, a TXT record whose name ends in ._domainkey.yourorganization.org. It's made for your organization alone, and a new one is made each time the address is set up.
  3. Add the record. Ask whoever manages your domain (your IT team, Cloudflare, GoDaddy, Google or Microsoft's domain settings) to add it exactly as shown. Its value is longer than 255 characters; if your DNS provider asks for shorter pieces, split it into two quoted strings in the same record. You don't need to change your existing SPF record.
  4. Check it. Back in TicketHappy, click Check records. It usually works within minutes, though DNS can take up to 48 hours. A record that isn't found within three days needs setting up again.
  5. Send a test. Click Send a test e-mail; it comes to you from your address.
  6. Turn it on. Switch on Send ticket e-mails from this address. Ticket emails now come from your address. Replies still land on the right ticket, and sign-in and billing emails still come from TicketHappy.

If the record is ever removed, TicketHappy goes back to sending from its own address and emails your administrators, so no email is lost. If it isn't back within 30 days, the address is released and needs setting up again. A domain can only be set up by one organization at a time.

Working with tickets

Raising a ticket

Anyone in your organization can choose Raise a ticket, pick the department (when there's more than one) and a category, describe the problem and attach files or photos. Allowed files are pictures (PNG, JPEG, GIF, WebP and iPhone HEIC), PDF, Word, Excel, text and CSV, up to 10 MB each and 10 per ticket. Photos are cleaned on upload, which removes their location data.

From new to closed

A ticket moves through Unassigned → Assigned → In progress → Resolved → Closed, and can be reopened. Every step is time-stamped, which is what the reports and service levels are built on.

  • Waiting on requester and On hold (waiting on a vendor or a part) pause the service-level clock, and the deadlines move on by the time spent waiting. When the requester replies, a ticket waiting on them goes straight back to the help desk.
  • A reply reopens a resolved ticket. Resolved tickets close by themselves after 7 days (change it, or switch it off, under Settings → Workspace); a reply to a closed ticket doesn't reopen it.
  • Pick it up: an agent can take any unassigned ticket in their departments.
  • Assign it: agents, managers and administrators can give a ticket to anyone in its department, or reassign it.
  • Reply or add a note: a reply is emailed to the requester; an internal note is only for staff. Canned responses insert saved wording.
  • Resolve it: add a resolution note, and the requester is told by email.
  • Move it: use Move to department when it belongs to someone else.

Bringing in your old tickets

Owners and administrators can import tickets from another help desk or a spreadsheet: Settings → Import tickets, or the “Bring in your old tickets” step of the setup guide. Export from Zendesk, Freshdesk, Spiceworks or wherever they are now, or save your spreadsheet as CSV.

  • Each row is a ticket. Only Subject and Requester email are required; the page lists the other columns (status, priority, department, category, team, assignee, opened, resolved and closed dates, resolution and the old ticket number) and the other names they go by, so most exports work as they are.
  • Check file shows what would be imported, or the rows to fix, and saves nothing. A file with any bad row imports nothing.
  • Imported tickets keep their dates and get new numbers here; search for an old number to find its ticket. Nobody is e-mailed, nothing is auto-assigned, and they have no service-level deadlines, so old open tickets don't arrive overdue.
  • People who aren't members are recorded by e-mail address and name. Departments, teams and assignees must exist first; new categories are added for you.
  • Undo under Past imports puts an import's tickets in Recently deleted together; restoring it there brings the whole import back.

Copying people in

Under Copied in on a ticket, the requester or staff can add anyone's e-mail address: a principal, an aide, a vendor. They get the replies and updates by e-mail (never internal notes) and can reply. People on the Cc line of the e-mail that opened a ticket are copied in automatically. Staff can choose Follow this ticket to keep up with one that isn't theirs.

Who else is looking

When someone else has the same ticket open, a bar at the top names them. If they've started typing a reply, it turns amber and says Someone is replying, so check before you answer too. The requester shows up there too, tagged requester. A ticket left open in another browser tab doesn't count, and only staff see the bar.

Deleting a ticket

Spam, a test, or a ticket raised by mistake: a department manager or administrator can choose Delete ticket at the bottom of its Actions. It disappears from the queue, the dashboard, reports and search. An owner or administrator can restore it from Recently deleted for 30 days; after that it's gone for good. To clear out a lot of spam, tick the tickets in the ticket list and choose Delete. Agents can't delete tickets. For a real request that's finished, resolve or close it instead.

Duplicates and outages

  • Merge a duplicate: under Related tickets, start typing in Merge this duplicate into: a word from the subject, the person's name or the number. Choose the right ticket from the list, then Merge. The duplicate's replies and files move across, its requester is told, and it closes. Only the same person's tickets in the same department can be merged, so nobody reads someone else's ticket; for the same problem reported by different people, link them instead.
  • An outage: tick the reports in the ticket list and choose Link to ticket # with the main ticket's number. When it's fixed, Resolve all on the main ticket resolves every linked one and sends each requester your note.

Finding tickets

Use the tabs above the list (All tickets, Assigned to me, Unassigned, My teams), or search: it looks in replies too, and staff also search their departments' internal notes. The Filters button opens the rest: status, priority, department, team, assignee, service levels and your custom fields. Click + Save view to keep a set of filters as your own tab.

Changing many at once

Tick tickets in the list (or the box at the top to tick the whole page). In the bar that appears, choose Assign to… to give them all to one person (or Unassigned to put them back in the queue), Mark as… to resolve or close them, or Link to ticket # for an outage. Each ticket follows the usual rules, and any that can't change are listed with the reason.

Who gets e-mailed

  • New and assigned tickets: each department chooses, on the Departments page, who hears about new tickets (nobody, its managers, or everyone in it) and whether managers hear about assignments. Each team can e-mail its members too.
  • Your own: click your name in the top right, choose Profile and e-mail settings, and under E-mail me when turn off the ones you don't want.
  • Requesters: under Settings → Requester e-mails, choose which they get: received, replies, waiting on them, work started, resolved, closed, merged.

Your account menu and theme

Click your name in the top right for your profile, the theme and Sign out. Pick a theme: match your device, light, dark, green terminal, black and white terminal, forest or glitter (which comes with a sparkle trail behind your mouse). It changes straight away and is saved on your account, so it follows you to any computer you sign in on. Everyone chooses their own; it doesn't change anyone else's screen.

The menu is in three parts: Support for tickets and reports, Resources for inventory, the knowledge base and this guide, and Organization for owners and managers. Click Collapse menu at the top to shrink it to small icons and give the page more room; hover over an icon to see its name, and click Expand menu to bring the words back. Each computer remembers which way you left it.

Service levels

Under Settings → Service levels, set your working days and hours, then, for each priority, how many working hours you aim to take to send the first reply and to resolve the ticket. The clock only runs during working hours.

  • Tickets show countdown badges, such as Reply due in 40 minutes, and the ticket list can filter for SLA at risk or SLA breached.
  • When a target is close, the assignee is emailed (or the department's managers, if nobody has the ticket). When it's missed, the managers are told too.
  • The dashboard and reports show how often targets were met.

Data retention

Under Settings → Data retention, choose how long finished tickets are kept: 3 or 6 months, or 1, 2, 3, 4, 5, 6, 7 or 10 years (2 years unless you change it). Once a ticket has been closed (or resolved and never closed) for that long, it's deleted for good overnight, with its replies, notes, attachments and history. Open tickets are never deleted.

  • A department can keep its own period, such as HR keeping records longer. Leave it on Same as above to use the organization's.
  • The owner sets the organization's period. The owner, or a department's administrator, sets that department's.
  • A shorter period starts a week after you choose it, and the owners and the administrators it affects (and a department's managers) are e-mailed. The card shows what's waiting and how many tickets will go then. Choose a longer period before then and nothing is deleted early. A longer period starts straight away.
  • Imported tickets keep their old dates, so some may already be past the period. They're kept for 14 days after the import, so the period can be lengthened first; the import says how many there are.

Restoring something that was deleted

Deleted tickets, attachments, assets, articles, canned responses, categories, custom fields, teams and departments aren't gone straight away. Owners and administrators can find them under Recently deleted in the sidebar for 30 days, see who deleted them, and Restore them; anything that went with them, or used them, comes back too. After 30 days they're deleted for good. Delete now removes something at once, for example a file with someone's private details in it.

Export your data

The owner can choose Download export on the same card for one ZIP file with everything: every ticket, reply, internal note, person, knowledge base article and piece of equipment, as JSON and as CSV spreadsheets, plus the files attached to tickets. It works even after the subscription has ended, so you can take your data before it's deleted.

Categories, canned responses and custom fields

Categories

Each department's categories sort its tickets and can set a default priority and default assignee. Manage them on the Departments page.

Canned responses

Save replies you write often under Canned responses, either shared with your team or just for you. Placeholders fill themselves in when you use one: {{requester_first_name}}, {{ticket_key}}, {{agent_first_name}} and {{organization}}.

A shared reply can be for the whole organization or for one department. Choose the department under Shared with: only that department's staff see it, and only on that department's tickets, so HR's replies don't clutter IT's reply box. Managers look after their own departments' replies.

Custom fields

Under Settings → Custom fields, add the details you always need, such as Room number or Division: text, a list of choices, yes/no and more. A field can be required, kept to staff only, or offered as a filter on the ticket list.

Knowledge base

Write articles under Knowledge base. Each has a visibility:

  • Technicians only: runbooks and internal notes.
  • Signed-in members: everyone in your organization.
  • Public: anyone, through your public knowledge base.

Your public knowledge base

  1. Under Settings → Public knowledge base, tick Publish a public knowledge base. It lives at https://tickethappy.app/help/your-org/ and needs no sign-in.
  2. Upload your logo (PNG, JPEG or WebP; a transparent PNG looks best), choose a brand color, and choose whether it opens light, dark or follows the visitor's device.
  3. Publish some articles as Public. Only published public articles appear there.

Each department's own articles

Give an article a department and it belongs to that department. Leave it on The whole organization for articles everyone shares.

  • While it's a draft, or for technicians only, only that department's staff see it. IT's runbooks stay with IT, and HR's notes stay with HR.
  • That department's managers can edit it, as can whoever wrote it.
  • Once it's published for signed-in members or the public, everyone can read it, whichever department wrote it.
  • When more than one department has public articles, your public knowledge base lists Browse by department, so visitors can go straight to IT's or HR's answers.

Inventory and reports

Inventory

Record your equipment with an asset tag, serial number and location, assign it to a person, and link it to tickets about it. Click an asset's name to open its page: its details, the tickets about it, and the history of who has had it. Owners, administrators and managers can edit its details there, and hand it to anyone in the organization, requesters included: search for them under Who has it. They can also Delete an asset, from its row in the list or from its page; it goes to Recently deleted for 30 days.

Importing from a spreadsheet

Owners, administrators and managers can add or update many assets at once: on the Inventory page, choose a CSV file under Import from a spreadsheet. Each row is matched to an asset by its asset tag; new tags are added, and blank cells leave what's there alone. Put a member's e-mail address under Assigned to to hand the asset to them. Check file shows what would change without saving anything. If any row has a problem, nothing is imported and every problem is listed by line, so you can fix them all at once. Download the template shows the columns; Download as CSV gives you the whole inventory in the same layout, ready to edit and import again.

Syncing from Jamf Pro or Intune

Administrators can connect Jamf Pro or Microsoft Intune under Settings → Inventory sync; the card explains what to create on their side. Every night, computers, iPads and phones come in, matched to assets you already have by serial number, and their names, models and users are kept up to date. A device is handed to its user only when that person is a member here who has confirmed their e-mail address; users who aren't are counted in the sync's result, not named. Nothing is ever deleted or taken back from someone. Use Test connection to check the details, and Sync now to run it straight away. If a sync starts failing, the owner and administrators are e-mailed once.

Syncing Chromebooks from Google Admin

Organizations on Google Workspace can bring their Chromebooks in from the Google Admin console. The card under Settings → Inventory sync walks through it: a service account in Google Cloud with the Admin SDK API turned on, domain-wide delegation of one read-only scope in the Admin console, and the e-mail of an administrator for it to act as. Every night each Chromebook's serial number, model, asset ID, location, organizational unit, ChromeOS version and status come in. It's handed to its annotated user only when that person is a member here who has confirmed their e-mail address. Its recent users and activity are never read. A disabled Chromebook is marked lost or stolen (and goes back when it's re-enabled); a deprovisioned one is left out, so it shows as missing from the sync.

Reports

Owners, administrators and managers can open Reports for the last 7, 30 or 90 days, or 12 months: tickets opened and resolved, first-reply and resolution times, how often service levels were met, the busiest categories and requesters, and each person's workload. Each manager sees their own departments.

Signing in: Google, Microsoft, Okta and two-step

Anyone can sign in with an email and password, or with Sign in with Google or Sign in with Microsoft on the sign-in page. If your organization has its own single sign-on (Okta and the like, below), people choose Sign in with SSO and enter their work email address. The iPhone app has the same button.

For schools: students signing in with Google

Google Workspace for Education blocks users marked as under 18 from signing in to apps the school hasn't approved, so Sign in with Google won't work for students until your Google administrator trusts TicketHappy. It takes a couple of minutes, once:

  1. In the Google Admin console, open Security → Access and data control → API controls, then Manage third-party app access.
  2. Click Configure new app and search for TicketHappy's client ID: 627573507048-0u30c3u4i0u2foi3mg3n95dgr9qmpjfb.apps.googleusercontent.com. Select TicketHappy.
  3. Choose who it applies to: your whole domain, or just the students' organizational unit.
  4. Choose Trusted, then Configure.

Staff over 18 can usually sign in without this step. TicketHappy asks Google only for each person's name and e-mail address.

Approve TicketHappy in Microsoft 365 (IT admin, once)

Many organizations' Microsoft 365 stops staff from approving new apps, so the first person who clicks Sign in with Microsoft sees Approval required. Your Microsoft 365 administrator approves TicketHappy once, for your whole organization:

  1. In TicketHappy, open Settings → Microsoft 365 sign-in and click Approve TicketHappy for your whole Microsoft 365 organization.
  2. Sign in on Microsoft's page with an administrator account (a Global, Cloud Application or Application Administrator), then choose Accept. Microsoft shows the publisher as Kooster Bear LLC, with its verified badge.

After that, staff sign in with Microsoft as normal. If someone else is your Microsoft 365 administrator, copy the button's link and send it to them (it only opens Microsoft's approval page), make them an administrator in TicketHappy, or sit with them while they click it. Another way: when an administrator signs in to TicketHappy with Microsoft, they can tick Consent on behalf of your organization on Microsoft's prompt.

Allow TicketHappy in your web filter

If your web filter hasn't seen TicketHappy before, it may block it or show a warning page. Add both of these to your filter's allow list:

  • tickethappy.app
  • *.tickethappy.app (every address under it)

In Lightspeed, Securly, GoGuardian, Zscaler and most others, you do this in your own admin console. While you're there, you can also suggest a category for the site, such as Information Technology or Business software, so it's sorted correctly for other customers too.

Two-step sign-in

Anyone with a password can add a second step under Profile → Two-step sign-in:

  • An authenticator app, such as Google Authenticator, Microsoft Authenticator or 1Password: scan the QR code, then type the 6-digit code it shows each time you sign in.
  • A passkey: Face ID, Touch ID or a security key. A passkey can also sign you in on its own, without the password.
  • Recovery codes are made for you with the first one. Keep them somewhere safe: each gets you in once if you lose your phone.

In the iPhone app, sign in with your password as usual; the app then asks for the code from your authenticator app (or a recovery code).

Lost your phone and your recovery codes? Contact TicketHappy support. We'll check it's really you, usually by calling your organization's main number, before removing your two-step sign-in and e-mailing you a link to choose a new password. Your organization's owners and administrators are told whenever this happens, and it's recorded in its audit log. It can't be done by e-mail alone, and text messages are never used for sign-in codes.

Verify your domain so people join automatically

  1. Under Settings → Single sign-on domains, add your domain, such as yourdomain.org.
  2. Publish the TXT record it shows in your domain's DNS, then click Verify. DNS changes can take a while to appear.
  3. In the Workspace settings, tick Let anyone with a verified company e-mail domain join automatically and choose the role they join with (usually Requester).

A domain can belong to only one organization. Joining as staff still needs a free seat; if there isn't one, the person joins as a requester.

Use Okta or your own single sign-on

Your organization can sign in through its own identity provider: Okta, OneLogin, JumpCloud, Microsoft Entra, Google Workspace, ADFS, or any other that speaks SAML 2.0 or OpenID Connect. Only the owner can set it up, and it only signs in people with an address on your verified domains, so verify your domain first (above).

  1. Under Settings → Single sign-on, choose SAML 2.0 (or OpenID Connect), name it (say, Okta) and click Start setting up.
  2. In Okta, go to Applications → Create App Integration → SAML 2.0. Copy in the Single sign-on URL and Audience URI that TicketHappy shows. Set Name ID format to EmailAddress and Application username to Email. If you want a tile on people's Okta dashboards, also copy in the Initiate login URI.
  3. Finish the app in Okta and assign the people who should use TicketHappy.
  4. Copy the app's Metadata URL from its Sign On tab, paste it into TicketHappy and click Save. It should say Ready.
  5. Click Sign in with Okta under Try it to check it works.
  • People who already have a TicketHappy account with that address are signed in to it; nobody loses their tickets or history.
  • New people get an account. To let them in without an invitation, tick Let anyone with a verified company e-mail domain join automatically.
  • Removing someone in Okta stops them signing in again. Unless Okta provisions people (below), deactivate them under People too, to end a session they already have.
  • When Okta's certificate changes, paste the metadata URL again.

Let Okta add and remove people (provisioning)

Okta can add people to TicketHappy, keep their names up to date, and deactivate them the moment they leave, in the browser and the iPhone app, so nobody has to do it under People. It needs Okta Lifecycle Management (in Microsoft Entra ID, Entra ID P1). Without it, keep deactivating people under People; that works the same. Set up single sign-on first (above).

  1. Under Settings → Single sign-on → Provisioning, click Make token and copy it. It's shown once; if it's lost, make a new one.
  2. In Okta, open the TicketHappy app and go to General → App Settings. Set Provisioning to SCIM and save.
  3. On the new Provisioning tab, under Integration, copy in what TicketHappy shows: the SCIM connector base URL (https://tickethappy.app/scim/v2/) and userName as the Unique identifier field for users. Tick Push New Users and Push Profile Updates, set Authentication Mode to HTTP Header and paste the token. Click Test Connector Configuration, then Save.
  4. Under Provisioning → To App, enable Create Users, Update User Attributes and Deactivate Users.
  5. Assign the people or groups who should have TicketHappy. Back in TicketHappy, Last used shows when Okta last called.
  • New people join with the role set under Workspace (requester unless you chose otherwise), and only if their address is on a verified domain. Roles are changed in TicketHappy, not Okta.
  • Deactivating someone in Okta deactivates them here and returns their open tickets to the queue. Nobody is ever deleted, and Okta can't deactivate an owner.
  • Making a new token stops the old one at once. Revoke stops provisioning; the people already here stay as they are.

Choose how your members sign in

Under Settings → Workspace → How members sign in, the owner or an administrator picks one of: any way; Require SSO; or Require two-step sign-in for password accounts. You can't require both, because signing in with single sign-on already counts as two-step.

Require everyone to sign in with single sign-on

When this is on, your members can't sign in with a password, in the browser or the iPhone app. If you've set up your own single sign-on (Okta and so on), it's the only way in; otherwise it's Google or Microsoft.

  1. The owner sets up two-step sign-in first (above). The owner keeps their password as a way back in, so it needs a second step; TicketHappy won't switch SSO on until it has one.
  2. Sign in with your single sign-on: Try it under Settings → Single sign-on, or sign out and back in with Okta, Google or Microsoft. Do this before switching it on: TicketHappy won't save the setting unless you're signed in that way, so you know it works before everyone has to use it.
  3. Under Settings → Workspace, choose Require Okta (SSO) (or Require Google or Microsoft) and click Save settings.
  • People already signed in another way are asked to sign in with their work account the next time they open a page. If it isn't connected to their TicketHappy account yet, they connect it there and carry straight on.
  • Password resets don't send a reset link. The email explains how to sign in instead.
  • The owner keeps their password, with two-step sign-in, as a way back in if single sign-on ever stops working. The owner can't remove their last authenticator app or passkey while SSO is required, and is reminded on every page if they don't have one.
  • Someone who also belongs to another organization that doesn't require it can still use a password there.

Require two-step sign-in

When this is on, anyone who signs in with a password also needs their authenticator app code or a passkey. People who sign in with Google, Microsoft or your own single sign-on aren't asked for anything more.

  1. Set up two-step sign-in for yourself, and sign in with it. TicketHappy won't switch the setting on until you do.
  2. Under Settings → Workspace, choose Require two-step sign-in for password accounts and click Save settings.
  • Anyone without it is asked to set it up the next time they open a page, and carries straight on once they have.
  • While it's required, people can't remove their last authenticator app or passkey; they can add a new one first, then remove the old one.

Plans and billing

BillingPriceMinimum
Monthly$10 per agent seat a monthNone: 1 seat is $10
Yearly$100 per agent seat a year (two months free)None: 1 seat is $100
  • Seats: owners, administrators, managers and agents use seats. Requesters are free and unlimited.
  • The trial: 30 days, with a card saved at the start. The card is charged when the trial ends, unless you cancel first.
  • Adding seats: under Billing → Seats, enter the new number and choose Update seats. Stripe charges or credits the difference for the rest of the month (or year). You can't go below the seats in use.
  • Sales tax: public bodies, schools, districts and nonprofits are usually exempt. Under Billing → Sales tax, choose Yes and enter your exemption number, then e-mail the certificate to [email protected].
  • Refunds: cancel within 30 days of a payment for a full refund of it; after that, a yearly plan is refunded for the whole months left.
  • Cards and invoices: Manage payment & invoices opens Stripe's secure page. Card details never pass through TicketHappy.
  • If a payment fails: after the first bill, the workspace becomes read-only until the invoice is paid. Later, a failed renewal gets 14 days' grace first. Read-only means everyone can still read tickets, but nothing can be changed until the bill is paid from the Billing page.
  • If the subscription ends (you cancel, or a renewal is never paid), the workspace stays readable for 90 days. A week before the end, the owner and administrators are emailed; after 90 days everything is deleted for good: tickets, files, the knowledge base, inventory, settings, and the accounts of people who belong to no other organization. Renewing in Billing before then keeps it all. The owner can download an export at any time (see Data retention).

Troubleshooting

An email didn't become a ticket.
Check, in order: that email intake is switched on in Settings; that the department takes tickets by email; that the sender is allowed by the department's Who can email in setting; and that the forwarding rule sends to the right TicketHappy address. Tickets arrive within about five minutes.
A colleague can't see a ticket.
They probably aren't in that ticket's department. Add them on the Departments page, or move the ticket.
An agent can't change a ticket.
Agents can change any ticket in their own departments. If they can't, the ticket is in a department they aren't in: add them on the Departments page, or move the ticket.
I can't invite another agent.
All the seats you pay for are used. Deactivate someone who has left, or add seats under Billing.
A file won't upload.
It has to be one of the allowed types and 10 MB or less, and a ticket holds up to 10 files. The message that appears says which rule it broke.
I can't switch on Require SSO.
The message says why. The owner needs two-step sign-in set up first; then sign in with your single sign-on (Try it under Settings → Single sign-on), since a password sign-in can't switch it on. If it says single sign-on isn't set up, set up your own (above).
Okta says it signed someone in, but TicketHappy refuses.
TicketHappy only accepts addresses on your verified domains. Check the address Okta sends (the app's username should be the person's email) and that its domain is verified under Settings → Single sign-on domains.
I can't switch on Require two-step sign-in.
Set up two-step sign-in for yourself under Profile → Two-step sign-in, then try again.
Someone lost the phone with their authenticator app.
They can sign in with one of their recovery codes, then set up the app again on their new phone. If they have no recovery codes either, contact us.
Someone can't sign in with their password any more.
Your organization requires single sign-on. They should choose Sign in with SSO (or Google or Microsoft, if that's what you use) with their work account. (If it asks for a code instead, your organization requires two-step sign-in: see above.)
Everything says the workspace is read-only.
A bill is unpaid, or the card hasn't been added yet. The owner or an administrator can fix it from the Billing page; tickets stay readable meanwhile.

Still stuck? Sign in and raise a ticket, or email us.

Are you sure?