Team:Infodesk/Planning

Before Save the Date

• Initial website (wiki) (with: communication; design)
• team mailinglist
• team roles, tasks, and planning
• Social media:
  • Claiming channels
  • Redirecting to wiki
  • sporadic announcement
  • responding to replies on social media
• Responding to 'outside' questions (mail, social media): answering known questions, redirecting when needed

• team filestorage
• wiki information architecture (with infra, communication, ?)

Before ticketsales (2017-01-01?)

• Wiki:
  • FAQ
  • Dates
  • Information about volunteering
  • Information on how to get there
• Social media
  • 'branding' (logo etc.)
  • policy (with communication)
• helpdesk ticketing system (Linux trackers)
  • Knowledge system (FAQ, including standard customisable replies to frequently sent requests like visa)
  • Escalation system
• team IRC channel
• wiki usage tracking (Piwik, Google search console)

Before event

• Booklets (with communication; design)
• Physical infodesk
• Full FAQ

At event

• • Routing visitors to Tickets
  • Routing volunteers to Volunteers
  • Routing press to PR/communications
  • Assemble a knowledgebase (based on questions and presumed questions)Event:
• Routing people, welcoming them, handing out booklets (with Ticket?)
• trying to accommodate simple needs (who accommodates more complex needs?)