Guidelines around favicon usage

[tonge495]

Hi Paste team,

Are there any standards around when we should be using a custom favicon for certain sites vs just using the default Twilio logo? Asking as our team is unsure if we need to be using a custom favicon for One Support Center, which is not technically a product, but is a bit separate from Console.

Here are some examples of favicons that we've seen, though these are different products:

Any help would be much appreciated, thank you!

[TwilioPasteBot]

Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary.

---

Sorry, I don't know how to help with that.

I did do a search though, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:

• Business icon use example (updated: 07/31/2023, similarity score: 87%)
• Business icon use example - Answer (updated: 07/31/2023, similarity score: 86%)
• Task icon (updated: 10/05/2023, similarity score: 85%)

[dosubot[bot]]

🤖

Thanks for reaching out with your question about favicon usage in the Paste design system. Unfortunately, I wasn't able to find specific guidelines around favicon usage within the Paste repository.

To better assist you, could you provide more context or any specific requirements your team has for the favicon? For instance, are there any branding guidelines or specific design elements that your team is considering for the One Support Center favicon?

Also, if there are any discussions or decisions that have been made previously within your team regarding favicon usage, that information could be helpful as well.

Looking forward to your response.

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[SiTaggart]

Hi @tonge495

This is somewhat brand related, not necessarily design systems, but I'll outline what I think should be the approach.

To start with the examples you provided are essentially sub brands, and have their own identities within the Twilio brand collection. I can't recall seeing Authy in the new brand guidelines though, maybe it is, but it's extra special as it's a stand alone product almost entirely, as a consumer product.

Ultimately, I think the favicon for a given property/application should reflect the sub brand it belongs to. So the comms console will be switching to the new twilio comms logo, SendGrid things should use the SendGrid logo (like in your example), and segment things should switch to the new segment logo.

For applications that are marketed as products and stand alone, like Authy and the Flex client application, I'd use the product logo as provided by marketing and brand.

For everything else, things that span across all sub brands and are broad to the entire company, or are just internal tools, just use the Twilio logo.

[tonge495]

Makes sense, thanks Simon!

Do you know what the new Twilio comms logo is or when it's expected to be released? Are we still using the old Twilio logo moving forward or is everything going to be changed to the new logo? I don't think I've personally seen any examples of it.