Confluence for Hubs

Important Pointers:

  • Hub-vise Space to be created as a part of Setup to Ops process
  • Under each space a standard template should be formed for hubs to replicate and use it in their day to day functioning
  • Specific pages include a parent page for all Meeting details (Standups, Weekly team meetings etc.), a section for all the projects in place. Taking ideas from our current PMW. Other sections include all vendor related details and other documentation required at the hub level.

[Extras]Documentation

Confluence as a Collaboration Tool

Support Ticketing for Members

Ops Support

PMW basics: What questions do we need to answer ? Assumptions ? Is it a must have or good to have ?

Suggestions box

Analysis and documentation done till date in PMW format

Tasks Table

Why did we shortlist Intercom for Hub-Support Interaction ?

Next Steps: Visualizing how Intercom will turn out if we implement this for members ? Use cases ? Possible scenarios and issues in place ? Having a proactive approach to this etc.

Intercom: Current scheme of things and how can we streamline it
using automation tools etc. ?

Daily Work log adding all day to day activities at one place

What Ops Support does ?

Recurring Payments Solution: Understand what needs to be done here.

Discussion Logs

Chatbot for Intercom Or Operator ? Makes Sense ?

Beverage Consumption Analysis

Confluence Information Architecture (IA) ?

Intercom Conversations Type Arcitechture

Step: 1 Building a conversations tree around Intercom that supports