Skip to main content
Visit Freshworks.com Visit Freshworks

We created 3 portals:



  1. emailsignature.xink.io (soon to be discontinued)
  2. help.xink.io (agent login for internal use only)
  3. support@xink.io

I wonder if I misunderstood our setup as {{ticket.url}} field show help.xink.io where I would expect support.xink.io.

  • Is help.xink.io required? (It's intended agent internal use only)
  • Can agents just log in using support@xink.io?
  • How do we change so that {{ticket.url}} show support.xink.io links?




image



Hello Jesper, 


If you're supporting different segments of customers or running multiple brands, you can use different portals for your customers to login. For the agents, it's not going to make much of a difference since the agent side of the portal will not change based on the portal url. You can make the support.xink.io as the primary portal so that the links are constructed using this url.


Cheers!

Hello Aravind,


How do I change support.xink.io to be the primary portal?


Thanks

Jesper



Hello Jesper, 


Since you've already listed the support.xink.io as a product portal, I'm afraid it's not an easy switch to make it the primary portal. You might have to delete the existing portal and then add support.xink.io as the portal url for Xink Default Portal. Since you also have a custom SSL enabled for this url, we might have to see if we need to reset the settings at our end. 


Let me work on these scenarios and get back to you with the optimal solution.


Cheers!

Jesper,


The URL swap can be done with immediate effect but as I had already mentioned, the SSL certificate has to be re-uploaded to work for the new association. This means that the users visiting the portal will be seeing a security error for a maximum of 2 days.


Let me know how we can go about this.


Cheers!

Terms of Use