Your first workspace, one working request at a time.

• Sign up. You land in your new workspace — no card is requested.
• It starts on the Free plan with a 30-day Pro trial, so five members and Pro features are available while you set up.

You’ll know it worked when you see the workspace’s ticket list, possibly empty.

• Pick the closest profile — MSP / IT Support, Internal Services / Operations, Marketing / Creative, Product Development, Finance / Procurement, or Custom / Mixed — and choose Continue.
• Change it later under Settings → General. Use Fine-tune this workspace to rename terms or switch modules.

You’ll know it worked when menus and labels use your profile’s words, and a starter request type exists.

• Every workspace gets a ready-to-use request address. Share it, or forward an existing shared inbox to it.
• To use your own mailbox address, add it as a channel and complete the verification and DNS steps shown.

You’ll know it worked when an email you send to the address appears as a new request.

• Open the starter type for your profile. Add the fields your team always asks for — Short text, Long text, Number, Date, Single select, Multi select, Checkbox, Email or Web address.
• Mark the answers you cannot work without as required.
• Under Conditional visibility, show a field only when an earlier choice matches — for example Material only when the deliverable is Print.

You’ll know it worked when the form preview shows only the questions that apply to each choice.

• Create a portal for an organization and choose its request types.
• In Branding & content, add your logo, colour and welcome text. In Request experience, choose Guided steps or All questions.
• In Access & defaults, decide who may submit: Anonymous, SSO (Microsoft or Google), Require SSO, and any allowed email domains.
• Optional: turn on a requested due date, and Schedule & alerts for busy-day warnings and reminders. Your own domain is under Domain & links (Pro).

You’ll know it worked when the portal opens at its address and shows your branding and form.

• Invite teammates as Admin, Technician or Viewer.
• On Pro, limit a member to specific clients, knowledge, portals or email channels.

You’ll know it worked when invited people can sign in and see the queue.

• Automatic analysis and categorisation are on. Set the confidence a category needs before it is applied.
• Leave automatic responses off while you learn how the suggestions read for your work.

You’ll know it worked when new requests show an analysis panel after they arrive.

• Submit a fictional request through the portal, as a requester would.
• Open it from the queue. Read the analysis, assign an owner and add an internal note.
• Send a reply and check it appears in the requester’s portal view. If a decision is needed, use Request approval.
• Resolve it. Under How was this resolved?, choose Save & Generate KB Article, then review the draft in the knowledge base.

You’ll know it worked when you have a resolved request, a reply the requester saw, and a knowledge-base draft.

• Start from a template such as Stale Ticket Reminder or Resolution Feedback Request.
• After it runs, open its execution history to see what happened and why.

You’ll know it worked when the rule shows recent executions with a result for each.