Create Activity follow-ups for Agent, Carrier, Group, or Individual records in AgencyBloc when something happens in third-party apps, such as CRMs. Choose what information is sent to AgencyBloc in the fields below.

In AgencyBloc, Activities can be associated with (i.e., attached to) Agent, Carrier, Group, and Individual records. For a Zap to create Activities, you must:

1. Specify the record type
2. Map to record IDs in a third-party app

Every Activity created must be associated with an Agent, Carrier Group, or Individual record in AgencyBloc. Option 1: Choose a record type from the list. This will be the record type for every Activity created. Option 2: Map to record type values in a third-party app. They must be formatted as "agent," "carrier," "group," or "individual." This allows you to associate every Activity created with a different type of record.

Option 1: Map to the ID numbers of Agent, Carrier, Group, and Individual records in a third-party app. This allows you to associate every Activity created with different records in AgencyBloc. Option 2: Provide the ID number of an Agent, Carrier, Group, or Individual record in AgencyBloc. Every Activity created will be associated with the same record.

Option 1: Map to text values in a third-party app. This allows you to set a different subject for every Activity created. Option 2: Provide a default text value. This will set the same subject for every Activity created.

Option 1: Map to text values in a third-party app. This allows you to set different notes for every Activity created. Option 2: Provide a default text value. This will set the same notes for every Activity created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Activity Status field options in AgencyBloc. This allows you to set a different status for every Activity created. Option 2: Provide a default text value. It must match exactly with an existing Activity Status field option in AgencyBloc. This will set the same status for every Activity created.

Option 3: Every Activity Status field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different status for every Activity created. Option 4: Choose a default value from the list. This will set the same status for every Activity created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Activity Type field options in AgencyBloc. This allows you to set a different type for every Activity created. Option 2: Provide a default text value. It must match exactly with an existing Activity Type field option in AgencyBloc. This will set the same type for every Activity created.

Option 3: Every Activity Type field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different type for every Activity created. Option 4: Choose a default value from the list. This will set the same type for every Activity created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Activity Priority field options in AgencyBloc. This allows you to set a different priority for every Activity created. Option 2: Provide a default text value. It must match exactly with an existing Activity Priority field option in AgencyBloc. This will set the same priority for every Activity created.

Option 3: Every Activity Priority field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different priority for every Activity created. Option 4: Choose a default value from the list. This will set the same priority for every Activity created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Activity Method field options in AgencyBloc. This allows you to set a different method for every Activity created. Option 2: Provide a default text value. It must match exactly with an existing Activity Method field option in AgencyBloc. This will set the same method for every Activity created.

Option 3: Every Activity Method field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different method for every Activity created. Option 4: Choose a default value from the list. This will set the same method for every Activity created.

Option 1: Map to date values in a third-party app. This allows you to set a different activity date for every Activity created. Option 2: Provide a default date value. This will set the same activity date for every Activity created.

Option 1: Map to date values in a third-party app. This allows you to set a different follow-up date for every Activity created. Option 2: Provide a default date value. This will set the same follow-up date for every Activity created.

Option 1: Map to "True" and "False" values in a third-party app. This allows you to set the follow-up duration differently for every Activity created. Option 2: Choose a default "Yes" or "No" value from the list. The follow-up duration for every Activity created will be all day or no depending on your choice.

Option 1: Map to date & time values in a third-party app. Learn how to format the values. This allows you to set a different start date & time for every Activity created. Option 2: Provide a default date & time value. This will set the same start date & time for every Activity created.

Option 1: Map to date & time values in a third-party app. Learn how to format the values. This allows you to set a different end date & time for every Activity created. Option 2: Provide a default date & time value. This will set the same end date & time for every Activity created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing AgencyBloc User by first name. If a match is found, we'll assign it as the follow-up user. To improve matching accuracy, provide the "Follow-up User - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing AgencyBloc User by last name. If a match is found, we'll assign it as the follow-up user. To improve matching accuracy, provide the "Follow-up User - First Name."

Option 2: Map to the ID numbers of AgencyBloc Users in a third-party app. This allows you to assign a different follow-up user to every Activity created. Option 3: Provide the ID for a specific AgencyBloc User. This will assign the same follow-up user for every Activity created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing AgencyBloc Team. If a match is found, we'll assign it as the follow-up team.

Option 2: Map to the ID numbers of AgencyBloc Users in a third-party app. This allows you to assign a different follow-up user to every Activity created. Option 3: Provide the ID for a specific AgencyBloc User. This will assign the same follow-up user for every Activity created.

Option 1: Map to the ID numbers of Activities in a third-party app. This allows you to append changes to existing Activities in AgencyBloc. Option 2: Provide the ID for a specific Activity. Every Activity created will be appended as a change to its thread.

Attach up to 5 files from Zapier directly in the fields below. Learn how to attach files from 3rd party resources.

Please note, the files must have an accepted file type to attach to the Activity in AgencyBloc. See accepted file types.

If you are attaching files directly from a 3rd party host, provide a filename in the first field and corresponding URL in the second field where the file can be downloaded from.

Example File Name: SampleFile.txt

Example URL: https://www.yourstorageprovider.com/files/SampleFile.txt

Please note, the files must have an accepted file type to attach to the Activity in AgencyBloc. See accepted file types.

Create Individual records in AgencyBloc when something happens in third-party apps, such as lead forms, enrollment platforms, and CRMs. Choose what information is sent to AgencyBloc in the fields below.

Option 1: Map to name values in a third-party app. This allows you to set a different first name for every Individual created. Option 2: Provide a default name value. This will set the same first name for every Individual created.

Option 1: Map to name values in a third-party app. This allows you to set a different last name for every Individual created. Option 2: Provide a default name value. This will set the same last name for every Individual created.

Option 1: Map to name values in a third-party app. This allows you to set a different middle name for every Individual created. Option 2: Provide a default name value. This will set the same middle name for every Individual created.

Option 1: Map to name values in a third-party app. This allows you to set a different nickname for every Individual created. Option 2: Provide a default name value. This will set the same nickname for every Individual created.

Option 1: Map to text values in a third-party app. This allows you to set a different title for every Individual created. Option 2: Provide a default text value. This will set the title same for every Individual created.

Option 1: Map to date values in a third-party app. This allows you to set a different date of birth for every Individual created. Option 2: Provide a default date value. This will set the same date of birth for every Individual created.

Option 1: Map to "M" and "F" values in a third-party app. This allows you to set the gender differently for every Individual created. Option 2: Choose a default value from the list. This will set the same gender for every Individual created.

Option 1: Map to SSN values in a third-party app. This allows you to set a different SSN for every Individual created. Option 2: Provide a default SSN value. This will set the same SSN for every Individual created.

Option 1: Map to DLN values in a third-party app. This allows you to set a different DLN for every Individual created. Option 2: Provide a default DLN value. This will set the same DLN for every Individual created.

Option 1: Map to date values in a third-party app. This allows you to set a different deceased date for every Individual created. Option 2: Provide a default date value. This will set the same deceased date for every Individual created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Individual Type field options in AgencyBloc. This allows you to set a different type for every Individual created. Option 2: Provide a default text value. It must match exactly with an existing Individual Type field option in AgencyBloc. This will set the same type for every Individual created.

Option 3: Every Individual Type field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different type for every Individual created. Option 4: Choose a default value from the list. This will set the same type for every Individual created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Individual Status field options in AgencyBloc. This allows you to set a different status for every Individual created. Option 2: Provide a default text value. It must match exactly with an existing Individual Status field option in AgencyBloc. This will set the same status for every Individual created.

Option 3: Every Individual Status field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different status for every Individual created. Option 4: Choose a default value from the list. This will set the same status for every Individual created.

Option 1: Map to MBI values in a third-party app. This allows you to set a different MBI for every Individual created. Option 2: Provide a default MBI value. This will set the same MBI for every Individual created.

Option 1: Map to date values in a third-party app. This allows you to set a different Medicare Effective Date Part A for every Individual created. Option 2: Provide a default date value. This will set the same Medicare Effective Date Part A for every Individual created.

Option 1: Map to date values in a third-party app. This allows you to set a different Medicare Effective Date Part B for every Individual created. Option 2: Provide a default date value. This will set the same Medicare Effective Date Part B for every Individual created.

Option 1: Map to "Yes" and "No" values in a third-party app. This allows you to set a different smoker status for every Individual created. Option 2: Choose a default value from the list. This will set the same smoker status for every Individual created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as the servicing agent. To improve matching accuracy, provide the "Servicing Agent - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as the servicing agent. To improve matching accuracy, provide the "Servicing Agent - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as the servicing agent. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different servicing agent for every Individual created. Option 3: Provide the ID for a specific Agent record. This will be the servicing agent for every Individual created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 1. To improve matching accuracy, provide the "Additional Agent 1 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 1. To improve matching accuracy, provide the "Additional Agent 1 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 1. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 1 for every Individual created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 1 for every Individual created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 2. To improve matching accuracy, provide the "Additional Agent 2 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 2. To improve matching accuracy, provide the "Additional Agent 2 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 2. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 2 for every Individual created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 2 for every Individual created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 3. To improve matching accuracy, provide the "Additional Agent 3 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 3. To improve matching accuracy, provide the "Additional Agent 3 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 3. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 3 for every Individual created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 3 for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different home phone number for every Individual created. Option 2: Provide a default number value. This will set the same home phone number for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different home phone extension for every Individual created. Option 2: Provide a default number value. This will set the same home phone extension for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different business phone number for every Individual created. Option 2: Provide a default number value. This will set the same business phone number for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different business phone extension for every Individual created. Option 2: Provide a default number value. This will set the same business phone extension for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different cell phone number for every Individual created. Option 2: Provide a default number value. This will set the same cell phone number for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different cell phone extension for every Individual created. Option 2: Provide a default number value. This will set the same cell phone extension for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different fax number for every Individual created. Option 2: Provide a default number value. This will set the same fax number for every Individual created.

Option 1: Map to number values in a third-party app. This allows you to set a different fax extension for every Individual created. Option 2: Provide a default number value. This will set the same fax extension for every Individual created.

Required to add address information. Option 1: Map to text values in a third-party app. They must match exactly with existing Address Type field options in AgencyBloc. This allows you to set a different address type for every Individual created. Option 2: Provide a default text value. It must match exactly with an existing Address Type field option in AgencyBloc. This will set the same address type for every Individual created.

Option 1: Map to "True" and "False" values in a third-party app. This allows you to set the primary address differently for every Individual created. Option 2: Choose a default value from the list. This will set the primary address the same for every Individual created.

Option 1: Map to address values in a third-party app. This allows you to set a different address street 1 for every Individual created. Option 2: Provide a default address value. This will set address street 1 the same for every Individual created.

Option 1: Map to address values in a third-party app. This allows you to set a different address street 2 for every Individual created. Option 2: Provide a default address value. This will set address street 2 the same for every Individual created.

Option 1: Map to city values in a third-party app. This allows you to set a different city for every Individual created. Option 2: Provide a default city value. This will set the same city for every Individual created.

Option 1: Map to county values in a third-party app. They must match exactly with existing County values in AgencyBloc. This allows you to set a different county for every Individual created. Option 2: Provide a default county value. It must match exactly with an existing county in AgencyBloc. This will set the same county for every Individual created.

Option 1: Map to State values in a third-party app. They must be formatted as two letters (ex. AZ for Arizona) and be real U.S. States or Territories or Provinces. This allows you to set a different State/Province for every Individual created. Option 2: Provide a default State/Province value. It must be formatted as two letters (ex. AZ for Arizona) and be a real U.S. State or Territory or Province. This will set the same State/Province for every Individual created.

Option 1: Map to valid zip code values in a third-party app. This allows you to set a different zip code for every Individual created. Option 2: Provide a default valid zip code value. This will set the same zip code for every Individual created.

Option 1: Map to valid email address values in a third-party app. This allows you to set a different email address for every Individual created. Option 2: Provide a default email address value. This will set the same email address for every Individual created.

Option 1: Map to valid email address values in a third-party app. This allows you to set a different secondary email address for every Individual created. Option 2: Provide a default email address value. This will set the same secondary email address for every Individual created.

Option 1: Map to "True" and "False" values in a third-party app. This allows you to set the email opt-out differently for every Individual created. Option 2: Choose a default value from the list. This will be set the email opt-out the same for every Individual created.

Option 1: Map to date values in a third-party app. This allows you to set a different lead date for every Individual created. Option 2: Provide a default date value. This will set the same lead date for every Individual created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Lead Source field options in AgencyBloc. This allows you to set a different lead source for every Individual created. Option 2: Provide a default text value. It must match exactly with an existing Lead Source field option in AgencyBloc. This will set the same lead source for every Individual created.

Option 3: Every Lead Source field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different lead source for every Individual created. Option 4: Choose a default value from the list. This will set the same lead source for every Individual created.

Option 1: Map to text values in a third-party app. This allows you to set the other lead source differently for every Individual created. Option 2: Provide a default text value. This will set the other lead source the same for every Individual created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as the lead agent/affiliate. To improve matching accuracy, provide the "Lead Agent/Affiliate - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as the lead agent/affiliate. To improve matching accuracy, provide the "Lead Agent/Affiliate - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as the lead agent/affiliate. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different lead affiliate/agent for every Individual created. Option 3: Provide the ID for a specific Agent record. This will be the lead agent/affiliate for every Individual created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Project Code field options in AgencyBloc. This allows you to set a different project code for every Individual created. Option 2: Provide a default text value. It must match exactly with an existing Project Code field option in AgencyBloc. This will set the same project code for every Individual created.

Option 3: Every Project Code field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different project code for every Individual created. Option 4: Choose a default value from the list. This will set the same project code for every Individual created.

Custom Fields for Individual records in AgencyBloc will appear below. If mapping to the "Checkbox" field type, please note that we accept only "True" or "False" values. If mapping to the "Checkbox List" or "Dropdown" field types, please note that the provided values must match exactly with existing values in AgencyBloc.

Create Group records in AgencyBloc when something happens in third-party apps, such as lead forms, enrollment platforms, and CRMs. Choose what information is sent to AgencyBloc in the fields below.

Option 1: Map to name values in a third-party app. This allows you to set a different name for every Group created. Option 2: Provide a default name value. This will set the same first name for every Group created.

Option 1: Map to DBA values in a third-party app. This allows you to set a different DBA for every Group created. Option 2: Provide a default DBA value. This will set the same DBA for every Group created.

Option 1: Map to text values in a third-party app. This allows you to set a different description for every Group created. Option 2: Provide a default text value. This will set the same description for every Group created.

Option 1: Map to federal tax ID values in a third-party app. This allows you to set a different federal tax ID for every Group created. Option 2: Provide a default federal tax ID value. This will set the same federal tax ID for every Group created.

Option 1: Map to SIC ID values in a third-party app. This allows you to set a different industry for every Group created. Option 2: Provide a default SIC ID value. This will set the same industry for every Group created.

Option 3: Map to SIC description values in a third-party app. This allows you to set a different industry for every Group created. Option 4: Provide a default SIC description value. This will set the same industry for every Group created.

Option 1: Map to industry ID values in a third-party app. The ID is a unique number tied to every Industry value in AgencyBloc. This allows you to set a different industry for every Group created. Option 2: Provide a default industry ID value. This will set the same industry for every Group created.

Option 1: Map to website values in a third-party app. This allows you to set a different website for every Group created. Option 2: Provide a default website value. This will set the same website for every Group created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Group Type field options in AgencyBloc. This allows you to set a different type for every Group created. Option 2: Provide a default text value. It must match exactly with an existing Group Type field option in AgencyBloc. This will set the same type for every Group created.

Option 3: Every Group Type field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different type for every Group created. Option 4: Choose a default value from the list. This will set the same type for every Group created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Group Status field options in AgencyBloc. This allows you to set a different status for every Group created. Option 2: Provide a default text value. It must match exactly with an existing Group Status field option in AgencyBloc. This will set the same status for every Group created.

Option 3: Every Group Status field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different status for every Group created. Option 4: Choose a default value from the list. This will set the same status for every Group created.

Option 1: Map to the ID numbers of AgencyBloc Users in a third-party app. This allows you to set a different account manager for every Group created. Option 2: Provide the ID number of an AgencyBloc User that you want to be the account manager for every Group created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as the servicing agent. To improve matching accuracy, provide the "Servicing Agent - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as the servicing agent. To improve matching accuracy, provide the "Servicing Agent - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as the servicing agent. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different servicing agent for every Group created. Option 3: Provide the ID for a specific Agent record. This will be the servicing agent for every Group created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 1. To improve matching accuracy, provide the "Additional Agent 1 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 1. To improve matching accuracy, provide the "Additional Agent 1 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 1. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 1 for every Group created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 1 for every Group created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 2. To improve matching accuracy, provide the "Additional Agent 2 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 2. To improve matching accuracy, provide the "Additional Agent 2 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 2. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 2 for every Group created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 2 for every Group created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 3. To improve matching accuracy, provide the "Additional Agent 3 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 3. To improve matching accuracy, provide the "Additional Agent 3 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 3. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 3 for every Group created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 3 for every Group created.

Option 1: Map to number values in a third-party app. This allows you to set a different business phone number for every Group created. Option 2: Provide a default number value. This will set the same business phone number for every Group created.

Option 1: Map to numerical values in a third-party app. This allows you to set a different business phone extension for every Group created. Option 2: Provide a default numerical value. This will set the same business phone extension for every Group created.

Option 1: Map to number values in a third-party app. This allows you to set a different fax number for every Group created. Option 2: Provide a default number value. This will set the same fax number for every Group created.

Option 1: Map to number values in a third-party app. This allows you to set a different fax extension for every Group created. Option 2: Provide a default number value. This will set the same fax extension for every Group created.

Required to add address information. Option 1: Map to text values in a third-party app. They must match exactly with existing Address Type field options in AgencyBloc. This allows you to set a different address type for every Group created. Option 2: Provide a default text value. It must match exactly with an existing Address Type field option in AgencyBloc. This will set the same address type for every Group created.

Option 1: Map to "True" and "False" values in a third-party app. This allows you to set the primary address differently for every Group created. Option 2: Choose a default value from the list. This will set the primary address the same for every Group created.

Option 1: Map to address values in a third-party app. This allows you to set a different address street 1 for every Group created. Option 2: Provide a default address value. This will set address street 1 the same for every Group created.

Option 1: Map to address values in a third-party app. This allows you to set a different address street 2 for every Group created. Option 2: Provide a default address value. This will set address street 2 the same for every Group created.

Option 1: Map to city values in a third-party app. This allows you to set a different city for every Group created. Option 2: Provide a default city value. This will set the same city for every Group created.

Option 1: Map to county values in a third-party app. They must match exactly with existing County values in AgencyBloc. This allows you to set a different county for every Group created. Option 2: Provide a default county value. It must match exactly with an existing county in AgencyBloc. This will set the same county for every Group created.

Option 1: Map to State/Province values in a third-party app. They must be formatted as two letters (ex. AZ for Arizona) and be real U.S. States or Territories or Provinces. This allows you to set a different State/Province for every Group created. Option 2: Provide a default State/Province value. It must be formatted as two letters (ex. AZ for Arizona) and be a real U.S. State or Territory or Province. This will set the same State/Province for every Group created.

Option 1: Map to valid zip code values in a third-party app. This allows you to set a different zip code for every Group created. Option 2: Provide a default valid zip code value. This will set the same zip code for every Group created.

Option 1: Map to date values in a third-party app. This allows you to set a different lead date for every Group created. Option 2: Provide a default date value. This will set the same lead date for every Group created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Lead Source field options in AgencyBloc. This allows you to set a different lead source for every Group created. Option 2: Provide a default text value. It must match exactly with an existing Lead Source field option in AgencyBloc. This will set the same lead source for every Group created.

Option 3: Every Lead Source field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different lead source for every Group created. Option 4: Choose a default value from the list. This will set the same lead source for every Group created.

Option 1: Map to text/numerical values in a third-party app. This allows you to set the other lead source differently for every Group created. Option 2: Provide a default text/numerical value. This will set the other lead source the same for every Group created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as the lead agent/affiliate. To improve matching accuracy, provide the "Lead Agent/Affiliate - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as the lead agent/affiliate. To improve matching accuracy, provide the "Lead Agent/Affiliate - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as the lead agent/affiliate. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different lead affiliate/agent for every Group created. Option 3: Provide the ID for a specific Agent record. This will be the lead agent/affiliate for every Group created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Project Code field options in AgencyBloc. This allows you to set a different project code for every Group created. Option 2: Provide a default text value. It must match exactly with an existing Project Code field option in AgencyBloc. This will set the same project code for every Group created.

Option 3: Every Project Code field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different project code for every Group created. Option 4: Choose a default value from the list. This will set the same project code for every Group created.

Custom Fields for Group records in AgencyBloc will appear below. If mapping to the "Checkbox" field type, please note that we accept only "True" or "False" values. If mapping to the "Checkbox List" or "Dropdown" field types, please note that the provided values must match exactly with existing values in AgencyBloc.

Create Policy records in AgencyBloc when something happens in third-party apps, such as enrollment platforms and CRMs. Choose what information is sent to AgencyBloc in the fields below.

Every Policy created must be associated with a Group or Individual record in AgencyBloc. Option 1: Choose the Group or Individual value from the list. This will set the same policyholder type for every Policy created. Option 2: Map to "Group" and "Individual" values in a third-party app. This allows you to set a different policyholder type for every Policy created.

Option 1: Map to the ID numbers of Group and Individual records in a third-party app. This allows you to associate every Policy created with a different policyholder. Option 2: Provide the ID for a specific Group or Individual record. This will associate every Policy created with the same record.

Option 1: Map to name values in a third-party app. We'll look for an existing Carrier record with the same name in AgencyBloc and associate it with the Policy created. If we can't find a Carrier record with the same name, the Policy will not be created. Option 2: Provide a name value. We'll look for an existing Carrier record with the same name in AgencyBloc and associate it with every Policy created.

Option 3: Map to the ID numbers of Carrier records in a third-party app. This allows you to associate every Policy created with a different carrier. Option 4: Provide the ID for a specific Carrier record. This will associate every Policy created with the same record.

Option 1: Map to number/text values in a third-party app. This allows you to set a different policy number for every Policy created. Option 2: Provide a default number/text value. This will set the same policy number for every Policy created.

Option 1: Map to number values in a third-party app. This allows you to set a different premium for every Policy created. Option 2: Provide a default number value. This will set the same premium for every Policy created.

Option 1: Map to number values in a third-party app. This allows you to set the number of lives differently for every Policy created. Option 2: Provide a default number value. This will set the same number of lives for every Policy created.

Option 1: Map to pay frequency values in a third-party app. This allows you to set a different pay frequency for every Policy created. Option 2: Choose a default value from the list. This will set the same pay frequency for every Policy created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Project Code field options in AgencyBloc. This allows you to set a different project code for every Policy created. Option 2: Provide a default text value. It must match exactly with an existing Project Code field option in AgencyBloc. This will set the same project code for every Policy created.

Option 3: Every Project Code field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different project code for every Policy created. Option 4: Choose a default value from the list. This will set the same project code for every Policy created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Policy Status field options in AgencyBloc. This allows you to set a different status for every Policy created. Option 2: Provide a default text value. It must match exactly with an existing Policy Status field option in AgencyBloc. This will set the same status for every Policy created.

Option 3: Every Policy Status field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different status for every Policy created. Option 4: Choose a default value from the list. This will set the same status for every Policy created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Coverage Type field options in AgencyBloc. This allows you to set a different coverage type for every Policy created. Option 2: Provide a default text value. It must match exactly with an existing Coverage Type field option in AgencyBloc. This will set the same coverage type for every Policy created.

Option 3: Every Coverage Type field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different coverage type for every Policy created. Option 4: Choose a default value from the list. This will set the same coverage type for every Policy created.

Option 1: Map to date values in a third-party app. This allows you to set a different app submit date for every Policy created. Option 2: Provide a default date value. This will set the same app submit date for every Policy created.

Option 1: Map to date values in a third-party app. This allows you to set a different effective date for every Policy created. Option 2: Provide a default date value. This will set the same effective date for every Policy created.

Option 1: Map to date values in a third-party app. This allows you to set a different renewal date for every Policy created. Option 2: Provide a default date value. This will set the same renewal date for every Policy created.

Option 1: Map to date values in a third-party app. This allows you to set a different term date for every Policy created. Option 2: Provide a default date value. This will set the same term date for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as the signed by. To improve matching accuracy, provide the "Signed By - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as the signed by. To improve matching accuracy, provide the "Signed By - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as the signed by. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set the signed by differently for every Policy created. Option 3: Provide the ID for a specific Agent record. This will set the signed by the same for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to a User in AgencyBloc by first name. If a match is found, we'll set it as the account manager. To improve matching accuracy, provide the "Account Manager - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to a User in AgencyBloc by last name. If a match is found, we'll set it as the account manager. To improve matching accuracy, provide the "Account Manager - First Name."

Option 2: Map to the ID numbers of AgencyBloc Users in a third-party app. This allows you to set a different account manager for every Policy created. Option 3: Provide the ID for a specific AgencyBloc User. This will be the account manager for every Policy created.

Option 1: Map to agency name values in a third-party app. This allows you to set a different agency for the servicing agent of every Policy created. Option 2: Provide a default agency name value. This will set the same agency for the servicing agent of every Policy created.

Option 2: Map to the ID numbers of Agency records in a third-party app. This allows you to set a different agency for the servicing agent of every Policy created. Option 3: Provide the ID for a specific Agency record. This will set the same agency for the servicing agent of every Policy created.

Option 1: Map to agent number values in a third-party app. This allows you to set a different agent number for the servicing agent of every Policy created. Option 2: Provide a default agency number value. This will set the same agent number for the servicing agent of every Policy created.

Option 3: Map to agent number IDs in a third-party app. This allows you to set a different agent number for the servicing agent of every Policy created. Option 4: Provide a default agent number ID. This will be the agent number for the servicing agent assigned to every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as the servicing agent. To improve matching accuracy, provide the "Servicing Agent - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as the servicing agent. To improve matching accuracy, provide the "Servicing Agent - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as the servicing agent. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different servicing agent for every Policy created. Option 3: Provide the ID for a specific Agent record. This will be the servicing agent for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 1. To improve matching accuracy, provide the "Additional Agent 1 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 1. To improve matching accuracy, provide the "Additional Agent 1 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 1. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 1 for every Policy created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 1 for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 2. To improve matching accuracy, provide the "Additional Agent 2 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 2. To improve matching accuracy, provide the "Additional Agent 2 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 2. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 2 for every Policy created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 2 for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 3. To improve matching accuracy, provide the "Additional Agent 3 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 3. To improve matching accuracy, provide the "Additional Agent 3 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 3. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 3 for every Policy created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 3 for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 4. To improve matching accuracy, provide the "Additional Agent 4 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 4. To improve matching accuracy, provide the "Additional Agent 4 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 4. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 4 for every Policy created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 4 for every Policy created.

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by first name. If a match is found, we'll set it as additional agent 5. To improve matching accuracy, provide the "Additional Agent 5 - Last Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by last name. If a match is found, we'll set it as additional agent 5. To improve matching accuracy, provide the "Additional Agent 5 - First Name."

Option 1: Map to name values in a third-party app, or provide a default name value. We'll attempt to match each value to an existing Agent record in AgencyBloc by middle name. If a match is found, we'll set it as additional agent 5. You only need first and last name but middle name may improve matching accuracy.

Option 2: Map to the ID numbers of Agent records in a third-party app. This allows you to set a different additional agent 5 for every Policy created. Option 3: Provide the ID for a specific Agent record. This will be additional agent 5 for every Policy created.

Option 1: Map to number values in a third-party app. This allows you to set a different renewal percent for every Group Policy created. Option 2: Provide a default number value. This will set the same renewal percent for every Group Policy created.

Option 1: Map to text values in a third-party app. They must match exactly with existing New Hire Eligibility field options in AgencyBloc. This allows you to set the new hire eligibility differently for every Policy created. Option 2: Provide a default text value. It must match exactly with an existing New Hire Eligibility field option in AgencyBloc. This will set the new hire eligibility the same for every Group Policy created.

Option 3: Every New Hire Eligibility field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set the new hire eligibility differently for every Policy created. Option 4: Choose a default value from the list. This will set the new hire eligibility the same for every Group Policy created.

Option 1: Map to text values in a third-party app. They must match exactly with existing Eligibility Hours field options in AgencyBloc. This allows you to set the eligibility hours differently for every Policy created. Option 2: Provide a default text value. It must match exactly with an existing Eligibility Hours field option in AgencyBloc. This will set the same eligibility hours for every Group Policy created.

Option 3: Every Eligibility Hours field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set the eligibility hours differently for every Policy created. Option 4: Choose a default value from the list. This will set the same eligibility hours for every Group Policy created.

Option 1: Map to rate method values in a third-party app. They must match exactly with existing Rate Method field options in AgencyBloc. This allows you to set a different rate method for every Group Policy created. Option 2: Choose a default value from the list. This will set the same rate method for every Group Policy created.

Option 1: Map to waiting period values in a third-party app. This allows you to set a different waiting period for every Group Policy created. Option 2: Provide a default waiting period value. This will set the same waiting period for every Group Policy created.

Option 1: Map to classification values in a third-party app. This allows you to set a different classification for every Group Policy created. Option 2: Provide a default classification value. This will set the same classification for every Group Policy created.

Option 1: Map to text values in a third-party app. This allows you to set a different note for every Group Policy created. Option 2: Provide a default text value. This will set the same note for every Group Policy created.

Option 1: Map to pay method values in a third-party app. They must match exactly with existing Pay Method field options in AgencyBloc. This allows you to set a different pay method for every Individual Policy created. Option 2: Provide a default pay method value. This will set the same pay method for every Individual Policy created.

Option 3: Every Pay Method field option in AgencyBloc has an ID number. Map to these IDs in a third-party app to set a different pay method for every Individual Policy created. Option 4: Choose a default value from the list. This will set the same pay method for every Individual Policy created.

Option 1: Map to text values in a third-party app. This allows you to set different notes for every Individual Policy created. Option 2: Provide a default text value. This will set the same notes for every Individual Policy created.

Option 1: Map to text/number values in a third-party app. This allows you to set a different member ID for every Individual Policy created. Option 2: Provide a default text/number value. This will set the same member ID for every Individual Policy created.

Option 1: Map to carrier product values in a third-party app. This allows you to set a different carrier product on every coverage added to the Policy. Option 2: Provide a default carrier product value. This will associate the same carrier product with every coverage added to the Policy.

Option 3: Map to the ID numbers of carrier products in a third-party app. This allows you to associate a different product with every coverage added to the Policy. Option 4: Choose a default value from the list. This will be the carrier product on every coverage added to the Policy.

Option 1: Map to date values in a third-party app. This allows you to set a different effective date on every coverage added to the Policy. Option 2: Provide a default date value. This will set the same effective date on every coverage added to the Policy.

Option 1: Map to number values in a third-party app. This allows you to set a different premium on every coverage added to the Policy. Option 2: Provide a default number value. This will set the same premium on every Policy Coverage.

Option 1: Map to date values in a third-party app. This allows you to set a different renewal date on every coverage added to the Policy. Option 2: Provide a default date value. This will set the same renewal date on every coverage added to the Policy.

Option 1: Map to "True" and "False" values in a third-party app. This allows you to set a different status on every coverage added to the Policy. Option 2: Provide a default "True" or "False" value. This will set the same status on every coverage added to the Policy.

Option 1: Map to text values in a third-party app. This allows you to set different notes on every coverage added to the Policy. Option 2: Provide a default text value. This will set the same notes on every coverage added to the Policy.

Option 1: Map to text values in a third-party app. This allows you to set different fees on every coverage added to the Policy. Option 2: Provide a default text value. This will set the same fees on every coverage added to the Policy.

Option 1: Choose a FieldSet value from the list. This will override the default FieldSet on every coverage added to the Policy. Option 2: Every FieldSet in AgencyBloc has an ID number. If a third-party app has these IDs, you can map to them and set a different FieldSet on every coverage added to the Policy.

Custom Fields for Policy records in AgencyBloc will appear below. If mapping to the "Checkbox" field type, please note that we accept only "True" or "False" values. If mapping to the "Checkbox List" or "Dropdown" field types, please note that the provided values must match exactly with existing values in AgencyBloc.