Question 1

How to create a ticket

Accepted Answer

Agents can open a ticket from anywhere in the dashboard — customers can too, via the portal, inbound email, or live chat. 1. Click the + New button in the topbar (or press the c key from any dashboard page). 2. In the New ticket dialog, enter a Subject ("What's the issue?") and pick a Type and Priority. 3. Optionally set a Contact, Assignee, Sprint, and Story points. 4. Add a Description — it doubles as the input for AI triage, which suggests a type, priority, and tags from what you wrote. 5. Submit the form (⌘↵ works). The ticket gets a real key like INC-42 or REQ-101, allocated atomically per workspace.

Question 2

How to work the shared inbox with queues

Accepted Answer

Queues are saved views of the same shared inbox — built-in ones for the common cuts, plus unlimited custom ones. 1. In the sidebar under Work, click Queues. Built-in queues cover Mine, Unassigned, Urgent, Breached, Awaiting Customer, and by-Type views. 2. Click any queue to open its ticket list. Filters are URL-synced, so every queue is a shareable link. 3. To make a custom queue, filter All tickets the way you want, then on the Queues page click New under "Save current view as queue", give it a Queue name, and click Save. 4. Use the density toggle (comfortable / compact) and sort by deadline, priority, or key to match how you triage.

Question 3

How to assign tickets (one at a time or in bulk)

Accepted Answer

Every ticket has one assignee; bulk actions handle the Monday-morning pile. 1. On a ticket, use the Assignee dropdown in the Details sidebar — the change saves immediately. 2. For many tickets at once, open All tickets and tick the checkboxes next to each one (or the header checkbox to select the whole page). 3. A bulk bar appears showing "N selected" with Mark resolved, Close, → Urgent, Assign me, and an Assign to… dropdown for any teammate. 4. Bulk updates apply to up to 200 tickets per batch.

Question 4

How to reply to a customer vs. leave an internal note

Accepted Answer

The same composer sends public replies and private team notes — one checkbox decides which. 1. Open the ticket and scroll to the reply composer at the bottom of the Conversation tab. 2. Write your message — Markdown is supported, and @mentioning a teammate adds them as a watcher. 3. For a customer-visible reply, leave "Internal note" unchecked and click Send reply. 4. For a private note only your team can see, check "Internal note" and click Add note. Internal notes render on an amber background so nobody mistakes them for public replies. 5. Drag and drop files straight onto the composer to attach them (uploads use signed URLs).

Question 5

How to merge duplicate tickets

Accepted Answer

When the same issue arrives twice, merge moves the whole conversation into one surviving ticket and closes the duplicate. 1. Open the duplicate ticket and click Merge into… in the header action row. 2. In the merge picker, search for the survivor by key or subject and click it. 3. Review the confirmation ("Move all messages from REQ-101 into INC-42?") and click Merge & close. 4. The duplicate becomes read-only with a banner linking to the survivor; its messages now live in the surviving ticket's conversation.

Question 6

How to snooze a ticket

Accepted Answer

Snooze keeps waiting-on-something tickets out of your active queues until a date passes or the customer replies. 1. Open the ticket and click Snooze in the header action row. 2. Pick 1 day, 3 days, 1 week, or "Until customer replies". 3. The ticket shows a Snoozed label and drops out of active queue views until the snooze ends. 4. To wake it early, open the same menu and click Clear snooze.

Question 7

How to create a custom ticket type

Accepted Answer

Every workspace ships with 8 types (Incident, Service Request, Change, Problem, Bug, Feature, Task, Epic) — and you can add your own. 1. In the sidebar under Admin, click "Types, workflows & tags". 2. Under Ticket types, click + New type. 3. Enter a Name (e.g. "Incident") and a Key prefix (e.g. INC) — new tickets of this type get keys like INC-42. 4. Pick a Color and an icon, then click Create.

Question 8

How to add custom fields to a ticket type

Accepted Answer

Custom fields collect structured data per ticket type — text, number, date, or select. 1. Go to Admin → "Types, workflows & tags" and find the ticket type under Ticket types. 2. Open "Edit custom fields" for that type. 3. Click + Add field and set a Label, a Type (text / number / date / select), and for selects the Options (comma-separated). 4. Click Save schema. The fields now appear on tickets of that type, and the customer portal's service catalog collects them up front.

Question 9

How to build a custom workflow

Accepted Answer

Workflows define the states a ticket moves through and which transitions are allowed. 1. Go to Admin → "Types, workflows & tags" and scroll to Workflows. 2. Click + New workflow and list your States one per line in the format key:Label:#color (e.g. open:Open:#3b82f6). 3. Give each state a category (todo / doing / done) so boards and reports know what "in progress" means. 4. Click Create, then open "Edit transitions", click + Add transition for each allowed move, and click Save transitions. 5. On a ticket, the workflow renders as a state strip with "Move to:" buttons for the valid transitions only.

Question 10

How to turn inbound email into tickets

Accepted Answer

Point your email provider's inbound webhook at Desk and every forwarded email becomes a tracked ticket. 1. In the sidebar under Admin, click Inbound email, then click New endpoint. 2. Name it (e.g. "support@ inbox"), pick your Provider (Postmark, Mailgun, SES, SendGrid, or generic), and set the Default type and Default priority for tickets it creates. 3. Click Create, then Copy the endpoint's webhook URL — your workspace's inbound key is embedded in it, so no shared secret is needed. 4. Paste that URL into your provider's inbound-webhook settings for the mailbox you forward support mail to. 5. Each email auto-creates (or matches) the contact from the From: address, allocates a real ticket key, and threads the body as the first message. The endpoint row shows a receipt count and last-received time so you can confirm it's wired.

Question 11

How to embed the live chat widget on your site

Accepted Answer

A one-line script adds real-time chat to any page you control; agents answer from the dashboard. 1. In the sidebar under Admin, click "Chat widget install". 2. Under Customize, set the Brand color, Header title, and Greeting — the Preview pane updates live. 3. Under Embed snippet, click Copy and paste the <script> tag into any HTML page. 4. Agents answer incoming chats from Live chats in the sidebar (under Manage), with realtime updates. 5. When a chat ends, "Close + Make ticket" replays the transcript into a real ticket so the conversation persists in your inbox.

Question 12

How to set up auto-acknowledgement replies

Accepted Answer

Send every new request an instant "we've received it" confirmation — with an honest after-hours ETA computed from your business hours. 1. In the sidebar under Admin, click Workspace, then open the Automation tab. 2. Check "Enable auto-acknowledgement" (it's off by default). 3. Optionally customize the Subject and Body — merge fields like {{contact.first_name}}, {{ticket.subject}}, and {{workspace.name}} are filled per ticket. Leave blank to use the built-in default. 4. Click Save. Tickets created from the customer portal and inbound email now get an immediate confirmation email. 5. If a ticket arrives outside your business hours, a "we'll respond by…" line is appended automatically, computed from your business-hours calendar.

Question 13

How to create automation rules

Accepted Answer

Rules fire on ticket events and run actions — set priority, set status, send a macro reply, add a tag, assign, or notify. 1. In the sidebar under Manage, click Automations, then click New rule. 2. Name the rule (e.g. "Escalate VIP tickets"). 3. Under When, pick the trigger event: ticket.created, ticket.updated, or ticket.replied. 4. Optionally add a condition (field, operator, value — e.g. priority equals urgent). 5. Under Then, add one or more actions: set priority, set status, send a macro reply, add a tag, auto-assign (round-robin or least-busy), or notify a user. 6. Save the rule. It runs on every matching event from now on, and each firing is recorded in the audit log.

Question 14

How to create macros (canned replies with actions)

Accepted Answer

A macro bundles a reply template with ticket field changes, so "Escalate to Tier 2" is one click instead of four. 1. In the sidebar under Admin, click Settings and scroll to the Macros section. 2. Enter a Macro name (e.g. "Escalate to Tier 2") and the reply body — merge fields like {{contact.first_name}} and {{ticket.key}} are supported. 3. Optionally attach actions: set status, set priority, assign, or add a tag. They apply alongside the reply. 4. Save. On any ticket, pick it from the Insert macro… dropdown in the composer; the body drops in with merge fields already rendered. 5. To apply one macro across many tickets at once, use the Bulk apply a macro page (/dashboard/bulk-macro) — up to 50 tickets per batch.

Question 15

How to use saved replies

Accepted Answer

Saved replies are lighter than macros — pure text snippets, personal or shared with the team. 1. In the sidebar under Admin, click Saved replies, then click New reply. 2. Enter a Name, an optional Shortcut (e.g. /ack), and the Body — Markdown is fine. 3. Your own replies appear under "My replies"; admin-created ones appear under "Shared with team" for everyone. 4. In any ticket composer, pick from the Saved reply… dropdown — merge fields like {{agent.name}} fill in automatically, and unknown tokens are stripped so a raw placeholder never reaches a customer.

Question 16

How to schedule a reply to send later

Accepted Answer

Write the reply now, deliver it when it lands best — at a specific time or when your business hours next open. 1. Write your reply in the ticket composer as usual. 2. Instead of Send reply, click Send later next to it. 3. Choose "Next business-hours open" (resolved from the ticket's SLA calendar) or pick a date & time and click Schedule send. 4. The pending send appears in a Scheduled queue below the composer, with a cancel button if you change your mind. 5. At send time the reply posts, emails the customer, and sets first-response exactly as a live reply would. Closed or merged tickets are skipped automatically.

Question 17

How to auto-assign new tickets (round-robin or least-busy)

Accepted Answer

One toggle routes every new inbox ticket to an available agent the moment it arrives — nothing sits unowned burning its first-response SLA. 1. In the sidebar under Work, click Queues and find the "Automatic ticket assignment" panel. 2. Flip the toggle on and pick a strategy: Round-robin (cycles evenly through available agents) or Least busy (assigns to whoever has the fewest open tickets). 3. That's it — every new ticket in the inbox now routes itself. Manual assignment still works and always wins. 4. Agents control their own availability: in Workspace → Members, the "Accepting new tickets" switch pauses auto-assignment for you (out sick, heads-down) while manual assignment keeps working. 5. If nobody is available, tickets simply stay unassigned until someone frees up — never dropped.

Question 18

How to schedule recurring tickets

Accepted Answer

For the things you must do every Monday, month, or quarter — a template that recreates itself on a cadence. 1. In the sidebar under Admin, click Recurring tickets, then click New schedule. 2. Give it an Internal name, then set the Ticket subject, Ticket body, Type, Priority, and Assignee for the tickets it will create. 3. Set "Every (days)" — anywhere from 1 to 365 — and optionally "Max runs" to cap the total (e.g. create this 12 times, then stop). 4. Click Create. Each run allocates a fresh ticket key (INC-103, INC-104…) with your pre-filled fields.

Question 19

How to create an SLA policy

Accepted Answer

SLA policies set first-response and resolution targets per priority, and every ticket card shows a live countdown against them. 1. In the sidebar under Admin, click SLA policies, then under Policies click + New policy. 2. Name it (e.g. "Standard support") and enter first-response and resolution targets in minutes for each priority (low / normal / high / urgent). 3. Choose how the policy applies — by contact, tag, channel, or as the workspace default. 4. Save. Tickets under the policy show a live SLA countdown pill (green → amber → pulsing red), and breaches are flagged automatically on first response and resolution.

Question 20

How to set up SLA escalation rules

Accepted Answer

Act before a breach, not after — escalate, bump priority, reassign, or notify when a ticket is heading toward its deadline. 1. Go to Admin → SLA policies and scroll to Escalation rules, then click + New rule. 2. Name it (e.g. "Page leads on breach") and pick a Trigger: first response at risk, resolution at risk, first response breached, or resolution breached. 3. For at-risk triggers, set the "At-risk threshold (minutes before due)". 4. Click + Add action and choose what happens: escalate, bump priority, reassign to the least-busy agent, notify a user, or escalate to a role (e.g. notify all owners/admins) — with an optional notification message. 5. Save. Each rule fires exactly once per ticket per stage, so nobody gets spammed.

Question 21

How business hours and holidays affect SLA timers

Accepted Answer

SLA clocks only tick during working hours, so a Friday-evening ticket doesn't breach over the weekend. 1. In the sidebar under Admin, click Workspace and open the Business hours tab to view your workspace's current schedule and holiday calendar. 2. SLA due-by times are computed within these hours; holidays pause the clock entirely. 3. The same calendar powers other features: the auto-acknowledgement after-hours ETA line, "Next business-hours open" scheduled replies, and the unstaffed shading on the Reports coverage heatmap. 4. Editing the schedule is currently done via the API (the Workspace tab shows the active JSON configuration) — a visual editor is on the roadmap.

Question 22

How to write and publish a knowledge-base article

Accepted Answer

Your knowledge base powers the help center your customers see in the portal — and deflects tickets before they're filed. 1. In the sidebar under Manage, click Knowledge Base, then click New article. 2. Enter a Title, pick a Category (create one inline with "New category name" if needed), and write the Body in Markdown. 3. Choose a Visibility: Public (customers), Internal (team only), or Private (admins only). 4. Set the Status to published when it's ready — drafts stay invisible everywhere — and click Save. 5. Published public articles appear immediately in your customer portal's help center and in ticket-deflection search.

Question 23

How to control who can read each article

Accepted Answer

Three visibility levels keep customer-facing docs, internal runbooks, and admin notes in one knowledge base without leaks. 1. Open Knowledge Base and edit (or create) an article. 2. In the Visibility select, choose: "Public — customers" (readable on your help center once published), "Internal — team only" (never shown to customers), or "Private — admins only" (workspace owners and admins). 3. Save. The article list shows a Visibility badge per row so you can audit at a glance. 4. The customer portal and deflection search only ever surface public, published articles — internal and private content cannot leak.

Question 24

How to find knowledge-base gaps from failed searches

Accepted Answer

Every search customers run against your help center is logged — the ones that returned nothing are your highest-ROI writing backlog. 1. In the sidebar under Manage, click Reports. 2. Find the "Content gaps — top searches with no results" card and the zero-result-rate tile. 3. Zero-result queries are grouped by phrase and ranked, so you can see exactly what customers looked for and couldn't find. 4. Write a public KB article for each top phrase, then watch the Deflected tile and Top deflecting articles card to confirm it's working.

Question 25

How to set up the customer portal

Accepted Answer

A passwordless, brand-colored portal where customers open tickets, track them, and read your help center. 1. In the sidebar under Admin, click Workspace and set your "Public URL handle" (e.g. your-company). Your portal lives at /portal/your-company. 2. Set your Brand color on the Branding tab — the portal inherits it. 3. Customers sign in with just their email: the portal sends a single-use magic link that expires in 15 minutes. No passwords, ever. 4. Signed-in customers see "Your tickets", can reply, and can open a "New support ticket". As they type a subject, matching published KB articles surface inline ("These might answer your question") — opening one instead of filing counts as a measurable deflection. 5. The portal's service catalog shows your ticket types so customers pick the right request, and your custom fields are collected up front.

Question 26

How CSAT surveys work (and how to read per-agent scores)

Accepted Answer

Every resolved ticket triggers a one-click 1–5 satisfaction survey automatically — no setup required. 1. Resolve a ticket. The customer receives a survey link asking "How did we do?" with a 1 (poor) to 5 (great) scale and an optional comment. 2. Responses land on the ticket (a Customer feedback panel appears on the detail page) and aggregate into Reports. 3. Open Reports to see the CSAT distribution card for the selected window. 4. The Agent leaderboard shows per-agent CSAT (average score + response count) alongside resolved counts, first-reply time, FCR, and reopens — satisfaction by agent, not just for the team. 5. Every 1- or 2-star rating instantly flags the ticket, pings the assigned agent, and fires a webhook so you can win back unhappy customers before they churn.

Question 27

How to read ticket trends and SLA attainment

Accepted Answer

Reports turns your ticket history into volume trends, first-reply histograms, and honest SLA attainment numbers. 1. In the sidebar under Manage, click Reports and pick a window: 7, 30, 90, or 180 days. 2. Ticket volume charts arrivals over the window; First-reply time is a histogram of how fast you actually respond. 3. SLA attainment shows the percentage of tickets that met their first-response and resolution deadlines, broken down by priority with met/eligible counts. 4. Channel mix and Type mix show where tickets come from and what kind they are; First Contact Resolution is reported net of reopens so the number can't be gamed. 5. Backlog aging (its own page under Work) buckets open tickets by age with a priority breakdown and posture indicator.

Question 28

How to use the coverage heatmap to fix off-hours gaps

Accepted Answer

See exactly when tickets arrive vs. when you're staffed — the off-hours gaps that quietly breach SLAs become obvious. 1. Open Reports and scroll to the Coverage heatmap — a 7×24 weekday × hour-of-day grid in your workspace timezone. 2. Toggle between arrival volume and median first-reply time per cell. 3. Cells outside your business hours (and on holidays) are shaded "Unstaffed" — dark cells with high arrivals are your gap. 4. Read the auto-generated insight line (e.g. "14% of tickets arrive outside business hours; their median first reply is 6.2h vs 41m in-hours") and adjust staffing or business hours accordingly.

Question 29

How to see what customers write in about with tag mix

Accepted Answer

Your team already tags tickets — tag mix turns that curation into a ranked view of topics by volume and satisfaction. 1. Open Reports and find the Tag mix card. 2. Your top support tags are ranked by ticket volume for the selected window. 3. Each tag also shows its average CSAT score, so you can spot the highest-volume and worst-scoring subjects at a glance. 4. Pair it with the Content gaps card: a high-volume, low-CSAT tag with zero-result searches is your next KB article and automation candidate.

Question 30

How to publish a public status page

Accepted Answer

A public health dashboard powered by your CMDB assets — one click to enable, no separate tool to pay for. 1. In the sidebar under Admin, click "Public status page". 2. Under Configuration, enable the page and set a Title, Subtitle, and Contact email (shown in the footer). 3. Choose which asset kinds are visible (empty = all) or pick specific assets, and optionally add custom CSS. 4. Click Save changes. Your page is live at /status/your-slug, showing assets grouped by kind with their current status and an overall posture banner (operational / minor / major / critical).

Question 31

How to create uptime monitors (and auto-declare incidents)

Accepted Answer

Active HTTP(S) checks that flip your CMDB asset status, notify the team, and can open public incidents entirely on their own. 1. In the sidebar under Admin, click Uptime monitors, then click New monitor. 2. Enter a Name and the URL to check, pick a Method and Interval, and set a Timeout. 3. Optionally assert an Expected status code (blank = any 2xx/3xx) and a "Body must contain" keyword. 4. Link the monitor to a CMDB asset — up/down transitions flip that asset's status automatically (which your status page reflects). 5. Set "Open after N failed checks" to avoid flapping, and choose an Impact level. 6. To fully automate outage comms, check "Auto-declare public incident": a failed check opens a public incident and emails confirmed subscribers, then resolves itself the moment the monitor recovers — one incident per outage, never a duplicate.

Question 32

How to declare and update a public incident

Accepted Answer

Keep customers informed with a public timeline — investigating, identified, monitoring, resolved. 1. Go to Admin → "Public status page" and under Incidents click + Declare incident. 2. Enter a Title (e.g. "Auth service degraded"), pick the Impact and Affected assets (affected assets are posted to degraded automatically), set the Initial status, and write the initial public update (Markdown OK). Click Declare. 3. As things progress, click Post update on the incident, pick the new Status (investigating / identified / monitoring / resolved), and write the update body. 4. Each incident gets a stable permalink (/status/your-slug/incidents/:id) with its full timeline — the same link subscribers receive by email. 5. After resolution, add a Postmortem from the same page: a root-cause retrospective that renders below the public timeline.

Question 33

How to schedule a maintenance window

Accepted Answer

Give customers a calm heads-up before planned downtime instead of a red alert during it. 1. Go to Admin → "Public status page" and under Scheduled maintenance click + Schedule window. 2. Enter a Title (e.g. "Database upgrade — brief downtime"), the Starts and Ends times, and Details shown publicly (Markdown OK). 3. Click Schedule. The window appears on your status page as an "Upcoming" notice, flips to "In progress" during the window, then "Completed". 4. Maintenance never trips the failure posture banner and never changes any asset status — it reads as planned, because it is.

Question 34

How customers subscribe to status updates

Accepted Answer

Double opt-in email subscriptions keep customers informed on every incident — declare or update, they get the mail. 1. Customers enter their email in the Subscribe form on your public status page. 2. They receive a confirmation email and must click it before any updates are sent (double opt-in — no accidental spam). 3. Confirmed subscribers are emailed automatically whenever you declare or update an incident — including incidents auto-declared by uptime monitors — with the title, current status, update body, and a link to the incident permalink. 4. Every email includes a one-click unsubscribe link.

Question 35

How to import Sentry issues as tickets

Accepted Answer

A daily sync opens a Desk ticket for every unresolved Sentry issue that matches your filters — deduped across runs. 1. In the sidebar under Admin, click Sentry import. 2. Enter your Sentry base URL (https://sentry.io or self-hosted), organization slug, project slug, and a Sentry auth token. 3. Set the Minimum level (debug → fatal) and optionally an Environment filter (e.g. production). 4. Choose which ticket type imports are reported as and their Ticket priority, then save. 5. The sync runs daily; imported issues are tracked so re-runs never create duplicates. The Recent imports list shows what came in.

Question 36

How to link GitLab commits and MRs to tickets

Accepted Answer

Mention a ticket key in a commit or merge request and it links itself to the ticket — optionally resolving it on merge. 1. In the sidebar under Admin, click GitLab links and enable the integration. 2. Under Webhook setup, Copy the webhook URL and add it to your GitLab project (Settings → Webhooks) for push and merge-request events. 3. Choose which member internal notes are posted as. 4. From now on, any commit or MR that mentions a ticket key (REQ-101, INC-42) is linked to that ticket, with a system note recording the ref, title, author, and URL. 5. Optionally check "Auto-resolve tickets when a referencing merge request is merged" — the resolve runs through the same audited pipeline as a human resolve, webhooks and CSAT included.

Question 37

How to import contacts (from Hitt CRM or CSV)

Accepted Answer

Bulk-onboard your existing customers from the suite CRM or any CSV export. 1. In the sidebar under Manage, click Contacts. 2. Click "Import from CRM", search your Hitt CRM contacts, and pick the ones to bring over — names, emails, and companies come with them. 3. Or click Import CSV and upload a file with headers: name, email, phone, company, notes (quoted fields, commas in values, and multi-line cells are handled). 4. Imports dedupe on email, so re-importing the same file is safe. CSV batches are bounded to 500 rows with a per-row audit.

Question 38

How to send ticket events to other systems with webhooks

Accepted Answer

HMAC-signed POSTs push ticket events into team chat, on-call tools, automation platforms, or your own services. 1. In the sidebar under Admin, click Webhooks, then click New webhook. 2. Enter a Name and the destination URL (https only), then pick the Events to subscribe to: created, updated, replied, assigned, resolved, closed, snoozed. 3. Set Max attempts (1–10, with exponential backoff) and add any custom headers the target needs. 4. Click Create, then copy the Webhook signing secret — verify the X-Desk-Signature (HMAC-SHA256) header on your side. 5. Click Test fire to validate the wiring, then open Deliveries to see the result. The delivery log keeps status code, latency, error, and attempt count for the last 50 deliveries.

Question 39

How to create API tokens for programmatic access

Accepted Answer

Personal access tokens give scripts and CI jobs Bearer access to the whole Desk API — no password sharing. 1. In the sidebar under Admin, click API tokens, then click New token. 2. Name it after what will use it (e.g. "GitHub Actions deploy log"), pick a Scope (read-only, read-write, or admin), and optionally set an expiry. 3. Click Create, then "Copy to clipboard" — the hdsk_… token is shown once and stored SHA-256 hashed, so this is your only chance. 4. Use it as a Bearer token on any /api/desk/* endpoint. Each token tracks its last-used time, and you can revoke it anytime from the same page.

Question 40

How to invite teammates and set roles

Accepted Answer

Token-based invites with four roles — owner, admin, agent, viewer — and strict role-gated permissions. 1. In the sidebar under Admin, click Workspace and open the Members tab. 2. Click Invite member, enter their Email, and pick a Role. 3. Roles at a glance: Owner (everything, plus delete workspace and transfer ownership — exactly one per workspace), Admin (manage members, workflows, types, automations, SLAs, webhooks, tokens, status page, billing), Agent (work tickets they're assigned or that are unassigned), Viewer (read-only). 4. The invite link is single-use and expires; the invitee accepts it to join. 5. Change a member's role anytime from the Members table, or transfer ownership from the same page.

Question 41

How to start a trial and choose a plan

Accepted Answer

Every feature is available on every plan — plans differ only by seats. The 14-day trial unlocks everything, no card required. 1. Start from the Pricing page: the Free trial gives you 14 days of the full product. 2. When you're ready (or the trial ends), go to Billing in the sidebar under Admin and click "Choose a Plan". 3. Pick Pro or Business — both are honest per-seat pricing with everything included; nothing is feature-gated. 4. Complete checkout with your card. Invoices, card updates ("Update card"), and cancellation all live on the same Billing page. 5. Your data is never hostage: the Data export section gives you a full JSON workspace export anytime.

Question 42

How to apply a coupon at checkout

Accepted Answer

Coupon codes are entered on the checkout review step, before you reach payment. 1. Go to Billing → "Choose a Plan" and pick your plan to reach checkout. 2. On the review step, find the "Have a coupon?" field, enter your code, and apply it. 3. The discount is validated and shown before you pay. Then click "Continue to payment" and enter your card details. 4. Arrived from a link with ?coupon=CODE in the URL? The code is pre-filled and applied automatically — just review and continue.

How to get things done in Hitt Hosting Desk

Tickets & Shared Inbox

Types, Workflows & Custom Fields

Email, Chat & Auto-Replies

Automation & Productivity

SLAs & Business Hours

Knowledge Base & Customer Portal

CSAT & Reporting

Status Pages & Monitoring

Integrations & API

Team & Billing

Can't find what you need?