Support Center can't reach Brine Webs
What each Support Center connection message means, from a desk that isn't answering to a refused key or a project that isn't linked, and what to do about it.
- Applies to
- Support Center 1.1 and later
- Who can do this
- Administrator, Platform owner
- Permission
feature.sc. connection.edit
On this page
Symptom
Support Center shows a message instead of your tickets, or refuses to send a ticket or reply. Find the message below:
| Message | Go to |
|---|---|
| Brine Webs' support desk isn't answering, or Showing the figures from … | 1 |
| Connect Support Center to Brine Webs, or Support Center isn't connected to Brine Webs yet. | 2 |
| The support desk refused this installation's key | 3 |
| Not linked to a project yet | 4 |
| Brine Webs has your email address on another account, or has switched it off. | 5 |
| The support desk has no department for customer tickets yet. | 6 |
| Brine Webs' support desk doesn't accept audio files yet. | 7 |
| You can't raise support tickets or You can't see support tickets | 8 |
Tip: Your tickets are kept at Brine Webs, not in your Laramin. None of these problems loses a ticket.
Check these, in order
1. The desk isn't answering
Support Center couldn't get an answer from Brine Webs' desk. The screens keep showing what the desk last said, with its age, for up to a day. New tickets and replies are paused, and their buttons say why. Fix: wait a moment and select Retry. If it lasts, open the Connection panel and check that Desk address is right. If the address answers but isn't Brine Webs' desk, the panel says That address answered, but it isn't Brine Webs' support desk. Check the address.
2. Support Center isn't connected
Nobody has saved a desk address and key yet. Fix: connect your Laramin to Brine Webs support. If you can't change the connection, the screen says to ask an administrator.
3. The key was refused
The desk didn't accept the saved key. The message says which case it is:
- This is an admin key, not a customer key. Fix: ask Brine Webs for your company's customer key.
- Brine Webs doesn't recognise this key. It may have been mistyped, expired or revoked. Fix: copy it again from Brine Webs, or ask them for a new one. Then paste it into Customer API key and select Save changes.
4. The key isn't linked to a project
The key works, but Brine Webs hasn't linked it to your project yet, so there are no tickets to show. Only Brine Webs can fix this. Fix: ask them to link the key to your project, then select Check again.
5. Your email address is on another account at Brine Webs
You write tickets in your own name, using your email address. If Brine Webs already has that address on another customer's account, or has switched it off, your ticket or reply isn't sent. Fix: ask Brine Webs to add you to your company's account.
6. No department for customer tickets
Select Check the connection in the Connection panel. If it says The support desk has no department for customer tickets yet, Brine Webs needs to set one up. Fix: ask Brine Webs.
7. Voice notes are refused
Recording works, but the desk refuses the file. Fix: ask Brine Webs to allow .webm and .m4a attachments. Until then, attach a screenshot or describe the problem in writing. If the message is Microphone access was blocked, allow the microphone for your Laramin in your browser's site settings, then record again.
8. A permission is missing
Each Support Center action has its own permission. For example, raising a ticket needs feature. and seeing the list needs feature.. The full list is in How support tickets work. Fix: someone who manages roles adds the permission to your role. See Change or delete a role.
The "You can't…" messages name the permission in words, such as "Create support tickets" or "View support tickets". In the role editor, these are the Create, List and View actions on the Support ticket row, and replying is Reply among that row's extra actions.
Still not working?
If Support Center can't reach Brine Webs at all, contact Brine Webs another way, for example by email. Include this page's link and the exact message you see.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.laramin.in. The online article may have changed since.