From the first form to policy delivery, by email

Two ways to submit

Both reach the same independent brokers, and both are browser forms any assistant that can browse the web can use; no MCP server, API key, or integration is required, and the JSON endpoint beside each is optional. Choose by what the business can answer today: a short request when it wants guidance first, or the complete application when its answers are ready.

• Start with a broker review request. A short form: business basics, goals, timeline, and who to email. Best when the business cannot yet answer a full questionnaire or wants a broker’s guidance before it does. The follow-up inbox confirms itself by emailed link, the business representative authorizes shopping by emailed link, and a broker replies by email with questions and the next step. Browser form: Submit a business. The browser form is sufficient on its own; the endpoint is optional, for agents that prefer JSON. Optional endpoint: POST /api/ai-agents/requests.
• File the complete application. The full Business Application: the coverages, every required question answered or explicitly marked unknown, the operating states, the authorized representative, and the business’s acknowledgement. Fill the browser form, or send the same questionnaire as one JSON body. Best when the business has its answers ready. The application is stored, the representative receives an acknowledgement by email with the application reference, and a broker starts from the completed application. There is no link to click; questions and options come by email. Browser form: Open the Business Application. The browser form is sufficient on its own; the endpoint is optional, for agents that prefer JSON. Optional endpoint: POST /api/ai-agents/applications.

• Use the request when the business cannot yet answer the questionnaire, wants a broker’s guidance first, or has a fit question before applying.
• Use the application when the business can answer every required question now (an unknown may be marked explicitly, with a note) and an authorized representative is ready to be named.
• An application may cite an earlier request’s reference; the two records are linked for the broker, and the request’s own email steps continue unchanged.
• No MCP server, API key, or integration required: use the forms on this site, and everything after that is email.
• Neither door binds coverage. The business’s authorized representative approves any purchase in writing.

The complete process

The steps below follow the broker review request. An application filed in one call skips steps 2 and 3: there is no link to click, the representative receives an acknowledgement by email, and the process continues from broker review.

1. Submit the dedicated form. Business details, goals, context, timeline, and correspondence information. A request reference is issued on the receipt.
2. Confirm the inbox. An emailed, request-specific link confirms where correspondence should go. Opening the link is not enough; an explicit confirmation click is required.
3. Confirm business authorization. The authorized representative reviews the request summary and recipients and authorizes OnePark to shop. This is recorded separately from inbox confirmation.
4. Broker review. A broker reads the request. Our goal is a first substantive reply by email in one business day or less, measured from the original submission.
5. Follow-up questions. Questions arrive numbered. Reply in the same thread with the same numbering, marking estimates and unknowns.
6. Market shopping. We approach suitable insurance markets available through OnePark and tell you when submissions have gone out.
7. Review quotes. Options arrive in writing with insurer, coverage and limits, deductibles, premium and disclosed charges, dates, conditions, remaining requirements, and expiration.
8. Approve the specific option. The authorized representative approves the selected quote. Revised terms need fresh approval.
9. Complete transaction requirements. Applications, signatures, and payment arrangements are completed through secure links when required.
10. Binding confirmation and policy documents. We confirm in writing when coverage is bound, with the effective date and any remaining conditions. Policy documents follow.

Request statuses you will see

• Email confirmation needed. The request exists; the correspondence inbox needs verification.
• Business authorization needed. Shopping authorization or recipient approval is outstanding.
• Broker review. OnePark is reviewing the request.
• Information needed. A specific answer or document is outstanding.
• Shopping coverage. Appropriate market submissions have occurred.
• Options ready. Actual quotes or indications are available.
• Approval needed. The business must approve a specific next step.
• Bind request submitted. Binding has been requested; confirmation is pending.
• Coverage bound. Binding has been confirmed, with effective terms and any conditions identified.
• Policy delivered. Final policy documents have been supplied.
• Unable to place / withdrawn / closed. The request is no longer active. OnePark explains the reason and any available next action.

Response goal

This is the goal for the first substantive response from OnePark, measured from the original submission. It is not a guarantee that quotes, underwriting, or binding will be completed within one business day.

Disclosure

Submitting a request does not purchase or bind insurance. Availability depends on the business, location, coverage, and underwriting requirements. OnePark will confirm the required steps and provide written confirmation when coverage has been bound.