Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3483 Ideas

    Improved Table of Contents FormattingSubmitted

    The problem: The auto-generated table of contents in Help Center articles renders every entry identically — one font, one size, one color, no indentation. H1 and H2 headings appear as a flat list, so readers can't see the structure of the article at a glance. In long articles (exactly where a table of contents matters most), a flat list of a dozen identical entries is hard to scan and defeats the purpose of having a TOC.The request: Add visual hierarchy to the table of contents so heading levels are distinguishable. The standard treatment would be some combination of:1. Indentation — nest H2 entries under their parent H1, the way most documentation sites do.2. Size and weight — e.g., H1 entries in bold 16pt, H2 entries in regular 14pt.3. Color — e.g., H1 entries in the primary text color, H2 entries in a secondary gray.(Example attached showing the kind of differentiation we mean.)Even just automatic indentation by heading level — with no configuration options at all — would solve most of the problem. Configurable styles per level would be the ideal version.This applies wherever the TOC renders: both the Help Center on the web and in the Messenger. Since the TOC is already generated automatically from H1/H2 headings, the structural information exists — it just isn't reflected visually.The payoff: readers can see article structure instantly, jump to the right section faster, and self-serve more successfully on long articles. Thanks for considering!  

    maryddNew Participant

    Do not automatically update statuses for phone callsSubmitted

    At the moment the behavior of phone calls on Intercom do the following:When an agent picks up a call, it automatically sets their status to offline if they are online (this affects both phone calls and chats). When an agent hangs up a call or a live call is disconnected, it automatically sets their status to online (regardless if they were online or offline before the call). For 1, this causes major issues with our chat automations/assignments/etc. If someone picks up a call, it sets them to offline and the agent is not assigned new chats. If they have ongoing chats, it may cause an automatic offline message to be sent to the user. We’ve been told by Intercom that this is by design so as to avoid agents from getting overwhelmed. It is not feasible or scalable for teams to only take one call or chat at a time, and most teams do not operate this way anyways. For our team it just means more stress as they often have to manually toggle themselves to online once they pick up a call. For 2, if someone who is offline makes a one-off call, they often do not remember that they will automatically be set to online after making the call, which causes them to accidentally be online and therefore unintentional longer wait times for users calling in.In summary:active chats may receive offline responses and delayed handling. qualified agents are removed from chat queues while on calls. agents forget they’ll be set online after an outbound call, leading to unwanted availability. agents must manually toggle status repeatedly to work across channels.Suggestions:A classic setup would look like: agent sets themselves to online, which allows them to receive calls and chats. Only 1 call per agent at a time, the number of live chats one can be assigned (i.e. conversations not in closed or snoozed status) can be customized or set at a team or individual agent level. (see attached logic diagram proposal)