This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Response and Process
Rebekah-Hernandez edited this page Feb 26, 2020
·
3 revisions
The majority of customer service issues will be submitted to us through an email inquiry or a ServiceNow request. In both cases we will want to respond to the customer as quickly as possible and let them know that we are looking into their issue. If we can resolve the issue in one email, we by all means want to do so. If the incident was submitted through an email request only, with no accompanying ServiceNow ticket, you will want to create a ServiceNow ticket for tracking purposes. In all other cases please use the following process as a guide:
- If their issue is one that we cover in the Common Issues, send them the appropriate email template with edits as needed. Otherwise, reply to the customer’s inquiry with an initial response informing them that we are working to resolve their issue.
- If you can resolve their issue one response, please do so.
- Otherwise, ask any necessary follow-up questions to fully understand their needs.
- If you cannot resolve the issue with your knowledge, be sure to reach out to someone on your team who may know.
- If the issue is new and specific to the user experience or function of the program, create a "New Issue" story for the Platform Board and tag a team member with the ability to solve the problem or who would themselves assign someone who can.
- Make sure to thoroughly track all actions taken on a given issue. Each ServiceNow ticket will be saved as an artifact.
- If necessary, confirm the customer’s satisfaction after the issue has been resolved and encourage them to submit a feedback using the Open Forest feedback tool.
How we work
- Overview
- Onboarding Checklist
- Roles
- Agile Principles
- Skill area heuristics
- Open Forest design system
- Updating Christmas tree content
- Pilot customer response process
- POSS to FLREA Tracking
- Sprint Research Process
- Annual gap analysis process
- Manual accessibility testing process
- Feedback Tool
- Contracting and Task order Information
Technical Information
Past efforts
User Research
- Discovery Research
- Entry points to ePermit (June 2017)
- FLREA discovery sprint (July 2017)
- Law Enforcement Officer discovery sprint findings (December 2017)
- Naming the Open Forest platform
- GitHub repo research brief
- Usability Testing - for Christmas Trees
- Usability Testing - Special Uses (Non-Commercial and Outfitters modules)
- Research Plan - Update Sprint Number (Issue 489)
- Research Plan - Special Use permits evaluation content (June 2019)
- Usability Testing - Special Use permits evaluation content (June 2019)
- Research Plan - Manage User Access (Fall/Winter 2019)
Support
Support Manual
Support Guide for Frontline Staff
- Intro
- Why isn't something working?
- Where do I go to gather my firewood?
- I cannot print my permit.
- I don’t understand how to navigate through Open Forest, or how to purchase my permit online.
- I do not know how to gather firewood.
- I don’t want to purchase my permit online.
- I am not sure about the process to purchase online.
- Pay.gov looks different, is this a real site?
- What am I supposed to do with my permit once it is printed?
- I want to share my experience using Open Forest.