Support Center Icons

[HartiganHM]

Hey, all!

We're currently in the process of migrating the Twilio Support application over to the Console monorepo and need some new icons. The ones that are currently being used are from an old @twiliointernal dependency which we'd love to deprecate. The icons we need are in this screenshot for reference and are listed below.

I know that previously icon requests were on pause as Paste stability was being prioritized, so if there's anyway to get approval on these icons and then receive an SVG that we can use in our app directly (similar to a previous icon request I made) that would really help us expedite our migration.

Please let me know if you have any questions and thanks for the help!

---

Support screenshot

Help documentation icon

• Type: UI Icon
• Option 1
• Option 2

Ticket history icon

• Type: UI Icon
• Option 1
• Option 2

Submit ticket icon

• Type: UI Icon
• Option 1
• Option 2

Community icon

• Type: UI Icon
• Option 1

[serifluous]

Thanks, @HartiganHM ! We're actually working on getting some icons in our current release (including BusinessIcon), so I'll let you know when these are available in Paste, likely over the next 2 weeks.

For the ticket history icon, would the HistoryIcon we have already work for you? https://paste.twilio.design/components/icons

And for the community icon, we already have that glyph representing "users" in the admin center and "teams" in Flex. I'll take a look through Streamline and see if there's another glyph that can work and run it by you. See below

[serifluous]

Sure! The money icon is actually our Billing Icon in Console, which I think could be ok in this case, even if one of the plans are free.

If you do want to use another icon, though, feel free to take a look through Streamline: https://www.streamlinehq.com/icons/streamline-regular and let us know if there are icons that you feel like would work here (similar to how Hugh linked to a few options in the original post).

[tonge495]

Oh got it! Do you happen to know where else the Billing Icon is used on Console (I unfortunately don't have access, so am unable to check myself at the moment). I think if this icon is consistent with how it's used in other parts of Console, let's just keep the Billing Icon for now. Probably not worth introducing a new icon if it's already being used elsewhere for a similar purpose.

[serifluous]

For sure! It's mainly being used in the sidebar in the Billing section of the Console, and on overview pages for different products to link off to marketing and pricing pages. The links in the screenshot below link off to these 2 pages, as an example: https://www.twilio.com/live and https://www.twilio.com/sms/pricing/us

[tonge495]

OK, I think in that case I think the existing usage is close enough that we can just use the Billing Icon then, especially since the pricing screenshot on the 2nd screenshot also includes 'free plans.' I'm good with this.

Thank you for checking for me!

[serifluous]

Awesome, thanks! I'll follow up here once we've got all the new icons in Paste.

[SiTaggart]

Hi folks

A big icon drop just landed in Figma and NPM which should cover all these use cases. Documentation and Community as an example are now available. Let us know if we missed any.

[HartiganHM]

Looks good on my end, thanks all!

[tonge495]

Thanks everyone!

[HartiganHM]

Hey, @SiTaggart, quick check here, just to see if it's on my end or a Paste update. I've updated to 9.1.0 which has all of the icons, but I'm also getting some TS errors that all icons now require a disabled prop. We may have missed when this was introduced, but I also don't see it as a required prop in the docs, so I wanted to see what the gap might be here.

Thanks!

[HartiganHM]

UPDATE

Leaving this for posterity, but it looks like this was just a TS inconsistency and all icons are requiring disabled.

---

New little find, just to provide some more evidence, this seems to only happen with some icons. In this screenshot, the AgentIcon won't accept disabled as a prop whereas the CommunityIcon requires it.

[SiTaggart]

To round out this thread, offline we discovered it was a problem with Core being on v10, and needing to be on v15 for this type bug to disappear.