What your customers see
The support portal from a customer’s side: getting in, raising and following tickets, emails and help articles.
Your customers never see Projik’s staff app. They use a project’s support portal: a small site under your name, logo and colour, where they raise tickets, follow them and read help articles. This page walks through it from their side, so you can explain it to them.
A customer’s first visit to the portal
Video coming soon1:40
The portal’s address#
Each portal lives at its own address, built from the project’s code: support.projik.com/bms/ for the code BMS. Give customers that address, or let the invite email take them there.
There’s no list of portals anywhere. Someone who goes to the bare support.projik.com is told to ask their provider for their support link, and an address with no portal behind it says “This support portal isn’t available”.
Getting in#
Customers have no password. Every way in is a link sent to their email address, which works once and for 30 minutes.
- An invite. When you invite someone, they get an email in the project’s branding. The link signs them in, and a welcome card explains what the portal does.
- Signing in again. On the portal’s sign-in page they enter their email and choose Email me a sign-in link. At an invite-only portal the page shows the same “Check your email” message whatever address is typed, so it never reveals who is a customer.
- Signing up. At a portal you’ve set to Open, the same form says “Sign in or sign up”. Someone new gets a link that finishes signing them up. They appear on your Customers page, marked Signed up, only once they’ve used it.
If a link has expired or been used, the sign-in page says so and offers Email me a new link.
A customer with access to more than one portal gets a Your other support portals menu and moves between them without signing in again.
Raising a ticket#
Customers choose New ticket and fill in:
- Subject and Description. Both are required.
- Screenshots & files: dropped in, chosen, or pasted into the description. Images up to 10 MB, other files up to 25 MB.
- Category: Something isn’t working, Question / how do I…, Feature request, or Account & access.
- How urgent is it?: Low, Normal, High or Urgent. This becomes the ticket’s priority, which your team can change.
As they type the subject, up to three published help articles that match appear under These might help.
After Submit ticket they land on the ticket with its reference, such as SUP-0042.
Following a ticket#
My tickets lists a customer’s own tickets, with tabs for Open, Resolved & closed and All. Open tickets are grouped by who has the next move: Waiting on you first, then those with the support team.
Customers see your statuses in their own words:
| Your status | They see |
|---|---|
| New | Received |
| Open | Open |
| On hold | On hold |
| Waiting on customer | Waiting on you |
| Resolved | Resolved |
| Closed | Closed |
On a ticket they see their request, their own replies and your public replies, with any files attached to those. Your replies appear under the portal’s display name, not the name of the person who wrote them. Internal notes, the assignee, linked tasks and SLA deadlines are never sent to the portal.
From the ticket a customer can:
- Reply, with files if they want. Replying to a ticket that’s waiting on them, or resolved, reopens it for your team.
- Mark resolved, when it’s sorted for them. They can reopen it by replying.
- Close ticket, once it’s resolved. A closed ticket can be read but not replied to. If the problem comes back they open a new ticket and mention the old one.
- Turn Email me updates on or off for that ticket.
Emails#
| Sent when | |
|---|---|
| An invite, sign-in or sign-up link | They’re invited, or ask for a link. |
| “We’ve received your ticket” | A ticket is raised. |
| “Waiting on you” | Your team sets the ticket to Waiting on customer. |
| “Resolved” | Your team resolves the ticket. |
| A reply | Someone on your team chooses to email a reply. |
The three status emails have fixed wording and go out only while Automatic status emails is on for the project and Email me updates is on for the ticket. A reply your team chooses to email arrives either way. Replies aren’t emailed automatically, so a customer may need to check the portal to see one.
Every email carries your display name, logo and colour, and a button that opens the ticket in the portal. If they aren’t signed in, the portal asks them to sign in first. Replying to an email doesn’t reach your team: customers reply in the portal.
Help articles#
Once a project has published help articles, its portal gains a Help articles tab and opens on it. Customers can search the articles, browse them by category, and choose Raise a ticket from an article or an empty search, which starts a ticket with the subject filled in.
By default, articles are for signed-in customers of that project. An owner or admin can make them readable by anyone with the link in Settings › Knowledge. Signed-out visitors then see the articles with a Sign in button for tickets. See Help articles.
When access changes#
- Removed from a project, or the portal is turned off: the customer can’t use that portal. They can still read those tickets in another of your portals, if they have one.
- Blocked: they’re signed out everywhere and can’t ask for a new link.
- A ticket moved to another project: it stays in the customer’s list.