Important to know in general:

Your MyCase integration will need to be connected to your Hona Org to get access to your MyCase fields in your Data Mapper, and you will need to have at least one Project Type before you can map the values of those fields to them.

The MyCase field mapped here will determine which Project Type your Client(s) are assigned when their Project is generated in Hona. Typically, most Businesses will map their Project Types to the following MyCase fields:

The MyCase field mapped here will determine what Phase your Client is assigned in their Project Type. Typically, Businesses will map their Phase Names to the following MyCase fields:

The MyCase field you map here is typically a custom field you create with an Onboarding Manager during Hona onboarding. If you decide to use a different field, keep in mind that you will need to take extra steps to make sure it is mapped correctly. The purpose of this field is to help you filter which cases get synced into Hona and notified, from the MyCase side of the integration. For more information on the functionality of this field and on how to configure it, please visit MyCase: Disabling Hona from a Single Case.

The MyCase field titled Practice Area is currently being mapped to the Hona field Project Type.

The MyCase field titled Case Stage is currently being mapped to the Hona field Phase Name.

**The values from both of these MyCase fields are displayed in the Data Mapper as well after you run the Case ID. Remember, these values are unique to the case whose ID which was run. The display of these values is just for verification that you chose the right field from MyCase, and it's not likely that you will use these values for any Project Type or Phase Name mapping in the Data Mapper. You will, however, be using these values later to directly map your Project Types (and Phases) in a different part of Hona. This is not the case for Hona Enabled, which you will map directly to a value in the Data Mapper (see visual again and read below).

The value for the MyCase custom field Hona Enabled is currently being mapped to the Hona field Hona Enabled.

No. Your Clients will not see the values you put here, and by default will not even see the Project Type Name configured at the top of these settings. They will only see the Project Type Name if you define that as Project Name in these same settings. By default, Project Name pulls from the Case name in MyCase, so this is what your Client's will see in their Client Portal unless you define otherwise.

If your Hona Project Type field in is mapped to the default Practice Area field in MyCase, you will see a drop-down of all available values from your MyCase Practice Area field. If you are using a different field for Project Type mapping (like a custom field), the values from that field are not likely to pull through for preview, so take extra caution to make sure they are typed the same as they are in MyCase.

No. Your Clients will not see the values you put here. They will see the Customer Facing Name, which can be configured at the top of the Phase. This allows you to name the Phase whatever makes most sense for your Clients without changing the values of their correlating field in MyCase.

If your Hona Phase Name field in is mapped to the default Case Stage field in MyCase, you will see a drop-down of all available values from your MyCase Case Stage field. If you are using a different field for Phase mapping (like a custom field or tasks), the values from that field are not likely to pull through for preview, so take extra caution to make sure they are typed the same as they are in MyCase.

In that case, you will map all of the values from the field you are mapping to Project Types. This will make it so if you want to create additional Project Types down the line, your Hona Org is already configured for filtering.

The Project Type a Client is assigned in Hona will determine their entire experience since this is the backbone for firing all notifications such as case updates, Drip Notifications, Birthday Messages, and access to Form requests, NPS Surveys, and other Client Portal features.

1) MyCase does not send task information during a manual sync, only during a whole account nightly sync. This means you will not be able to test successful syncing of your Project Types using task-based Phase progression without making a plan with your Onboarding Manager to do so. This is not the case for information synced for phase-based Phase progression.

2) Task-based Phase progression also makes internal staff implementation and long-term management of Hona a heavier lift since there will be more technical logic that needs to be understood by everyone at your firm, not just the person in charge of setting up Hona. With that being said, we typically recommend creating Case Stages or a custom field which correlates with your task flow instead of mapping your actual task data to your Data Mapper or Phases, unless your internal staff has a strong, well-understood task flow that is not edited regularly. Case Stages are more of a 1:1 feature with Hona Phases than tasks, which makes understanding their progression (and overall function) much more attainable with your staff in the short- and long-term.

There are only 2 values (Yes or No) for the Hona Enabled field in Hona, both of which are hard-coded into Hona so you don't need to define them like you do Project Type and Phase values. The values for Project Type and Phases are completely Business-dependent because they are determined by the fields which you have configured in your MyCase. If you were to use a MyCase field for Hona Enabled that is not the one you created with an Onboarding Manager, you will be required to define the values from that field which mean Yes and No in Hona since they will not be hard-coded by default.

Simply put: Hona gets all the case information it needs to create a Project and its correlating Contact(s). However, it doesn't have enough case information to trigger any notifications which aren't Phase-dependent, and the vast majority of automations in Hona are dependent on your Phases/their mapping. Not mapping your Phases will not prevent Project or Contact creation; however, it will decrease the value of Hona by misunderstanding its core purpose.

The primary purpose of creating/mapping your Phases is to enable your Client Portal and all of the features which are configured for your Clients there to help your Business. Without Phases, Hona features will need to be triggered manually every time you want to use one, and the features available to your Clients without a Case Tracker (which does not exist without Phases) will be overall less satisfactory and valuable. Automations, which bring your Business and Client experience immense value, depend on timing, and Phases are how we "time" or "pace" the notifications your Clients receive automatically, and what features they receive access to through those notifications.