InquireAI Use Cases
Use Cases
Classification and Summary
Leveraging InquireAI, document classification becomes a trivial task. Provide a description of the documents you expect to analyze, ask the AI to summarize the document, and you are ready to go.
Prompt
You are responsible for classifying and summarizing documents being received.
Summarize the document 100 words or less and assign it to the Summary field.
For classification purposes, documents received may be a Purchase Order (a request for goods and or services), a Contract (a legal agreement outlining terms between two parties), or Meeting Minutes (an outline or summary of a prior meeting). Classify the document type and assign it to the Document Type field.
Using this prompt, you will need the following process fields to access the data in your workflow:
Summary
Document Type
Purchase Order/Sales Order
Eliminate the need for multiple complex templates to extract header and line item information from Accounts Payable/Receivable documents using Inquire AI. As a general rule, it’s best to be as descriptive as possible, but oftentimes, a very simple prompt will suffice.
Simple Prompt
You are a knowledge worker tasked with understanding purchase orders and sales orders. Carefully read the PDF file and extract header fields that will aid in management of these document types. Extract the following fields:
Order Number
Order Date
Ship To
Bill To
Amount
Description
The following are line item fields:
Item Description
Quantity
Unit Price
Extended Amount
Descriptive Prompt
You are a knowledge worker tasked with understanding purchase orders and sales orders. Carefully read the PDF file and extract header fields that will aid in management of these document types. Extract the following fields:
Order Number
Order Date
Ship To
Bill To
Amount
Description
The following are line item fields:
Item Description
Quantity
Unit Price
Extended Amount
Order Number represents a value that normally has a key or order, order number, po number, or sales order number. Sometimes the value is a derivative of those keys.
Order date represents the date the order was placed. Orders may sometimes be placed by non-us entities, and in those cases, dates may be presented in non-us formats. Always assume dates are to be normalized as US date formats unless there is reasonable suspicion the document originated from a non-us entity.
Ship To is the name and address where the goods are to be sent. All the lines of this value should be returned as a single string.
Bill To is the name of the company who produced the document. This is often the same company name that is found as the company logo on the document. This field would only ever be the name, never a complete address.
Amount is the total amount of the order. If no total amount is found, the amount may be calculated by summing all the amount values of any lines with dollar amounts in a table.
Description should be a summary of the order's purpose in 100 words or less
Extract line items for the following fields:
ItemDescription is a field that might represent the item number, a product description, or both. If both fields are found, combine them into a single string value.
Quantity is a numeric only value indicating the number of items ordered or purchased.
Unit Price is the dollar amount of a single item
Extended Price is a dollar amount that is generally specifically expressed, but is a calculation of the quantity multiplied by the unit price.
Using either prompt, you will need the following process fields to access the data in your workflow:
Regular Process Fields
Order Number
Order Date
Ship To
Bill To
Amount
Description
A Table Containing Process Fields
Item Description
Quantity
Unit Price
Extended Amount
Contracts
Contracts are a complex document format that at times can require contextual understanding to collect accurate data points. Using traditional approaches to extraction, this task is often difficult or impossible. For documents of this nature, it’s best to speak to the AI engine as you would a new employee being trained to read and understand these documents.
Prompt
You are a knowledge worker tasked with understanding business contracts. Carefully read the PDF file and extract header fields that will aid in management of the contract. Extract the following fields:
Contract Term
Effective Date
Contract Originator
Contract Recipient
Description
Instructions:
Contract Term is a numeric value, generally expressed in months, used to identify the duration of the contract. Whenever possible, express the value as a numeric number of months.
Effective date is the start date of the contract, which might be directly stated on the document, or might be based on the date the contract was signed.
Contract Originator is the name of the business who authored the contract.
Contract recipient is the 2nd party involved in contract execution. This could be a business or could be an individual in the case of an agreement with a consultant or sole proprietor.
Description should be a summary of the contracts purpose in 100 words or less
Countersigned indicates whether or not the contract is fully executed by all parties. Contract signatures are generally found on a single page where there is a signature block for the contract originator and the contract recipient who is often referred to as the customer. Find the signature page and look for multiple signatures on one page. When there are unsigned signature lines present, the value should be No for Countersigned indicating the contract has not been executed by all parties. If all signature lines contain a signature, the value should be Yes.
Using this prompt, you will need the following process fields to access the data in your workflow:
Contract Term
Effective Date
Contract Originator
Contract Recipient
Description
Countersigned
Handwritten Documents
Handwritten Applications, regardless of their use are a problem for any traditional extraction technology, depending on the need, you may run into some challenges, including:
Needing to Extract Handwritten Data (from varying forms/quality of handwriting)
Needing to read Checkboxes
Identify if a document is signed
Normalize data such as dates, regardless of how the data is written.
Prompt
You are a Homestead Tax Exemption Extractor. You will take careful care to read data off of incoming documents. This data will be returned as header data as a JSON. You will extract header values off of documents with great care, below are the data points to look for:
Owner Name 1 - Label/Key as "Owner 1"
Owner Name 2 - Label/Key as "Owner 2"
Property Address - Label/key as "Property Address"
Mailing Address - Label/key as "Mailing Address" - If it's indicated it's the same as the property address, use the property address.
OPA Account Number. - Label/key as "Account Number"
Phone Number - Label/key as "Phone Number" - Format as ###-###-####
Document Date, if no Document Date is available, use the Date Signed. (Formatted as MM/dd/yyyy) Label/key as "Document Date")
Email Address - Label/key as "Email".
Is this Property your primary residence? Read if Yes or No is checked, and return "Yes" or "No" if both are checked, return "Both" if none are checked return "None". - Label/key as "Primary Residence"
Do you claim anywhere else as your primary residence? Read if Yes or No is checked, and return "Yes" or "No" if both are checked, return "Both" if none are checked return "None". - Label/key as "Other Primary Residence"
Is this residence part of a cooperative where some or all the taxes are paid jointly? Read if Yes or No is checked, and return "Yes" or "No" if both are checked, return "Both" if none are checked return "None". - Label/key as "Cooperative"
If "Yes" is checked for "Is this residence part of a cooperative where some or all the taxes are paid jointly? " read the percentage and return as a percentage ie: 50%. - Label as "Cooperative Percentage"
Is part of the property used as a business or rental property? Read if Yes or No is checked, and return "Yes" or "No" if both are checked, return "Both" if none are checked return "None". - Label/key as "Rental Property"
If "Yes" is checked for "Is part of the property used as a business or rental property?" read the percentage and return as a percentage ie: 50%. - Label as "Rental Property Percentage"
Signed - If the document has been signed, indicate a "Yes", otherwise a "No". - Label/key as "Signed"
16. Return the Date the document was signed, you will find that date below the signature. - (Formatted as MM/dd/yyyy) - Label/key as "Date Signed"
Using the prompt, you will need the following process fields to access the data in your workflow:
Owner 1
Owner 2
Property Address
Mailing Address
Account Number
Phone Number
Document Date
Email
Primary Residence
Other Primary Residence
Cooperative
Cooperative Percentage
Rental Property
Rental Property Percentage
Signed
Date Signed
Other Uses
Using S9 Notation, use the data collected by InquireAI in an email. This can be useful as a notifier of receipt of a document, a summary of the document, etc.
Data Export
Take advantage of data export nodes available in GlobalCapture to export extracted data.
Export Data - Use the Export Data node to release the extracted data to a SQL database. Once released to an SQL database, use the SQL/CSV node to generate a CSV file.
JSON Export - Use the JSON Export node to generate a JSON file of your data. This file can then be released to a GlobalSearch inbox or archive using the Release node or release to another file share such as: Google Drive Release, ShareFile Release, SFTP Release, or FTP Release.