Skip to the page

DocsSupport desk

DocsSupport desk

Set up a support portal

Give a project a portal address, choose who can sign in, brand it, and name who triages its tickets.

Team plan and aboveFor owners and admins

A support portal is where a project’s customers sign in to raise and follow tickets. Each project has its own, at its own address, and you choose whether only the people you invite can use it or anyone can sign up.

Open the project, choose Settings in its header, then Support portal. Owners and admins change these settings. Support agents see the same screen read-only. On an archived project the settings are frozen.

Everything on the page except the logo is a draft until you choose Save changes. Discard puts it back. The Live preview beside the form shows the portal’s sign-in card with your unsaved values, at Desktop or Phone size.

Turn on a project’s support portal

Turn the portal on#

  1. Under Project code, type a code. It becomes the portal’s address, so it’s unique across all of Projik. The line under the box says Available, Taken or Reserved word as you type.
  2. Under Support portal, switch the portal on. It starts as Invite only.
  3. Under Routing & email, choose a Triage owner. A portal that’s on must have one.
  4. Choose Save changes.

The Portal address is then live. Copy it to share with customers, or Open it to see the portal yourself.

The project code#

A code is 2 to 10 letters and digits and starts with a letter. It’s shown in capitals, and the address uses lower case: the code BMS gives support.projik.com/bms/. When the box is empty, Projik suggests one from the project’s name.

You can change a code later. Old links keep working and send people to the new address, and the old code stays reserved for this project, so nobody else can take it.

Who can sign in#

ChoiceWhat it means
Invite onlyOnly customers you invite. Recommended.
OpenAnyone can sign up with their email address.
OffNo portal, no new tickets.

At an Open portal, anyone with the address can sign up and raise tickets, and your team can add a customer while raising a ticket for them without inviting them first. They confirm their email address first, then appear in Customers marked Signed up, where you can block them. Help articles that are for signed-in customers can be read by anyone who signs up.

Switching from Open back to Invite only stops sign-ups straight away, including ones where the link was emailed but not yet used. Customers who already have access keep it.

Use your own domain#

The portal can run on your own subdomain, such as support.yourcompany.com, instead of support.projik.com/{code}/. Customers then see your address in the browser and in every email: sign-in links, invitations, replies and status emails. It’s on the Team plan and above, and needs the portal on.

  1. Under Custom domain, type the subdomain and choose Connect.
  2. The section shows two records to add at your DNS provider (where your domain’s DNS is managed): a CNAME that sends the domain to Projik, and a TXT that shows the domain is yours. Add each with the Type, Name and Value it shows. Copy copies a value.
  3. Wait. Projik checks every minute, and once both records reach it, it sets up the secure certificate. DNS changes can take a few hours to reach everyone. Check now checks straight away.

When the domain is Live, the section says since when, and the Portal address above notes that it forwards there: old support.projik.com links and bookmarks still work, and land on your domain. Customers sign in once more the first time they use it.

Only a subdomain works, because your main domain (yourcompany.com) can’t hold this kind of record. Emails still come from Projik’s sending address.

What it saysWhat to do
WaitingAdd both records, or wait for them to reach everyone. The message under the records says which one Projik is still waiting for. If it’s still waiting after a day, check each record’s name and value at your DNS provider.
Stopped workingThe CNAME no longer points at Projik, so emails link to the Projik address again. Put the records back and the domain comes back by itself. After 7 days it’s taken off and has to be connected again.
The domain didn’t go live within 72 hoursIt was removed so you can fix the records and connect it again.

Owners and admins hear in the bell when a domain goes live, stops working or doesn’t go live, and get an email when it stops working.

To stop using it, choose Remove domain. The portal goes back to its Projik address, links in emails already sent to your domain stop working, and customers sign in again. Turning the portal Off removes the domain too.

Branding#

Customers see these on the sign-in page, in the portal and in emails. Leave any of them blank to use the default.

  • Display name: up to 60 characters. Defaults to the project’s name.
  • Email sender name: the “From” name on emails. Defaults to the display name.
  • Logo: PNG, JPEG or WebP, up to 1 MB. Square works best. SVG isn’t accepted. The logo uploads, and Remove takes it away, as soon as you choose, without waiting for Save changes.
  • Intro: plain text, up to 280 characters, shown under the logo on the sign-in page.
  • Brand colour: a hex colour such as #0F766E, used for the header and buttons. Buttons carry white text, so the colour has to be dark enough to read against. If it isn’t, the page tells you, and the portal uses Projik’s blue for buttons and keeps your colour for the header line.

Routing and email#

  • Triage owner: new tickets from this portal are assigned to this person. They hear about each one by email, in the bell and on My Work. If they’re suspended or removed from the workspace, new tickets arrive unassigned until you choose someone else.
  • Dev tasks go to: the project where Create dev task on a ticket puts new tasks. It starts as this project. See Turn a ticket into a task.
  • Support email address: optional, on the Business plan. A shared inbox that’s also emailed about every new ticket. The email names the ticket, the customer and who has it, never the customer’s message.
  • Automatic status emails: on by default. Customers get “We’ve received your ticket”, “Waiting on you” and “Resolved”. These contain no staff-written text, and customers can turn them off on each ticket. Replies are never emailed automatically.

Service levels#

At the bottom of the page, Service levels sets this project’s reply and resolution targets. Choose Use the workspace SLA or Set this project’s own. See SLAs.

Limits by plan#

PlanSupport portals
FreeNone
TeamOne
Business and EnterpriseNo limit

The limit counts portals that are on, across the workspace. Turning on one more than your plan allows is refused with a message naming the limit. A portal that’s already on stays on if your plan changes. A support email address that’s already set also stays.

    Type to search every page. ↑ ↓ to move, Enter to open.