
Welcome to the InsuraConnect User Guide! This guide serves as a complete manual to every aspect of InsuraConnect, your streamlined conduit to peak productivity in the insurance sector. Eschewing the complexity of redundant features, InsuraConnect is forged from in-depth research to deliver a swift, efficient, and user-friendly experience for the modern insurance agent.
Refer to the Table of contents to find your answers as well as step-by-step instructions for all the features to be a master of InsuraConnect.
InsuraConnect is a desktop application tailored for managing client interactions and insurance policies. It is optimized for speed via a Command Line Interface (CLI), backed by the visual accessibility of a Graphical User Interface (GUI). For agents adept at typing, InsuraConnect enhances task execution, outpacing conventional GUI applications.
With InsuraConnect, you can swiftly access client information, manage policies, track meetings, and stay organized in a competitive landscape. Our goal is to transform your workflow into an efficient model of productivity.
This user guide provides the installation process, clear explanations for each command, step-by-step instructions, insightful examples and troubleshooting recommendations to ensure you harness the full potential of InsuraConnect. In addition, the quick start guide provides an end-to-end setup process to get started.
InsuraConnect is designed for insurance agents who desire the efficacy of CLI without relinquishing GUI advantages. It is an essential tool for those who manage a broad client base, track multiple insurance policies, organise meetings, and value the efficiency of their time and resources.
❓ What truly sets InsuraConnect apart? This is only the tip of the iceberg of the things you can do working with InsuraConnect.
Comprehensive Policy Management: Dive into the essence of each policy with InsuraConnect's in-depth tracking system. Visualize expiry dates, premiums, and detailed coverage information, all laid out for clear understanding and quick access.
Dynamic Policy Administration: Add zest to policy handling with agile tools that allow you to add, update, or remove policy details effortlessly. Maintain accurate client portfolios with just a few intuitive commands.
Streamlined Meeting Coordination: Command your schedule with robust scheduling capabilities. Organize, adjust, and cancel meetings with ease, enhanced by our integrated agenda setting and comprehensive note-taking tools.
Client Engagement Tracker: Keep your finger on the pulse of client relations. Monitor interactions and gauge policy engagement levels to ensure high client retention and satisfaction rates.
Proactive Meeting Reminders: Stay ahead of the game with proactive notifications for impending meetings, ensuring you're always prepared to seize every client engagement opportunity.
To explore more, visit the Features section for more advanced tips.
Ensure you have Java 11 or above installed in your Computer. You can download Java 11 for your system here.
Download the latest InsuraConnect.jar from here.
Copy the file to the folder you want to use as the home folder for InsuraConnect.
Open a command terminal, cd into the folder you put the jar file in, and use the java -jar InsuraConnect.jar command to run the application.
A GUI similar to the image below should appear in a few seconds. Note how the app contains some sample data.
Fig 1: InsuraConnect's GUI
Type the command in the command box and press Enter to execute it. e.g. typing help and pressing Enter will open the help window.
Some example commands you can try:
list : Lists all contacts.
add n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01 r/client : Adds a contact named John Doe to InsuraConnect.
delete 3 : Deletes the 3rd contact shown in the current list.
schedule 1 md/2024-05-05 mt/09:00 ma/Discuss health policy mdur/60 : Schedules a meeting with the 1st contact in the current list at 5th May 2024 9am to discuss health policy.
policy 1 po/Health policy ed/2029-06-06 pm/1000 Adds a policy with the 1st contact in the current list with name of
Health policy, expiry date on the 6th of June 2029, with a premium of 1000 SGD.
exit : Exits the app.
Refer to the Features below for further details of each command.
Refer to the Command summary for a full list of the available commands
The InsuraConnect User Guide is structured to help you navigate as easily as possible. You can use the Table of contents to navigate any section you want. Hyperlinks are also included that will take you to relevant sections or features. If you already an experienced user, you can use the Supported prefixes and Command summary sections for a quick overview.
In the Features section, each feature will contain:
You can also find visuals that highlight how the features of InsuraConnect will look. They are located below the description of the feature and are labelled for your convenience.
This guide uses the following coloured icons and segments. They represent different information to help you better understand how to use InsuraConnect.
Tip: This indicates a helpful tip on how to utilise a particular feature of InsuraConnect.
Constraint: This indicates a constraint on the command format or feature of InsuraConnect.
Caution: This indicates a precaution that you should read carefully and remember when using InsuraConnect.
Before you dive into the features, read through the notes regarding InsuraConnect's command format.
Notes about the command format:
Words in UPPER_CASE are the parameters for you to input.
Example: In add n/NAME, NAME is a parameter which you can use as add n/John Doe.
Prefixes are in the form of a shortened word followed by a / such as po/ for policy ormd/ for meeting date.
You can refer to the supported prefixes section for a full list of prefixes.
Prefixes require a space before being used, such as n/NAME e/EMAIL requiring a space between NAME and e/.
Items in square brackets are optional.
Example: You can use n/NAME [t/TAG] as n/John Doe t/friend or as n/John Doe.
You can use items with … after them multiple times including zero times.
Example: You can use [t/TAG]… as (i.e. 0 times), t/friend, or t/friend t/family, etc.
You can use parameters in any order.
Example: If the command specifies n/NAME p/PHONE_NUMBER, you can also input p/PHONE_NUMBER n/NAME.
Extraneous parameters for commands that do not take in parameters (such as help, list, exit and clear) will be ignored.
Example: If you input the command help 123, it will be interpreted as help.
If you are using a PDF version of this document, be careful when copying and pasting commands that span multiple lines as space characters surrounding line-breaks may be omitted when copied over to the application.
If you encounter any errors when using commands, the output/error display will highlight potential formatting mistakes in your command.
helpShows a message explaining how to access the help page.
Format: help
addAdds a person to InsuraConnect.
Format: add n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS r/RELATIONSHIP [t/TAG]…
Tip: A person can have any number of tags (including 0) and the tag names should not have whitespaces in them.
Constraints:
s/o,
are currently not allowed. However, it is one of our considerations in our future planned enhancements and for now, a current workaround would be directly using "son of" or "so" instead.client or partner.Examples:
add n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01 r/client adds a client with the respective details to InsuraConnect.add n/Betsy Crowe t/friend e/betsycrowe@example.com a/Kent Ridge p/1234567 r/partner t/oweMoney adds a partner with the respective details to InsuraConnect.The following images show the InsuraConnect UI before and after executing the command add n/Betsy Crowe t/friend e/betsycrowe@example.com a/Kent Ridge p/1234567 r/partner t/oweMoney.
Fig 3: Before adding a person
Fig 4: Outcome after adding a person
listShows a list of all persons in InsuraConnect.
Format: list
editEdits an existing person in InsuraConnect.
Format: edit INDEX [n/NAME] [p/PHONE] [e/EMAIL] [a/ADDRESS] [t/TAG]…
INDEX. The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …t/ without specifying any tags after it.Examples:
edit 1 p/91234567 e/alexyeoh1234@example.com edits the phone number and email address of the 1st person to be 91234567 and johndoe@example.com respectively.edit 2 n/Betsy Crower t/ edits the name of the 2nd person to be Betsy Crower and clears all existing tags.The following images show the InsuraConnect UI before and after executing the command edit 1 p/91234567 e/alexyeoh1234@example.com.
Fig 5: Before editing Alex's email and phone number
Fig 6: After editing Alex's email and phone number
The following images show the InsuraConnect UI before and after executing the command edit 2 n/Betsy Crower t/.
Fig 7: Before editing the 2nd person
Fig 8: Outcome after editing the 2nd person
findFinds persons whose details contain any of the given keywords.
Format: find [n/NAME]... [r/RELATIONSHIP]... [t/TAG]... [po/POLICY]...
hans will match Hans. Hans, client .OR search).
e.g. find n/Hans n/Bo r/partner will return Hans Gruber, Bo Yang and all person who have relationship partner.Constraints:
find n/.NAME, RELATIONSHIP, TAG, POLICY) cannot contain spaces between words e.g: Hans Bo, owe money are not allowed.Han will not match Hans.Examples:
find n/ John returns john and John Doefind r/partner retrieves all the partners listed in the contact list.The following images show the InsuraConnect UI after executing the command find n/Alex n/David.
Fig 9: Outcome from finding Alex and David
deleteDeletes the specified person from InsuraConnect.
Format: delete INDEX
INDEX.Examples:
list followed by delete 2 deletes the 2nd person in InsuraConnect.find Betsy followed by delete 1 deletes the 1st person in the results of the find command.Constraints:
dd-mm-yyyy e.g.: 31-12-2025 and it should not be a past date.policyFormat: policy INDEX po/POLICY_NAME [ed/EXPIRY_DATE] [pm/PREMIUM]
INDEX.
The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …Examples: policy 1 po/Health Policy ed/01-01-2030 pm/500000 adds a new policy to the 1st person.
The following images show the InsuraConnect UI before and after executing the command policy 1 po/Health Policy ed/01-01-2030 pm/500000.
Fig 10: Before adding a policy
Fig 11: After adding a policy to the 1st person
policyFormat: policy INDEX pi/POLICY_INDEX po/POLICY_NAME [ed/EXPIRY_DATE] [pm/PREMIUM]
INDEX with a specified POLICY_INDEX.
Policy index refers to the index number shown in the person's displayed policy list. Both indices must be positive integer 1, 2, 3, …Examples: policy 1 pi/2 po/Travel Policy ed/01-01-2025 pm/2000 edits the 1st person's 2nd policy.
The following images show the InsuraConnect UI before and after executing the command policy 1 pi/2 po/Travel Policy ed/01-01-2025 pm/2000.
Fig 12: Before editing the policy
Fig 13: After editing the 2nd policy of the 1st person
policyFormat: policy INDEX pi/POLICY_INDEX po/
INDEX with a specified POLICY_INDEX. Both indices must be positive integer 1, 2, 3, …POLICY_NAME blank to remove a particular policy from a particular client.po/ will be ignored and the policy will still be deleted,
e.g., policy 1 pi/2 po/ ed/01-01-2025 pm/2000 will still delete the 1st person's 2nd policy.Examples: policy 1 pi/2 po/ deletes the 1st person's 2nd policy.
The following images show the InsuraConnect UI before and after executing the command policy 1 pi/2 po/.
Fig 14: Before deleting the policy
Fig 15: After deleting the 2nd policy of the 1st person
Constraints:
DATE:
DATE and 04:59 for TIME will choose
next weeks' monday while choosing 05:01 for TIME instead will choose the current monday at 05:01.scheduleSchedules a meeting with a person with an agenda and duration with optional notes
Format: schedule INDEX md/DATE mt/TIME mdur/DURATION ma/AGENDA mn/[NOTES]
INDEX. The index refers to the index number shown in the displayed persons list.Examples:
schedule 1 md/09-09-2024 mt/09:00 mdur/60 ma/discuss health policy mn/urgentschedule 1 md/01-09-2024 mt/13:00 mdur/60 ma/discuss vehicle policy mn/urgentThe following images show the InsuraConnect UI after executing two example commands above consecutively.
Fig 16: Schedule meeting at 9am 9th Sept 2024
Fig 17: Schedule another meeting at 1pm 1st Sept 2024
rescheduleReschedules a meeting with a person
Format: reschedule INDEX mi/MEETING_INDEX md/DATE mt/TIME
INDEX. The index is the same as the above for schedule.MEETING_INDEX.Examples: reschedule 1 mi/2 md/05-09-2024 mt/17:00
The following images show the InsuraConnect UI after executing the example command above from Fig 17.
Fig 18: Reschedule meeting from 9am 9th Sept 2024 to 5pm 5th Sept 2024
cancelCancels a meeting with a person
Format: cancel INDEX mi/MEETING_INDEX
INDEX and MEETING_INDEX is the same as the above for rescheduleExamples: cancel 1 mi/1
The following image shows the InsuraConnect UI after executing the example command above following the commands above in reschedule that resulted in Fig 18.
Fig 19: Cancel meeting at 1pm 1st Sept 2024
Meetings are automatically sorted by their scheduled dates and times. When multiple meetings are scheduled for a client, InsuraConnect will organize them in ascending order, showing the earliest upcoming meeting at the top. This feature allows insurance agents to quickly glance at their schedule and prioritize upcoming meetings.
Fig 20: Meetings for Alex Yeoh displayed from earliest to latest
To ensure the schedule remains current and manageable, InsuraConnect automatically purges past meetings. Once a meeting's end time has passed, it will be removed from the system during the next refresh cycle. This helps to maintain an up-to-date schedule for users, focusing only on relevant future engagements.
Clients and partners are sorted in the user interface according to the time of their earliest scheduled meeting. This sorting mechanism places those individuals with the most imminent meetings at the top of the list, allowing for efficient time management and planning. Should there be no scheduled meetings for a client or partner, they will be positioned in the list based on the default sorting criteria.
Fig 21: Client/Partners sorted by earliest meeting scheduled with insurance agent
statusChanges a client's status by one level to reflect the progress with that client. In increasing order, the possible status levels are Yet to start,
In progress, and Completed.
Format: status INDEX s/DIRECTION
INDEX.
The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …DIRECTION as up to increase the status, or down to decrease the status.Yet to start.Tip: You can use this whenever you schedule the first meeting with your client or assign them a policy to track your progress. The dashboard above the persons list automatically displays the number of clients that are currently at each status for your convenience.
Constraints:
DIRECTION can only be up, down, or blank.Examples:
status 1 s/up increases the status of the 1st person by one level if it is a client.status 1 s/ resets the status of the 1st person if it is a client.The following images show the InsuraConnect UI before and after executing the command status 1 s/up.
Fig 22: Before increasing the 1st client's status
Fig 23: After increasing the 1st client's status
undoUndoes a previous command.
Format: undo
Examples:
add n/Adam Ibnu p/11111111 e/Adam@gmail.com a/Sembawang road blk 509c #02-25 r/client t/friendThe following images show the InsuraConnect UI after executing the command above.
Fig 24: Newly added Adam contact
undo which undoes the previous command, removing the newly added person as shown below.The following images show the InsuraConnect UI after executing the command undo from Fig 24.
Fig 25: Undo removing the Adam contact
redoRedoes a previous undid command
Format: redo
Examples:
The following images show the InsuraConnect UI after executing the command redo from Fig 25.
Fig 26: Redo adding back Adam
clearClears all entries from InsuraConnect.
Format: clear
exitExits the program.
Format: exit
InsuraConnect data are saved in the hard disk automatically after any command that changes the data. There is no need to save manually.
InsuraConnect data are saved automatically as a JSON file [JAR file location]/data/addressbook.json. Advanced users are welcome to update data directly by editing that data file.
Caution:
If your changes to the data file makes its format invalid, InsuraConnect will discard all data and start with an empty data file at the next run. Hence, it is recommended to take a backup of the file before editing it.
Furthermore, certain edits can cause InsuraConnect to behave in unexpected ways (e.g., if a value entered is outside the acceptable range). Therefore, edit the data file only if you are confident that you can update it correctly.
Q: How do I transfer my data to another Computer?
A: Install the app in the other computer and overwrite the empty data file it creates with the file that contains the data of your previous InsuraConnect home folder.
Q: Can I access InsuraConnect from multiple devices?
A: Currently, InsuraConnect is designed to be installed and used on a single computer. However, we are exploring options for multi-device access in future updates.
Q: Is InsuraConnect compatible with all operating systems?
A: InsuraConnect is optimized for Windows, macOS, and Linux operating systems. Ensure your device meets the minimum system requirements for seamless performance.
Q: Can I import existing client data into InsuraConnect?
A: Currently, there is no direct import feature within InsuraConnect. However, you can manually input your client data using the add command or directly edit the JSON data file if you have a large dataset. We are considering adding import functionality in future updates.
Q: Is my data secure within InsuraConnect?
A: InsuraConnect prioritizes data security and confidentiality. All client data is stored locally on your computer in a JSON file and is not transmitted over the internet. However, it's advisable to take regular backups of your data to prevent loss in case of unforeseen circumstances.
preferences.json file created by the application before running the application again.list to list all tasks so that all operations are done on the correct index number. The filtered list doesn't revert back when doing next command, so user has to manually enter list to avoid any discrepancies.| Name of prefix | Prefix in command | Description |
|---|---|---|
| Name | n/ | The name of the person |
| Phone Number | p/ | The phone number of the person |
| Email Address | e/ | The email address of the person |
| Address | a/ | The address of the person |
| Relationship | r/ | The relationship of the person |
| Tag | t/ | The tag of the person |
| Policy Name | po/ | The name of the policy |
| Policy Index | pi/ | The index of the policy |
| Policy Expiry Date | ed/ | The expiry date of the policy |
| Policy Premium | pm/ | The premium of the policy |
| Meeting Date | md/ | The date of the meeting |
| Meeting Time | mt/ | The time of the meeting |
| Meeting Duration | mdur/ | The duration of the meeting |
Meeting Agenda (not editable through reschedule) | ma/ | The agenda of the meeting |
| Meeting Notes | mn/ | The notes of the meeting |
| Meeting Index | mi/ | The index in the meeting list |
| Client status direction | s/ | The direction of status change |
| Action | Format, Examples |
|---|---|
| Help | help |
| Add | add n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS r/RELATIONSHIP [t/TAG]… e.g., add n/James Ho p/22224444 e/jamesho@example.com a/123, Clementi Rd, 1234665 r/client t/friend |
| List | list |
| Edit | edit INDEX [n/NAME] [p/PHONE_NUMBER] [e/EMAIL] [a/ADDRESS] [t/TAG]…e.g., edit 2 n/James Lee e/jameslee@example.com |
| Find | find [n/NAME]... [r/RELATIONSHIP]... [t/TAG]... [po/POLICY]... e.g., find n/John n/Alex r/client |
| Delete | delete INDEXe.g., delete 3 |
| Add Policy | policy INDEX po/POLICY_NAME [ed/EXPIRY_DATE] [pm/PREMIUM] e.g., policy 1 po/Policy ABC ed/01-01-2025 |
| Edit Policy | policy INDEX pi/POLICY_INDEX po/POLICY_NAME [ed/EXPIRY_DATE] [pm/PREMIUM] e.g., policy 1 pi/2 po/Policy ABC pm/1000 |
| Delete Policy | policy INDEX pi/POLICY_INDEX po/ e.g., policy 2 pi/2 po/ |
| Schedule Meeting | schedule INDEX md/DATE mt/TIME mdur/DURATION ma/AGENDA [mn/NOTES] e.g., schedule 1 md/2024-05-05 mt/09:00 mdur/60 ma/Discuss health policy mn/Bring laptop |
| Reschedule Meeting | reschedule INDEX mi/MEETING_INDEX md/DATE mt/TIME e.g., reschedule 1 mi/1 md/2024-07-07 mt/11:00 |
| Cancel Meeting | cancel INDEX mi/MEETING_INDEX e.g., cancel 1 mi/1 |
| Change Client Status | status INDEX s/DIRECTION e.g., status 1 s/up |
| Undo | undo |
| Redo | redo |
| Clear | clear |
| Exit | exit |